Mapping für Dispensieranforderung
Diese Seite zeigt das Mapping der fachlichen Informationen aus dem Logisches Modell zur Dispensieranforderung:
GEM_ERP_SR_LOG_DispenseRequest (gem-erp-sr-log-dispense-request) | I | Element | Element idgem-erp-sr-log-dispense-request Logical Model Dispenseieranforderung DefinitionFachliches Modell zur Beschreibung einer Dispenseieranforderung
| |
id | 0..1 | string | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
MetaDaten | 1..1 | BackboneElement | Element idgem-erp-sr-log-dispense-request.MetaDaten Metadaten im MessageHeader DefinitionMetadaten im MessageHeader
| |
id | 0..1 | string | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.MetaDaten.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.MetaDaten.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.MetaDaten.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). 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. 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.
|
Empfaenger | 1..* | BackboneElement | Element idgem-erp-sr-log-dispense-request.MetaDaten.Empfaenger Empfänger der Nachricht DefinitionEmpfänger der Nachricht
| |
id | 0..1 | string | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.MetaDaten.Empfaenger.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.MetaDaten.Empfaenger.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.MetaDaten.Empfaenger.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). 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. 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.
|
KIMAdresse | 1..1 | url | Element idgem-erp-sr-log-dispense-request.MetaDaten.Empfaenger.KIMAdresse KIM-Adresse des Empfängers DefinitionKIM-Adresse des Empfängers see http://en.wikipedia.org/wiki/Uniform_resource_identifier
| |
TelematikID | 0..1 | url | Element idgem-erp-sr-log-dispense-request.MetaDaten.Empfaenger.TelematikID Telematik-ID des Absenders DefinitionTelematik-ID des Absenders see http://en.wikipedia.org/wiki/Uniform_resource_identifier
| |
Absender | 1..1 | BackboneElement | Element idgem-erp-sr-log-dispense-request.MetaDaten.Absender Absender der Nachricht DefinitionAbsender der Nachricht
| |
id | 0..1 | string | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.MetaDaten.Absender.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.MetaDaten.Absender.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.MetaDaten.Absender.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). 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. 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.
|
TelematikID | 0..1 | url | Element idgem-erp-sr-log-dispense-request.MetaDaten.Absender.TelematikID Telematik-ID des Absenders DefinitionTelematik-ID des Absenders see http://en.wikipedia.org/wiki/Uniform_resource_identifier
| |
Name | 1..1 | string | Element idgem-erp-sr-log-dispense-request.MetaDaten.Absender.Name Name des Absenders DefinitionName des Absenders Note that FHIR strings SHALL NOT exceed 1MB in size
| |
AbsendendesSystem | 1..1 | BackboneElement | Element idgem-erp-sr-log-dispense-request.MetaDaten.AbsendendesSystem Absendendes System DefinitionAbsendendes System
| |
id | 0..1 | string | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.MetaDaten.AbsendendesSystem.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.MetaDaten.AbsendendesSystem.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.MetaDaten.AbsendendesSystem.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). 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. 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.
|
Name | 1..1 | string | Element idgem-erp-sr-log-dispense-request.MetaDaten.AbsendendesSystem.Name Name des Herstellers des absendenden Systems DefinitionName des Herstellers des absendenden Systems Note that FHIR strings SHALL NOT exceed 1MB in size
| |
Software | 1..1 | string | Element idgem-erp-sr-log-dispense-request.MetaDaten.AbsendendesSystem.Software Name der Software des absendenden Systems DefinitionName der Software des absendenden Systems Note that FHIR strings SHALL NOT exceed 1MB in size
| |
Version | 1..1 | string | Element idgem-erp-sr-log-dispense-request.MetaDaten.AbsendendesSystem.Version Version des absendenden Systems DefinitionVersion des absendenden Systems Note that FHIR strings SHALL NOT exceed 1MB in size
| |
EMailKontakt | 1..1 | string | Element idgem-erp-sr-log-dispense-request.MetaDaten.AbsendendesSystem.EMailKontakt E-Mail-Kontakt des absendenden Systems DefinitionE-Mail-Kontakt des absendenden Systems Note that FHIR strings SHALL NOT exceed 1MB in size
| |
Website | 1..1 | url | Element idgem-erp-sr-log-dispense-request.MetaDaten.AbsendendesSystem.Website Website des absendenden Systems DefinitionWebsite des absendenden Systems see http://en.wikipedia.org/wiki/Uniform_resource_identifier
| |
Status | I | 1..1 | code | Element idgem-erp-sr-log-dispense-request.Status Status DefinitionStatus 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. Note that FHIR strings SHALL NOT exceed 1MB in size
|
VorgangsID | 1..1 | string | Element idgem-erp-sr-log-dispense-request.VorgangsID ID des Vorgangs DefinitionWird vom initialen Sender gesetzt und muss immer mitgeführt werden. Note that FHIR strings SHALL NOT exceed 1MB in size
| |
ERezeptToken | I | 1..1 | string | Element idgem-erp-sr-log-dispense-request.ERezeptToken E-Rezept-Token DefinitionToken der für die Einlösung der Verordnung gebraucht wird. Angabe nach gemSpec_DM_eRp#A_19554.
|
involvierteParteien | 1..* | BackboneElement | Element idgem-erp-sr-log-dispense-request.involvierteParteien Involvierte Parteien DefinitionAngaben zu den involvierten Parteien
| |
id | 0..1 | string | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.involvierteParteien.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.involvierteParteien.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.involvierteParteien.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). 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. 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.
|
Anfragender | 1..1 | BackboneElement | Element idgem-erp-sr-log-dispense-request.involvierteParteien.Anfragender Anfragender DefinitionAngaben zum anfragenden
| |
id | 0..1 | string | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.involvierteParteien.Anfragender.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.involvierteParteien.Anfragender.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.involvierteParteien.Anfragender.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). 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. 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.
|
AnfragenderTyp | I | 1..1 | Coding | Element idgem-erp-sr-log-dispense-request.involvierteParteien.Anfragender.AnfragenderTyp Typ des Anfragenden DefinitionFolgende Typen sind zulässig: Apotheke, Pflegeeinrichtung 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.
|
Name | 1..1 | string | Element idgem-erp-sr-log-dispense-request.involvierteParteien.Anfragender.Name Name des Anfragenden DefinitionName des Anfragenden Note that FHIR strings SHALL NOT exceed 1MB in size
| |
Adresse | 0..1 | Address | Element idgem-erp-sr-log-dispense-request.involvierteParteien.Anfragender.Adresse Straßenadresse des Anfragenden DefinitionStraßenadresse des Anfragenden 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).
| |
Telefon | 1..1 | string | Element idgem-erp-sr-log-dispense-request.involvierteParteien.Anfragender.Telefon Telefonnummer des Anfragenden DefinitionTelefonnummer des Anfragenden Note that FHIR strings SHALL NOT exceed 1MB in size
| |
PatientenInformationen | 1..1 | BackboneElement | Element idgem-erp-sr-log-dispense-request.involvierteParteien.PatientenInformationen Patienteninformationen DefinitionAngaben zum Patienten
| |
id | 0..1 | string | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.involvierteParteien.PatientenInformationen.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.involvierteParteien.PatientenInformationen.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.involvierteParteien.PatientenInformationen.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). 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. 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.
|
PatientenIdentifierKVNR | 1..1 | string | Element idgem-erp-sr-log-dispense-request.involvierteParteien.PatientenInformationen.PatientenIdentifierKVNR KVNR des Patienten DefinitionKVNR des Patienten Note that FHIR strings SHALL NOT exceed 1MB in size
| |
PatientenName | 1..1 | HumanName | Element idgem-erp-sr-log-dispense-request.involvierteParteien.PatientenInformationen.PatientenName Name des Patienten DefinitionStrukturierte Angabe des Namens des Patienten 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.
| |
PatientenGeburtstag | 1..1 | date | Element idgem-erp-sr-log-dispense-request.involvierteParteien.PatientenInformationen.PatientenGeburtstag Geburtstag des Patienten DefinitionAngabe des Geburtstags mit Jahr, Monat und Tag
| |
Freitext | 0..1 | string | Element idgem-erp-sr-log-dispense-request.Freitext Freitext DefinitionIndividuelle Nachricht an den Empfänger Note that FHIR strings SHALL NOT exceed 1MB in size
| |
Belieferungsart | I | 0..1 | Coding | Element idgem-erp-sr-log-dispense-request.Belieferungsart Belieferungsart DefinitionAngabe der Belieferungsart 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.Belieferungsart.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.Belieferungsart.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 0..1 | uri | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.Belieferungsart.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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.
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.Belieferungsart.version Version of the system - if relevant DefinitionThe 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. 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.
|
code | Σ | 0..1 | code | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.Belieferungsart.code Symbol in syntax defined by the system DefinitionA 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). Need to refer to a particular code in the system. Note that FHIR strings SHALL NOT exceed 1MB in size
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.Belieferungsart.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings SHALL NOT exceed 1MB in size
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.Belieferungsart.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). 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. 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.
|
BelieferungsartCode | 1..1 | Coding | Element idgem-erp-sr-log-dispense-request.Belieferungsart.BelieferungsartCode Belieferungsart-Code DefinitionFolgende Codes sind zulässig: Abholung durch Pflegedienst, Lieferung der Apotheke, Abholung durch Patienten 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.
| |
AlternativeAdresse | 0..1 | Address | Element idgem-erp-sr-log-dispense-request.Belieferungsart.AlternativeAdresse Alternative Adresse DefinitionAlternative Adresse für die Lieferung 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).
| |
Prioritaet | 0..1 | BackboneElement | Element idgem-erp-sr-log-dispense-request.Prioritaet Priorität DefinitionAngabe der Priorität der Anforderung
| |
id | 0..1 | string | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.Prioritaet.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.Prioritaet.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.Prioritaet.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). 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. 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.
|
PrioritaetCode | 1..1 | Coding | Element idgem-erp-sr-log-dispense-request.Prioritaet.PrioritaetCode Priorität der Anforderung DefinitionFolgende Prioritäten sind zulässig: Hoch, Normal 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.
| |
Anhaenge | I | 0..* | Attachment | Element idgem-erp-sr-log-dispense-request.Anhaenge Anhänge DefinitionAnhänge zur Bestätigung. Das können PDFs, Bilder oder andere Dokumente sein. Werden auf Ebene der KIM-Nachricht angehangen
|
id | 0..1 | string | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.Anhaenge.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.Anhaenge.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
contentType | Σ | 0..1 | codeBinding | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.Anhaenge.contentType Mime type of the content, with charset etc. DefinitionIdentifies 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. Processors of the data need to be able to know how to interpret the data. Note that FHIR strings SHALL NOT exceed 1MB in size The mime type of an attachment. Any valid mime type is allowed.
General text/plain; charset=UTF-8, image/png Mappings
|
language | Σ | 0..1 | codeBinding | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.Anhaenge.language Human language of the content (BCP-47) DefinitionThe human language of the content. The value can be any valid value according to BCP 47. Users need to be able to choose between the languages in a set of attachments. Note that FHIR strings SHALL NOT exceed 1MB in size A human language.
General en-AU Mappings
|
data | 0..1 | base64Binary | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.Anhaenge.data Data inline, base64ed DefinitionThe actual data of the attachment - a sequence of bytes, base64 encoded. The data needs to able to be transmitted inline. The base64-encoded data SHALL be expressed in the same character set as the base resource XML or JSON.
| |
url | Σ | 0..1 | url | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.Anhaenge.url Uri where the data can be found DefinitionA location where the data can be accessed. The data needs to be transmitted by reference. 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.
General http://www.acme.com/logo-small.png Mappings
|
size | Σ | 0..1 | unsignedInt | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.Anhaenge.size Number of bytes of content (if url provided) DefinitionThe number of bytes of data that make up this attachment (before base64 encoding, if that is done). Representing the size allows applications to determine whether they should fetch the content automatically in advance, or refuse to fetch it at all. 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.
|
hash | Σ | 0..1 | base64Binary | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.Anhaenge.hash Hash of the data (sha-1, base64ed) DefinitionThe calculated hash of the data using SHA-1. Represented using base64. 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). 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.
|
title | Σ | 0..1 | string | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.Anhaenge.title Label to display in place of the data DefinitionA label or set of text to display in place of the data. 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. Note that FHIR strings SHALL NOT exceed 1MB in size
General Official Corporate Logo Mappings
|
creation | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request.Anhaenge.creation Date attachment was first created DefinitionThe date that the attachment was first created. This is often tracked as an integrity issue for use of the attachment.
|
Medikationsplan | I | 0..1 | Attachment | Element idgem-erp-sr-log-dispense-request.Anhaenge.Medikationsplan Medikationsplan DefinitionAnhang des Medikationsplans 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".
|
weitereAnhaenge | I | 0..* | Attachment | Element idgem-erp-sr-log-dispense-request.Anhaenge.weitereAnhaenge Weitere Anhänge DefinitionWeitere Anhänge 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".
|
MetaDaten zur Nachricht
Im folgenden werden die Mappings der Metainformationen einer Dispensieranforderung zu den Profilen gelistet.
Fachliche Information | FHIR-Profil |
---|---|
MetaDaten | ERPServiceRequestDispenseRequestHeader |
Empfaenger | ERPServiceRequestDispenseRequestHeader.destination |
Empfaenger.KIMAdresse | ERPServiceRequestDispenseRequestHeader.destination.endpoint |
Empfaenger.TelematikID | ERPServiceRequestDispenseRequestHeader.destination.receiver.identifier.value |
Absender | ERPServiceRequestDispenseRequestHeader.sender |
Absender.TelematikID | ERPServiceRequestDispenseRequestHeader.sender.identifier.value |
Absender.Name | ERPServiceRequestDispenseRequestHeader.sender.display |
AbsendendesSystem | ERPServiceRequestDispenseRequestHeader.source |
AbsendendesSystem.Name | ERPServiceRequestDispenseRequestHeader.source.name |
AbsendendesSystem.Software | ERPServiceRequestDispenseRequestHeader.source.software |
AbsendendesSystem.Version | ERPServiceRequestDispenseRequestHeader.source.version |
AbsendendesSystem.EMailKontakt | ERPServiceRequestDispenseRequestHeader.source.contact.value |
AbsendendesSystem.Website | ERPServiceRequestDispenseRequestHeader.source.endpoint |
Involvierte Parteien
Im folgenden werden die Mappings der involvierten Parteien einer Dispensieranforderung zu den Profilen gelistet.
Fachliche Information | FHIR-Profil |
---|---|
involvierteParteien | ERPServiceRequestDispenseRequest.requester |
involvierteParteien.Anfragender | ERPServiceRequestDispenseRequest.requester(ERPServiceRequestOrganization) |
involvierteParteien.Anfragender.AnfragenderTyp | ERPServiceRequestDispenseRequest.requester.type |
involvierteParteien.Anfragender.Name | ERPServiceRequestOrganization.name |
involvierteParteien.Anfragender.Adresse | ERPServiceRequestOrganization.address |
involvierteParteien.Anfragender.Telefon | ERPServiceRequestOrganization.contact.telecom:tel.value |
involvierteParteien.PatientenInformationen | ERPServiceRequestDispenseRequest.subject(ERPServiceRequestPatient) |
involvierteParteien.PatientenInformationen.PatientenIdentifierKVNR | ERPServiceRequestPatient.identifier.value |
involvierteParteien.PatientenInformationen.PatientenName | ERPServiceRequestPatient.name |
involvierteParteien.PatientenInformationen.PatientenGeburtstag | ERPServiceRequestPatient.birthDate |
Weitere Informationen
Im folgenden werden die Mappings weiterer Informationen einer Dispensieranforderung zu den Profilen gelistet.
Fachliche Information | FHIR-Profil |
---|---|
MetaDaten | ERPServiceRequestDispenseRequestHeader |
Status | ERPServiceRequestDispenseRequest.status |
VorgangsID | ERPServiceRequestDispenseRequest.identifier:requestId.value |
ERezeptToken | ERPServiceRequestDispenseRequest.extension:EPrescriptionToken |
involvierteParteien | ERPServiceRequestDispenseRequest.requester |
Freitext | ERPServiceRequestDispenseRequest.note |
Belieferungsart | ERPServiceRequestDispenseRequest.code.coding[delivery-type] |
Belieferungsart.BelieferungsartCode | ERPServiceRequestDispenseRequest.code.coding[delivery-type].code |
Belieferungsart.AlternativeAdresse | ERPServiceRequestDispenseRequest.extension[alternativeDeliveryAddress] |
Prioritaet | ERPServiceRequestDispenseRequest.priority |
Prioritaet.PrioritaetCode | ERPServiceRequestDispenseRequest.priority |