ERP ServiceRequest DispenseRequest
Übersicht über das Profil
Name | Description | Canonical_URL | Status | Version | Basiert auf |
---|---|---|---|---|---|
ERPServiceRequestDispenseRequest | ServiceRequest that is used to supply a recipe | https://gematik.de/fhir/erp-servicerequest/StructureDefinition/erp-service-request-dispense-request | draft | 1.2 | http://hl7.org/fhir/StructureDefinition/ServiceRequest |
Über das Profil
Motivation
Als zentrales Element in einer Anfrage gelten in dieser Spezifikation ServiceRequests. Diese Bündeln die Informationen für eine konkrete Anfrage an einen anderen Leistungserbringer. Folgende Begriffe werden in diesem IG für diesen ServiceRequests genutzt:
- ServiceRequest meint den Request als Basisprofil von HL7
- ERPServiceRequestDispenseRequest meint konkret dieses Profil in diesem Projekt
- Dispensieranfrage ist der fachliche Begriff für dieses Profil
Der ERPServiceRequestDispenseRequest ist eine Anfrage zur Belieferung eines Präparates an eine ausliefernde Apotheke. Alle für die Apotheke relevanten Informationen sind in diesem ServiceRequest vorzuhalten, bzw. zu referenzieren.
Dieses Profil wird auch genutzt, um eine Pflegeeinrichtung über die Dispensierung einer Verordnung zu informieren.
Die Identifikation als ERPServiceRequestDispenseRequest (Belieferungsanfrage) wird über .code.coding.code = #dispense-request angegeben.
Inhalt des Profils
Folgende Ansichten existieren auf das Profil:
ERPServiceRequestDispenseRequest (ServiceRequest) | I | ServiceRequest | |
id | Σ | 0..1 | string |
meta | Σ | 0..1 | Meta |
implicitRules | Σ ?! | 0..1 | uri |
language | 0..1 | codeBinding | |
text | 0..1 | Narrative | |
contained | 0..* | Resource | |
extension | S I | 0..* | Extension |
EPrescriptionToken | S I | 0..1 | Extension(ERPServiceRequestEPrescriptionToken) |
alternativeDeliveryAddress | S I | 0..1 | Extension(AddressDeBasis) |
modifierExtension | ?! I | 0..* | Extension |
medicationChanged | S ?! I | 0..1 | Extension(boolean) |
identifier | S Σ | 1..* | Identifier |
requestId | Σ | 1..1 | ERPServiceRequestRequestIdentifier |
instantiatesCanonical | Σ | 0..* | canonical(ActivityDefinition | PlanDefinition) |
instantiatesUri | Σ | 0..* | uri |
basedOn | Σ I | 0..* | Reference(CarePlan | ServiceRequest | MedicationRequest) |
replaces | Σ I | 0..* | Reference(ServiceRequest) |
requisition | S Σ | 1..1 | ERPServiceRequestProcedureIdentifier |
status | S Σ ?! | 1..1 | codeBinding |
intent | Σ ?! | 1..1 | codeBindingFixed Value |
category | Σ | 0..* | CodeableConcept |
priority | S Σ | 0..1 | codeBinding |
doNotPerform | Σ ?! | 0..1 | boolean |
code | S Σ | 1..1 | CodeableConcept |
id | 0..1 | string | |
extension | I | 0..* | Extension |
coding | S Σ | 1..* | Coding |
request-type | S Σ | 1..1 | CodingBindingPattern |
id | 0..1 | string | |
extension | I | 0..* | Extension |
system | Σ | 1..1 | uriPattern |
version | Σ | 0..1 | string |
code | Σ | 1..1 | codePattern |
display | Σ | 0..1 | string |
userSelected | Σ | 0..1 | boolean |
delivery-type | S Σ | 0..1 | CodingBindingPattern |
id | 0..1 | string | |
extension | I | 0..* | Extension |
system | Σ | 1..1 | uriPattern |
version | Σ | 0..1 | string |
code | Σ | 1..1 | code |
display | Σ | 0..1 | string |
userSelected | Σ | 0..1 | boolean |
text | Σ | 0..1 | string |
orderDetail | Σ I | 0..* | CodeableConcept |
quantity[x] | Σ | 0..1 | |
quantityQuantity | Quantity | ||
quantityRatio | Ratio | ||
quantityRange | Range | ||
subject | S Σ I | 1..1 | Reference(ERPServiceRequestPatient) |
encounter | Σ I | 0..1 | Reference(Encounter) |
occurrence[x] | S Σ | 0..1 | |
occurrenceDateTime | dateTime | ||
asNeeded[x] | Σ | 0..1 | |
asNeededBoolean | boolean | ||
asNeededCodeableConcept | CodeableConcept | ||
authoredOn | S Σ | 1..1 | dateTime |
requester | S Σ I | 0..1 | Reference(ERPServiceRequestOrganization) |
performerType | Σ | 0..1 | CodeableConcept |
performer | Σ I | 0..* | Reference(Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService | Patient | Device | RelatedPerson) |
locationCode | Σ | 0..* | CodeableConcept |
locationReference | Σ I | 0..* | Reference(Location) |
reasonCode | Σ | 0..* | CodeableConcept |
reasonReference | Σ I | 0..* | Reference(Condition | Observation | DiagnosticReport | DocumentReference) |
insurance | I | 0..* | Reference(Coverage | ClaimResponse) |
supportingInfo | S I | 0..* | Reference(Resource) |
AbgabeDaten | S I | 0..1 | Reference(ERPServiceRequestMedicationDispense) |
id | 0..1 | string | |
extension | I | 0..* | Extension |
reference | Σ I | 0..1 | string |
type | Σ | 1..1 | uriBindingFixed Value |
identifier | Σ | 0..1 | Identifier |
display | Σ | 0..1 | string |
specimen | Σ I | 0..* | Reference(Specimen) |
bodySite | Σ | 0..* | CodeableConcept |
note | S | 0..* | Annotation |
id | 0..1 | string | |
extension | I | 0..* | Extension |
author[x] | Σ | 0..1 | |
authorString | string | ||
authorReference | Reference(Practitioner | Patient | RelatedPerson | Organization) | ||
time | S Σ | 1..1 | dateTime |
text | Σ | 1..1 | markdown |
patientInstruction | Σ | 0..1 | string |
relevantHistory | I | 0..* | Reference(Provenance) |
ServiceRequest | |
Definition | A record of a request for service such as diagnostic investigations, treatments, or operations to be performed. |
Cardinality | 0...* |
Alias | diagnostic request, referral, referral request, transfer of care request |
Invariants |
|
Mappings |
|
ServiceRequest.id | |
Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | The only time that a resource does not have an id is when it is being submitted to the server using a create operation. |
ServiceRequest.meta | |
Definition | The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource. |
Cardinality | 0...1 |
Type | Meta |
Summary | True |
Invariants |
|
Mappings |
|
ServiceRequest.implicitRules | |
Definition | A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. |
Cardinality | 0...1 |
Type | uri |
Modifier | True |
Summary | True |
Comments | Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc. |
Invariants |
|
Mappings |
|
ServiceRequest.language | |
Definition | The base language in which the resource is written. |
Cardinality | 0...1 |
Type | code |
Binding | A human language. |
Comments | Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). |
Invariants |
|
Mappings |
|
ServiceRequest.text | |
Definition | A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. |
Cardinality | 0...1 |
Type | Narrative |
Alias | narrative, html, xhtml, display |
Comments | Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later. |
Invariants |
|
Mappings |
|
ServiceRequest.contained | |
Definition | These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. |
Cardinality | 0...* |
Type | Resource |
Alias | inline resources, anonymous resources, contained resources |
Comments | This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels. |
Mappings |
|
ServiceRequest.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Cardinality | 0...* |
Type | Extension |
Must Support | True |
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 |
|
ServiceRequest.extension:EPrescriptionToken | |
Definition | Optional Extension Element - found in all resources. |
Cardinality | 0...1 |
Type | Extension(ERPServiceRequestEPrescriptionToken) |
Must Support | True |
Alias | extensions, user content |
Comments | The token is of the form '/Task/{PrescriptionID}/$accept?ac={AccessCode}. See gemSpec_DM_eRp'. |
Invariants |
|
Mappings |
|
ServiceRequest.extension:alternativeDeliveryAddress | |
Definition | If the ServiceRequest states that the delivery should be delivered to an alternative address, it must be stated here. |
Cardinality | 0...1 |
Type | Extension(AddressDeBasis) |
Must Support | True |
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. |
Invariants |
|
Mappings |
|
ServiceRequest.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it 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 is allowed to 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 |
Alias | extensions, user content |
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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
ServiceRequest.modifierExtension:medicationChanged | |
Definition | If the medication has been changed, the value is set to true. |
Cardinality | 0...1 |
Type | Extension(boolean) |
Must Support | True |
Modifier | True |
Alias | extensions, user content |
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 | If the medication has been changed, the receiving system must display the changed medication to the receiving user. |
Invariants |
|
Mappings |
|
ServiceRequest.identifier | |
Definition | Identifiers assigned to this order instance by the orderer and/or the receiver and/or order fulfiller. |
Cardinality | 1...* |
Type | Identifier |
Must Support | True |
Summary | True |
Comments | The identifier.type element is used to distinguish between the identifiers assigned by the orderer (known as the 'Placer' in HL7 v2) and the producer of the observations in response to the order (known as the 'Filler' in HL7 v2). For further discussion and examples see the resource notes section below. |
Slicing | Unordered, Open, by system(Pattern) |
Invariants |
|
Mappings |
|
ServiceRequest.identifier:requestId | |
Definition | An identifier - identifies some entity uniquely and unambiguously. Typically this is used for business identifiers. |
Cardinality | 1...1 |
Type | ERPServiceRequestRequestIdentifier |
Summary | True |
Comments | For referencing and assignment of ServiceRequest, e.g. if one ServiceRequest is to replace another, it is important to be able to make this assignment with the identifier. Can be mapped via a UUID, for example. |
Invariants |
|
Mappings |
|
ServiceRequest.instantiatesCanonical | |
Definition | The URL pointing to a FHIR-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this ServiceRequest. |
Cardinality | 0...* |
Type | canonical(ActivityDefinition | PlanDefinition) |
Summary | True |
Comments | Note: This is a business identifier, not a resource identifier (see discussion). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number. |
Invariants |
|
Mappings |
|
ServiceRequest.instantiatesUri | |
Definition | The URL pointing to an externally maintained protocol, guideline, orderset or other definition that is adhered to in whole or in part by this ServiceRequest. |
Cardinality | 0...* |
Type | uri |
Summary | True |
Comments | This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier. |
Invariants |
|
Mappings |
|
ServiceRequest.basedOn | |
Definition | Plan/proposal/order fulfilled by this request. |
Cardinality | 0...* |
Type | Reference(CarePlan | ServiceRequest | MedicationRequest) |
Summary | True |
Alias | fulfills |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
ServiceRequest.replaces | |
Definition | The request takes the place of the referenced completed or terminated request(s). |
Cardinality | 0...* |
Type | Reference(ServiceRequest) |
Summary | True |
Alias | supersedes, prior, renewed order |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
ServiceRequest.requisition | |
Definition | An identifier - identifies some entity uniquely and unambiguously. Typically this is used for business identifiers. |
Cardinality | 1...1 |
Type | ERPServiceRequestProcedureIdentifier |
Must Support | True |
Summary | True |
Alias | grouperId, groupIdentifier |
Requirements | Some business processes need to know if multiple items were ordered as part of the same "requisition" for billing or other purposes. |
Comments | Is to be understood as a case or process ID in order to be able to track which request the ServiceRequest belongs to. |
Invariants |
|
Mappings |
|
ServiceRequest.status | |
Definition | The status of the order. |
Cardinality | 1...1 |
Type | code |
Binding | The status of a service order. |
Must Support | True |
Modifier | True |
Summary | True |
Comments | If the status changes, this value is overwritten. |
Invariants |
|
Mappings |
|
ServiceRequest.intent | |
Definition | Whether the request is a proposal, plan, an original order or a reflex order. |
Cardinality | 1...1 |
Type | code |
Binding | The kind of service request. |
Modifier | True |
Summary | True |
Comments | This element is labeled as a modifier because the intent alters when and how the resource is actually applicable. |
Invariants |
|
Fixed Value | filler-order |
Mappings |
|
ServiceRequest.category | |
Definition | A code that classifies the service for searching, sorting and display purposes (e.g. "Surgical Procedure"). |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | Classification of the requested service. |
Summary | True |
Requirements | Used for filtering what service request are retrieved and displayed. |
Comments | There may be multiple axis of categorization depending on the context or use case for retrieving or displaying the resource. The level of granularity is defined by the category concepts in the value set. |
Invariants |
|
Mappings |
|
ServiceRequest.priority | |
Definition | The priority can be used to indicate the urgency of the request. |
Cardinality | 0...1 |
Type | code |
Binding | Identifies the level of importance to be assigned to actioning the request. |
Must Support | True |
Summary | True |
Comments | Allowed values: routine | urgent |
Invariants |
|
Mappings |
|
ServiceRequest.doNotPerform | |
Definition | Set this to true if the record is saying that the service/procedure should NOT be performed. |
Cardinality | 0...1 |
Type | boolean |
Modifier | True |
Summary | True |
Requirements | Used for do not ambulate, do not elevate head of bed, do not flush NG tube, do not take blood pressure on a certain arm, etc. |
Comments | In general, only the code and timeframe will be present, though occasional additional qualifiers such as body site or even performer could be included to narrow the scope of the prohibition. If the ServiceRequest.code and ServiceRequest.doNotPerform both contain negation, that will reinforce prohibition and should not have a double negative interpretation. |
Invariants |
|
Mappings |
|
ServiceRequest.code | |
Definition | A code that identifies a particular service (i.e., procedure, diagnostic investigation, or panel of investigations) that have been requested. |
Cardinality | 1...1 |
Type | CodeableConcept |
Binding | Codes for tests or services that can be carried out by a designated individual, organization or healthcare service. For laboratory, LOINC is (preferred)[http://build.fhir.org/terminologies.html#preferred] and a valueset using LOINC Order codes is available here. |
Must Support | True |
Summary | True |
Alias | service requested |
Comments | Many laboratory and radiology procedure codes embed the specimen/organ system in the test order name, for example, serum or serum/plasma glucose, or a chest x-ray. The specimen might not be recorded separately from the test code. |
Invariants |
|
Mappings |
|
ServiceRequest.code.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 |
|
ServiceRequest.code.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 |
|
ServiceRequest.code.coding | |
Definition | A reference to a code defined by a terminology system. |
Cardinality | 1...* |
Type | Coding |
Must Support | True |
Summary | True |
Requirements | Allows for alternative encodings within a code system, and translations to other code systems. |
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. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. |
Slicing | Unordered, Open, by $this(Pattern) |
Invariants |
|
Mappings |
|
ServiceRequest.code.coding:request-type | |
Definition | A reference to a code defined by a terminology system. |
Cardinality | 1...1 |
Type | Coding |
Binding | ServiceRequestTypeVS (required) |
Must Support | True |
Summary | True |
Requirements | Allows for alternative encodings within a code system, and translations to other code systems. |
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. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. |
Invariants |
|
Pattern | { "system": "https://gematik.de/fhir/erp-servicerequest/CodeSystem/service-request-type-cs", "code": "dispense-request" } |
Mappings |
|
ServiceRequest.code.coding:request-type.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 |
|
ServiceRequest.code.coding:request-type.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 |
|
ServiceRequest.code.coding:request-type.system | |
Definition | The identification of the code system that defines the meaning of the symbol in the code. |
Cardinality | 1...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 |
|
Pattern | https://gematik.de/fhir/erp-servicerequest/CodeSystem/service-request-type-cs |
Mappings |
|
ServiceRequest.code.coding:request-type.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 |
|
ServiceRequest.code.coding:request-type.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 | 1...1 |
Type | code |
Summary | True |
Requirements | Need to refer to a particular code in the system. |
Comments | #dispense-request serves as a service request for a pharmacy to deliver a prescription. |
Invariants |
|
Pattern | dispense-request |
Mappings |
|
ServiceRequest.code.coding:request-type.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 |
|
ServiceRequest.code.coding:request-type.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 |
|
ServiceRequest.code.coding:delivery-type | |
Definition | The delivery type can be used to indicate how the delivery should be made. The following options are available: pickup-by-healthcare-service, pickup-by-patient, delivery-to-healthcare-service, delivery-to-alternative-address. |
Cardinality | 0...1 |
Type | Coding |
Binding | DeliveryTypeVS (required) |
Must Support | True |
Summary | True |
Requirements | Allows for alternative encodings within a code system, and translations to other code systems. |
Comments | If the delivery type is delivery-to-alternative-address, the alternative address must be specified in location. |
Invariants |
|
Pattern | { "system": "https://gematik.de/fhir/erp-servicerequest/CodeSystem/delivery-type-cs" } |
Mappings |
|
ServiceRequest.code.coding:delivery-type.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 |
|
ServiceRequest.code.coding:delivery-type.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 |
|
ServiceRequest.code.coding:delivery-type.system | |
Definition | The identification of the code system that defines the meaning of the symbol in the code. |
Cardinality | 1...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 |
|
Pattern | https://gematik.de/fhir/erp-servicerequest/CodeSystem/delivery-type-cs |
Mappings |
|
ServiceRequest.code.coding:delivery-type.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 |
|
ServiceRequest.code.coding:delivery-type.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 | 1...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 |
|
ServiceRequest.code.coding:delivery-type.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 |
|
ServiceRequest.code.coding:delivery-type.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 |
|
ServiceRequest.code.text | |
Definition | A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Requirements | The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. |
Comments | Very often the text is the same as a displayName of one of the codings. |
Invariants |
|
Mappings |
|
ServiceRequest.orderDetail | |
Definition | Additional details and instructions about the how the services are to be delivered. For example, and order for a urinary catheter may have an order detail for an external or indwelling catheter, or an order for a bandage may require additional instructions specifying how the bandage should be applied. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | Codified order entry details which are based on order context. |
Summary | True |
Alias | detailed instructions |
Comments | For information from the medical record intended to support the delivery of the requested services, use the |
Invariants |
|
Mappings |
|
ServiceRequest.quantity[x] | |
Definition | An amount of service being requested which can be a quantity ( for example $1,500 home modification), a ratio ( for example, 20 half day visits per month), or a range (2.0 to 1.8 Gy per fraction). |
Cardinality | 0...1 |
Type | Quantity |
Summary | True |
Requirements | When ordering a service the number of service items may need to be specified separately from the the service item. |
Invariants |
|
Mappings |
|
ServiceRequest.subject | |
Definition | On whom or what the service is to be performed. This is usually a human patient, but can also be requested on animals, groups of humans or animals, devices such as dialysis machines, or even locations (typically for environmental scans). |
Cardinality | 1...1 |
Type | Reference(ERPServiceRequestPatient) |
Must Support | True |
Summary | True |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
ServiceRequest.encounter | |
Definition | An encounter that provides additional information about the healthcare context in which this request is made. |
Cardinality | 0...1 |
Type | Reference(Encounter) |
Summary | True |
Alias | context |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
ServiceRequest.occurrence[x] | |
Definition | The date/time at which the requested service should occur. |
Cardinality | 0...1 |
Type | dateTime |
Must Support | True |
Summary | True |
Alias | schedule |
Invariants |
|
Mappings |
|
ServiceRequest.asNeeded[x] | |
Definition | If a CodeableConcept is present, it indicates the pre-condition for performing the service. For example "pain", "on flare-up", etc. |
Cardinality | 0...1 |
Type | boolean |
Binding | A coded concept identifying the pre-condition that should hold prior to performing a procedure. For example "pain", "on flare-up", etc. |
Summary | True |
Invariants |
|
Mappings |
|
ServiceRequest.authoredOn | |
Definition | When the request transitioned to being actionable. |
Cardinality | 1...1 |
Type | dateTime |
Must Support | True |
Summary | True |
Alias | orderedOn |
Comments | Is initially created and then no longer changed. |
Invariants |
|
Mappings |
|
ServiceRequest.requester | |
Definition | The individual who initiated the request and has responsibility for its activation. |
Cardinality | 0...1 |
Type | Reference(ERPServiceRequestOrganization) |
Must Support | True |
Summary | True |
Alias | author, orderer |
Comments | The KIM address is already stored in the message header. |
Invariants |
|
Mappings |
|
ServiceRequest.performerType | |
Definition | Desired type of performer for doing the requested service. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc. |
Summary | True |
Alias | specialty |
Comments | This is a role, not a participation type. In other words, does not describe the task but describes the capacity. For example, “compounding pharmacy”, “psychiatrist” or “internal referral”. |
Invariants |
|
Mappings |
|
ServiceRequest.performer | |
Definition | The desired performer for doing the requested service. For example, the surgeon, dermatopathologist, endoscopist, etc. |
Cardinality | 0...* |
Type | Reference(Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService | Patient | Device | RelatedPerson) |
Summary | True |
Alias | request recipient |
Comments | If multiple performers are present, it is interpreted as a list of alternative performers without any preference regardless of order. If order of preference is needed use the request-performerOrder extension. Use CareTeam to represent a group of performers (for example, Practitioner A and Practitioner B). |
Invariants |
|
Mappings |
|
ServiceRequest.locationCode | |
Definition | The preferred location(s) where the procedure should actually happen in coded or free text form. E.g. at home or nursing day care center. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | A location type where services are delivered. |
Summary | True |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
ServiceRequest.locationReference | |
Definition | A reference to the the preferred location(s) where the procedure should actually happen. E.g. at home or nursing day care center. |
Cardinality | 0...* |
Type | Reference(Location) |
Summary | True |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
ServiceRequest.reasonCode | |
Definition | An explanation or justification for why this service is being requested in coded or textual form. This is often for billing purposes. May relate to the resources referred to in `supportingInfo`. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | Diagnosis or problem codes justifying the reason for requesting the service investigation. |
Summary | True |
Comments | This element represents why the referral is being made and may be used to decide how the service will be performed, or even if it will be performed at all. Use |
Invariants |
|
Mappings |
|
ServiceRequest.reasonReference | |
Definition | Indicates another resource that provides a justification for why this service is being requested. May relate to the resources referred to in `supportingInfo`. |
Cardinality | 0...* |
Type | Reference(Condition | Observation | DiagnosticReport | DocumentReference) |
Summary | True |
Comments | This element represents why the referral is being made and may be used to decide how the service will be performed, or even if it will be performed at all. To be as specific as possible, a reference to Observation or Condition should be used if available. Otherwise when referencing DiagnosticReport it should contain a finding in |
Invariants |
|
Mappings |
|
ServiceRequest.insurance | |
Definition | Insurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be needed for delivering the requested service. |
Cardinality | 0...* |
Type | Reference(Coverage | ClaimResponse) |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
ServiceRequest.supportingInfo | |
Definition | Additional clinical information about the patient or specimen that may influence the services or their interpretations. This information includes diagnosis, clinical findings and other observations. In laboratory ordering these are typically referred to as "ask at order entry questions (AOEs)". This includes observations explicitly requested by the producer (filler) to provide context or supporting information needed to complete the order. For example, reporting the amount of inspired oxygen for blood gas measurements. |
Cardinality | 0...* |
Type | Reference(Resource) |
Must Support | True |
Alias | Ask at order entry question, AOE |
Comments | To represent information about how the services are to be delivered use the |
Slicing | Unordered, Open, by type(Pattern) |
Invariants |
|
Mappings |
|
ServiceRequest.supportingInfo:AbgabeDaten | |
Definition | Additional clinical information about the patient or specimen that may influence the services or their interpretations. This information includes diagnosis, clinical findings and other observations. In laboratory ordering these are typically referred to as "ask at order entry questions (AOEs)". This includes observations explicitly requested by the producer (filler) to provide context or supporting information needed to complete the order. For example, reporting the amount of inspired oxygen for blood gas measurements. |
Cardinality | 0...1 |
Type | Reference(ERPServiceRequestMedicationDispense) |
Must Support | True |
Alias | Ask at order entry question, AOE |
Comments | To represent information about how the services are to be delivered use the |
Invariants |
|
Mappings |
|
ServiceRequest.supportingInfo:AbgabeDaten.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 |
|
ServiceRequest.supportingInfo:AbgabeDaten.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 |
|
ServiceRequest.supportingInfo:AbgabeDaten.reference | |
Definition | A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server. |
Invariants |
|
Mappings |
|
ServiceRequest.supportingInfo:AbgabeDaten.type | |
Definition | The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). |
Cardinality | 1...1 |
Type | uri |
Binding | Aa resource (or, for logical models, the URI of the logical model). |
Summary | True |
Comments | This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. |
Invariants |
|
Fixed Value | MedicationDispense |
Mappings |
|
ServiceRequest.supportingInfo:AbgabeDaten.identifier | |
Definition | An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. |
Cardinality | 0...1 |
Type | Identifier |
Summary | True |
Comments | When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). |
Invariants |
|
Mappings |
|
ServiceRequest.supportingInfo:AbgabeDaten.display | |
Definition | Plain text narrative that identifies the resource in addition to the resource reference. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. |
Invariants |
|
Mappings |
|
ServiceRequest.specimen | |
Definition | One or more specimens that the laboratory procedure will use. |
Cardinality | 0...* |
Type | Reference(Specimen) |
Summary | True |
Comments | Many diagnostic procedures need a specimen, but the request itself is not actually about the specimen. This element is for when the diagnostic is requested on already existing specimens and the request points to the specimen it applies to. Conversely, if the request is entered first with an unknown specimen, then the Specimen resource points to the ServiceRequest. |
Invariants |
|
Mappings |
|
ServiceRequest.bodySite | |
Definition | Anatomic location where the procedure should be performed. This is the target site. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | Codes describing anatomical locations. May include laterality. |
Summary | True |
Alias | location |
Requirements | Knowing where the procedure is performed is important for tracking if multiple sites are possible. |
Comments | Only used if not implicit in the code found in ServiceRequest.code. If the use case requires BodySite to be handled as a separate resource instead of an inline coded element (e.g. to identify and track separately) then use the standard extension procedure-targetBodyStructure. |
Invariants |
|
Mappings |
|
ServiceRequest.note | |
Definition | Any other notes and comments made about the service request. For example, internal billing notes. |
Cardinality | 0...* |
Type | Annotation |
Must Support | True |
Comments | Any use cases that are not specified can be placed here in free text. |
Invariants |
|
Mappings |
|
ServiceRequest.note.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 |
|
ServiceRequest.note.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 |
|
ServiceRequest.note.author[x] | |
Definition | The individual responsible for making the annotation. |
Cardinality | 0...1 |
Type | Reference(Practitioner | Patient | RelatedPerson | Organization) |
Summary | True |
Comments | Organization is used when there's no need for specific attribution as to who made the comment. |
Invariants |
|
Mappings |
|
ServiceRequest.note.time | |
Definition | Indicates when this particular annotation was made. |
Cardinality | 1...1 |
Type | dateTime |
Must Support | True |
Summary | True |
Comments | This is used in order to sort the Annotations |
Invariants |
|
Mappings |
|
ServiceRequest.note.text | |
Definition | The text of the annotation in markdown format. |
Cardinality | 1...1 |
Type | markdown |
Summary | True |
Comments | Systems are not required to have markdown support, so the text should be readable without markdown processing. The markdown syntax is GFM - see https://github.github.com/gfm/ |
Invariants |
|
Mappings |
|
ServiceRequest.patientInstruction | |
Definition | Instructions in terms that are understood by the patient or consumer. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
ServiceRequest.relevantHistory | |
Definition | Key events in the history of the request. |
Cardinality | 0...* |
Type | Reference(Provenance) |
Comments | This might not include provenances for all versions of the request – only those deemed “relevant” or important. This SHALL NOT include the Provenance associated with this current version of the resource. (If that provenance is deemed to be a “relevant” change, it will need to be added as part of a later update. Until then, it can be queried directly as the Provenance that points to this version using _revinclude All Provenances should have some historical version of this Request as their subject. |
Invariants |
|
Mappings |
|
<StructureDefinition xmlns="http://hl7.org/fhir"> <id value="erp-service-request-dispense-request" /> <url value="https://gematik.de/fhir/erp-servicerequest/StructureDefinition/erp-service-request-dispense-request" /> <version value="1.2" /> <name value="ERPServiceRequestDispenseRequest" /> <title value="ERP Service Request Dispense Request" /> <status value="draft" /> <experimental value="false" /> <date value="2025-01-01" /> <publisher value="gematik GmbH" /> <description value="ServiceRequest that is used to supply a recipe" /> <fhirVersion value="4.0.1" /> <kind value="resource" /> <abstract value="false" /> <type value="ServiceRequest" /> <baseDefinition value="http://hl7.org/fhir/StructureDefinition/ServiceRequest" /> <derivation value="constraint" /> <differential> <element id="ServiceRequest"> <path value="ServiceRequest" /> <constraint> <key value="servicerequest-dispense-request-1" /> <severity value="error" /> <human value="If the status is active, then requester must be present." /> <expression value="status = 'active' implies requester.exists()" /> <source value="https://gematik.de/fhir/erp-servicerequest/StructureDefinition/erp-service-request-dispense-request" /> </constraint> <constraint> <key value="servicerequest-dispense-request-2" /> <severity value="error" /> <human value="If the status is active, then the e-prescription-token must be present." /> <expression value="status = 'active' implies extension.where(url = 'https://gematik.de/fhir/erp-servicerequest/StructureDefinition/eprescription-token-ex').exists()" /> <source value="https://gematik.de/fhir/erp-servicerequest/StructureDefinition/erp-service-request-dispense-request" /> </constraint> <constraint> <key value="servicerequest-dispense-request-3" /> <severity value="error" /> <human value="If the status is completed, then the dispense data must be present." /> <expression value="status = 'completed' implies supportingInfo.where(type='MedicationDispense').exists()" /> <source value="https://gematik.de/fhir/erp-servicerequest/StructureDefinition/erp-service-request-dispense-request" /> </constraint> <constraint> <key value="servicerequest-dispense-request-4" /> <severity value="error" /> <human value="If the the code for the delivery type is alternatve-address, then the address must be stated." /> <expression value="(status = 'active' and code.coding.where(system='https://gematik.de/fhir/erp-servicerequest/CodeSystem/delivery-type-cs').exists() and code.coding.where(system='https://gematik.de/fhir/erp-servicerequest/CodeSystem/delivery-type-cs').code = 'delivery-to-alternative-address') implies (extension.where(url = 'https://gematik.de/fhir/erp-servicerequest/StructureDefinition/alternative-delivery-address-ex').exists() and extension.where(url = 'https://gematik.de/fhir/erp-servicerequest/StructureDefinition/alternative-delivery-address-ex').value.empty().not())" /> <source value="https://gematik.de/fhir/erp-servicerequest/StructureDefinition/erp-service-request-dispense-request" /> </constraint> </element> <element id="ServiceRequest.extension"> <path value="ServiceRequest.extension" /> <mustSupport value="true" /> </element> <element id="ServiceRequest.extension:EPrescriptionToken"> <path value="ServiceRequest.extension" /> <sliceName value="EPrescriptionToken" /> <short value="The e-prescription token for delivery to the pharmacy can be provided here." /> <comment value="The token is of the form '/Task/{PrescriptionID}/$accept?ac={AccessCode}. See [gemSpec_DM_eRp](https://fachportal.gematik.de/fachportal-import/files/gemSpec_DM_eRp_V1.5.0.pdf)'." /> <min value="0" /> <max value="1" /> <type> <code value="Extension" /> <profile value="https://gematik.de/fhir/erp-servicerequest/StructureDefinition/eprescription-token-ex" /> </type> <mustSupport value="true" /> </element> <element id="ServiceRequest.extension:alternativeDeliveryAddress"> <path value="ServiceRequest.extension" /> <sliceName value="alternativeDeliveryAddress" /> <short value="Alternative delivery address." /> <definition value="If the ServiceRequest states that the delivery should be delivered to an alternative address, it must be stated here." /> <min value="0" /> <max value="1" /> <type> <code value="Extension" /> <profile value="https://gematik.de/fhir/erp-servicerequest/StructureDefinition/alternative-delivery-address-ex" /> </type> <mustSupport value="true" /> </element> <element id="ServiceRequest.modifierExtension:medicationChanged"> <path value="ServiceRequest.modifierExtension" /> <sliceName value="medicationChanged" /> <short value="Indicates whether the medication has been changed by the pharmacy." /> <definition value="If the medication has been changed, the value is set to true." /> <comment value="If the medication has been changed, the receiving system must display the changed medication to the receiving user." /> <min value="0" /> <max value="1" /> <type> <code value="Extension" /> <profile value="https://gematik.de/fhir/erp-servicerequest/StructureDefinition/changed-medication-ex" /> </type> <mustSupport value="true" /> <isModifierReason value="If the medication has been changed, the receiving system must display the changed medication to the receiving user." /> </element> <element id="ServiceRequest.identifier"> <path value="ServiceRequest.identifier" /> <slicing> <discriminator> <type value="pattern" /> <path value="system" /> </discriminator> <description value="Defines identifiers to be used in a process" /> <rules value="open" /> </slicing> <min value="1" /> <mustSupport value="true" /> </element> <element id="ServiceRequest.identifier:requestId"> <path value="ServiceRequest.identifier" /> <sliceName value="requestId" /> <short value="Identifier that uniquely references a ServiceRequest." /> <comment value="For referencing and assignment of ServiceRequest, e.g. if one ServiceRequest is to replace another, it is important to be able to make this assignment with the identifier. Can be mapped via a UUID, for example." /> <min value="1" /> <max value="1" /> <type> <code value="Identifier" /> <profile value="https://gematik.de/fhir/erp-servicerequest/StructureDefinition/erp-service-request-request-identifier" /> </type> </element> <element id="ServiceRequest.requisition"> <path value="ServiceRequest.requisition" /> <short value="Identifier of the process. All ServiceRequests within a process receive the same ID." /> <comment value="Is to be understood as a case or process ID in order to be able to track which request the ServiceRequest belongs to." /> <min value="1" /> <type> <code value="Identifier" /> <profile value="https://gematik.de/fhir/erp-servicerequest/StructureDefinition/erp-service-request-procedure-identifier" /> </type> <mustSupport value="true" /> </element> <element id="ServiceRequest.status"> <path value="ServiceRequest.status" /> <short value="Indicates the processing status of a service request." /> <comment value="If the status changes, this value is overwritten." /> <mustSupport value="true" /> <binding> <strength value="required" /> <valueSet value="https://gematik.de/fhir/erp-servicerequest/ValueSet/service-request-status-vs" /> </binding> </element> <element id="ServiceRequest.intent"> <path value="ServiceRequest.intent" /> <fixedCode value="filler-order" /> </element> <element id="ServiceRequest.priority"> <path value="ServiceRequest.priority" /> <short value="Indicates the urgency of the request." /> <definition value="The priority can be used to indicate the urgency of the request." /> <comment value="Allowed values: routine | urgent" /> <mustSupport value="true" /> <binding> <strength value="required" /> <valueSet value="https://gematik.de/fhir/erp-servicerequest/ValueSet/service-request-priority-vs" /> </binding> </element> <element id="ServiceRequest.code"> <path value="ServiceRequest.code" /> <short value="Indicates the type of service request." /> <min value="1" /> <mustSupport value="true" /> </element> <element id="ServiceRequest.code.coding"> <path value="ServiceRequest.code.coding" /> <slicing> <discriminator> <type value="pattern" /> <path value="$this" /> </discriminator> <description value="Differentiates between the service request type and additional information." /> <ordered value="false" /> <rules value="open" /> </slicing> <min value="1" /> <mustSupport value="true" /> </element> <element id="ServiceRequest.code.coding:request-type"> <path value="ServiceRequest.code.coding" /> <sliceName value="request-type" /> <short value="Indicates the type of service request." /> <min value="1" /> <max value="1" /> <patternCoding> <system value="https://gematik.de/fhir/erp-servicerequest/CodeSystem/service-request-type-cs" /> <code value="dispense-request" /> </patternCoding> <mustSupport value="true" /> <binding> <strength value="required" /> <valueSet value="https://gematik.de/fhir/erp-servicerequest/ValueSet/service-request-type-vs" /> </binding> </element> <element id="ServiceRequest.code.coding:request-type.system"> <path value="ServiceRequest.code.coding.system" /> <min value="1" /> </element> <element id="ServiceRequest.code.coding:request-type.code"> <path value="ServiceRequest.code.coding.code" /> <comment value="#dispense-request serves as a service request for a pharmacy to deliver a prescription." /> <min value="1" /> </element> <element id="ServiceRequest.code.coding:delivery-type"> <path value="ServiceRequest.code.coding" /> <sliceName value="delivery-type" /> <short value="Indicates how the delivery should be made." /> <definition value="The delivery type can be used to indicate how the delivery should be made. The following options are available: pickup-by-healthcare-service, pickup-by-patient, delivery-to-healthcare-service, delivery-to-alternative-address." /> <comment value="If the delivery type is delivery-to-alternative-address, the alternative address must be specified in location." /> <min value="0" /> <max value="1" /> <patternCoding> <system value="https://gematik.de/fhir/erp-servicerequest/CodeSystem/delivery-type-cs" /> </patternCoding> <mustSupport value="true" /> <binding> <strength value="required" /> <valueSet value="https://gematik.de/fhir/erp-servicerequest/ValueSet/delivery-type-vs" /> </binding> </element> <element id="ServiceRequest.code.coding:delivery-type.system"> <path value="ServiceRequest.code.coding.system" /> <min value="1" /> </element> <element id="ServiceRequest.code.coding:delivery-type.code"> <path value="ServiceRequest.code.coding.code" /> <min value="1" /> </element> <element id="ServiceRequest.subject"> <path value="ServiceRequest.subject" /> <short value="Patient for whom a dispense is requested on behalf of the patient." /> <type> <code value="Reference" /> <targetProfile value="https://gematik.de/fhir/erp-servicerequest/StructureDefinition/erp-service-request-patient" /> </type> <mustSupport value="true" /> </element> <element id="ServiceRequest.occurrence[x]"> <path value="ServiceRequest.occurrence[x]" /> <short value="Indicates the date when the medication should be delivered." /> <type> <code value="dateTime" /> </type> <mustSupport value="true" /> </element> <element id="ServiceRequest.authoredOn"> <path value="ServiceRequest.authoredOn" /> <short value="Creation date of the request." /> <comment value="Is initially created and then no longer changed." /> <min value="1" /> <mustSupport value="true" /> </element> <element id="ServiceRequest.requester"> <path value="ServiceRequest.requester" /> <short value="Inquiring facility or practitioner." /> <comment value="The KIM address is already stored in the message header." /> <type> <code value="Reference" /> <targetProfile value="https://gematik.de/fhir/erp-servicerequest/StructureDefinition/erp-service-request-organization" /> </type> <mustSupport value="true" /> </element> <element id="ServiceRequest.supportingInfo"> <path value="ServiceRequest.supportingInfo" /> <slicing> <discriminator> <type value="pattern" /> <path value="type" /> </discriminator> <description value="Supporting information about dispense" /> <rules value="open" /> </slicing> <mustSupport value="true" /> </element> <element id="ServiceRequest.supportingInfo:AbgabeDaten"> <path value="ServiceRequest.supportingInfo" /> <sliceName value="AbgabeDaten" /> <min value="0" /> <max value="1" /> <type> <code value="Reference" /> <targetProfile value="https://gematik.de/fhir/erp-servicerequest/StructureDefinition/erp-service-request-medication-dispense" /> </type> <mustSupport value="true" /> </element> <element id="ServiceRequest.supportingInfo:AbgabeDaten.type"> <path value="ServiceRequest.supportingInfo.type" /> <short value="Dispense data that is also sent to the e-prescription server." /> <min value="1" /> <fixedUri value="MedicationDispense" /> </element> <element id="ServiceRequest.note"> <path value="ServiceRequest.note" /> <short value="Further information on the dispense request." /> <comment value="Any use cases that are not specified can be placed here in free text." /> <mustSupport value="true" /> </element> <element id="ServiceRequest.note.time"> <path value="ServiceRequest.note.time" /> <comment value="This is used in order to sort the Annotations" /> <min value="1" /> <mustSupport value="true" /> </element> </differential> </StructureDefinition>
{ "resourceType": "StructureDefinition", "id": "erp-service-request-dispense-request", "url": "https://gematik.de/fhir/erp-servicerequest/StructureDefinition/erp-service-request-dispense-request", "version": "1.2", "name": "ERPServiceRequestDispenseRequest", "title": "ERP Service Request Dispense Request", "status": "draft", "experimental": false, "date": "2025-01-01", "publisher": "gematik GmbH", "description": "ServiceRequest that is used to supply a recipe", "fhirVersion": "4.0.1", "kind": "resource", "abstract": false, "type": "ServiceRequest", "baseDefinition": "http://hl7.org/fhir/StructureDefinition/ServiceRequest", "derivation": "constraint", "differential": { "element": [ { "id": "ServiceRequest", "path": "ServiceRequest", "constraint": [ { "key": "servicerequest-dispense-request-1", "severity": "error", "human": "If the status is active, then requester must be present.", "expression": "status = 'active' implies requester.exists()", "source": "https://gematik.de/fhir/erp-servicerequest/StructureDefinition/erp-service-request-dispense-request" }, { "key": "servicerequest-dispense-request-2", "severity": "error", "human": "If the status is active, then the e-prescription-token must be present.", "expression": "status = 'active' implies extension.where(url = 'https://gematik.de/fhir/erp-servicerequest/StructureDefinition/eprescription-token-ex').exists()", "source": "https://gematik.de/fhir/erp-servicerequest/StructureDefinition/erp-service-request-dispense-request" }, { "key": "servicerequest-dispense-request-3", "severity": "error", "human": "If the status is completed, then the dispense data must be present.", "expression": "status = 'completed' implies supportingInfo.where(type='MedicationDispense').exists()", "source": "https://gematik.de/fhir/erp-servicerequest/StructureDefinition/erp-service-request-dispense-request" }, { "key": "servicerequest-dispense-request-4", "severity": "error", "human": "If the the code for the delivery type is alternatve-address, then the address must be stated.", "expression": "(status = 'active' and code.coding.where(system='https://gematik.de/fhir/erp-servicerequest/CodeSystem/delivery-type-cs').exists() and code.coding.where(system='https://gematik.de/fhir/erp-servicerequest/CodeSystem/delivery-type-cs').code = 'delivery-to-alternative-address') implies (extension.where(url = 'https://gematik.de/fhir/erp-servicerequest/StructureDefinition/alternative-delivery-address-ex').exists() and extension.where(url = 'https://gematik.de/fhir/erp-servicerequest/StructureDefinition/alternative-delivery-address-ex').value.empty().not())", "source": "https://gematik.de/fhir/erp-servicerequest/StructureDefinition/erp-service-request-dispense-request" } ] }, { "id": "ServiceRequest.extension", "path": "ServiceRequest.extension", "mustSupport": true }, { "id": "ServiceRequest.extension:EPrescriptionToken", "path": "ServiceRequest.extension", "sliceName": "EPrescriptionToken", "short": "The e-prescription token for delivery to the pharmacy can be provided here.", "comment": "The token is of the form '/Task/{PrescriptionID}/$accept?ac={AccessCode}. See [gemSpec_DM_eRp](https://fachportal.gematik.de/fachportal-import/files/gemSpec_DM_eRp_V1.5.0.pdf)'.", "min": 0, "max": "1", "type": [ { "code": "Extension", "profile": [ "https://gematik.de/fhir/erp-servicerequest/StructureDefinition/eprescription-token-ex" ] } ], "mustSupport": true }, { "id": "ServiceRequest.extension:alternativeDeliveryAddress", "path": "ServiceRequest.extension", "sliceName": "alternativeDeliveryAddress", "short": "Alternative delivery address.", "definition": "If the ServiceRequest states that the delivery should be delivered to an alternative address, it must be stated here.", "min": 0, "max": "1", "type": [ { "code": "Extension", "profile": [ "https://gematik.de/fhir/erp-servicerequest/StructureDefinition/alternative-delivery-address-ex" ] } ], "mustSupport": true }, { "id": "ServiceRequest.modifierExtension:medicationChanged", "path": "ServiceRequest.modifierExtension", "sliceName": "medicationChanged", "short": "Indicates whether the medication has been changed by the pharmacy.", "definition": "If the medication has been changed, the value is set to true.", "comment": "If the medication has been changed, the receiving system must display the changed medication to the receiving user.", "min": 0, "max": "1", "type": [ { "code": "Extension", "profile": [ "https://gematik.de/fhir/erp-servicerequest/StructureDefinition/changed-medication-ex" ] } ], "mustSupport": true, "isModifierReason": "If the medication has been changed, the receiving system must display the changed medication to the receiving user." }, { "id": "ServiceRequest.identifier", "path": "ServiceRequest.identifier", "slicing": { "discriminator": [ { "type": "pattern", "path": "system" } ], "rules": "open", "description": "Defines identifiers to be used in a process" }, "min": 1, "mustSupport": true }, { "id": "ServiceRequest.identifier:requestId", "path": "ServiceRequest.identifier", "sliceName": "requestId", "short": "Identifier that uniquely references a ServiceRequest.", "comment": "For referencing and assignment of ServiceRequest, e.g. if one ServiceRequest is to replace another, it is important to be able to make this assignment with the identifier. Can be mapped via a UUID, for example.", "min": 1, "max": "1", "type": [ { "code": "Identifier", "profile": [ "https://gematik.de/fhir/erp-servicerequest/StructureDefinition/erp-service-request-request-identifier" ] } ] }, { "id": "ServiceRequest.requisition", "path": "ServiceRequest.requisition", "short": "Identifier of the process. All ServiceRequests within a process receive the same ID.", "comment": "Is to be understood as a case or process ID in order to be able to track which request the ServiceRequest belongs to.", "min": 1, "type": [ { "code": "Identifier", "profile": [ "https://gematik.de/fhir/erp-servicerequest/StructureDefinition/erp-service-request-procedure-identifier" ] } ], "mustSupport": true }, { "id": "ServiceRequest.status", "path": "ServiceRequest.status", "short": "Indicates the processing status of a service request.", "comment": "If the status changes, this value is overwritten.", "mustSupport": true, "binding": { "strength": "required", "valueSet": "https://gematik.de/fhir/erp-servicerequest/ValueSet/service-request-status-vs" } }, { "id": "ServiceRequest.intent", "path": "ServiceRequest.intent", "fixedCode": "filler-order" }, { "id": "ServiceRequest.priority", "path": "ServiceRequest.priority", "short": "Indicates the urgency of the request.", "definition": "The priority can be used to indicate the urgency of the request.", "comment": "Allowed values: routine | urgent", "mustSupport": true, "binding": { "strength": "required", "valueSet": "https://gematik.de/fhir/erp-servicerequest/ValueSet/service-request-priority-vs" } }, { "id": "ServiceRequest.code", "path": "ServiceRequest.code", "short": "Indicates the type of service request.", "min": 1, "mustSupport": true }, { "id": "ServiceRequest.code.coding", "path": "ServiceRequest.code.coding", "slicing": { "discriminator": [ { "type": "pattern", "path": "$this" } ], "rules": "open", "description": "Differentiates between the service request type and additional information.", "ordered": false }, "min": 1, "mustSupport": true }, { "id": "ServiceRequest.code.coding:request-type", "path": "ServiceRequest.code.coding", "sliceName": "request-type", "short": "Indicates the type of service request.", "min": 1, "max": "1", "patternCoding": { "code": "dispense-request", "system": "https://gematik.de/fhir/erp-servicerequest/CodeSystem/service-request-type-cs" }, "mustSupport": true, "binding": { "strength": "required", "valueSet": "https://gematik.de/fhir/erp-servicerequest/ValueSet/service-request-type-vs" } }, { "id": "ServiceRequest.code.coding:request-type.system", "path": "ServiceRequest.code.coding.system", "min": 1 }, { "id": "ServiceRequest.code.coding:request-type.code", "path": "ServiceRequest.code.coding.code", "comment": "#dispense-request serves as a service request for a pharmacy to deliver a prescription.", "min": 1 }, { "id": "ServiceRequest.code.coding:delivery-type", "path": "ServiceRequest.code.coding", "sliceName": "delivery-type", "short": "Indicates how the delivery should be made.", "definition": "The delivery type can be used to indicate how the delivery should be made. The following options are available: pickup-by-healthcare-service, pickup-by-patient, delivery-to-healthcare-service, delivery-to-alternative-address.", "comment": "If the delivery type is delivery-to-alternative-address, the alternative address must be specified in location.", "min": 0, "max": "1", "patternCoding": { "system": "https://gematik.de/fhir/erp-servicerequest/CodeSystem/delivery-type-cs" }, "mustSupport": true, "binding": { "strength": "required", "valueSet": "https://gematik.de/fhir/erp-servicerequest/ValueSet/delivery-type-vs" } }, { "id": "ServiceRequest.code.coding:delivery-type.system", "path": "ServiceRequest.code.coding.system", "min": 1 }, { "id": "ServiceRequest.code.coding:delivery-type.code", "path": "ServiceRequest.code.coding.code", "min": 1 }, { "id": "ServiceRequest.subject", "path": "ServiceRequest.subject", "short": "Patient for whom a dispense is requested on behalf of the patient.", "type": [ { "code": "Reference", "targetProfile": [ "https://gematik.de/fhir/erp-servicerequest/StructureDefinition/erp-service-request-patient" ] } ], "mustSupport": true }, { "id": "ServiceRequest.occurrence[x]", "path": "ServiceRequest.occurrence[x]", "short": "Indicates the date when the medication should be delivered.", "type": [ { "code": "dateTime" } ], "mustSupport": true }, { "id": "ServiceRequest.authoredOn", "path": "ServiceRequest.authoredOn", "short": "Creation date of the request.", "comment": "Is initially created and then no longer changed.", "min": 1, "mustSupport": true }, { "id": "ServiceRequest.requester", "path": "ServiceRequest.requester", "short": "Inquiring facility or practitioner.", "comment": "The KIM address is already stored in the message header.", "type": [ { "code": "Reference", "targetProfile": [ "https://gematik.de/fhir/erp-servicerequest/StructureDefinition/erp-service-request-organization" ] } ], "mustSupport": true }, { "id": "ServiceRequest.supportingInfo", "path": "ServiceRequest.supportingInfo", "slicing": { "discriminator": [ { "type": "pattern", "path": "type" } ], "rules": "open", "description": "Supporting information about dispense" }, "mustSupport": true }, { "id": "ServiceRequest.supportingInfo:AbgabeDaten", "path": "ServiceRequest.supportingInfo", "sliceName": "AbgabeDaten", "min": 0, "max": "1", "type": [ { "code": "Reference", "targetProfile": [ "https://gematik.de/fhir/erp-servicerequest/StructureDefinition/erp-service-request-medication-dispense" ] } ], "mustSupport": true }, { "id": "ServiceRequest.supportingInfo:AbgabeDaten.type", "path": "ServiceRequest.supportingInfo.type", "short": "Dispense data that is also sent to the e-prescription server.", "min": 1, "fixedUri": "MedicationDispense" }, { "id": "ServiceRequest.note", "path": "ServiceRequest.note", "short": "Further information on the dispense request.", "comment": "Any use cases that are not specified can be placed here in free text.", "mustSupport": true }, { "id": "ServiceRequest.note.time", "path": "ServiceRequest.note.time", "comment": "This is used in order to sort the Annotations", "min": 1, "mustSupport": true } ] } }
Terminologie Bindings
Folgende Bindings sind für diese Ressource spezifiziert:
Path | Conformance | ValueSet |
---|---|---|
ServiceRequest.status | required | https://gematik.de/fhir/erp-servicerequest/ValueSet/service-request-status-vs |
ServiceRequest.priority | required | https://gematik.de/fhir/erp-servicerequest/ValueSet/service-request-priority-vs |
ServiceRequest.code.coding:request-type | required | https://gematik.de/fhir/erp-servicerequest/ValueSet/service-request-type-vs |
ServiceRequest.code.coding:delivery-type | required | https://gematik.de/fhir/erp-servicerequest/ValueSet/delivery-type-vs |
Constraints
Folgende Constraints sind für diese Ressource spezifiziert:
Pfad | Id | Grade | Details | Expression |
---|---|---|---|---|
ServiceRequest | servicerequest-dispense-request-1 | error | If the status is active, then requester must be present. | status = 'active' implies requester.exists() |
ServiceRequest | servicerequest-dispense-request-2 | error | If the status is active, then the e-prescription-token must be present. | status = 'active' implies extension.where(url = 'https://gematik.de/fhir/erp-servicerequest/StructureDefinition/eprescription-token-ex').exists() |
ServiceRequest | servicerequest-dispense-request-3 | error | If the status is completed, then the dispense data must be present. | status = 'completed' implies supportingInfo.where(type='MedicationDispense').exists() |
ServiceRequest | servicerequest-dispense-request-4 | error | If the the code for the delivery type is alternatve-address, then the address must be stated. | (status = 'active' and code.coding.where(system='https://gematik.de/fhir/erp-servicerequest/CodeSystem/delivery-type-cs').exists() and code.coding.where(system='https://gematik.de/fhir/erp-servicerequest/CodeSystem/delivery-type-cs').code = 'delivery-to-alternative-address') implies (extension.where(url = 'https://gematik.de/fhir/erp-servicerequest/StructureDefinition/alternative-delivery-address-ex').exists() and extension.where(url = 'https://gematik.de/fhir/erp-servicerequest/StructureDefinition/alternative-delivery-address-ex').value.empty().not()) |