Profile Comparison between https://gematik.de/fhir/isik/StructureDefinition/ISiKDiagnose vs http://hl7.eu/fhir/eps/StructureDefinition/condition-eu-eps

Left:ISiKDiagnose (https://gematik.de/fhir/isik/StructureDefinition/ISiKDiagnose)
Right:Condition (EPS) (http://hl7.eu/fhir/eps/StructureDefinition/condition-eu-eps)

Messages

ErrorStructureDefinition.urlValues for url differ: 'https://gematik.de/fhir/isik/StructureDefinition/ISiKDiagnose' vs 'http://hl7.eu/fhir/eps/StructureDefinition/condition-eu-eps'
ErrorStructureDefinition.versionValues for version differ: '5.0.0' vs '0.0.1-ci'
InformationStructureDefinition.nameValues for name differ: 'ISiKDiagnose' vs 'ConditionEuEps'
InformationStructureDefinition.statusValues for status differ: 'active' vs 'draft'
InformationStructureDefinition.dateValues for date differ: '2025-06-26' vs '2025-10-22T08:52:35+00:00'
InformationStructureDefinition.publisherValues for publisher differ: 'gematik GmbH' vs 'HL7 Europe'
InformationStructureDefinition.jurisdictionAdded the item 'http://unstats.un.org/unsd/methods/m49/m49.htm#150'
ErrorStructureDefinition.baseDefinitionValues for baseDefinition differ: 'http://hl7.org/fhir/StructureDefinition/Condition' vs 'http://hl7.org/fhir/uv/ips/StructureDefinition/Condition-uv-ips'
InformationStructureDefinition.shortValues for short differ: 'Detailed information about conditions, problems or diagnoses' vs 'Documentation of a health problem of the patient'
InformationCondition.languageExample/preferred bindings differ at Condition.language using binding from ISiKDiagnose
InformationStructureDefinition.definitionValues for definition differ: 'A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it 'clinically safe' for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.' vs 'Human readable specification of the problem. This is a general notes/comments entry for description of the problem, its diagnosis and prognosis.'
InformationStructureDefinition.shortValues for short differ: 'Additional content defined by implementations' vs 'Extension'
InformationStructureDefinition.definitionValues for definition differ: 'May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'An Extension'
WarningCondition.extensionElements differ in definition for mustSupport: 'true' vs 'false'
InformationStructureDefinition.requirementsValues for requirements differ: 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](extensibility.html#modifierExtension).' vs 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).'
InformationStructureDefinition.definitionValues for definition differ: 'Business identifiers assigned to this condition by the performer or other systems which remain constant as the resource is updated and propagates from server to server.' vs 'Globally unique identifier of this problem which remain constant as the resource is updated and propagates from server to server.'
InformationStructureDefinition.commentValues for comment differ: 'This is a business identifier, not a resource identifier (see [discussion](resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.' vs 'This is a business identifier, not a resource identifier (see [discussion](http://hl7.org/fhir/R4/resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.'
InformationStructureDefinition.shortValues for short differ: 'klinischer Status' vs 'active | recurrence | relapse | inactive | remission | resolved'
InformationStructureDefinition.definitionValues for definition differ: 'The clinical status of the condition.' vs 'The problem status describes the condition of the problem: 1. Active problems are problems of which the patient experiences symptoms or for which evidence exists. 2. If condition is abated, then clinicalStatus must be either inactive, resolved, or remission. 3. Problems with the status 'Inactive' refer to problems that don't affect the patient anymore or that of which there is no evidence of existence anymore.'
InformationStructureDefinition.commentValues for comment differ: '**Begründung MS:** Auch in Stufe 4 sind keine (client-seitigen) schreibenden Operationen für das Erstellen einer Condition-Ressource vorgesehen (siehe CapabilityStatement). Das heißt, entweder führen KISe entsprechende Informationen und exponieren diese, oder es gibt keinen pragmatischen Mechanismus (im ISIK-Kontext), um den Use Case einer zusätzlichen Annotation mittels Client zu erfüllen. Da alle KIS-Hersteller, die sich zu Wort gemeldet haben, eine Befüllung von Condition.clinicalStatus NICHT unterstützen, erscheint das MS nach übergreifender Definition und ein verpflichtender Testfall nicht angemessen. **Einschränkung der übergreifenden MS-Definition:** Verfügt ein bestätigungsrelevantes System nicht über die Datenstruktur zur Hinterlegung des Status einer Diagnose, so MUSS dieses System die Information NICHT abbilden. Das System MUSS jedoch `clinicalStatus` befüllen, sofern die entsprechende Information verfügbar ist. **Hinweis:** Für Diagnosen aus der *ambulanten* Versorgung können die Werte für `clinicalStatus` und `verificationStatus` aus dem [ICD-10-Zusatzkennzeichen für die Diagnosesicherheit](https://www.bfarm.de/DE/Kodiersysteme/Services/Kodierfragen/ICD-10-GM/Allgemeine-Kodierfragen/icd-10-gm-1010.html) abgeleitet werden. Das entsprechende Mapping kann den [Deutschen Basisprofilen](https://simplifier.net/guide/leitfaden-de-basis-r4/ig-markdown-Ressourcen-DiagnosenCondition?version=current) entnommen werden.' vs 'The data type is CodeableConcept because clinicalStatus has some clinical judgment involved, such that there might need to be more specificity than the required FHIR value set allows. For example, a SNOMED coding might allow for additional specificity.'
InformationStructureDefinition.commentValues for comment differ: 'verificationStatus is not required. For example, when a patient has abdominal pain in the ED, there is not likely going to be a verification status. The data type is CodeableConcept because verificationStatus has some clinical judgment involved, such that there might need to be more specificity than the required FHIR value set allows. For example, a SNOMED coding might allow for additional specificity.' vs 'This element is labeled as a modifier because the status contains the code refuted and entered-in-error that mark the Condition as not currently valid.'
InformationStructureDefinition.definitionValues for definition differ: 'A category assigned to the condition.' vs 'A category assigned to the condition. In this profile, a health problem of the patient, therefore a 'problem-list-item'.'
InformationStructureDefinition.commentValues for comment differ: 'The categorization is often highly contextual and may appear poorly differentiated or not very useful in other contexts.' vs 'In this profile, Condition represents a health problem of the patient. Therefore one of the category value(s) must be problem-list-item.'
WarningCondition.categoryElements differ in definition for mustSupport: 'false' vs 'true'
WarningCondition.severityElements differ in definition for mustSupport: 'false' vs 'true'
InformationStructureDefinition.shortValues for short differ: 'Diagnose-Code' vs 'Identification of the condition, problem or diagnosis'
InformationStructureDefinition.definitionValues for definition differ: 'Identification of the condition, problem or diagnosis.' vs 'Identification of the Problem or recording of 'absence of problem' or of 'procedures unknown'.'
InformationCondition.codeExample/preferred bindings differ at Condition.code using binding from ConditionEuEps
InformationStructureDefinition.commentValues for comment differ: '**Begründung MS:** Harmonisierung mit KBV-Profil (KBV_PR_Base_Condition_Diagnosis)' vs 'Only used if not implicit in code found in Condition.code. If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension [bodySite](http://hl7.org/fhir/R4/extension-bodysite.html). May be a summary code, or a reference to a very precise definition of the location, or both.'
WarningCondition.bodySiteElements differ in definition for mustSupport: 'true' vs 'false'
InformationStructureDefinition.shortValues for short differ: 'Patientenbezug' vs 'Who has the condition?'
InformationStructureDefinition.shortValues for short differ: 'Patienten-Link' vs 'Literal reference, Relative, internal or absolute URL'
InformationStructureDefinition.commentValues for comment differ: 'Die Verlinkung auf eine Patienten-Ressource dient der technischen Zuordnung der Dokumentation zu einem Patienten und ermöglicht wichtige API-Funktionen wie verkettete Suche, (Reverse-)Include etc.' vs 'Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure '/[type]/[id]' then it should be assumed that the reference is to a FHIR RESTful server.'
InformationStructureDefinition.shortValues for short differ: 'Aufenthaltsbezug' vs 'Encounter created as part of'
InformationStructureDefinition.commentValues for comment differ: '**Begründung Must-Support:** Ein Aufenthaltsbezug der Diagnose MUSS stets zum Zwecke der Nachvollziehbarkeit und Datenintegrität vorliegen.' vs 'This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter. This record indicates the encounter this particular record is associated with. In the case of a 'new' diagnosis reflecting ongoing/revised information about the condition, this might be distinct from the first encounter in which the underlying condition was first 'known'.'
WarningCondition.encounterElements differ in definition for mustSupport: 'true' vs 'false'
InformationStructureDefinition.shortValues for short differ: 'Erkrankungsbeginn' vs 'Estimated or actual date, date-time, or age'
InformationStructureDefinition.commentValues for comment differ: 'Datum oder Alter/Lebensphase des Erkrankungsbeginns **Begründung MS:** Die Kenntnis des Erkrankungszeitraumes ist wichtig für die korrekte Einschätzung der medizinischen Relevanz einer Erkraknung. **Einschränkung der übergreifenden MS-Definition:** Verfügt ein bestätigungsrelevantes System nicht über die Datenstruktur zur Hinterlegung des Erkrankungszeitraumes, so MUSS dieses System die Information NICHT abbilden. Das System MUSS jedoch klinischen Status (`active`/`inactive`/`resolved`...) der Diagnose korrekt angeben, sofern die Information verfügbar ist.' vs 'Age is generally used when the patient reports an age at which the Condition began to occur.'
InformationStructureDefinition.shortValues for short differ: 'Klinische relevanter Zeitraum Ende' vs 'When in resolution/remission'
InformationStructureDefinition.commentValues for comment differ: 'Ende des klinisch relevanten Zeitraums der Diagnose **Begründung MS:** Die Kenntnis des Erkrankungszeitraumes ist wichtig für die korrekte Einschätzung der medizinischen Relevanz einer Erkraknung. **Einschränkung der übergreifenden MS-Definition:** Verfügt ein bestätigungsrelevantes System nicht über die Datenstruktur zur Hinterlegung des Erkrankungszeitraumes, so MUSS dieses System die Information NICHT abbilden. Das System MUSS jedoch klinischen Status (`active`/`inactive`/`resolved`...) der Diagnose korrekt angeben, sofern die Information verfügbar ist.' vs 'There is no explicit distinction between resolution and remission because in many cases the distinction is not clear. Age is generally used when the patient reports an age at which the Condition abated. If there is no abatement element, it is unknown whether the condition has resolved or entered remission; applications and users should generally assume that the condition is still valid. When abatementString exists, it implies the condition is abated.'
WarningCondition.abatement[x]Elements differ in definition for mustSupport: 'true' vs 'false'
InformationStructureDefinition.shortValues for short differ: 'Dokumentationsdatum' vs 'Date record was first recorded'
WarningCondition.recordedDateElements differ in definition for mustSupport: 'true' vs 'false'
InformationCondition.recordedDateElement minimum cardinalities differ: '1' vs '0'
InformationStructureDefinition.requirementsValues for requirements differ: 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](extensibility.html#modifierExtension).' vs 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).'
InformationStructureDefinition.requirementsValues for requirements differ: 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](extensibility.html#modifierExtension).' vs 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).'
InformationStructureDefinition.shortValues for short differ: 'Notizen' vs 'Additional information about the Condition'
WarningCondition.noteElements differ in definition for mustSupport: 'true' vs 'false'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/StructureDefinition/Conditionhttp://hl7.org/fhir/uv/ips/StructureDefinition/Condition-uv-ips
    • Values Differ
    .copyrightUsed by permission of HL7 Europe, all rights reserved Creative Commons License
    • Added the item 'Used by permission of HL7 Europe, all rights reserved Creative Commons License'
    .date2025-06-262025-10-22T08:52:35+00:00
    • Values Differ
    .descriptionDieses Profil spezifiziert die Minimalanforderungen für die Bereitstellung von Informationen über die Diagnosen eines Patienten im Rahmen des Bestätigungsverfahrens der gematik. ### Motivation Die Möglichkeit, auf eine Übersicht der Diagnosen eines Patienten zuzugreifen, Patienten anhand ihrer Diagnose zu suchen oder zu prüfen, ob eine konkrete Diagnose bei einem Patienten vorliegt, sind wichtige Funktionen im klinischen Behandlungsablauf. In FHIR werden Diagnosen mit der Condition-Ressource repräsentiert. Da die Diagnosen in klinischen Primärsystemen in der Regel in ICD-10-codierter Form vorliegen, fordert ISiK in erster Linie diese Form des Austausches. Falls eine Diagnose zwar dokumentiert, aber noch nicht codiert wurde (z.B. wenn die Kodierung erst nach der Entlassung erfolgt), ist alternativ eine Repräsentation als Freitext-Diagnose möglich. ### Kompatibilität Für das Profil ISiKDiagnose wird eine Kompatibilität mit folgenden Profilen angestrebt; allerdings kann nicht sichergestellt werden, dass Instanzen, die gegen ISiKDiagnose valide sind, auch valide sind gegen: * das [Profil ProfileConditionDiagnose der Medizininformatik-Initative](https://www.medizininformatik-initiative.de/fhir/core/modul-diagnose/StructureDefinition/Diagnose) * das [Profil KBV_PR_Base_Condition_Diagnosis der KBV](https://fhir.kbv.de/StructureDefinition/KBV_PR_Base_Condition_Diagnosis)] Hinweise zu Inkompatibilitäten können über die [Portalseite](https://service.gematik.de/servicedesk/customer/portal/16) gemeldet werden.This profile constrains the Condition resource for the purpose of the European patient summary.
    • Values Differ
    .experimentalfalse
    • Removed the item 'false'
    .fhirVersion4.0.1
      .jurisdiction
        ..jurisdiction[0]http://unstats.un.org/unsd/methods/m49/m49.htm#150
        • Added the item 'http://unstats.un.org/unsd/methods/m49/m49.htm#150'
        .kindresource
          .nameISiKDiagnoseConditionEuEps
          • Values Differ
          .publishergematik GmbHHL7 Europe
          • Values Differ
          .purposeThis profile constrains the Condition resource for the purpose of the European patient summary.
          • Added the item 'This profile constrains the Condition resource for the purpose of the European patient summary.'
          .statusactivedraft
          • Values Differ
          .titleCondition (EPS)
          • Added the item 'Condition (EPS)'
          .typeCondition
            .urlhttps://gematik.de/fhir/isik/StructureDefinition/ISiKDiagnosehttp://hl7.eu/fhir/eps/StructureDefinition/condition-eu-eps
            • Values Differ
            .version5.0.00.0.1-ci
            • Values Differ

            Structure

            NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.R TypeR Description & ConstraintsCommentsdoco
            .. Condition C0..*ConditionDetailed information about conditions, problems or diagnoses
            con-3: Condition.clinicalStatus SHALL be present if verificationStatus is not entered-in-error and category is problem-list-item
            con-4: If condition is abated, then clinicalStatus must be either inactive, resolved, or remission
            con-5: Condition.clinicalStatus SHALL NOT be present if verification Status is entered-in-error
            isik-con1: Falls eine kodierte Diagnose vorliegt muss angegeben werden durch welchen Kontakt diese Dokumentation erfolgte.
            		C0..*ConditionUvIps(2.0.0)Documentation of a health problem of the patient
            con-3: Condition.clinicalStatus SHALL be present if verificationStatus is not entered-in-error and category is problem-list-item
            con-4: If condition is abated, then clinicalStatus must be either inactive, resolved, or remission
            con-5: Condition.clinicalStatus SHALL NOT be present if verification Status is entered-in-error
              ... id Σ0..1stringLogical id of this artifactΣ0..1idLogical id of this artifact
                ... meta Σ0..1MetaMetadata about the resourceΣ0..1MetaMetadata about the resource
                  ... implicitRules ?!Σ0..1uriA set of rules under which this content was created?!Σ0..1uriA set of rules under which this content was created
                    ... language 0..1codeLanguage of the resource content
                    Binding: ?? (preferred): A human language.

                    Additional BindingsPurpose
                    ??Max Binding
                    		0..1codeLanguage of the resource content
                    Binding: ?? (preferred): A human language.

                    Additional BindingsPurpose
                    ??Max Binding
                    • Example/preferred bindings differ at Condition.language using binding from ISiKDiagnose
                    ... text 0..1NarrativeText summary of the resource, for human interpretation0..1NarrativeText summary of the resource, for human interpretation
                      ... contained 0..*ResourceContained, inline Resources
                      		0..*ResourceContained, inline Resources
                        ... Slices for extension S0..*ExtensionAdditional content defined by implementations
                        Slice: Unordered, Open by value:url
                        		0..*ExtensionExtension
                        Slice: Unordered, Open by value:url
                        • Elements differ in definition for mustSupport: 'true' vs 'false'
                        ... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
                        		?!0..*ExtensionExtensions that cannot be ignored
                          ... identifier Σ0..*IdentifierExternal Ids for this condition
                          		Σ0..*IdentifierExternal Ids for this condition
                            ... clinicalStatus ?!SΣC0..1CodeableConceptklinischer Status
                            Binding: ?? (required): The clinical status of the condition or diagnosis.

                            		?!SOΣC0..1??active | recurrence | relapse | inactive | remission | resolved
                            Binding: ?? (required)
                            ObligationsActor
                            SHALL:populate-if-knownhttp://hl7.org/fhir/uv/ips/ActorDefinition/Creator
                            SHALL:handlehttp://hl7.org/fhir/uv/ips/ActorDefinition/Consumer
                            SHOULD:displayhttp://hl7.org/fhir/uv/ips/ActorDefinition/Consumer
                              ... verificationStatus ?!ΣC0..1CodeableConceptunconfirmed | provisional | differential | confirmed | refuted | entered-in-error
                              Binding: ?? (required): The verification status to support or decline the clinical status of the condition or diagnosis.

                              		?!ΣC0..1??unconfirmed | provisional | differential | confirmed | refuted | entered-in-error
                              Binding: ?? (required)
                                ... category 0..*CodeableConceptproblem-list-item | encounter-diagnosis
                                Binding: ?? (extensible): A category assigned to the condition.


                                		SO0..*??problem-list-item | encounter-diagnosis
                                Binding: ?? (extensible)
                                Additional BindingsPurpose
                                ??candidate

                                ObligationsActor
                                SHALL:populate-if-knownhttp://hl7.org/fhir/uv/ips/ActorDefinition/Creator
                                SHALL:handlehttp://hl7.org/fhir/uv/ips/ActorDefinition/Consumer
                                SHOULD:displayhttp://hl7.org/fhir/uv/ips/ActorDefinition/Consumer
                                • Elements differ in definition for mustSupport: 'false' vs 'true'
                                ... severity 0..1CodeableConceptSubjective severity of condition
                                Binding: ?? (preferred): A subjective assessment of the severity of the condition as evaluated by the clinician.

                                		SO0..1??Subjective severity of condition
                                Binding: ?? (preferred)
                                ObligationsActor
                                SHALL:populate-if-knownhttp://hl7.org/fhir/uv/ips/ActorDefinition/Creator
                                SHALL:handlehttp://hl7.org/fhir/uv/ips/ActorDefinition/Consumer
                                SHOULD:displayhttp://hl7.org/fhir/uv/ips/ActorDefinition/Consumer
                                • Elements differ in definition for mustSupport: 'false' vs 'true'
                                ... code SΣC1..1CodeableConceptDiagnose-Code
                                Binding: ?? (example): Identification of the condition or diagnosis.


                                icd-text-1: Entweder MUSS eine kodierte Diagnose vorliegen oder eine textuelle Beschreibung. Stattdessen nur Extensions hinzuzufügen (vgl. https://www.hl7.org/fhir/element.html - ele-1), ist explizit nicht erlaubt.                                		SOΣ1..1??Identification of the condition, problem or diagnosis
                                Binding: ?? (preferred): A problem code or a code for absent/unknown problem

                                Additional BindingsPurpose
                                ??candidate
                                ObligationsActor
                                SHALL:populate-if-knownhttp://hl7.org/fhir/uv/ips/ActorDefinition/Creator
                                SHALL:handlehttp://hl7.org/fhir/uv/ips/ActorDefinition/Consumer
                                SHOULD:displayhttp://hl7.org/fhir/uv/ips/ActorDefinition/Consumer
                                • Example/preferred bindings differ at Condition.code using binding from ConditionEuEps
                                .... id 0..1stringUnique id for inter-element referencing
                                • Removed this element
                                .... Slices for extension 0..*ExtensionAdditional content defined by implementations
                                Slice: Unordered, Open by value:url
                                • Removed this element
                                .... Slices for coding SΣ0..*CodingCode defined by a terminology system
                                Slice: Unordered, Open by pattern:$this
                                • Removed this element
                                .... text Σ0..1stringPlain text representation of the concept
                                • Removed this element
                                ... bodySite SΣ0..*CodeableConceptAnatomical location, if relevant
                                Binding: ?? (example): Codes describing anatomical locations. May include laterality.


                                		Σ0..*??Anatomical location, if relevant
                                Binding: ?? (preferred)
                                • Elements differ in definition for mustSupport: 'true' vs 'false'
                                .... id 0..1stringUnique id for inter-element referencing
                                • Removed this element
                                .... Slices for extension 0..*ExtensionAdditional content defined by implementations
                                Slice: Unordered, Open by value:url
                                • Removed this element
                                .... Slices for coding SΣ0..*CodingCode defined by a terminology system
                                Slice: Unordered, Open by pattern:system
                                • Removed this element
                                .... text Σ0..1stringPlain text representation of the concept
                                • Removed this element
                                ... subject SΣ1..1Reference(Patient | Group)PatientenbezugSOΣ1..1Reference(Patient (EPS))Who has the condition?
                                ObligationsActor
                                SHALL:populate-if-knownhttp://hl7.org/fhir/uv/ips/ActorDefinition/Creator
                                SHALL:handlehttp://hl7.org/fhir/uv/ips/ActorDefinition/Consumer
                                SHOULD:displayhttp://hl7.org/fhir/uv/ips/ActorDefinition/Consumer
                                  .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                    .... Slices for extension 0..*ExtensionAdditional content defined by implementations
                                    Slice: Unordered, Open by value:url
                                    		0..*ExtensionAdditional content defined by implementations
                                    Slice: Unordered, Open by value:url
                                      .... reference SΣC1..1stringPatienten-LinkSOΣC1..1stringLiteral reference, Relative, internal or absolute URL
                                      ObligationsActor
                                      SHALL:populate-if-knownhttp://hl7.org/fhir/uv/ips/ActorDefinition/Creator
                                      SHALL:handlehttp://hl7.org/fhir/uv/ips/ActorDefinition/Consumer
                                        .... type Σ0..1uriType the reference refers to (e.g. "Patient")
                                        Binding: ?? (extensible): Aa resource (or, for logical models, the URI of the logical model).

                                        		Σ0..1uriType the reference refers to (e.g. "Patient")
                                        Binding: ?? (extensible): Aa resource (or, for logical models, the URI of the logical model).

                                          .... identifier Σ0..1IdentifierLogical reference, when literal reference is not knownΣ0..1IdentifierLogical reference, when literal reference is not known
                                            .... display Σ0..1stringText alternative for the resourceΣ0..1stringText alternative for the resource
                                              ... encounter SΣ0..1Reference(Encounter)AufenthaltsbezugΣ0..1Reference(Encounter)Encounter created as part of
                                              • Elements differ in definition for mustSupport: 'true' vs 'false'
                                              .... id 0..1stringUnique id for inter-element referencing
                                              • Removed this element
                                              .... Slices for extension 0..*ExtensionAdditional content defined by implementations
                                              Slice: Unordered, Open by value:url
                                              • Removed this element
                                              .... reference SΣC1..1stringEncounter-Link
                                              • Removed this element
                                              .... type Σ0..1uriType the reference refers to (e.g. "Patient")
                                              Binding: ?? (extensible): Aa resource (or, for logical models, the URI of the logical model).

                                              • Removed this element
                                              .... identifier Σ0..1IdentifierLogical reference, when literal reference is not known
                                              • Removed this element
                                              .... display Σ0..1stringText alternative for the resource
                                              • Removed this element
                                              ... Slices for onset[x] SΣ0..1dateTime, AgeErkrankungsbeginn
                                              Slice: Unordered, Open by type:$this                                              		SOΣ0..1dateTimeEstimated or actual date, date-time, or age
                                              Slice: Unordered, Closed by type:$this
                                              ObligationsActor
                                              SHALL:populate-if-knownhttp://hl7.org/fhir/uv/ips/ActorDefinition/Creator
                                              SHALL:handlehttp://hl7.org/fhir/uv/ips/ActorDefinition/Consumer
                                              SHOULD:displayhttp://hl7.org/fhir/uv/ips/ActorDefinition/Consumer
                                                ... Slices for abatement[x] SC0..1dateTime, AgeKlinische relevanter Zeitraum Ende
                                                Slice: Unordered, Open by type:$this                                                		C0..1dateTime, Age, Period, Range, stringWhen in resolution/remission
                                                Slice: Unordered, Open by type:$this
                                                • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                ... recordedDate SΣ1..1dateTimeDokumentationsdatumΣ0..1dateTimeDate record was first recorded
                                                • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                • Element minimum cardinalities differ: '1' vs '0'
                                                ... recorder Σ0..1Reference(Practitioner | PractitionerRole | Patient | RelatedPerson)Who recorded the conditionΣ0..1Reference(Practitioner | PractitionerRole | Patient | RelatedPerson)Who recorded the condition
                                                  ... asserter Σ0..1Reference(Practitioner | PractitionerRole | Patient | RelatedPerson)Person who asserts this conditionΣ0..1Reference(Practitioner | PractitionerRole | Patient | RelatedPerson)Person who asserts this condition
                                                    ... stage C0..*BackboneElementStage/grade, usually assessed formally
                                                    con-1: Stage SHALL have summary or assessment
                                                    		C0..*BackboneElementStage/grade, usually assessed formally
                                                    con-1: Stage SHALL have summary or assessment
                                                      .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                        .... extension 0..*ExtensionAdditional content defined by implementations
                                                        		0..*ExtensionAdditional content defined by implementations
                                                          .... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                          		?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                            .... summary C0..1CodeableConceptSimple summary (disease specific)
                                                            Binding: ?? (example): Codes describing condition stages (e.g. Cancer stages).

                                                            		C0..1CodeableConceptSimple summary (disease specific)
                                                            Binding: ?? (example): Codes describing condition stages (e.g. Cancer stages).

                                                              .... assessment C0..*Reference(ClinicalImpression | DiagnosticReport | Observation)Formal record of assessment
                                                              		C0..*Reference(ClinicalImpression | DiagnosticReport | Observation)Formal record of assessment
                                                                .... type 0..1CodeableConceptKind of staging
                                                                Binding: ?? (example): Codes describing the kind of condition staging (e.g. clinical or pathological).

                                                                		0..1CodeableConceptKind of staging
                                                                Binding: ?? (example): Codes describing the kind of condition staging (e.g. clinical or pathological).

                                                                  ... evidence C0..*BackboneElementSupporting evidence
                                                                  con-2: evidence SHALL have code or details
                                                                  		C0..*BackboneElementSupporting evidence
                                                                  con-2: evidence SHALL have code or details
                                                                    .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                                      .... extension 0..*ExtensionAdditional content defined by implementations
                                                                      		0..*ExtensionAdditional content defined by implementations
                                                                        .... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                        		?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                          .... code ΣC0..*CodeableConceptManifestation/symptom
                                                                          Binding: ?? (example): Codes that describe the manifestation or symptoms of a condition.


                                                                          		ΣC0..*CodeableConceptManifestation/symptom
                                                                          Binding: ?? (example): Codes that describe the manifestation or symptoms of a condition.


                                                                            .... detail ΣC0..*Reference(Resource)Supporting information found elsewhere
                                                                            		ΣC0..*Reference(Resource)Supporting information found elsewhere
                                                                              ... note S0..*AnnotationNotizen
                                                                              		0..*AnnotationAdditional information about the Condition
                                                                              • Elements differ in definition for mustSupport: 'true' vs 'false'

                                                                              doco Documentation for this format