Logisches Modell zur Dispensieranforderungs Bestätigung
Übersicht über das Profil
Name | Description | Canonical_URL | Status | Version | Basiert auf |
---|---|---|---|---|---|
GEM_ERP_SR_LOG_DispenseRequest_Confirmation | Fachliches Modell zur Beschreibung einer Bestätigung einer Dispenseieranforderung | https://gematik.de/fhir/erp-servicerequest/StructureDefinition/gem-erp-sr-log-dispense-request-confirmation | draft | 1.2 | http://hl7.org/fhir/StructureDefinition/Element |
Über das Profil
Motivation
Dieses logische Modell beschreibt die Inhalte einer erfüllten und bestätigten Dispensieranforderung seitens einer Apotheke an die anfragende Pflegeeinrichtung.
Inhalt des Profils
Folgende Ansichten existieren auf das Profil:
GEM_ERP_SR_LOG_DispenseRequest_Confirmation (gem-erp-sr-log-dispense-request-confirmation) | I | Element | |
id | 0..1 | string | |
extension | I | 0..* | Extension |
MetaDaten | 1..1 | BackboneElement | |
id | 0..1 | string | |
extension | I | 0..* | Extension |
modifierExtension | Σ ?! I | 0..* | Extension |
Empfaenger | 1..* | BackboneElement | |
id | 0..1 | string | |
extension | I | 0..* | Extension |
modifierExtension | Σ ?! I | 0..* | Extension |
KIMAdresse | 1..1 | url | |
TelematikID | 0..1 | url | |
Absender | 1..1 | BackboneElement | |
id | 0..1 | string | |
extension | I | 0..* | Extension |
modifierExtension | Σ ?! I | 0..* | Extension |
TelematikID | 0..1 | url | |
Name | 1..1 | string | |
AbsendendesSystem | 1..1 | BackboneElement | |
id | 0..1 | string | |
extension | I | 0..* | Extension |
modifierExtension | Σ ?! I | 0..* | Extension |
Name | 1..1 | string | |
Software | 1..1 | string | |
Version | 1..1 | string | |
EMailKontakt | 1..1 | string | |
Website | 1..1 | url | |
Status | I | 1..1 | code |
VorgangsID | 1..1 | string | |
Freitext | 0..1 | string | |
Anhaenge | I | 0..* | Attachment |
Belieferungsart | 0..1 | Coding | |
id | 0..1 | string | |
extension | I | 0..* | Extension |
system | Σ | 0..1 | uri |
version | Σ | 0..1 | string |
code | Σ | 0..1 | code |
display | Σ | 0..1 | string |
userSelected | Σ | 0..1 | boolean |
BelieferungsartCode | 1..1 | Coding | |
Medikation | I | 1..1 | BackboneElement |
id | 0..1 | string | |
extension | I | 0..* | Extension |
modifierExtension | Σ ?! I | 0..* | Extension |
Abgabeinformationen | I | 1..1 | Reference(MedicationDispense) |
gem-erp-sr-log-dispense-request-confirmation | |
Definition | Fachliches Modell zur Beschreibung einer Bestätigung einer Dispenseieranforderung |
Cardinality | 0...* |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.MetaDaten | |
Definition | Metadaten im MessageHeader |
Cardinality | 1...1 |
Type | BackboneElement |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.MetaDaten.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.MetaDaten.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.MetaDaten.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.MetaDaten.Empfaenger | |
Definition | Empfänger der Nachricht |
Cardinality | 1...* |
Type | BackboneElement |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.MetaDaten.Empfaenger.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.MetaDaten.Empfaenger.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.MetaDaten.Empfaenger.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.MetaDaten.Empfaenger.KIMAdresse | |
Definition | KIM-Adresse des Empfängers |
Cardinality | 1...1 |
Type | url |
Comments | see http://en.wikipedia.org/wiki/Uniform_resource_identifier |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.MetaDaten.Empfaenger.TelematikID | |
Definition | Telematik-ID des Absenders |
Cardinality | 0...1 |
Type | url |
Comments | see http://en.wikipedia.org/wiki/Uniform_resource_identifier |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.MetaDaten.Absender | |
Definition | Absender der Nachricht |
Cardinality | 1...1 |
Type | BackboneElement |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.MetaDaten.Absender.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.MetaDaten.Absender.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.MetaDaten.Absender.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.MetaDaten.Absender.TelematikID | |
Definition | Telematik-ID des Absenders |
Cardinality | 0...1 |
Type | url |
Comments | see http://en.wikipedia.org/wiki/Uniform_resource_identifier |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.MetaDaten.Absender.Name | |
Definition | Name des Absenders |
Cardinality | 1...1 |
Type | string |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.MetaDaten.AbsendendesSystem | |
Definition | Absendendes System |
Cardinality | 1...1 |
Type | BackboneElement |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.MetaDaten.AbsendendesSystem.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.MetaDaten.AbsendendesSystem.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.MetaDaten.AbsendendesSystem.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.MetaDaten.AbsendendesSystem.Name | |
Definition | Name des Herstellers des absendenden Systems |
Cardinality | 1...1 |
Type | string |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.MetaDaten.AbsendendesSystem.Software | |
Definition | Name der Software des absendenden Systems |
Cardinality | 1...1 |
Type | string |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.MetaDaten.AbsendendesSystem.Version | |
Definition | Version des absendenden Systems |
Cardinality | 1...1 |
Type | string |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.MetaDaten.AbsendendesSystem.EMailKontakt | |
Definition | E-Mail-Kontakt des absendenden Systems |
Cardinality | 1...1 |
Type | string |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.MetaDaten.AbsendendesSystem.Website | |
Definition | Website des absendenden Systems |
Cardinality | 1...1 |
Type | url |
Comments | see http://en.wikipedia.org/wiki/Uniform_resource_identifier |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.Status | |
Definition | Status der Anforderung. Wird genutzt, um den Bearbeitungsstand einer Anfrage zu verfolgen. Im Falle der Dispensieranforderung wird eine erledigte Anfrage mit dem Status 'completed' geschickt und signalisiert somit eine neue Anfrage. |
Cardinality | 1...1 |
Type | code |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.VorgangsID | |
Definition | Wird vom initialen Sender gesetzt und muss immer mitgeführt werden. |
Cardinality | 1...1 |
Type | string |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.Freitext | |
Definition | Individuelle Nachricht an den Empfänger |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.Anhaenge | |
Definition | Anhänge zur Anforderung. Das können PDFs, Bilder oder andere Dokumente sein. |
Cardinality | 0...* |
Type | Attachment |
Comments | Werden auf Ebene der KIM-Nachricht angehangen |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.Belieferungsart | |
Definition | Angabe der Belieferungsart |
Cardinality | 0...1 |
Type | Coding |
Comments | Codes may be defined very casually in enumerations or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.Belieferungsart.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.Belieferungsart.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.Belieferungsart.system | |
Definition | The identification of the code system that defines the meaning of the symbol in the code. |
Cardinality | 0...1 |
Type | uri |
Summary | True |
Requirements | Need to be unambiguous about the source of the definition of the symbol. |
Comments | The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously. |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.Belieferungsart.version | |
Definition | The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.Belieferungsart.code | |
Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). |
Cardinality | 0...1 |
Type | code |
Summary | True |
Requirements | Need to refer to a particular code in the system. |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.Belieferungsart.display | |
Definition | A representation of the meaning of the code in the system, following the rules of the system. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.Belieferungsart.userSelected | |
Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). |
Cardinality | 0...1 |
Type | boolean |
Summary | True |
Requirements | This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. |
Comments | Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.Belieferungsart.BelieferungsartCode | |
Definition | Folgende Codes sind zulässig: Abholung durch Pflegedienst, Lieferung der Apotheke, Abholung durch Patienten |
Cardinality | 1...1 |
Type | Coding |
Comments | Codes may be defined very casually in enumerations or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.Medikation | |
Definition | Angaben zur Medikation |
Cardinality | 1...1 |
Type | BackboneElement |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.Medikation.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.Medikation.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.Medikation.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request-confirmation.Medikation.Abgabeinformationen | |
Definition | MedicationDispense und Medication Objekt aus den Abgabedaten. |
Cardinality | 1...1 |
Type | Reference(MedicationDispense) |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
<StructureDefinition xmlns="http://hl7.org/fhir"> <id value="gem-erp-sr-log-dispense-request-confirmation" /> <url value="https://gematik.de/fhir/erp-servicerequest/StructureDefinition/gem-erp-sr-log-dispense-request-confirmation" /> <version value="1.2" /> <name value="GEM_ERP_SR_LOG_DispenseRequest_Confirmation" /> <title value="Logical Model Dispenseieranforderung_Bestätigung" /> <status value="draft" /> <experimental value="false" /> <date value="2025-01-01" /> <publisher value="gematik GmbH" /> <description value="Fachliches Modell zur Beschreibung einer Bestätigung einer Dispenseieranforderung" /> <fhirVersion value="4.0.1" /> <mapping> <identity value="Dispensieranforderung-Bestaetigung-Fachliches-Mapping" /> <uri value="ERPServiceRequestDispenseRequest" /> <name value="Dispensieranforderung Bestätigung Fachliches Mapping" /> <comment value="Mapping des Fachmodells aus GEM_ERP_SR_LOG_DispenseRequest_Confirmation auf das FHIR-Modell ERPServiceRequestDispenseRequest" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Bestaetigung-Mapping" /> <name value="Quelle der Dispensieranforderung Bestätigung Informationen" /> <comment value="Beschreibt die Quelle der Dispensieranforderung Bestätigung Informatione" /> </mapping> <kind value="logical" /> <abstract value="false" /> <type value="https://gematik.de/fhir/erp-servicerequest/StructureDefinition/gem-erp-sr-log-dispense-request-confirmation" /> <baseDefinition value="http://hl7.org/fhir/StructureDefinition/Element" /> <derivation value="specialization" /> <differential> <element id="gem-erp-sr-log-dispense-request-confirmation"> <path value="gem-erp-sr-log-dispense-request-confirmation" /> <short value="Logical Model Dispenseieranforderung_Bestätigung" /> <definition value="Fachliches Modell zur Beschreibung einer Bestätigung einer Dispenseieranforderung" /> <constraint> <key value="log-dispense-request-confirmation-1" /> <severity value="error" /> <human value="Wenn eine Anfrage erfüllt wird (status = 'completed'), müssen Abgabeinformationen vorhanden sein." /> <source value="https://gematik.de/fhir/erp-servicerequest/StructureDefinition/gem-erp-sr-log-dispense-request-confirmation" /> </constraint> </element> <element id="gem-erp-sr-log-dispense-request-confirmation.MetaDaten"> <path value="gem-erp-sr-log-dispense-request-confirmation.MetaDaten" /> <short value="Metadaten im MessageHeader" /> <definition value="Metadaten im MessageHeader" /> <min value="1" /> <max value="1" /> <type> <code value="BackboneElement" /> </type> <mapping> <identity value="Dispensieranforderung-Bestaetigung-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequestHeader" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Bestaetigung-Mapping" /> <map value="Erstellendes AVS" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request-confirmation.MetaDaten.Empfaenger"> <path value="gem-erp-sr-log-dispense-request-confirmation.MetaDaten.Empfaenger" /> <short value="Empfänger der Nachricht" /> <definition value="Empfänger der Nachricht" /> <min value="1" /> <max value="*" /> <type> <code value="BackboneElement" /> </type> <mapping> <identity value="Dispensieranforderung-Bestaetigung-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequestHeader.destination" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Bestaetigung-Mapping" /> <map value="Aus initialer Dispensieranforderung" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request-confirmation.MetaDaten.Empfaenger.KIMAdresse"> <path value="gem-erp-sr-log-dispense-request-confirmation.MetaDaten.Empfaenger.KIMAdresse" /> <short value="KIM-Adresse des Empfängers" /> <definition value="KIM-Adresse des Empfängers" /> <min value="1" /> <max value="1" /> <type> <code value="url" /> </type> <mapping> <identity value="Dispensieranforderung-Bestaetigung-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequestHeader.destination.endpoint" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Bestaetigung-Mapping" /> <map value="Aus initialer Dispensieranforderung (KIM Nachricht)" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request-confirmation.MetaDaten.Empfaenger.TelematikID"> <path value="gem-erp-sr-log-dispense-request-confirmation.MetaDaten.Empfaenger.TelematikID" /> <short value="Telematik-ID des Absenders" /> <definition value="Telematik-ID des Absenders" /> <min value="0" /> <max value="1" /> <type> <code value="url" /> </type> <mapping> <identity value="Dispensieranforderung-Bestaetigung-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequestHeader.destination.receiver.identifier.value" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Bestaetigung-Mapping" /> <map value="Aus initialer Dispensieranforderung" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request-confirmation.MetaDaten.Absender"> <path value="gem-erp-sr-log-dispense-request-confirmation.MetaDaten.Absender" /> <short value="Absender der Nachricht" /> <definition value="Absender der Nachricht" /> <min value="1" /> <max value="1" /> <type> <code value="BackboneElement" /> </type> <mapping> <identity value="Dispensieranforderung-Bestaetigung-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequestHeader.sender" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Bestaetigung-Mapping" /> <map value="Erstellendes AVS" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request-confirmation.MetaDaten.Absender.TelematikID"> <path value="gem-erp-sr-log-dispense-request-confirmation.MetaDaten.Absender.TelematikID" /> <short value="Telematik-ID des Absenders" /> <definition value="Telematik-ID des Absenders" /> <min value="0" /> <max value="1" /> <type> <code value="url" /> </type> <mapping> <identity value="Dispensieranforderung-Bestaetigung-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequestHeader.sender.identifier.value" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Bestaetigung-Mapping" /> <map value="Erstellendes AVS, SMC-B oder HBA Zertifikat" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request-confirmation.MetaDaten.Absender.Name"> <path value="gem-erp-sr-log-dispense-request-confirmation.MetaDaten.Absender.Name" /> <short value="Name des Absenders" /> <definition value="Name des Absenders" /> <min value="1" /> <max value="1" /> <type> <code value="string" /> </type> <mapping> <identity value="Dispensieranforderung-Bestaetigung-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequestHeader.sender.display" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Bestaetigung-Mapping" /> <map value="Erstellendes AVS" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request-confirmation.MetaDaten.AbsendendesSystem"> <path value="gem-erp-sr-log-dispense-request-confirmation.MetaDaten.AbsendendesSystem" /> <short value="Absendendes System" /> <definition value="Absendendes System" /> <min value="1" /> <max value="1" /> <type> <code value="BackboneElement" /> </type> <mapping> <identity value="Dispensieranforderung-Bestaetigung-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequestHeader.source" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Bestaetigung-Mapping" /> <map value="Erstellendes AVS" /> <comment value="Automatisiert durch Software gesetzt" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request-confirmation.MetaDaten.AbsendendesSystem.Name"> <path value="gem-erp-sr-log-dispense-request-confirmation.MetaDaten.AbsendendesSystem.Name" /> <short value="Name des Herstellers des absendenden Systems" /> <definition value="Name des Herstellers des absendenden Systems" /> <min value="1" /> <max value="1" /> <type> <code value="string" /> </type> <mapping> <identity value="Dispensieranforderung-Bestaetigung-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequestHeader.source.name" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Bestaetigung-Mapping" /> <map value="Erstellendes AVS" /> <comment value="Automatisiert durch Software gesetzt" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request-confirmation.MetaDaten.AbsendendesSystem.Software"> <path value="gem-erp-sr-log-dispense-request-confirmation.MetaDaten.AbsendendesSystem.Software" /> <short value="Name der Software des absendenden Systems" /> <definition value="Name der Software des absendenden Systems" /> <min value="1" /> <max value="1" /> <type> <code value="string" /> </type> <mapping> <identity value="Dispensieranforderung-Bestaetigung-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequestHeader.source.software" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Bestaetigung-Mapping" /> <map value="Erstellendes AVS" /> <comment value="Automatisiert durch Software gesetzt" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request-confirmation.MetaDaten.AbsendendesSystem.Version"> <path value="gem-erp-sr-log-dispense-request-confirmation.MetaDaten.AbsendendesSystem.Version" /> <short value="Version des absendenden Systems" /> <definition value="Version des absendenden Systems" /> <min value="1" /> <max value="1" /> <type> <code value="string" /> </type> <mapping> <identity value="Dispensieranforderung-Bestaetigung-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequestHeader.source.version" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Bestaetigung-Mapping" /> <map value="Erstellendes AVS" /> <comment value="Automatisiert durch Software gesetzt" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request-confirmation.MetaDaten.AbsendendesSystem.EMailKontakt"> <path value="gem-erp-sr-log-dispense-request-confirmation.MetaDaten.AbsendendesSystem.EMailKontakt" /> <short value="E-Mail-Kontakt des absendenden Systems" /> <definition value="E-Mail-Kontakt des absendenden Systems" /> <min value="1" /> <max value="1" /> <type> <code value="string" /> </type> <mapping> <identity value="Dispensieranforderung-Bestaetigung-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequestHeader.source.contact.value" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Bestaetigung-Mapping" /> <map value="Erstellendes AVS" /> <comment value="Automatisiert durch Software gesetzt" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request-confirmation.MetaDaten.AbsendendesSystem.Website"> <path value="gem-erp-sr-log-dispense-request-confirmation.MetaDaten.AbsendendesSystem.Website" /> <short value="Website des absendenden Systems" /> <definition value="Website des absendenden Systems" /> <min value="1" /> <max value="1" /> <type> <code value="url" /> </type> <mapping> <identity value="Dispensieranforderung-Bestaetigung-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequestHeader.source.endpoint" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Bestaetigung-Mapping" /> <map value="Erstellendes AVS" /> <comment value="Automatisiert durch Software gesetzt" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request-confirmation.Status"> <path value="gem-erp-sr-log-dispense-request-confirmation.Status" /> <short value="Status" /> <definition value="Status der Anforderung. Wird genutzt, um den Bearbeitungsstand einer Anfrage zu verfolgen. Im Falle der Dispensieranforderung wird eine erledigte Anfrage mit dem Status 'completed' geschickt und signalisiert somit eine neue Anfrage." /> <min value="1" /> <max value="1" /> <type> <code value="code" /> </type> <constraint> <key value="log-dispense-request-confirmation-1" /> <severity value="error" /> <human value="Wenn eine Anfrage erfüllt wird (status = 'completed'), müssen Abgabeinformationen vorhanden sein." /> <source value="https://gematik.de/fhir/erp-servicerequest/StructureDefinition/gem-erp-sr-log-dispense-request-confirmation" /> </constraint> <mapping> <identity value="Dispensieranforderung-Bestaetigung-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequest.status" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Bestaetigung-Mapping" /> <map value="AVS" /> <comment value="Setzt den Status der Anfrage auf 'completed'" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request-confirmation.VorgangsID"> <path value="gem-erp-sr-log-dispense-request-confirmation.VorgangsID" /> <short value="ID des Vorgangs" /> <definition value="Wird vom initialen Sender gesetzt und muss immer mitgeführt werden." /> <min value="1" /> <max value="1" /> <type> <code value="string" /> </type> <mapping> <identity value="Dispensieranforderung-Bestaetigung-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequest.identifier:requestId.value" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Bestaetigung-Mapping" /> <map value="Dispensieranforderung" /> <comment value="VorgangsID aus der initialen Dispensieranforderung" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request-confirmation.Freitext"> <path value="gem-erp-sr-log-dispense-request-confirmation.Freitext" /> <short value="Freitext" /> <definition value="Individuelle Nachricht an den Empfänger" /> <min value="0" /> <max value="1" /> <type> <code value="string" /> </type> <mapping> <identity value="Dispensieranforderung-Bestaetigung-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequest.note" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Bestaetigung-Mapping" /> <map value="Nutzer des AVS" /> <comment value="Abfrage im Moment der Bestätigung" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request-confirmation.Anhaenge"> <path value="gem-erp-sr-log-dispense-request-confirmation.Anhaenge" /> <short value="Anhänge" /> <definition value="Anhänge zur Anforderung. Das können PDFs, Bilder oder andere Dokumente sein." /> <comment value="Werden auf Ebene der KIM-Nachricht angehangen" /> <min value="0" /> <max value="*" /> <type> <code value="Attachment" /> </type> <mapping> <identity value="Quelle-Dispensieranforderung-Bestaetigung-Mapping" /> <map value="Nutzer" /> <comment value="Angabe im Moment der Bestätigung" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request-confirmation.Belieferungsart"> <path value="gem-erp-sr-log-dispense-request-confirmation.Belieferungsart" /> <short value="Belieferungsart" /> <definition value="Angabe der Belieferungsart" /> <min value="0" /> <max value="1" /> <type> <code value="Coding" /> </type> <mapping> <identity value="Dispensieranforderung-Bestaetigung-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequest.code.coding[delivery-type]" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request-confirmation.Belieferungsart.BelieferungsartCode"> <path value="gem-erp-sr-log-dispense-request-confirmation.Belieferungsart.BelieferungsartCode" /> <short value="Belieferungsart-Code" /> <definition value="Folgende Codes sind zulässig: Abholung durch Pflegedienst, Lieferung der Apotheke, Abholung durch Patienten" /> <min value="1" /> <max value="1" /> <type> <code value="Coding" /> </type> <mapping> <identity value="Dispensieranforderung-Bestaetigung-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequest.code.coding[delivery-type].code" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request-confirmation.Medikation"> <path value="gem-erp-sr-log-dispense-request-confirmation.Medikation" /> <short value="Medikation" /> <definition value="Angaben zur Medikation" /> <min value="1" /> <max value="1" /> <type> <code value="BackboneElement" /> </type> <constraint> <key value="log-dispense-request-confirmation-1" /> <severity value="error" /> <human value="Wenn eine Anfrage erfüllt wird (status = 'completed'), müssen Abgabeinformationen vorhanden sein." /> <source value="https://gematik.de/fhir/erp-servicerequest/StructureDefinition/gem-erp-sr-log-dispense-request-confirmation" /> </constraint> <mapping> <identity value="Dispensieranforderung-Bestaetigung-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequest.supportingInfo:Abgabedaten" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Bestaetigung-Mapping" /> <map value="AVS" /> <comment value="Informationen aus Abgabedatensatz" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request-confirmation.Medikation.Abgabeinformationen"> <path value="gem-erp-sr-log-dispense-request-confirmation.Medikation.Abgabeinformationen" /> <short value="Medizinische Verordnungsinformationen" /> <definition value="MedicationDispense und Medication Objekt aus den Abgabedaten." /> <min value="1" /> <max value="1" /> <type> <code value="Reference" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/MedicationDispense" /> </type> <mapping> <identity value="Dispensieranforderung-Bestaetigung-Fachliches-Mapping" /> <map value="ERPServiceRequestMedicationDispense" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Bestaetigung-Mapping" /> <map value="AVS" /> <comment value="Informationen aus Abgabedatensatz (MedicationDispense und Medication)" /> </mapping> </element> </differential> </StructureDefinition>
{ "resourceType": "StructureDefinition", "id": "gem-erp-sr-log-dispense-request-confirmation", "url": "https://gematik.de/fhir/erp-servicerequest/StructureDefinition/gem-erp-sr-log-dispense-request-confirmation", "version": "1.2", "name": "GEM_ERP_SR_LOG_DispenseRequest_Confirmation", "title": "Logical Model Dispenseieranforderung_Bestätigung", "status": "draft", "experimental": false, "date": "2025-01-01", "publisher": "gematik GmbH", "description": "Fachliches Modell zur Beschreibung einer Bestätigung einer Dispenseieranforderung", "fhirVersion": "4.0.1", "mapping": [ { "identity": "Dispensieranforderung-Bestaetigung-Fachliches-Mapping", "name": "Dispensieranforderung Bestätigung Fachliches Mapping", "uri": "ERPServiceRequestDispenseRequest", "comment": "Mapping des Fachmodells aus GEM_ERP_SR_LOG_DispenseRequest_Confirmation auf das FHIR-Modell ERPServiceRequestDispenseRequest" }, { "identity": "Quelle-Dispensieranforderung-Bestaetigung-Mapping", "name": "Quelle der Dispensieranforderung Bestätigung Informationen", "comment": "Beschreibt die Quelle der Dispensieranforderung Bestätigung Informatione" } ], "kind": "logical", "abstract": false, "type": "https://gematik.de/fhir/erp-servicerequest/StructureDefinition/gem-erp-sr-log-dispense-request-confirmation", "baseDefinition": "http://hl7.org/fhir/StructureDefinition/Element", "derivation": "specialization", "differential": { "element": [ { "id": "gem-erp-sr-log-dispense-request-confirmation", "path": "gem-erp-sr-log-dispense-request-confirmation", "short": "Logical Model Dispenseieranforderung_Bestätigung", "definition": "Fachliches Modell zur Beschreibung einer Bestätigung einer Dispenseieranforderung", "constraint": [ { "key": "log-dispense-request-confirmation-1", "severity": "error", "human": "Wenn eine Anfrage erfüllt wird (status = 'completed'), müssen Abgabeinformationen vorhanden sein.", "source": "https://gematik.de/fhir/erp-servicerequest/StructureDefinition/gem-erp-sr-log-dispense-request-confirmation" } ] }, { "id": "gem-erp-sr-log-dispense-request-confirmation.MetaDaten", "path": "gem-erp-sr-log-dispense-request-confirmation.MetaDaten", "short": "Metadaten im MessageHeader", "definition": "Metadaten im MessageHeader", "min": 1, "max": "1", "type": [ { "code": "BackboneElement" } ], "mapping": [ { "identity": "Dispensieranforderung-Bestaetigung-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequestHeader" }, { "identity": "Quelle-Dispensieranforderung-Bestaetigung-Mapping", "map": "Erstellendes AVS" } ] }, { "id": "gem-erp-sr-log-dispense-request-confirmation.MetaDaten.Empfaenger", "path": "gem-erp-sr-log-dispense-request-confirmation.MetaDaten.Empfaenger", "short": "Empfänger der Nachricht", "definition": "Empfänger der Nachricht", "min": 1, "max": "*", "type": [ { "code": "BackboneElement" } ], "mapping": [ { "identity": "Dispensieranforderung-Bestaetigung-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequestHeader.destination" }, { "identity": "Quelle-Dispensieranforderung-Bestaetigung-Mapping", "map": "Aus initialer Dispensieranforderung" } ] }, { "id": "gem-erp-sr-log-dispense-request-confirmation.MetaDaten.Empfaenger.KIMAdresse", "path": "gem-erp-sr-log-dispense-request-confirmation.MetaDaten.Empfaenger.KIMAdresse", "short": "KIM-Adresse des Empfängers", "definition": "KIM-Adresse des Empfängers", "min": 1, "max": "1", "type": [ { "code": "url" } ], "mapping": [ { "identity": "Dispensieranforderung-Bestaetigung-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequestHeader.destination.endpoint" }, { "identity": "Quelle-Dispensieranforderung-Bestaetigung-Mapping", "map": "Aus initialer Dispensieranforderung (KIM Nachricht)" } ] }, { "id": "gem-erp-sr-log-dispense-request-confirmation.MetaDaten.Empfaenger.TelematikID", "path": "gem-erp-sr-log-dispense-request-confirmation.MetaDaten.Empfaenger.TelematikID", "short": "Telematik-ID des Absenders", "definition": "Telematik-ID des Absenders", "min": 0, "max": "1", "type": [ { "code": "url" } ], "mapping": [ { "identity": "Dispensieranforderung-Bestaetigung-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequestHeader.destination.receiver.identifier.value" }, { "identity": "Quelle-Dispensieranforderung-Bestaetigung-Mapping", "map": "Aus initialer Dispensieranforderung" } ] }, { "id": "gem-erp-sr-log-dispense-request-confirmation.MetaDaten.Absender", "path": "gem-erp-sr-log-dispense-request-confirmation.MetaDaten.Absender", "short": "Absender der Nachricht", "definition": "Absender der Nachricht", "min": 1, "max": "1", "type": [ { "code": "BackboneElement" } ], "mapping": [ { "identity": "Dispensieranforderung-Bestaetigung-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequestHeader.sender" }, { "identity": "Quelle-Dispensieranforderung-Bestaetigung-Mapping", "map": "Erstellendes AVS" } ] }, { "id": "gem-erp-sr-log-dispense-request-confirmation.MetaDaten.Absender.TelematikID", "path": "gem-erp-sr-log-dispense-request-confirmation.MetaDaten.Absender.TelematikID", "short": "Telematik-ID des Absenders", "definition": "Telematik-ID des Absenders", "min": 0, "max": "1", "type": [ { "code": "url" } ], "mapping": [ { "identity": "Dispensieranforderung-Bestaetigung-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequestHeader.sender.identifier.value" }, { "identity": "Quelle-Dispensieranforderung-Bestaetigung-Mapping", "map": "Erstellendes AVS, SMC-B oder HBA Zertifikat" } ] }, { "id": "gem-erp-sr-log-dispense-request-confirmation.MetaDaten.Absender.Name", "path": "gem-erp-sr-log-dispense-request-confirmation.MetaDaten.Absender.Name", "short": "Name des Absenders", "definition": "Name des Absenders", "min": 1, "max": "1", "type": [ { "code": "string" } ], "mapping": [ { "identity": "Dispensieranforderung-Bestaetigung-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequestHeader.sender.display" }, { "identity": "Quelle-Dispensieranforderung-Bestaetigung-Mapping", "map": "Erstellendes AVS" } ] }, { "id": "gem-erp-sr-log-dispense-request-confirmation.MetaDaten.AbsendendesSystem", "path": "gem-erp-sr-log-dispense-request-confirmation.MetaDaten.AbsendendesSystem", "short": "Absendendes System", "definition": "Absendendes System", "min": 1, "max": "1", "type": [ { "code": "BackboneElement" } ], "mapping": [ { "identity": "Dispensieranforderung-Bestaetigung-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequestHeader.source" }, { "identity": "Quelle-Dispensieranforderung-Bestaetigung-Mapping", "map": "Erstellendes AVS", "comment": "Automatisiert durch Software gesetzt" } ] }, { "id": "gem-erp-sr-log-dispense-request-confirmation.MetaDaten.AbsendendesSystem.Name", "path": "gem-erp-sr-log-dispense-request-confirmation.MetaDaten.AbsendendesSystem.Name", "short": "Name des Herstellers des absendenden Systems", "definition": "Name des Herstellers des absendenden Systems", "min": 1, "max": "1", "type": [ { "code": "string" } ], "mapping": [ { "identity": "Dispensieranforderung-Bestaetigung-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequestHeader.source.name" }, { "identity": "Quelle-Dispensieranforderung-Bestaetigung-Mapping", "map": "Erstellendes AVS", "comment": "Automatisiert durch Software gesetzt" } ] }, { "id": "gem-erp-sr-log-dispense-request-confirmation.MetaDaten.AbsendendesSystem.Software", "path": "gem-erp-sr-log-dispense-request-confirmation.MetaDaten.AbsendendesSystem.Software", "short": "Name der Software des absendenden Systems", "definition": "Name der Software des absendenden Systems", "min": 1, "max": "1", "type": [ { "code": "string" } ], "mapping": [ { "identity": "Dispensieranforderung-Bestaetigung-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequestHeader.source.software" }, { "identity": "Quelle-Dispensieranforderung-Bestaetigung-Mapping", "map": "Erstellendes AVS", "comment": "Automatisiert durch Software gesetzt" } ] }, { "id": "gem-erp-sr-log-dispense-request-confirmation.MetaDaten.AbsendendesSystem.Version", "path": "gem-erp-sr-log-dispense-request-confirmation.MetaDaten.AbsendendesSystem.Version", "short": "Version des absendenden Systems", "definition": "Version des absendenden Systems", "min": 1, "max": "1", "type": [ { "code": "string" } ], "mapping": [ { "identity": "Dispensieranforderung-Bestaetigung-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequestHeader.source.version" }, { "identity": "Quelle-Dispensieranforderung-Bestaetigung-Mapping", "map": "Erstellendes AVS", "comment": "Automatisiert durch Software gesetzt" } ] }, { "id": "gem-erp-sr-log-dispense-request-confirmation.MetaDaten.AbsendendesSystem.EMailKontakt", "path": "gem-erp-sr-log-dispense-request-confirmation.MetaDaten.AbsendendesSystem.EMailKontakt", "short": "E-Mail-Kontakt des absendenden Systems", "definition": "E-Mail-Kontakt des absendenden Systems", "min": 1, "max": "1", "type": [ { "code": "string" } ], "mapping": [ { "identity": "Dispensieranforderung-Bestaetigung-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequestHeader.source.contact.value" }, { "identity": "Quelle-Dispensieranforderung-Bestaetigung-Mapping", "map": "Erstellendes AVS", "comment": "Automatisiert durch Software gesetzt" } ] }, { "id": "gem-erp-sr-log-dispense-request-confirmation.MetaDaten.AbsendendesSystem.Website", "path": "gem-erp-sr-log-dispense-request-confirmation.MetaDaten.AbsendendesSystem.Website", "short": "Website des absendenden Systems", "definition": "Website des absendenden Systems", "min": 1, "max": "1", "type": [ { "code": "url" } ], "mapping": [ { "identity": "Dispensieranforderung-Bestaetigung-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequestHeader.source.endpoint" }, { "identity": "Quelle-Dispensieranforderung-Bestaetigung-Mapping", "map": "Erstellendes AVS", "comment": "Automatisiert durch Software gesetzt" } ] }, { "id": "gem-erp-sr-log-dispense-request-confirmation.Status", "path": "gem-erp-sr-log-dispense-request-confirmation.Status", "short": "Status", "definition": "Status der Anforderung. Wird genutzt, um den Bearbeitungsstand einer Anfrage zu verfolgen. Im Falle der Dispensieranforderung wird eine erledigte Anfrage mit dem Status 'completed' geschickt und signalisiert somit eine neue Anfrage.", "min": 1, "max": "1", "type": [ { "code": "code" } ], "constraint": [ { "key": "log-dispense-request-confirmation-1", "severity": "error", "human": "Wenn eine Anfrage erfüllt wird (status = 'completed'), müssen Abgabeinformationen vorhanden sein.", "source": "https://gematik.de/fhir/erp-servicerequest/StructureDefinition/gem-erp-sr-log-dispense-request-confirmation" } ], "mapping": [ { "identity": "Dispensieranforderung-Bestaetigung-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequest.status" }, { "identity": "Quelle-Dispensieranforderung-Bestaetigung-Mapping", "map": "AVS", "comment": "Setzt den Status der Anfrage auf 'completed'" } ] }, { "id": "gem-erp-sr-log-dispense-request-confirmation.VorgangsID", "path": "gem-erp-sr-log-dispense-request-confirmation.VorgangsID", "short": "ID des Vorgangs", "definition": "Wird vom initialen Sender gesetzt und muss immer mitgeführt werden.", "min": 1, "max": "1", "type": [ { "code": "string" } ], "mapping": [ { "identity": "Dispensieranforderung-Bestaetigung-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequest.identifier:requestId.value" }, { "identity": "Quelle-Dispensieranforderung-Bestaetigung-Mapping", "map": "Dispensieranforderung", "comment": "VorgangsID aus der initialen Dispensieranforderung" } ] }, { "id": "gem-erp-sr-log-dispense-request-confirmation.Freitext", "path": "gem-erp-sr-log-dispense-request-confirmation.Freitext", "short": "Freitext", "definition": "Individuelle Nachricht an den Empfänger", "min": 0, "max": "1", "type": [ { "code": "string" } ], "mapping": [ { "identity": "Dispensieranforderung-Bestaetigung-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequest.note" }, { "identity": "Quelle-Dispensieranforderung-Bestaetigung-Mapping", "map": "Nutzer des AVS", "comment": "Abfrage im Moment der Bestätigung" } ] }, { "id": "gem-erp-sr-log-dispense-request-confirmation.Anhaenge", "path": "gem-erp-sr-log-dispense-request-confirmation.Anhaenge", "short": "Anhänge", "definition": "Anhänge zur Anforderung. Das können PDFs, Bilder oder andere Dokumente sein.", "comment": "Werden auf Ebene der KIM-Nachricht angehangen", "min": 0, "max": "*", "type": [ { "code": "Attachment" } ], "mapping": [ { "identity": "Quelle-Dispensieranforderung-Bestaetigung-Mapping", "map": "Nutzer", "comment": "Angabe im Moment der Bestätigung" } ] }, { "id": "gem-erp-sr-log-dispense-request-confirmation.Belieferungsart", "path": "gem-erp-sr-log-dispense-request-confirmation.Belieferungsart", "short": "Belieferungsart", "definition": "Angabe der Belieferungsart", "min": 0, "max": "1", "type": [ { "code": "Coding" } ], "mapping": [ { "identity": "Dispensieranforderung-Bestaetigung-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequest.code.coding[delivery-type]" } ] }, { "id": "gem-erp-sr-log-dispense-request-confirmation.Belieferungsart.BelieferungsartCode", "path": "gem-erp-sr-log-dispense-request-confirmation.Belieferungsart.BelieferungsartCode", "short": "Belieferungsart-Code", "definition": "Folgende Codes sind zulässig: Abholung durch Pflegedienst, Lieferung der Apotheke, Abholung durch Patienten", "min": 1, "max": "1", "type": [ { "code": "Coding" } ], "mapping": [ { "identity": "Dispensieranforderung-Bestaetigung-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequest.code.coding[delivery-type].code" } ] }, { "id": "gem-erp-sr-log-dispense-request-confirmation.Medikation", "path": "gem-erp-sr-log-dispense-request-confirmation.Medikation", "short": "Medikation", "definition": "Angaben zur Medikation", "min": 1, "max": "1", "type": [ { "code": "BackboneElement" } ], "constraint": [ { "key": "log-dispense-request-confirmation-1", "severity": "error", "human": "Wenn eine Anfrage erfüllt wird (status = 'completed'), müssen Abgabeinformationen vorhanden sein.", "source": "https://gematik.de/fhir/erp-servicerequest/StructureDefinition/gem-erp-sr-log-dispense-request-confirmation" } ], "mapping": [ { "identity": "Dispensieranforderung-Bestaetigung-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequest.supportingInfo:Abgabedaten" }, { "identity": "Quelle-Dispensieranforderung-Bestaetigung-Mapping", "map": "AVS", "comment": "Informationen aus Abgabedatensatz" } ] }, { "id": "gem-erp-sr-log-dispense-request-confirmation.Medikation.Abgabeinformationen", "path": "gem-erp-sr-log-dispense-request-confirmation.Medikation.Abgabeinformationen", "short": "Medizinische Verordnungsinformationen", "definition": "MedicationDispense und Medication Objekt aus den Abgabedaten.", "min": 1, "max": "1", "type": [ { "code": "Reference", "targetProfile": [ "http://hl7.org/fhir/StructureDefinition/MedicationDispense" ] } ], "mapping": [ { "identity": "Dispensieranforderung-Bestaetigung-Fachliches-Mapping", "map": "ERPServiceRequestMedicationDispense" }, { "identity": "Quelle-Dispensieranforderung-Bestaetigung-Mapping", "map": "AVS", "comment": "Informationen aus Abgabedatensatz (MedicationDispense und Medication)" } ] } ] } }
Terminologie Bindings
Folgende Bindings sind für diese Ressource spezifiziert:
Constraints
Folgende Constraints sind für diese Ressource spezifiziert:
Pfad | Id | Grade | Details |
---|---|---|---|
gem-erp-sr-log-dispense-request-confirmation | log-dispense-request-confirmation-1 | error | Wenn eine Anfrage erfüllt wird (status = 'completed'), müssen Abgabeinformationen vorhanden sein. |
gem-erp-sr-log-dispense-request-confirmation.Status | log-dispense-request-confirmation-1 | error | Wenn eine Anfrage erfüllt wird (status = 'completed'), müssen Abgabeinformationen vorhanden sein. |
gem-erp-sr-log-dispense-request-confirmation.Medikation | log-dispense-request-confirmation-1 | error | Wenn eine Anfrage erfüllt wird (status = 'completed'), müssen Abgabeinformationen vorhanden sein. |