Mapping für Dispensieranforderung Bestätigung
Diese Seite zeigt das Mapping der fachlichen Informationen aus dem Logisches Modell zur Dispensieranforderungs Bestätigung:
GEM_ERP_SR_LOG_DispenseRequest_Confirmation (gem-erp-sr-log-dispense-request-confirmation) | I | Element | Element idgem-erp-sr-log-dispense-request-confirmation Logical Model Dispenseieranforderung_Bestätigung DefinitionFachliches Modell zur Beschreibung einer Bestätigung einer Dispenseieranforderung
| |
id | 0..1 | string | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request-confirmation.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-confirmation.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-confirmation.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-confirmation.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-confirmation.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-confirmation.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-confirmation.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-confirmation.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-confirmation.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-confirmation.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-confirmation.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-confirmation.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-confirmation.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-confirmation.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-confirmation.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-confirmation.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-confirmation.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-confirmation.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-confirmation.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-confirmation.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-confirmation.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-confirmation.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-confirmation.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-confirmation.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-confirmation.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-confirmation.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-confirmation.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-confirmation.Status Status DefinitionStatus der Anforderung. Wird genutzt, um den Bearbeitungsstand einer Anfrage zu verfolgen. Im Falle der Dispensieranforderung wird eine erledigte Anfrage mit dem Status 'completed' geschickt und signalisiert somit eine neue Anfrage. Note that FHIR strings SHALL NOT exceed 1MB in size
|
VorgangsID | 1..1 | string | Element idgem-erp-sr-log-dispense-request-confirmation.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
| |
Freitext | 0..1 | string | Element idgem-erp-sr-log-dispense-request-confirmation.Freitext Freitext DefinitionIndividuelle Nachricht an den Empfänger Note that FHIR strings SHALL NOT exceed 1MB in size
| |
Anhaenge | I | 0..* | Attachment | Element idgem-erp-sr-log-dispense-request-confirmation.Anhaenge Anhänge DefinitionAnhänge zur Anforderung. Das können PDFs, Bilder oder andere Dokumente sein. Werden auf Ebene der KIM-Nachricht angehangen
|
Belieferungsart | 0..1 | Coding | Element idgem-erp-sr-log-dispense-request-confirmation.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-confirmation.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-confirmation.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-confirmation.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-confirmation.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-confirmation.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-confirmation.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-confirmation.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-confirmation.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.
| |
Medikation | I | 1..1 | BackboneElement | Element idgem-erp-sr-log-dispense-request-confirmation.Medikation Medikation DefinitionAngaben zur Medikation
|
id | 0..1 | string | There are no (further) constraints on this element Element idgem-erp-sr-log-dispense-request-confirmation.Medikation.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-confirmation.Medikation.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-confirmation.Medikation.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.
|
Abgabeinformationen | I | 1..1 | Reference(MedicationDispense) | Element idgem-erp-sr-log-dispense-request-confirmation.Medikation.Abgabeinformationen Medizinische Verordnungsinformationen DefinitionMedicationDispense und Medication Objekt aus den Abgabedaten. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
MetaDaten zur Nachricht
Im folgenden werden die Mappings der Metainformationen einer Dispensieranforderungs Bestätigung 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 |
Weitere Informationen
Im folgenden werden die Mappings weiterer Informationen einer Dispensieranforderungs Bestätigung zu den Profilen gelistet.
Fachliche Information | FHIR-Profil |
---|---|
MetaDaten | ERPServiceRequestDispenseRequestHeader |
Status | ERPServiceRequestDispenseRequest.status |
VorgangsID | ERPServiceRequestDispenseRequest.identifier:requestId.value |
Freitext | ERPServiceRequestDispenseRequest.note |
Belieferungsart | ERPServiceRequestDispenseRequest.code.coding[delivery-type] |
Belieferungsart.BelieferungsartCode | ERPServiceRequestDispenseRequest.code.coding[delivery-type].code |
Medikation | ERPServiceRequestDispenseRequest.supportingInfo:Abgabedaten |