Logisches Modell zur Dispensieranforderung
Übersicht über das Profil
Name | Description | Canonical_URL | Status | Version | Basiert auf |
---|---|---|---|---|---|
GEM_ERP_SR_LOG_DispenseRequest | Fachliches Modell zur Beschreibung einer Dispenseieranforderung | https://gematik.de/fhir/erp-servicerequest/StructureDefinition/gem-erp-sr-log-dispense-request | draft | 1.2 | http://hl7.org/fhir/StructureDefinition/Element |
Über das Profil
Motivation
Dieses logische Modell beschreibt die Inhalte einer initialen Dispensieranforderung seitens Pflegeeinrichtung an eine Apotheke.
Inhalt des Profils
Folgende Ansichten existieren auf das Profil:
GEM_ERP_SR_LOG_DispenseRequest (gem-erp-sr-log-dispense-request) | 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 | |
ERezeptToken | I | 1..1 | string |
involvierteParteien | 1..* | BackboneElement | |
id | 0..1 | string | |
extension | I | 0..* | Extension |
modifierExtension | Σ ?! I | 0..* | Extension |
Anfragender | 1..1 | BackboneElement | |
id | 0..1 | string | |
extension | I | 0..* | Extension |
modifierExtension | Σ ?! I | 0..* | Extension |
AnfragenderTyp | I | 1..1 | Coding |
Name | 1..1 | string | |
Adresse | 0..1 | Address | |
Telefon | 1..1 | string | |
PatientenInformationen | 1..1 | BackboneElement | |
id | 0..1 | string | |
extension | I | 0..* | Extension |
modifierExtension | Σ ?! I | 0..* | Extension |
PatientenIdentifierKVNR | 1..1 | string | |
PatientenName | 1..1 | HumanName | |
PatientenGeburtstag | 1..1 | date | |
Freitext | 0..1 | string | |
Belieferungsart | I | 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 | |
AlternativeAdresse | 0..1 | Address | |
Prioritaet | 0..1 | BackboneElement | |
id | 0..1 | string | |
extension | I | 0..* | Extension |
modifierExtension | Σ ?! I | 0..* | Extension |
PrioritaetCode | 1..1 | Coding | |
Anhaenge | I | 0..* | Attachment |
id | 0..1 | string | |
extension | I | 0..* | Extension |
contentType | Σ | 0..1 | codeBinding |
language | Σ | 0..1 | codeBinding |
data | 0..1 | base64Binary | |
url | Σ | 0..1 | url |
size | Σ | 0..1 | unsignedInt |
hash | Σ | 0..1 | base64Binary |
title | Σ | 0..1 | string |
creation | Σ | 0..1 | dateTime |
Medikationsplan | I | 0..1 | Attachment |
weitereAnhaenge | I | 0..* | Attachment |
gem-erp-sr-log-dispense-request | |
Definition | Fachliches Modell zur Beschreibung einer Dispenseieranforderung |
Cardinality | 0...* |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request.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.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.MetaDaten | |
Definition | Metadaten im MessageHeader |
Cardinality | 1...1 |
Type | BackboneElement |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request.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.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.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.MetaDaten.Empfaenger | |
Definition | Empfänger der Nachricht |
Cardinality | 1...* |
Type | BackboneElement |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request.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.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.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.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.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.MetaDaten.Absender | |
Definition | Absender der Nachricht |
Cardinality | 1...1 |
Type | BackboneElement |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request.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.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.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.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.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.MetaDaten.AbsendendesSystem | |
Definition | Absendendes System |
Cardinality | 1...1 |
Type | BackboneElement |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request.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.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.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.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.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.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.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.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.Status | |
Definition | Status der Anforderung. Wird genutzt, um den Bearbeitungsstand einer Anfrage zu verfolgen. Im Falle der initialen Dispensieranforderung wird eine Anfrage mit dem Status 'active' erstellt und 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.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.ERezeptToken | |
Definition | Token der für die Einlösung der Verordnung gebraucht wird. |
Cardinality | 1...1 |
Type | string |
Comments | Angabe nach gemSpec_DM_eRp#A_19554. |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request.involvierteParteien | |
Definition | Angaben zu den involvierten Parteien |
Cardinality | 1...* |
Type | BackboneElement |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request.involvierteParteien.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.involvierteParteien.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.involvierteParteien.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.involvierteParteien.Anfragender | |
Definition | Angaben zum anfragenden |
Cardinality | 1...1 |
Type | BackboneElement |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request.involvierteParteien.Anfragender.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.involvierteParteien.Anfragender.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.involvierteParteien.Anfragender.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.involvierteParteien.Anfragender.AnfragenderTyp | |
Definition | Folgende Typen sind zulässig: Apotheke, Pflegeeinrichtung |
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.involvierteParteien.Anfragender.Name | |
Definition | Name des Anfragenden |
Cardinality | 1...1 |
Type | string |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request.involvierteParteien.Anfragender.Adresse | |
Definition | Straßenadresse des Anfragenden |
Cardinality | 0...1 |
Type | Address |
Comments | Note: address is intended to describe postal addresses for administrative purposes, not to describe absolute geographical coordinates. Postal addresses are often used as proxies for physical locations (also see the Location resource). |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request.involvierteParteien.Anfragender.Telefon | |
Definition | Telefonnummer des Anfragenden |
Cardinality | 1...1 |
Type | string |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request.involvierteParteien.PatientenInformationen | |
Definition | Angaben zum Patienten |
Cardinality | 1...1 |
Type | BackboneElement |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request.involvierteParteien.PatientenInformationen.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.involvierteParteien.PatientenInformationen.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.involvierteParteien.PatientenInformationen.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.involvierteParteien.PatientenInformationen.PatientenIdentifierKVNR | |
Definition | KVNR des Patienten |
Cardinality | 1...1 |
Type | string |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request.involvierteParteien.PatientenInformationen.PatientenName | |
Definition | Strukturierte Angabe des Namens des Patienten |
Cardinality | 1...1 |
Type | HumanName |
Comments | Names may be changed, or repudiated, or people may have different names in different contexts. Names may be divided into parts of different type that have variable significance depending on context, though the division into parts does not always matter. With personal names, the different parts might or might not be imbued with some implicit meaning; various cultures associate different importance with the name parts and the degree to which systems must care about name parts around the world varies widely. |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request.involvierteParteien.PatientenInformationen.PatientenGeburtstag | |
Definition | Angabe des Geburtstags mit Jahr, Monat und Tag |
Cardinality | 1...1 |
Type | date |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request.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.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.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.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.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.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.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.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.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.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.Belieferungsart.AlternativeAdresse | |
Definition | Alternative Adresse für die Lieferung |
Cardinality | 0...1 |
Type | Address |
Comments | Note: address is intended to describe postal addresses for administrative purposes, not to describe absolute geographical coordinates. Postal addresses are often used as proxies for physical locations (also see the Location resource). |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request.Prioritaet | |
Definition | Angabe der Priorität der Anforderung |
Cardinality | 0...1 |
Type | BackboneElement |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request.Prioritaet.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.Prioritaet.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.Prioritaet.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.Prioritaet.PrioritaetCode | |
Definition | Folgende Prioritäten sind zulässig: Hoch, Normal |
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.Anhaenge | |
Definition | Anhänge zur Bestätigung. 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.Anhaenge.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.Anhaenge.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.Anhaenge.contentType | |
Definition | Identifies the type of the data in the attachment and allows a method to be chosen to interpret or render the data. Includes mime type parameters such as charset where appropriate. |
Cardinality | 0...1 |
Type | code |
Binding | The mime type of an attachment. Any valid mime type is allowed. |
Summary | True |
Requirements | Processors of the data need to be able to know how to interpret the data. |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Examples | General text/plain; charset=UTF-8, image/png |
Mappings |
|
gem-erp-sr-log-dispense-request.Anhaenge.language | |
Definition | The human language of the content. The value can be any valid value according to BCP 47. |
Cardinality | 0...1 |
Type | code |
Binding | A human language. |
Summary | True |
Requirements | Users need to be able to choose between the languages in a set of attachments. |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Examples | General en-AU |
Mappings |
|
gem-erp-sr-log-dispense-request.Anhaenge.data | |
Definition | The actual data of the attachment - a sequence of bytes, base64 encoded. |
Cardinality | 0...1 |
Type | base64Binary |
Requirements | The data needs to able to be transmitted inline. |
Comments | The base64-encoded data SHALL be expressed in the same character set as the base resource XML or JSON. |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request.Anhaenge.url | |
Definition | A location where the data can be accessed. |
Cardinality | 0...1 |
Type | url |
Summary | True |
Requirements | The data needs to be transmitted by reference. |
Comments | If both data and url are provided, the url SHALL point to the same content as the data contains. Urls may be relative references or may reference transient locations such as a wrapping envelope using cid: though this has ramifications for using signatures. Relative URLs are interpreted relative to the service url, like a resource reference, rather than relative to the resource itself. If a URL is provided, it SHALL resolve to actual data. |
Invariants |
|
Examples | General http://www.acme.com/logo-small.png |
Mappings |
|
gem-erp-sr-log-dispense-request.Anhaenge.size | |
Definition | The number of bytes of data that make up this attachment (before base64 encoding, if that is done). |
Cardinality | 0...1 |
Type | unsignedInt |
Summary | True |
Requirements | Representing the size allows applications to determine whether they should fetch the content automatically in advance, or refuse to fetch it at all. |
Comments | The number of bytes is redundant if the data is provided as a base64binary, but is useful if the data is provided as a url reference. |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request.Anhaenge.hash | |
Definition | The calculated hash of the data using SHA-1. Represented using base64. |
Cardinality | 0...1 |
Type | base64Binary |
Summary | True |
Requirements | Included so that applications can verify that the contents of a location have not changed due to technical failures (e.g., storage rot, transport glitch, incorrect version). |
Comments | The hash is calculated on the data prior to base64 encoding, if the data is based64 encoded. The hash is not intended to support digital signatures. Where protection against malicious threats a digital signature should be considered, see Provenance.signature for mechanism to protect a resource with a digital signature. |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request.Anhaenge.title | |
Definition | A label or set of text to display in place of the data. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Requirements | Applications need a label to display to a human user in place of the actual data if the data cannot be rendered or perceived by the viewer. |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Examples | General Official Corporate Logo |
Mappings |
|
gem-erp-sr-log-dispense-request.Anhaenge.creation | |
Definition | The date that the attachment was first created. |
Cardinality | 0...1 |
Type | dateTime |
Summary | True |
Requirements | This is often tracked as an integrity issue for use of the attachment. |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request.Anhaenge.Medikationsplan | |
Definition | Anhang des Medikationsplans |
Cardinality | 0...1 |
Type | Attachment |
Comments | When providing a summary view (for example with Observation.value[x]) Attachment should be represented with a brief display text such as "Signed Procedure Consent". |
Invariants |
|
Mappings |
|
gem-erp-sr-log-dispense-request.Anhaenge.weitereAnhaenge | |
Definition | Weitere Anhänge |
Cardinality | 0...* |
Type | Attachment |
Comments | When providing a summary view (for example with Observation.value[x]) Attachment should be represented with a brief display text such as "Signed Procedure Consent". |
Invariants |
|
Mappings |
|
<StructureDefinition xmlns="http://hl7.org/fhir"> <id value="gem-erp-sr-log-dispense-request" /> <url value="https://gematik.de/fhir/erp-servicerequest/StructureDefinition/gem-erp-sr-log-dispense-request" /> <version value="1.2" /> <name value="GEM_ERP_SR_LOG_DispenseRequest" /> <title value="Logical Model Dispenseieranforderung" /> <status value="draft" /> <experimental value="false" /> <date value="2025-01-01" /> <publisher value="gematik GmbH" /> <description value="Fachliches Modell zur Beschreibung einer Dispenseieranforderung" /> <fhirVersion value="4.0.1" /> <mapping> <identity value="Dispensieranforderung-Fachliches-Mapping" /> <uri value="ERPServiceRequestDispenseRequest" /> <name value="Dispensieranforderung Fachliches Mapping" /> <comment value="Mapping des Fachmodells aus GEM_ERP_SR_LOG_DispenseRequest auf das FHIR-Modell ERPServiceRequestDispenseRequest" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Mapping" /> <name value="Quelle der Dispensieranforderungsinformationen" /> <comment value="Beschreibt die Quelle der Dispensieranforderungsinformationen. Wird von der Pflegeeinrichtung zur Anforderung zur Abgabe von Arzneimitteln verwendet." /> </mapping> <kind value="logical" /> <abstract value="false" /> <type value="https://gematik.de/fhir/erp-servicerequest/StructureDefinition/gem-erp-sr-log-dispense-request" /> <baseDefinition value="http://hl7.org/fhir/StructureDefinition/Element" /> <derivation value="specialization" /> <differential> <element id="gem-erp-sr-log-dispense-request"> <path value="gem-erp-sr-log-dispense-request" /> <short value="Logical Model Dispenseieranforderung" /> <definition value="Fachliches Modell zur Beschreibung einer Dispenseieranforderung" /> <constraint> <key value="log-dispense-request-1" /> <severity value="error" /> <human value="Wenn eine Anfrage gestellt wird (status = 'active'), muss der Anfragende eine Pflegeeinrichtung sein." /> <source value="https://gematik.de/fhir/erp-servicerequest/StructureDefinition/gem-erp-sr-log-dispense-request" /> </constraint> <constraint> <key value="log-dispense-request-2" /> <severity value="error" /> <human value="Wenn eine Anfrage gestellt wird (status = 'active'), muss auch der E-Rezept-Token vorhanden sein." /> <source value="https://gematik.de/fhir/erp-servicerequest/StructureDefinition/gem-erp-sr-log-dispense-request" /> </constraint> <constraint> <key value="log-dispense-request-3" /> <severity value="error" /> <human value="Wenn als Belieferungsart 'Lieferung an Alternative Addresse' angegeben wird, dann muss die Adresse auch angegeben werden." /> <source value="https://gematik.de/fhir/erp-servicerequest/StructureDefinition/gem-erp-sr-log-dispense-request" /> </constraint> </element> <element id="gem-erp-sr-log-dispense-request.MetaDaten"> <path value="gem-erp-sr-log-dispense-request.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-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequestHeader" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Mapping" /> <map value="Erstellendes PS" /> <comment value="Pflegesystem" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request.MetaDaten.Empfaenger"> <path value="gem-erp-sr-log-dispense-request.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-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequestHeader.destination" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Mapping" /> <map value="Aus Kontaktmanagement oder VZD Suche" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request.MetaDaten.Empfaenger.KIMAdresse"> <path value="gem-erp-sr-log-dispense-request.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-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequestHeader.destination.endpoint" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Mapping" /> <map value="Aus Kontaktmanagement oder VZD Suche" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request.MetaDaten.Empfaenger.TelematikID"> <path value="gem-erp-sr-log-dispense-request.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-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequestHeader.destination.receiver.identifier.value" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Mapping" /> <map value="Aus Kontaktmanagement oder VZD Suche" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request.MetaDaten.Absender"> <path value="gem-erp-sr-log-dispense-request.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-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequestHeader.sender" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Mapping" /> <map value="Erstellendes PS" /> <comment value="Pflegesystem" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request.MetaDaten.Absender.TelematikID"> <path value="gem-erp-sr-log-dispense-request.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-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequestHeader.sender.identifier.value" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Mapping" /> <map value="Erstellendes PS, SMC-B Zertifikat" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request.MetaDaten.Absender.Name"> <path value="gem-erp-sr-log-dispense-request.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-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequestHeader.sender.display" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Mapping" /> <map value="Erstellendes PS" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request.MetaDaten.AbsendendesSystem"> <path value="gem-erp-sr-log-dispense-request.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-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequestHeader.source" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Mapping" /> <map value="Erstellendes PS" /> <comment value="Automatisiert durch Software gesetzt" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request.MetaDaten.AbsendendesSystem.Name"> <path value="gem-erp-sr-log-dispense-request.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-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequestHeader.source.name" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Mapping" /> <map value="Erstellendes PS" /> <comment value="Automatisiert durch Software gesetzt" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request.MetaDaten.AbsendendesSystem.Software"> <path value="gem-erp-sr-log-dispense-request.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-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequestHeader.source.software" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Mapping" /> <map value="Erstellendes PS" /> <comment value="Automatisiert durch Software gesetzt" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request.MetaDaten.AbsendendesSystem.Version"> <path value="gem-erp-sr-log-dispense-request.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-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequestHeader.source.version" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Mapping" /> <map value="Erstellendes PS" /> <comment value="Automatisiert durch Software gesetzt" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request.MetaDaten.AbsendendesSystem.EMailKontakt"> <path value="gem-erp-sr-log-dispense-request.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-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequestHeader.source.contact.value" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Mapping" /> <map value="Erstellendes PS" /> <comment value="Automatisiert durch Software gesetzt" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request.MetaDaten.AbsendendesSystem.Website"> <path value="gem-erp-sr-log-dispense-request.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-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequestHeader.source.endpoint" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Mapping" /> <map value="Erstellendes PS" /> <comment value="Automatisiert durch Software gesetzt" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request.Status"> <path value="gem-erp-sr-log-dispense-request.Status" /> <short value="Status" /> <definition value="Status der Anforderung. Wird genutzt, um den Bearbeitungsstand einer Anfrage zu verfolgen. Im Falle der initialen Dispensieranforderung wird eine Anfrage mit dem Status 'active' erstellt und geschickt und signalisiert somit eine neue Anfrage." /> <min value="1" /> <max value="1" /> <type> <code value="code" /> </type> <constraint> <key value="log-dispense-request-1" /> <severity value="error" /> <human value="Wenn eine Anfrage gestellt wird (status = 'active'), muss der Anfragende eine Pflegeeinrichtung sein." /> <source value="https://gematik.de/fhir/erp-servicerequest/StructureDefinition/gem-erp-sr-log-dispense-request" /> </constraint> <constraint> <key value="log-dispense-request-2" /> <severity value="error" /> <human value="Wenn eine Anfrage gestellt wird (status = 'active'), muss auch der E-Rezept-Token vorhanden sein." /> <source value="https://gematik.de/fhir/erp-servicerequest/StructureDefinition/gem-erp-sr-log-dispense-request" /> </constraint> <mapping> <identity value="Dispensieranforderung-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequest.status" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Mapping" /> <map value="Anfragendes PS" /> <comment value="Setzt den Status der Anfrage auf 'active'" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request.VorgangsID"> <path value="gem-erp-sr-log-dispense-request.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-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequest.identifier:requestId.value" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Mapping" /> <map value="Initiale Rezeptanforderung" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request.ERezeptToken"> <path value="gem-erp-sr-log-dispense-request.ERezeptToken" /> <short value="E-Rezept-Token" /> <definition value="Token der für die Einlösung der Verordnung gebraucht wird." /> <comment value="Angabe nach gemSpec_DM_eRp#A_19554." /> <min value="1" /> <max value="1" /> <type> <code value="string" /> </type> <constraint> <key value="log-dispense-request-2" /> <severity value="error" /> <human value="Wenn eine Anfrage gestellt wird (status = 'active'), muss auch der E-Rezept-Token vorhanden sein." /> <source value="https://gematik.de/fhir/erp-servicerequest/StructureDefinition/gem-erp-sr-log-dispense-request" /> </constraint> <mapping> <identity value="Dispensieranforderung-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequest.extension:EPrescriptionToken" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Mapping" /> <map value="Rezeptanforderung_Bestätigung" /> <comment value="Wurde vom verordnenden Arzt bereitgestellt" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request.involvierteParteien"> <path value="gem-erp-sr-log-dispense-request.involvierteParteien" /> <short value="Involvierte Parteien" /> <definition value="Angaben zu den involvierten Parteien" /> <min value="1" /> <max value="*" /> <type> <code value="BackboneElement" /> </type> <mapping> <identity value="Dispensieranforderung-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequest.requester" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request.involvierteParteien.Anfragender"> <path value="gem-erp-sr-log-dispense-request.involvierteParteien.Anfragender" /> <short value="Anfragender" /> <definition value="Angaben zum anfragenden" /> <min value="1" /> <max value="1" /> <type> <code value="BackboneElement" /> </type> <mapping> <identity value="Dispensieranforderung-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequest.requester(ERPServiceRequestOrganization)" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Mapping" /> <map value="Anfragendes PS" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request.involvierteParteien.Anfragender.AnfragenderTyp"> <path value="gem-erp-sr-log-dispense-request.involvierteParteien.Anfragender.AnfragenderTyp" /> <short value="Typ des Anfragenden" /> <definition value="Folgende Typen sind zulässig: Apotheke, Pflegeeinrichtung" /> <min value="1" /> <max value="1" /> <type> <code value="Coding" /> </type> <constraint> <key value="log-dispense-request-1" /> <severity value="error" /> <human value="Wenn eine Anfrage gestellt wird (status = 'active'), muss der Anfragende eine Pflegeeinrichtung sein." /> <source value="https://gematik.de/fhir/erp-servicerequest/StructureDefinition/gem-erp-sr-log-dispense-request" /> </constraint> <mapping> <identity value="Dispensieranforderung-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequest.requester.type" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request.involvierteParteien.Anfragender.Name"> <path value="gem-erp-sr-log-dispense-request.involvierteParteien.Anfragender.Name" /> <short value="Name des Anfragenden" /> <definition value="Name des Anfragenden" /> <min value="1" /> <max value="1" /> <type> <code value="string" /> </type> <mapping> <identity value="Dispensieranforderung-Fachliches-Mapping" /> <map value="ERPServiceRequestOrganization.name" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Mapping" /> <map value="Anfragendes PS" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request.involvierteParteien.Anfragender.Adresse"> <path value="gem-erp-sr-log-dispense-request.involvierteParteien.Anfragender.Adresse" /> <short value="Straßenadresse des Anfragenden" /> <definition value="Straßenadresse des Anfragenden" /> <min value="0" /> <max value="1" /> <type> <code value="Address" /> </type> <mapping> <identity value="Dispensieranforderung-Fachliches-Mapping" /> <map value="ERPServiceRequestOrganization.address" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Mapping" /> <map value="Anfragendes PS" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request.involvierteParteien.Anfragender.Telefon"> <path value="gem-erp-sr-log-dispense-request.involvierteParteien.Anfragender.Telefon" /> <short value="Telefonnummer des Anfragenden" /> <definition value="Telefonnummer des Anfragenden" /> <min value="1" /> <max value="1" /> <type> <code value="string" /> </type> <mapping> <identity value="Dispensieranforderung-Fachliches-Mapping" /> <map value="ERPServiceRequestOrganization.contact.telecom:tel.value" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Mapping" /> <map value="Anfragendes PS" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request.involvierteParteien.PatientenInformationen"> <path value="gem-erp-sr-log-dispense-request.involvierteParteien.PatientenInformationen" /> <short value="Patienteninformationen" /> <definition value="Angaben zum Patienten" /> <min value="1" /> <max value="1" /> <type> <code value="BackboneElement" /> </type> <mapping> <identity value="Dispensieranforderung-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequest.subject(ERPServiceRequestPatient)" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request.involvierteParteien.PatientenInformationen.PatientenIdentifierKVNR"> <path value="gem-erp-sr-log-dispense-request.involvierteParteien.PatientenInformationen.PatientenIdentifierKVNR" /> <short value="KVNR des Patienten" /> <definition value="KVNR des Patienten" /> <min value="1" /> <max value="1" /> <type> <code value="string" /> </type> <mapping> <identity value="Dispensieranforderung-Fachliches-Mapping" /> <map value="ERPServiceRequestPatient.identifier.value" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request.involvierteParteien.PatientenInformationen.PatientenName"> <path value="gem-erp-sr-log-dispense-request.involvierteParteien.PatientenInformationen.PatientenName" /> <short value="Name des Patienten" /> <definition value="Strukturierte Angabe des Namens des Patienten" /> <min value="1" /> <max value="1" /> <type> <code value="HumanName" /> </type> <mapping> <identity value="Dispensieranforderung-Fachliches-Mapping" /> <map value="ERPServiceRequestPatient.name" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request.involvierteParteien.PatientenInformationen.PatientenGeburtstag"> <path value="gem-erp-sr-log-dispense-request.involvierteParteien.PatientenInformationen.PatientenGeburtstag" /> <short value="Geburtstag des Patienten" /> <definition value="Angabe des Geburtstags mit Jahr, Monat und Tag" /> <min value="1" /> <max value="1" /> <type> <code value="date" /> </type> <mapping> <identity value="Dispensieranforderung-Fachliches-Mapping" /> <map value="ERPServiceRequestPatient.birthDate" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request.Freitext"> <path value="gem-erp-sr-log-dispense-request.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-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequest.note" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Mapping" /> <map value="Nutzer des PS" /> <comment value="Abfrage im Moment der Anforderung" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request.Belieferungsart"> <path value="gem-erp-sr-log-dispense-request.Belieferungsart" /> <short value="Belieferungsart" /> <definition value="Angabe der Belieferungsart" /> <min value="0" /> <max value="1" /> <type> <code value="Coding" /> </type> <constraint> <key value="log-dispense-request-3" /> <severity value="error" /> <human value="Wenn als Belieferungsart 'Lieferung an Alternative Addresse' angegeben wird, dann muss die Adresse auch angegeben werden." /> <source value="https://gematik.de/fhir/erp-servicerequest/StructureDefinition/gem-erp-sr-log-dispense-request" /> </constraint> <mapping> <identity value="Dispensieranforderung-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequest.code.coding[delivery-type]" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request.Belieferungsart.BelieferungsartCode"> <path value="gem-erp-sr-log-dispense-request.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-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequest.code.coding[delivery-type].code" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request.Belieferungsart.AlternativeAdresse"> <path value="gem-erp-sr-log-dispense-request.Belieferungsart.AlternativeAdresse" /> <short value="Alternative Adresse" /> <definition value="Alternative Adresse für die Lieferung" /> <min value="0" /> <max value="1" /> <type> <code value="Address" /> </type> <mapping> <identity value="Dispensieranforderung-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequest.extension[alternativeDeliveryAddress]" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request.Prioritaet"> <path value="gem-erp-sr-log-dispense-request.Prioritaet" /> <short value="Priorität" /> <definition value="Angabe der Priorität der Anforderung" /> <min value="0" /> <max value="1" /> <type> <code value="BackboneElement" /> </type> <mapping> <identity value="Dispensieranforderung-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequest.priority" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Mapping" /> <map value="Nutzer des PS" /> <comment value="Abfrage im Moment der Anforderung" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request.Prioritaet.PrioritaetCode"> <path value="gem-erp-sr-log-dispense-request.Prioritaet.PrioritaetCode" /> <short value="Priorität der Anforderung" /> <definition value="Folgende Prioritäten sind zulässig: Hoch, Normal" /> <min value="1" /> <max value="1" /> <type> <code value="Coding" /> </type> <mapping> <identity value="Dispensieranforderung-Fachliches-Mapping" /> <map value="ERPServiceRequestDispenseRequest.priority" /> </mapping> <mapping> <identity value="Quelle-Dispensieranforderung-Mapping" /> <map value="Nutzer des PS" /> <comment value="Abfrage im Moment der Anforderung" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request.Anhaenge"> <path value="gem-erp-sr-log-dispense-request.Anhaenge" /> <short value="Anhänge" /> <definition value="Anhänge zur Bestätigung. 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-Mapping" /> <map value="Nutzer oder PS" /> <comment value="Angabe im Moment der Bestätigung" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request.Anhaenge.Medikationsplan"> <path value="gem-erp-sr-log-dispense-request.Anhaenge.Medikationsplan" /> <short value="Medikationsplan" /> <definition value="Anhang des Medikationsplans" /> <min value="0" /> <max value="1" /> <type> <code value="Attachment" /> </type> <mapping> <identity value="Quelle-Dispensieranforderung-Mapping" /> <map value="Nutzer, PS oder Rezeptanforderung_Bestätigung" /> <comment value="Aktualisierung und ggf. automatische Generierung vom PS" /> </mapping> </element> <element id="gem-erp-sr-log-dispense-request.Anhaenge.weitereAnhaenge"> <path value="gem-erp-sr-log-dispense-request.Anhaenge.weitereAnhaenge" /> <short value="Weitere Anhänge" /> <definition value="Weitere Anhänge" /> <min value="0" /> <max value="*" /> <type> <code value="Attachment" /> </type> <mapping> <identity value="Quelle-Dispensieranforderung-Mapping" /> <map value="Nutzer oder PS" /> </mapping> </element> </differential> </StructureDefinition>
{ "resourceType": "StructureDefinition", "id": "gem-erp-sr-log-dispense-request", "url": "https://gematik.de/fhir/erp-servicerequest/StructureDefinition/gem-erp-sr-log-dispense-request", "version": "1.2", "name": "GEM_ERP_SR_LOG_DispenseRequest", "title": "Logical Model Dispenseieranforderung", "status": "draft", "experimental": false, "date": "2025-01-01", "publisher": "gematik GmbH", "description": "Fachliches Modell zur Beschreibung einer Dispenseieranforderung", "fhirVersion": "4.0.1", "mapping": [ { "identity": "Dispensieranforderung-Fachliches-Mapping", "name": "Dispensieranforderung Fachliches Mapping", "uri": "ERPServiceRequestDispenseRequest", "comment": "Mapping des Fachmodells aus GEM_ERP_SR_LOG_DispenseRequest auf das FHIR-Modell ERPServiceRequestDispenseRequest" }, { "identity": "Quelle-Dispensieranforderung-Mapping", "name": "Quelle der Dispensieranforderungsinformationen", "comment": "Beschreibt die Quelle der Dispensieranforderungsinformationen. Wird von der Pflegeeinrichtung zur Anforderung zur Abgabe von Arzneimitteln verwendet." } ], "kind": "logical", "abstract": false, "type": "https://gematik.de/fhir/erp-servicerequest/StructureDefinition/gem-erp-sr-log-dispense-request", "baseDefinition": "http://hl7.org/fhir/StructureDefinition/Element", "derivation": "specialization", "differential": { "element": [ { "id": "gem-erp-sr-log-dispense-request", "path": "gem-erp-sr-log-dispense-request", "short": "Logical Model Dispenseieranforderung", "definition": "Fachliches Modell zur Beschreibung einer Dispenseieranforderung", "constraint": [ { "key": "log-dispense-request-1", "severity": "error", "human": "Wenn eine Anfrage gestellt wird (status = 'active'), muss der Anfragende eine Pflegeeinrichtung sein.", "source": "https://gematik.de/fhir/erp-servicerequest/StructureDefinition/gem-erp-sr-log-dispense-request" }, { "key": "log-dispense-request-2", "severity": "error", "human": "Wenn eine Anfrage gestellt wird (status = 'active'), muss auch der E-Rezept-Token vorhanden sein.", "source": "https://gematik.de/fhir/erp-servicerequest/StructureDefinition/gem-erp-sr-log-dispense-request" }, { "key": "log-dispense-request-3", "severity": "error", "human": "Wenn als Belieferungsart 'Lieferung an Alternative Addresse' angegeben wird, dann muss die Adresse auch angegeben werden.", "source": "https://gematik.de/fhir/erp-servicerequest/StructureDefinition/gem-erp-sr-log-dispense-request" } ] }, { "id": "gem-erp-sr-log-dispense-request.MetaDaten", "path": "gem-erp-sr-log-dispense-request.MetaDaten", "short": "Metadaten im MessageHeader", "definition": "Metadaten im MessageHeader", "min": 1, "max": "1", "type": [ { "code": "BackboneElement" } ], "mapping": [ { "identity": "Dispensieranforderung-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequestHeader" }, { "identity": "Quelle-Dispensieranforderung-Mapping", "map": "Erstellendes PS", "comment": "Pflegesystem" } ] }, { "id": "gem-erp-sr-log-dispense-request.MetaDaten.Empfaenger", "path": "gem-erp-sr-log-dispense-request.MetaDaten.Empfaenger", "short": "Empfänger der Nachricht", "definition": "Empfänger der Nachricht", "min": 1, "max": "*", "type": [ { "code": "BackboneElement" } ], "mapping": [ { "identity": "Dispensieranforderung-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequestHeader.destination" }, { "identity": "Quelle-Dispensieranforderung-Mapping", "map": "Aus Kontaktmanagement oder VZD Suche" } ] }, { "id": "gem-erp-sr-log-dispense-request.MetaDaten.Empfaenger.KIMAdresse", "path": "gem-erp-sr-log-dispense-request.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-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequestHeader.destination.endpoint" }, { "identity": "Quelle-Dispensieranforderung-Mapping", "map": "Aus Kontaktmanagement oder VZD Suche" } ] }, { "id": "gem-erp-sr-log-dispense-request.MetaDaten.Empfaenger.TelematikID", "path": "gem-erp-sr-log-dispense-request.MetaDaten.Empfaenger.TelematikID", "short": "Telematik-ID des Absenders", "definition": "Telematik-ID des Absenders", "min": 0, "max": "1", "type": [ { "code": "url" } ], "mapping": [ { "identity": "Dispensieranforderung-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequestHeader.destination.receiver.identifier.value" }, { "identity": "Quelle-Dispensieranforderung-Mapping", "map": "Aus Kontaktmanagement oder VZD Suche" } ] }, { "id": "gem-erp-sr-log-dispense-request.MetaDaten.Absender", "path": "gem-erp-sr-log-dispense-request.MetaDaten.Absender", "short": "Absender der Nachricht", "definition": "Absender der Nachricht", "min": 1, "max": "1", "type": [ { "code": "BackboneElement" } ], "mapping": [ { "identity": "Dispensieranforderung-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequestHeader.sender" }, { "identity": "Quelle-Dispensieranforderung-Mapping", "map": "Erstellendes PS", "comment": "Pflegesystem" } ] }, { "id": "gem-erp-sr-log-dispense-request.MetaDaten.Absender.TelematikID", "path": "gem-erp-sr-log-dispense-request.MetaDaten.Absender.TelematikID", "short": "Telematik-ID des Absenders", "definition": "Telematik-ID des Absenders", "min": 0, "max": "1", "type": [ { "code": "url" } ], "mapping": [ { "identity": "Dispensieranforderung-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequestHeader.sender.identifier.value" }, { "identity": "Quelle-Dispensieranforderung-Mapping", "map": "Erstellendes PS, SMC-B Zertifikat" } ] }, { "id": "gem-erp-sr-log-dispense-request.MetaDaten.Absender.Name", "path": "gem-erp-sr-log-dispense-request.MetaDaten.Absender.Name", "short": "Name des Absenders", "definition": "Name des Absenders", "min": 1, "max": "1", "type": [ { "code": "string" } ], "mapping": [ { "identity": "Dispensieranforderung-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequestHeader.sender.display" }, { "identity": "Quelle-Dispensieranforderung-Mapping", "map": "Erstellendes PS" } ] }, { "id": "gem-erp-sr-log-dispense-request.MetaDaten.AbsendendesSystem", "path": "gem-erp-sr-log-dispense-request.MetaDaten.AbsendendesSystem", "short": "Absendendes System", "definition": "Absendendes System", "min": 1, "max": "1", "type": [ { "code": "BackboneElement" } ], "mapping": [ { "identity": "Dispensieranforderung-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequestHeader.source" }, { "identity": "Quelle-Dispensieranforderung-Mapping", "map": "Erstellendes PS", "comment": "Automatisiert durch Software gesetzt" } ] }, { "id": "gem-erp-sr-log-dispense-request.MetaDaten.AbsendendesSystem.Name", "path": "gem-erp-sr-log-dispense-request.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-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequestHeader.source.name" }, { "identity": "Quelle-Dispensieranforderung-Mapping", "map": "Erstellendes PS", "comment": "Automatisiert durch Software gesetzt" } ] }, { "id": "gem-erp-sr-log-dispense-request.MetaDaten.AbsendendesSystem.Software", "path": "gem-erp-sr-log-dispense-request.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-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequestHeader.source.software" }, { "identity": "Quelle-Dispensieranforderung-Mapping", "map": "Erstellendes PS", "comment": "Automatisiert durch Software gesetzt" } ] }, { "id": "gem-erp-sr-log-dispense-request.MetaDaten.AbsendendesSystem.Version", "path": "gem-erp-sr-log-dispense-request.MetaDaten.AbsendendesSystem.Version", "short": "Version des absendenden Systems", "definition": "Version des absendenden Systems", "min": 1, "max": "1", "type": [ { "code": "string" } ], "mapping": [ { "identity": "Dispensieranforderung-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequestHeader.source.version" }, { "identity": "Quelle-Dispensieranforderung-Mapping", "map": "Erstellendes PS", "comment": "Automatisiert durch Software gesetzt" } ] }, { "id": "gem-erp-sr-log-dispense-request.MetaDaten.AbsendendesSystem.EMailKontakt", "path": "gem-erp-sr-log-dispense-request.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-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequestHeader.source.contact.value" }, { "identity": "Quelle-Dispensieranforderung-Mapping", "map": "Erstellendes PS", "comment": "Automatisiert durch Software gesetzt" } ] }, { "id": "gem-erp-sr-log-dispense-request.MetaDaten.AbsendendesSystem.Website", "path": "gem-erp-sr-log-dispense-request.MetaDaten.AbsendendesSystem.Website", "short": "Website des absendenden Systems", "definition": "Website des absendenden Systems", "min": 1, "max": "1", "type": [ { "code": "url" } ], "mapping": [ { "identity": "Dispensieranforderung-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequestHeader.source.endpoint" }, { "identity": "Quelle-Dispensieranforderung-Mapping", "map": "Erstellendes PS", "comment": "Automatisiert durch Software gesetzt" } ] }, { "id": "gem-erp-sr-log-dispense-request.Status", "path": "gem-erp-sr-log-dispense-request.Status", "short": "Status", "definition": "Status der Anforderung. Wird genutzt, um den Bearbeitungsstand einer Anfrage zu verfolgen. Im Falle der initialen Dispensieranforderung wird eine Anfrage mit dem Status 'active' erstellt und geschickt und signalisiert somit eine neue Anfrage.", "min": 1, "max": "1", "type": [ { "code": "code" } ], "constraint": [ { "key": "log-dispense-request-1", "severity": "error", "human": "Wenn eine Anfrage gestellt wird (status = 'active'), muss der Anfragende eine Pflegeeinrichtung sein.", "source": "https://gematik.de/fhir/erp-servicerequest/StructureDefinition/gem-erp-sr-log-dispense-request" }, { "key": "log-dispense-request-2", "severity": "error", "human": "Wenn eine Anfrage gestellt wird (status = 'active'), muss auch der E-Rezept-Token vorhanden sein.", "source": "https://gematik.de/fhir/erp-servicerequest/StructureDefinition/gem-erp-sr-log-dispense-request" } ], "mapping": [ { "identity": "Dispensieranforderung-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequest.status" }, { "identity": "Quelle-Dispensieranforderung-Mapping", "map": "Anfragendes PS", "comment": "Setzt den Status der Anfrage auf 'active'" } ] }, { "id": "gem-erp-sr-log-dispense-request.VorgangsID", "path": "gem-erp-sr-log-dispense-request.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-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequest.identifier:requestId.value" }, { "identity": "Quelle-Dispensieranforderung-Mapping", "map": "Initiale Rezeptanforderung" } ] }, { "id": "gem-erp-sr-log-dispense-request.ERezeptToken", "path": "gem-erp-sr-log-dispense-request.ERezeptToken", "short": "E-Rezept-Token", "definition": "Token der für die Einlösung der Verordnung gebraucht wird.", "comment": "Angabe nach gemSpec_DM_eRp#A_19554.", "min": 1, "max": "1", "type": [ { "code": "string" } ], "constraint": [ { "key": "log-dispense-request-2", "severity": "error", "human": "Wenn eine Anfrage gestellt wird (status = 'active'), muss auch der E-Rezept-Token vorhanden sein.", "source": "https://gematik.de/fhir/erp-servicerequest/StructureDefinition/gem-erp-sr-log-dispense-request" } ], "mapping": [ { "identity": "Dispensieranforderung-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequest.extension:EPrescriptionToken" }, { "identity": "Quelle-Dispensieranforderung-Mapping", "map": "Rezeptanforderung_Bestätigung", "comment": "Wurde vom verordnenden Arzt bereitgestellt" } ] }, { "id": "gem-erp-sr-log-dispense-request.involvierteParteien", "path": "gem-erp-sr-log-dispense-request.involvierteParteien", "short": "Involvierte Parteien", "definition": "Angaben zu den involvierten Parteien", "min": 1, "max": "*", "type": [ { "code": "BackboneElement" } ], "mapping": [ { "identity": "Dispensieranforderung-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequest.requester" } ] }, { "id": "gem-erp-sr-log-dispense-request.involvierteParteien.Anfragender", "path": "gem-erp-sr-log-dispense-request.involvierteParteien.Anfragender", "short": "Anfragender", "definition": "Angaben zum anfragenden", "min": 1, "max": "1", "type": [ { "code": "BackboneElement" } ], "mapping": [ { "identity": "Dispensieranforderung-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequest.requester(ERPServiceRequestOrganization)" }, { "identity": "Quelle-Dispensieranforderung-Mapping", "map": "Anfragendes PS" } ] }, { "id": "gem-erp-sr-log-dispense-request.involvierteParteien.Anfragender.AnfragenderTyp", "path": "gem-erp-sr-log-dispense-request.involvierteParteien.Anfragender.AnfragenderTyp", "short": "Typ des Anfragenden", "definition": "Folgende Typen sind zulässig: Apotheke, Pflegeeinrichtung", "min": 1, "max": "1", "type": [ { "code": "Coding" } ], "constraint": [ { "key": "log-dispense-request-1", "severity": "error", "human": "Wenn eine Anfrage gestellt wird (status = 'active'), muss der Anfragende eine Pflegeeinrichtung sein.", "source": "https://gematik.de/fhir/erp-servicerequest/StructureDefinition/gem-erp-sr-log-dispense-request" } ], "mapping": [ { "identity": "Dispensieranforderung-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequest.requester.type" } ] }, { "id": "gem-erp-sr-log-dispense-request.involvierteParteien.Anfragender.Name", "path": "gem-erp-sr-log-dispense-request.involvierteParteien.Anfragender.Name", "short": "Name des Anfragenden", "definition": "Name des Anfragenden", "min": 1, "max": "1", "type": [ { "code": "string" } ], "mapping": [ { "identity": "Dispensieranforderung-Fachliches-Mapping", "map": "ERPServiceRequestOrganization.name" }, { "identity": "Quelle-Dispensieranforderung-Mapping", "map": "Anfragendes PS" } ] }, { "id": "gem-erp-sr-log-dispense-request.involvierteParteien.Anfragender.Adresse", "path": "gem-erp-sr-log-dispense-request.involvierteParteien.Anfragender.Adresse", "short": "Straßenadresse des Anfragenden", "definition": "Straßenadresse des Anfragenden", "min": 0, "max": "1", "type": [ { "code": "Address" } ], "mapping": [ { "identity": "Dispensieranforderung-Fachliches-Mapping", "map": "ERPServiceRequestOrganization.address" }, { "identity": "Quelle-Dispensieranforderung-Mapping", "map": "Anfragendes PS" } ] }, { "id": "gem-erp-sr-log-dispense-request.involvierteParteien.Anfragender.Telefon", "path": "gem-erp-sr-log-dispense-request.involvierteParteien.Anfragender.Telefon", "short": "Telefonnummer des Anfragenden", "definition": "Telefonnummer des Anfragenden", "min": 1, "max": "1", "type": [ { "code": "string" } ], "mapping": [ { "identity": "Dispensieranforderung-Fachliches-Mapping", "map": "ERPServiceRequestOrganization.contact.telecom:tel.value" }, { "identity": "Quelle-Dispensieranforderung-Mapping", "map": "Anfragendes PS" } ] }, { "id": "gem-erp-sr-log-dispense-request.involvierteParteien.PatientenInformationen", "path": "gem-erp-sr-log-dispense-request.involvierteParteien.PatientenInformationen", "short": "Patienteninformationen", "definition": "Angaben zum Patienten", "min": 1, "max": "1", "type": [ { "code": "BackboneElement" } ], "mapping": [ { "identity": "Dispensieranforderung-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequest.subject(ERPServiceRequestPatient)" } ] }, { "id": "gem-erp-sr-log-dispense-request.involvierteParteien.PatientenInformationen.PatientenIdentifierKVNR", "path": "gem-erp-sr-log-dispense-request.involvierteParteien.PatientenInformationen.PatientenIdentifierKVNR", "short": "KVNR des Patienten", "definition": "KVNR des Patienten", "min": 1, "max": "1", "type": [ { "code": "string" } ], "mapping": [ { "identity": "Dispensieranforderung-Fachliches-Mapping", "map": "ERPServiceRequestPatient.identifier.value" } ] }, { "id": "gem-erp-sr-log-dispense-request.involvierteParteien.PatientenInformationen.PatientenName", "path": "gem-erp-sr-log-dispense-request.involvierteParteien.PatientenInformationen.PatientenName", "short": "Name des Patienten", "definition": "Strukturierte Angabe des Namens des Patienten", "min": 1, "max": "1", "type": [ { "code": "HumanName" } ], "mapping": [ { "identity": "Dispensieranforderung-Fachliches-Mapping", "map": "ERPServiceRequestPatient.name" } ] }, { "id": "gem-erp-sr-log-dispense-request.involvierteParteien.PatientenInformationen.PatientenGeburtstag", "path": "gem-erp-sr-log-dispense-request.involvierteParteien.PatientenInformationen.PatientenGeburtstag", "short": "Geburtstag des Patienten", "definition": "Angabe des Geburtstags mit Jahr, Monat und Tag", "min": 1, "max": "1", "type": [ { "code": "date" } ], "mapping": [ { "identity": "Dispensieranforderung-Fachliches-Mapping", "map": "ERPServiceRequestPatient.birthDate" } ] }, { "id": "gem-erp-sr-log-dispense-request.Freitext", "path": "gem-erp-sr-log-dispense-request.Freitext", "short": "Freitext", "definition": "Individuelle Nachricht an den Empfänger", "min": 0, "max": "1", "type": [ { "code": "string" } ], "mapping": [ { "identity": "Dispensieranforderung-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequest.note" }, { "identity": "Quelle-Dispensieranforderung-Mapping", "map": "Nutzer des PS", "comment": "Abfrage im Moment der Anforderung" } ] }, { "id": "gem-erp-sr-log-dispense-request.Belieferungsart", "path": "gem-erp-sr-log-dispense-request.Belieferungsart", "short": "Belieferungsart", "definition": "Angabe der Belieferungsart", "min": 0, "max": "1", "type": [ { "code": "Coding" } ], "constraint": [ { "key": "log-dispense-request-3", "severity": "error", "human": "Wenn als Belieferungsart 'Lieferung an Alternative Addresse' angegeben wird, dann muss die Adresse auch angegeben werden.", "source": "https://gematik.de/fhir/erp-servicerequest/StructureDefinition/gem-erp-sr-log-dispense-request" } ], "mapping": [ { "identity": "Dispensieranforderung-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequest.code.coding[delivery-type]" } ] }, { "id": "gem-erp-sr-log-dispense-request.Belieferungsart.BelieferungsartCode", "path": "gem-erp-sr-log-dispense-request.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-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequest.code.coding[delivery-type].code" } ] }, { "id": "gem-erp-sr-log-dispense-request.Belieferungsart.AlternativeAdresse", "path": "gem-erp-sr-log-dispense-request.Belieferungsart.AlternativeAdresse", "short": "Alternative Adresse", "definition": "Alternative Adresse für die Lieferung", "min": 0, "max": "1", "type": [ { "code": "Address" } ], "mapping": [ { "identity": "Dispensieranforderung-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequest.extension[alternativeDeliveryAddress]" } ] }, { "id": "gem-erp-sr-log-dispense-request.Prioritaet", "path": "gem-erp-sr-log-dispense-request.Prioritaet", "short": "Priorität", "definition": "Angabe der Priorität der Anforderung", "min": 0, "max": "1", "type": [ { "code": "BackboneElement" } ], "mapping": [ { "identity": "Dispensieranforderung-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequest.priority" }, { "identity": "Quelle-Dispensieranforderung-Mapping", "map": "Nutzer des PS", "comment": "Abfrage im Moment der Anforderung" } ] }, { "id": "gem-erp-sr-log-dispense-request.Prioritaet.PrioritaetCode", "path": "gem-erp-sr-log-dispense-request.Prioritaet.PrioritaetCode", "short": "Priorität der Anforderung", "definition": "Folgende Prioritäten sind zulässig: Hoch, Normal", "min": 1, "max": "1", "type": [ { "code": "Coding" } ], "mapping": [ { "identity": "Dispensieranforderung-Fachliches-Mapping", "map": "ERPServiceRequestDispenseRequest.priority" }, { "identity": "Quelle-Dispensieranforderung-Mapping", "map": "Nutzer des PS", "comment": "Abfrage im Moment der Anforderung" } ] }, { "id": "gem-erp-sr-log-dispense-request.Anhaenge", "path": "gem-erp-sr-log-dispense-request.Anhaenge", "short": "Anhänge", "definition": "Anhänge zur Bestätigung. 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-Mapping", "map": "Nutzer oder PS", "comment": "Angabe im Moment der Bestätigung" } ] }, { "id": "gem-erp-sr-log-dispense-request.Anhaenge.Medikationsplan", "path": "gem-erp-sr-log-dispense-request.Anhaenge.Medikationsplan", "short": "Medikationsplan", "definition": "Anhang des Medikationsplans", "min": 0, "max": "1", "type": [ { "code": "Attachment" } ], "mapping": [ { "identity": "Quelle-Dispensieranforderung-Mapping", "map": "Nutzer, PS oder Rezeptanforderung_Bestätigung", "comment": "Aktualisierung und ggf. automatische Generierung vom PS" } ] }, { "id": "gem-erp-sr-log-dispense-request.Anhaenge.weitereAnhaenge", "path": "gem-erp-sr-log-dispense-request.Anhaenge.weitereAnhaenge", "short": "Weitere Anhänge", "definition": "Weitere Anhänge", "min": 0, "max": "*", "type": [ { "code": "Attachment" } ], "mapping": [ { "identity": "Quelle-Dispensieranforderung-Mapping", "map": "Nutzer oder PS" } ] } ] } }
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 | log-dispense-request-1 | error | Wenn eine Anfrage gestellt wird (status = 'active'), muss der Anfragende eine Pflegeeinrichtung sein. |
gem-erp-sr-log-dispense-request | log-dispense-request-2 | error | Wenn eine Anfrage gestellt wird (status = 'active'), muss auch der E-Rezept-Token vorhanden sein. |
gem-erp-sr-log-dispense-request | log-dispense-request-3 | error | Wenn als Belieferungsart 'Lieferung an Alternative Addresse' angegeben wird, dann muss die Adresse auch angegeben werden. |
gem-erp-sr-log-dispense-request.Status | log-dispense-request-1 | error | Wenn eine Anfrage gestellt wird (status = 'active'), muss der Anfragende eine Pflegeeinrichtung sein. |
gem-erp-sr-log-dispense-request.Status | log-dispense-request-2 | error | Wenn eine Anfrage gestellt wird (status = 'active'), muss auch der E-Rezept-Token vorhanden sein. |
gem-erp-sr-log-dispense-request.ERezeptToken | log-dispense-request-2 | error | Wenn eine Anfrage gestellt wird (status = 'active'), muss auch der E-Rezept-Token vorhanden sein. |
gem-erp-sr-log-dispense-request.involvierteParteien.Anfragender.AnfragenderTyp | log-dispense-request-1 | error | Wenn eine Anfrage gestellt wird (status = 'active'), muss der Anfragende eine Pflegeeinrichtung sein. |
gem-erp-sr-log-dispense-request.Belieferungsart | log-dispense-request-3 | error | Wenn als Belieferungsart 'Lieferung an Alternative Addresse' angegeben wird, dann muss die Adresse auch angegeben werden. |