NHSDigital-MedicationRequest
Profile url | FHIR Module | Normative Status |
---|---|---|
https://fhir.nhs.uk/StructureDefinition/NHSDigital-MedicationRequest | Medicines | trial-use |
MedicationRequest | I | MedicationRequest | Element IdMedicationRequest Ordering of medication for patient or group Alternate namesPrescription, Order DefinitionAn order or request for both supply of the medication and the instructions for administration of the medication to a patient. The resource is called "MedicationRequest" rather than "MedicationPrescription" or "MedicationOrder" to generalize the use across inpatient and outpatient settings, including care plans, etc., and to harmonize with workflow patterns.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
extension | I | 1..* | Extension | Element IdMedicationRequest.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 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. 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) Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
medicationRepeatInformation | S I | 0..1 | Extension(Complex) | Element IdMedicationRequest.extension:medicationRepeatInformation Continous and Continuous Repeat Dispensing Alternate namesextensions, user content DefinitionThis extension MUST be present for
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. Extension(Complex) Extension URLhttps://fhir.hl7.org.uk/StructureDefinition/Extension-UKCore-MedicationRepeatInformation Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
responsiblePractitioner | S I | 0..1 | Extension(Reference(NHSDigitalPractitionerRole)) | Element IdMedicationRequest.extension:responsiblePractitioner Responsible Practitioner for the prescription Alternate namesextensions, user content DefinitionMust only be populated if the
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. Extension(Reference(NHSDigitalPractitionerRole)) Extension URLhttps://fhir.nhs.uk/StructureDefinition/Extension-DM-ResponsiblePractitioner Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
prescriptionEndorsement | S I | 0..* | Extension(CodeableConcept) | Element IdMedicationRequest.extension:prescriptionEndorsement NHS BSA Prescription Endorsements Alternate namesextensions, user content DefinitionThe codes are contained in the valueset
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. https://fhir.nhs.uk/StructureDefinition/Extension-DM-PrescriptionEndorsement Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
prescriptionTaskStatusReason | S I | 0..* | Extension(Complex) | Element IdMedicationRequest.extension:prescriptionTaskStatusReason Prescription task status reason Alternate namesextensions, user content DefinitionThe status history within EPS is primarily a technical Status and the statusReason will reflect current clinical status of the order. 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. Extension(Complex) Extension URLhttps://fhir.nhs.uk/StructureDefinition/Extension-DM-PrescriptionStatusHistory Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
NHSBSAprescriptionType | S I | 1..1 | Extension(Coding) | Element IdMedicationRequest.extension:NHSBSAprescriptionType NHS BSA Prescription Type Alternate namesextensions, user content DefinitionThe vocabulary for the ‘PrescriptionType’ vocabulary is defined within the NHSBSA Overprint Specification. The System must populate the ‘PrescriptionType’ attribute for the appropriate combination of prescriber and care setting. Retired codes within this vocabulary must not be used
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. https://fhir.nhs.uk/StructureDefinition/Extension-DM-PrescriptionType Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
controlledDrug | S I | 0..1 | Extension(Complex) | Element IdMedicationRequest.extension:controlledDrug Optional Controlled Drug Extensions Alternate namesextensions, user content DefinitionThe table below summarises the EPS requirements for the CD schedules. The terms “Hand signature” and “Electronic signature” expressed in the table are shortened references to the legal definition of signature requirements within government legislation.
It is a legal requirement to state the prescribed quantity as words in the
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. Extension(Complex) Extension URLhttps://fhir.nhs.uk/StructureDefinition/Extension-DM-ControlledDrug Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
dispensingInformation | S I | 0..1 | Extension(Complex) | Element IdMedicationRequest.extension:dispensingInformation For EPS use only Alternate namesextensions, user content DefinitionThis extension is used in
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. Extension(Complex) Extension URLhttps://fhir.nhs.uk/StructureDefinition/Extension-EPS-DispensingInformation Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
identifier | S | 1..* | Identifier | Element IdMedicationRequest.identifier Each MedicationRequest MUST be identified by an Universal Unique Identifiers (UUIDs) with a system of https://fhir.nhs.uk/Id/prescription-order-item-number DefinitionUUID example (for illustration purposes only); a54219b8-f741-4c47-b662-e4f8dfa49ab6
This is a business identifier, not a resource identifier. Unordered, Open, by system(Value) Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(All Slices) | There are no (further) constraints on this element | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdMedicationRequest.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdMedicationRequest.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdMedicationRequest.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patient Mappings
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdMedicationRequest.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdMedicationRequest.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
prescriptionOrderItem | 1..1 | Identifier | Element IdMedicationRequest.identifier:prescriptionOrderItem Prescription Order Item DefinitionUnique Id of the MedicationRequest within EPS This is a business identifier, not a resource identifier.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdMedicationRequest.identifier:prescriptionOrderItem.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdMedicationRequest.identifier:prescriptionOrderItem.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 1..1 | uriFixed Value | Element IdMedicationRequest.identifier:prescriptionOrderItem.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
https://fhir.nhs.uk/Id/prescription-order-item-number
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 1..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.identifier:prescriptionOrderItem.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdMedicationRequest.identifier:prescriptionOrderItem.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdMedicationRequest.identifier:prescriptionOrderItem.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
status | S Σ ?! | 1..1 | codeBinding | Element IdMedicationRequest.status active | cancelled | stopped DefinitionA code specifying the current state of the order. Generally, this will be active or completed state.
Logical medicationRequest status transitionsThis state transition diagram is an enhancement over the generic State Machine defined within the FHIR specification. It includes the status values associated with a medication request with transitions applicable to a UK implementation. ![]() This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid. A coded concept specifying the state of the prescribing event. Describes the lifecycle of the prescription. medicationrequest Status (required)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
statusReason | S | 0..1 | CodeableConceptBinding | Element IdMedicationRequest.statusReason Reason for current status DefinitionThis is generally only used for exception statuses such as This is mandatory for 'prescription-order-update' messages.
This is generally only used for "exception" statuses such as "suspended" or "cancelled". The reason why the MedicationRequest was created at all is captured in reasonCode, not here. Identifies the reasons for a given status. MedicationRequestStatusReason (required)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
coding | Σ | 1..1 | Coding | There are no (further) constraints on this element Element IdMedicationRequest.statusReason.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. 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.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 1..1 | uri | There are no (further) constraints on this element Element IdMedicationRequest.statusReason.coding.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 IdMedicationRequest.statusReason.coding.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 | Σ | 1..1 | code | There are no (further) constraints on this element Element IdMedicationRequest.statusReason.coding.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 | Σ | 1..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.statusReason.coding.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 IdMedicationRequest.statusReason.coding.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.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
text | Σ | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.statusReason.text Plain text representation of the concept DefinitionA 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. 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. Very often the text is the same as a displayName of one of the codings.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
intent | Σ ?! | 1..1 | codeBinding | Element IdMedicationRequest.intent proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option DefinitionWhether the request is a proposal, plan, or an original order. Indicates the type of order. A code specifying the current state of the order. Generally, this will be active or completed state.
The kind of medication order. medicationRequest Intent (required)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
category | S | 1..* | CodeableConceptBinding | Element IdMedicationRequest.category Type of medication usage DefinitionIn primary care the code of
The category can be used to include where the medication is expected to be consumed or other types of requests. A coded concept identifying the category of medication request. For example, where the medication is to be consumed or administered, or the type of medication treatment. UKCoreMedicationRequestCategory (extensible)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
coding | Σ | 1..1 | Coding | Element IdMedicationRequest.category.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. 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. Unordered, Open, by system(Value) Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
patientClassFHIR | Σ | 0..1 | CodingBinding | Element IdMedicationRequest.category.coding:patientClassFHIR Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. 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. MedicationRequestCategory (required) Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 1..1 | uriFixed Value | Element IdMedicationRequest.category.coding:patientClassFHIR.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.
http://terminology.hl7.org/CodeSystem/medicationrequest-category
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
version | Σ | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.category.coding:patientClassFHIR.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 | Σ | 1..1 | code | There are no (further) constraints on this element Element IdMedicationRequest.category.coding:patientClassFHIR.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 IdMedicationRequest.category.coding:patientClassFHIR.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 IdMedicationRequest.category.coding:patientClassFHIR.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.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
patientClassUK | Σ | 0..1 | CodingBinding | Element IdMedicationRequest.category.coding:patientClassUK Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. 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. MedicationRequestCategory (required) Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 1..1 | uriFixed Value | Element IdMedicationRequest.category.coding:patientClassUK.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.
https://fhir.nhs.uk/CodeSystem/medicationrequest-category
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
version | Σ | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.category.coding:patientClassUK.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 | Σ | 1..1 | code | There are no (further) constraints on this element Element IdMedicationRequest.category.coding:patientClassUK.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 IdMedicationRequest.category.coding:patientClassUK.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 IdMedicationRequest.category.coding:patientClassUK.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.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
text | Σ | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.category.text Plain text representation of the concept DefinitionA 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. 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. Very often the text is the same as a displayName of one of the codings.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
priority | Σ | 0..1 | codeBinding | There are no (further) constraints on this element Element IdMedicationRequest.priority routine | urgent | asap | stat DefinitionIndicates how quickly the Medication Request should be addressed with respect to other requests. Note that FHIR strings SHALL NOT exceed 1MB in size Identifies the level of importance to be assigned to actioning the request. RequestPriority (required)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
doNotPerform | Σ ?! | 0..1 | boolean | There are no (further) constraints on this element Element IdMedicationRequest.doNotPerform True if request is prohibiting action DefinitionIf true indicates that the provider is asking for the medication request not to occur. If do not perform is not specified, the request is a positive request e.g. "do perform".
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
reported[x] | Σ | 0..1 | There are no (further) constraints on this element Element IdMedicationRequest.reported[x] Reported rather than primary record DefinitionIndicates if this record was captured as a secondary 'reported' record rather than as an original primary source-of-truth record. It may also indicate the source of the report.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
reportedBoolean | boolean | There are no (further) constraints on this element Data Type | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
reportedReference | Reference(UK Core Patient | UK Core Practitioner | UK Core PractitionerRole | UK Core RelatedPerson | UK Core Organization) | There are no (further) constraints on this element Data Type Reference(UK Core Patient | UK Core Practitioner | UK Core PractitionerRole | UK Core RelatedPerson | UK Core Organization) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
medication[x] | S Σ | 1..1 | Binding | Element IdMedicationRequest.medication[x] Medication to be taken DefinitionOnly Virtual Medical Products (VMP) and Actual Medical Products (AMP) can be used. Any code from the SnomedCT UK DMD subset for VMP, AMP and VTM concepts
A coded concept identifying substance or product that can be ordered. NHS Digital Medication Code (extensible)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
medicationCodeableConcept | NHSDigitalMedicationRequestCodeableConcept | Data Type | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
medicationReference | Reference(NHSDigitalMedicationRequestMedication) | Data Type Reference(NHSDigitalMedicationRequestMedication) Allowed aggregation: bundled | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
subject | S Σ I | 1..1 | Reference(NHSDigitalPatientPDS) | Element IdMedicationRequest.subject Who or group medication request is for DefinitionA resource reference to a Patient with a traced NHS Number is required, an untraced NHS Number MUST NOT be used.
The subject on a medication request is mandatory. For the secondary use case where the actual subject is not provided, there still must be an anonymized subject specified. Reference(NHSDigitalPatientPDS) Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
reference | Σ I | 1..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.subject.reference Literal reference, Relative, internal or absolute URL DefinitionA 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. 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.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdMedicationRequest.subject.type Type the reference refers to (e.g. "Patient") DefinitionThe 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). 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. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdMedicationRequest.subject.identifier Logical reference, when literal reference is not known DefinitionAn 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. 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).
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdMedicationRequest.subject.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdMedicationRequest.subject.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 1..1 | uriFixed Value | Element IdMedicationRequest.subject.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
https://fhir.nhs.uk/Id/nhs-number
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 1..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.subject.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdMedicationRequest.subject.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdMedicationRequest.subject.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.subject.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. 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.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
encounter | I | 0..1 | Reference(NHSDigitalEncounter) | Element IdMedicationRequest.encounter Encounter created as part of encounter/admission/stay DefinitionEncounter is required for secondary care prescriptions. This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter." If there is a need to link to episodes of care they will be handled with an extension. Reference(NHSDigitalEncounter) Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
reference | Σ I | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.encounter.reference Literal reference, Relative, internal or absolute URL DefinitionA 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. 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.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdMedicationRequest.encounter.type Type the reference refers to (e.g. "Patient") DefinitionThe 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). 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. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdMedicationRequest.encounter.identifier Logical reference, when literal reference is not known DefinitionAn 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. 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).
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdMedicationRequest.encounter.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdMedicationRequest.encounter.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdMedicationRequest.encounter.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patient Mappings
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.encounter.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdMedicationRequest.encounter.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdMedicationRequest.encounter.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.encounter.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. 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.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
supportingInformation | I | 0..* | Reference(Resource) | There are no (further) constraints on this element Element IdMedicationRequest.supportingInformation Information to support ordering of the medication DefinitionInclude additional information (for example, patient height and weight) that supports the ordering of the medication. 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.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
reference | Σ I | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.supportingInformation.reference Literal reference, Relative, internal or absolute URL DefinitionA 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. 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.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdMedicationRequest.supportingInformation.type Type the reference refers to (e.g. "Patient") DefinitionThe 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). 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. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdMedicationRequest.supportingInformation.identifier Logical reference, when literal reference is not known DefinitionAn 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. 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).
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdMedicationRequest.supportingInformation.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdMedicationRequest.supportingInformation.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdMedicationRequest.supportingInformation.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patient Mappings
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.supportingInformation.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdMedicationRequest.supportingInformation.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdMedicationRequest.supportingInformation.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.supportingInformation.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. 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.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
authoredOn | S Σ | 1..1 | dateTime | There are no (further) constraints on this element Element IdMedicationRequest.authoredOn When request was initially authored DefinitionThe date (and perhaps time) when the prescription was initially written or authored on.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
requester | S Σ I | 1..1 | Reference(NHSDigitalPractitionerRoleEPSLegal | NHSDigitalPractitionerRoleSDS) | Element IdMedicationRequest.requester Who/What requested the Request DefinitionThe requester must contain a resource reference to the Practitioner who has electronically signed the prescription. If the
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. Reference(NHSDigitalPractitionerRoleEPSLegal | NHSDigitalPractitionerRoleSDS) Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
reference | Σ I | 1..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.requester.reference Literal reference, Relative, internal or absolute URL DefinitionA 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. 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.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdMedicationRequest.requester.type Type the reference refers to (e.g. "Patient") DefinitionThe 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). 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. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdMedicationRequest.requester.identifier Logical reference, when literal reference is not known DefinitionAn 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. 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).
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdMedicationRequest.requester.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdMedicationRequest.requester.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdMedicationRequest.requester.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patient Mappings
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.requester.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdMedicationRequest.requester.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdMedicationRequest.requester.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.requester.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. 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.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
performer | I | 0..1 | NHSDigitalReference(UK Core Device | UK Core Practitioner | UK Core PractitionerRole | UK Core Organization | UK Core Patient | UK Core RelatedPerson | UK Core CareTeam) | Element IdMedicationRequest.performer A reference from one resource to another DefinitionA reference from one resource to another. 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. NHSDigitalReference(UK Core Device | UK Core Practitioner | UK Core PractitionerRole | UK Core Organization | UK Core Patient | UK Core RelatedPerson | UK Core CareTeam) Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
reference | Σ I | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.performer.reference Literal reference, Relative, internal or absolute URL DefinitionA 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. 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.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdMedicationRequest.performer.type Type the reference refers to (e.g. "Patient") DefinitionThe 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). 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. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdMedicationRequest.performer.identifier Logical reference, when literal reference is not known DefinitionAn 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. 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).
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdMedicationRequest.performer.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdMedicationRequest.performer.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdMedicationRequest.performer.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patient Mappings
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.performer.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdMedicationRequest.performer.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdMedicationRequest.performer.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.performer.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. 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.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
performerType | Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element IdMedicationRequest.performerType Desired kind of performer of the medication administration DefinitionIndicates the type of performer of the administration of the medication. If specified without indicating a performer, this indicates that the performer must be of the specified type. If specified with a performer then it indicates the requirements of the performer if the designated performer is not available. Identifies the type of individual that is desired to administer the medication. ProcedurePerformerRoleCodes (example)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
recorder | I | 0..1 | Reference(NHSDigitalPractitioner) | Element IdMedicationRequest.recorder Person who entered the request DefinitionThe person who entered the order on behalf of another individual for example in the case of a verbal or a telephone order. 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. Reference(NHSDigitalPractitioner) Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
reference | Σ I | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.recorder.reference Literal reference, Relative, internal or absolute URL DefinitionA 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. 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.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdMedicationRequest.recorder.type Type the reference refers to (e.g. "Patient") DefinitionThe 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). 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. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdMedicationRequest.recorder.identifier Logical reference, when literal reference is not known DefinitionAn 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. 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).
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdMedicationRequest.recorder.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdMedicationRequest.recorder.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdMedicationRequest.recorder.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patient Mappings
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.recorder.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdMedicationRequest.recorder.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdMedicationRequest.recorder.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.recorder.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. 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.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
reasonCode | 0..* | CodeableConcept | There are no (further) constraints on this element Element IdMedicationRequest.reasonCode Reason or indication for ordering or not ordering the medication DefinitionThe reason or the indication for ordering or not ordering the medication. This could be a diagnosis code. If a full condition record exists or additional detail is needed, use reasonReference. A coded concept indicating why the medication was ordered. Condition/Problem/DiagnosisCodes (example)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
reasonReference | I | 0..* | Reference(UK Core Condition | UK Core Observation) | There are no (further) constraints on this element Element IdMedicationRequest.reasonReference Condition or observation that supports why the prescription is being written DefinitionCondition or observation that supports why the medication was ordered. This is a reference to a condition or observation that is the reason for the medication order. If only a code exists, use reasonCode. Reference(UK Core Condition | UK Core Observation) Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
reference | Σ I | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.reasonReference.reference Literal reference, Relative, internal or absolute URL DefinitionA 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. 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.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdMedicationRequest.reasonReference.type Type the reference refers to (e.g. "Patient") DefinitionThe 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). 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. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdMedicationRequest.reasonReference.identifier Logical reference, when literal reference is not known DefinitionAn 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. 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).
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdMedicationRequest.reasonReference.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdMedicationRequest.reasonReference.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdMedicationRequest.reasonReference.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patient Mappings
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.reasonReference.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdMedicationRequest.reasonReference.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdMedicationRequest.reasonReference.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.reasonReference.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. 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.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
instantiatesCanonical | Σ | 0..* | canonical() | There are no (further) constraints on this element Element IdMedicationRequest.instantiatesCanonical Instantiates FHIR protocol or definition DefinitionThe URL pointing to a protocol, guideline, orderset, or other definition that is adhered to in whole or in part by this MedicationRequest.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
instantiatesUri | Σ | 0..* | uri | There are no (further) constraints on this element Element IdMedicationRequest.instantiatesUri Instantiates external protocol or definition DefinitionThe URL pointing to an externally maintained protocol, guideline, orderset or other definition that is adhered to in whole or in part by this MedicationRequest. see http://en.wikipedia.org/wiki/Uniform_resource_identifier
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
basedOn | S Σ I | 0..* | Reference(ImmunizationRecommendation | NHSDigitalMedicationRequest) | Element IdMedicationRequest.basedOn What request fulfills DefinitionThis MUST be populated for Example for a
Example for a
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. Reference(ImmunizationRecommendation | NHSDigitalMedicationRequest) Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
extension | I | 0..* | Extension | Element IdMedicationRequest.basedOn.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) Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
repeatInformation | S I | 0..1 | Extension(Complex) | Element IdMedicationRequest.basedOn.extension:repeatInformation Additional repeatInformation Alternate namesextensions, user content DefinitionThe extension The meaning of An integer indicating the number of times, in addition to the original dispense, (aka refills or repeats) that the patient can receive the prescribed medication. Usage Notes: This integer does not include the original order dispense. This means that if an order indicates dispense 30 tablets plus "3 repeats", then the order can be dispensed a total of 4 times and the patient can receive a total of 120 tablets. A prescriber may explicitly say that zero refills are permitted after the initial dispense.
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. Extension(Complex) Extension URLhttps://fhir.nhs.uk/StructureDefinition/Extension-EPS-RepeatInformation Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
orignalPrescriptionId | I | 0..1 | Extension(Identifier) | Element IdMedicationRequest.basedOn.extension:orignalPrescriptionId Optional Extensions Element Alternate namesextensions, user content DefinitionThe original prescription id, used in repeats. This is taken from the same extension in the original MedicationRequest.groupIdentifier.
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. https://fhir.nhs.uk/StructureDefinition/Extension-DM-PrescriptionId Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
reference | Σ I | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.basedOn.reference Literal reference, Relative, internal or absolute URL DefinitionA 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. 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.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdMedicationRequest.basedOn.type Type the reference refers to (e.g. "Patient") DefinitionThe 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). 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. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdMedicationRequest.basedOn.identifier Logical reference, when literal reference is not known DefinitionAn 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. 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).
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdMedicationRequest.basedOn.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdMedicationRequest.basedOn.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdMedicationRequest.basedOn.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patient Mappings
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.basedOn.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdMedicationRequest.basedOn.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdMedicationRequest.basedOn.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.basedOn.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. 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.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
groupIdentifier | S Σ | 1..1 | Identifier | Element IdMedicationRequest.groupIdentifier groupIdentifier (Short Form Prescription ID) DefinitionThe purpose of the Short Form Prescription ID is to identify the prescription during its lifecycle within the Spine (i.e. prescribe, dispense & claim). The prescription UUID is retained to provide the link through to the Spine medication record within the PSIS and must be included as the first identifier within the prescription message. The format of the Short Form Prescription ID is as follows;
Where;
Note. Hyphens are always included to separate the ID into 3 blocks of 6 characters. Note. The implementation of the MOD 37-2 standard uses a “+” character for char 36 opposed to a “*” character. Short Form Prescription ID example (for illustration purposes only); 83C40E-A23856-00123W
Requests are linked either by a "basedOn" relationship (i.e. one request is fulfilling another) or by having a common requisition. Requests that are part of the same requisition are generally treated independently from the perspective of changing their state or maintaining them after initial creation. ITK HL7v3 Mapping = The groupIdentifier is equivalent to ParentPrescription.id (prescription-order-number). The extension is used to carry the ParentPrescription.id (UUID).
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
extension | I | 1..* | Extension | Element IdMedicationRequest.groupIdentifier.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) Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
PrescriptionOrderUUID | I | 1..1 | Extension(Identifier) | Element IdMedicationRequest.groupIdentifier.extension:PrescriptionOrderUUID UUID order number for grouped MedciationRequests Alternate namesextensions, user content DefinitionWhen UUIDs are used within HL7 messages they must be represented in an upper case human-readable hexadecimal format where hyphen separators are used as per the example below and as defined by the ‘datatype’ schema within the DMS. UUID example (for illustration purposes only); 34026084-A445-84AD-2D01-97D69ED25865
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. https://fhir.nhs.uk/StructureDefinition/Extension-DM-PrescriptionId Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
url | 1..1 | System.StringFixed Value | There are no (further) constraints on this element Element IdMedicationRequest.groupIdentifier.extension:PrescriptionOrderUUID.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. System.String Fixed Valuehttps://fhir.nhs.uk/StructureDefinition/Extension-DM-PrescriptionId
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
value[x] | 0..1 | There are no (further) constraints on this element Element IdMedicationRequest.groupIdentifier.extension:PrescriptionOrderUUID.value[x] Value of extension DefinitionValue of extension - must be one of a constrained set of the data types (see Extensibility for a list).
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueIdentifier | Identifier | There are no (further) constraints on this element Data Type | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdMedicationRequest.groupIdentifier.extension:PrescriptionOrderUUID.value[x].use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdMedicationRequest.groupIdentifier.extension:PrescriptionOrderUUID.value[x].type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 1..1 | uriFixed Value | There are no (further) constraints on this element Element IdMedicationRequest.groupIdentifier.extension:PrescriptionOrderUUID.value[x].system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
https://fhir.nhs.uk/Id/prescription
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 1..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.groupIdentifier.extension:PrescriptionOrderUUID.value[x].value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdMedicationRequest.groupIdentifier.extension:PrescriptionOrderUUID.value[x].period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(Organization) | There are no (further) constraints on this element Element IdMedicationRequest.groupIdentifier.extension:PrescriptionOrderUUID.value[x].assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdMedicationRequest.groupIdentifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdMedicationRequest.groupIdentifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 1..1 | uriFixed Value | Element IdMedicationRequest.groupIdentifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
https://fhir.nhs.uk/Id/prescription-order-number
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 1..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.groupIdentifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdMedicationRequest.groupIdentifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdMedicationRequest.groupIdentifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
courseOfTherapyType | S | 1..1 | CodeableConceptBinding | Element IdMedicationRequest.courseOfTherapyType A course of therapy for a medication request Definition
The type of prescription e.g. acute, continuous, etc. Was extension in STU3 https://fhir.hl7.org.uk/STU3/StructureDefinition/Extension-CareConnect-PrescriptionType-1 and Digital Medicine uses international codes, so continuous in place of repeat. Identifies the overall pattern of medication administratio. Medication Request Course of Therapy Codes (required)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
coding | Σ | 1..1 | Coding | There are no (further) constraints on this element Element IdMedicationRequest.courseOfTherapyType.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. 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.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 1..1 | uri | There are no (further) constraints on this element Element IdMedicationRequest.courseOfTherapyType.coding.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 IdMedicationRequest.courseOfTherapyType.coding.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 | Σ | 1..1 | code | There are no (further) constraints on this element Element IdMedicationRequest.courseOfTherapyType.coding.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 IdMedicationRequest.courseOfTherapyType.coding.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 IdMedicationRequest.courseOfTherapyType.coding.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.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
text | Σ | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.courseOfTherapyType.text Plain text representation of the concept DefinitionA 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. 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. Very often the text is the same as a displayName of one of the codings.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
insurance | I | 0..* | Reference(Coverage | ClaimResponse) | There are no (further) constraints on this element Element IdMedicationRequest.insurance Associated insurance coverage DefinitionInsurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be required for delivering the requested service. 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. Reference(Coverage | ClaimResponse) Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
reference | Σ I | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.insurance.reference Literal reference, Relative, internal or absolute URL DefinitionA 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. 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.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdMedicationRequest.insurance.type Type the reference refers to (e.g. "Patient") DefinitionThe 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). 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. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdMedicationRequest.insurance.identifier Logical reference, when literal reference is not known DefinitionAn 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. 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).
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdMedicationRequest.insurance.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdMedicationRequest.insurance.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdMedicationRequest.insurance.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patient Mappings
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.insurance.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdMedicationRequest.insurance.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdMedicationRequest.insurance.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.insurance.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. 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.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
note | S | 0..* | Annotation | Element IdMedicationRequest.note Dispensing Note DefinitionClinical information relating to a prescribed medication item that cannot be conveyed within dosage instructions is populated within Examples of dispensing notes are:
One scenario where
For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. Annotations SHOULD NOT be used to communicate "modifying" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible).
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
author[x] | Σ | 0..1 | There are no (further) constraints on this element Element IdMedicationRequest.note.author[x] Individual responsible for the annotation DefinitionThe individual responsible for making the annotation. Organization is used when there's no need for specific attribution as to who made the comment.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
authorString | string | There are no (further) constraints on this element Data Type | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
authorReference | Reference(UK Core Practitioner | UK Core Patient | UK Core RelatedPerson | UK Core Organization) | There are no (further) constraints on this element Data Type Reference(UK Core Practitioner | UK Core Patient | UK Core RelatedPerson | UK Core Organization) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
time | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element IdMedicationRequest.note.time When the annotation was made DefinitionIndicates when this particular annotation was made.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
text | Σ | 1..1 | markdown | There are no (further) constraints on this element Element IdMedicationRequest.note.text The annotation - text content (as markdown) DefinitionThe text of the annotation in markdown format. 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/
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
dosageInstruction | S | 1..* | NHSDigitalDosage | Element IdMedicationRequest.dosageInstruction How the medication is/was taken or should be taken DefinitionThe content of the
The prescriber is required to enter a medication item dosage. The use of a generic default value, for example “Use as directed”, if a value is not entered, is not acceptable from a clinical perspective. The user must be asked to select a dosage instruction from a pick list, type by hand or have the system populate with a valid and clinically safe dosage instruction relevant to the prescribed medication or clinical circumstances. As per BNF guidelines, the dosage must be presented to the user without abbreviation although it may be entered and stored within the PMR in an abbreviated form. Within HL7 messaging, the dosage instruction must be represented without abbreviation.
There are examples where a medication request may include the option of an oral dose or an Intravenous or Intramuscular dose. For example, "Ondansetron 8mg orally or IV twice a day as needed for nausea" or "Compazine® (prochlorperazine) 5-10mg PO or 25mg PR bid prn nausea or vomiting". In these cases, two medication requests would be created that could be grouped together. The decision on which dose and route of administration to use is based on the patient's condition at the time the dose is needed.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
sequence | S Σ | 0..1 | integer | Element IdMedicationRequest.dosageInstruction.sequence Multi-sequence dosage instructions. DefinitionA multi-sequence would be required where a dosage instruction changes over a given time schedule, where a dosage instruction includes optional follow-up doses or where a concurrent dosage instruction is required for the same medication at a different dose. Examples below include Prednisolone to treat Bell’s palsy where a dose starts at 60 mg per day for a period of time then reduces by 10 mg per day. This would be described as a sequential dosage instruction. A concurrent dosage example is provided to describe a different dose in the morning to that at midday. Sequential InstructionsWhere the value of sequence is an incremental integer it defines a sequential instruction. Concurrent InstructionsWhere the same integer value of sequence is defines it means a concurrent instruction. If the sequence number of multiple Dosages is the same, then it is implied that the instructions are to be treated as concurrent. If the sequence number is different, then the Dosages are intended to be sequential. 32 bit number; for values larger than this, use decimal
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
text | S Σ | 0..1 | string | Element IdMedicationRequest.dosageInstruction.text The complete dosage instruction as a human readable string. DefinitionThe complete dosage instruction as a human readable string.
Recommendation: Use the translation algorithm published within this guide to create a string from the coded Dosage elements. It is planned for this translation algorithm to be available as an API.
For example;
Where additional dosage instructions need to be conveyed that cannot be described using any other element of the Dosage structure, then append these to the end of the translated dosage text. For example, the instruction to For example;
For example, the instruction For example;
Free text dosage instructions can be used for cases where the instructions are too complex to code. The content of this attribute does not include the name or description of the medication. When coded instructions are present, the free text instructions may still be present for display to humans taking or administering the medication. It is expected that the text instructions will always be populated. If the dosage.timing attribute is also populated, then the dosage.text should reflect the same information as the timing. Additional information about administration or preparation of the medication should be included as text. Note that FHIR strings SHALL NOT exceed 1MB in size
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
additionalInstruction | S Σ | 0..* | CodeableConcept | Element IdMedicationRequest.dosageInstruction.additionalInstruction Additional dosage instructions that can be either SNOMED-CT coded terms or free-text instructions. DefinitionThese sections MUST be used only be used to pass notes regarding the prescription to the pharmacist or patient. Lists of repeat medications and general practice notifications to the patient SHOULD be recorded in NHSDigital-CommunicationRequest resource. Patient instructions for taking the drug are contained with in the
Additional instruction is intended to be coded, but where no code exists, the element could include text. For example, "Swallow with plenty of water" which might or might not be coded. Information about administration or preparation of the medication (e.g. "infuse as rapidly as possibly via intraperitoneal port" or "immediately following drug x") should be populated in dosage.text. A coded concept identifying additional instructions such as "take with water" or "avoid operating heavy machinery". SNOMEDCTAdditionalDosageInstructions (example)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
patientInstruction | S Σ | 0..1 | string | Element IdMedicationRequest.dosageInstruction.patientInstruction Patient or consumer oriented instructions DefinitionThese sections MUST be used only be used to pass notes regarding the prescription to the pharmacist or patient. Lists of repeat medications and general practice notifications to the patient SHOULD be recorded in NHSDigital-CommunicationRequest resource. Patient instructions for taking the drug are contained with in the
Note that FHIR strings SHALL NOT exceed 1MB in size
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
timing | S Σ | 0..1 | Timing | Element IdMedicationRequest.dosageInstruction.timing When medication should be administered DefinitionAdding constraints, bounds or limits to a dosage instruction. The timing schedule for giving the medication to the patient. This data type allows many different expressions. For example: "Every 8 hours"; "Three times a day"; "1/2 an hour before breakfast for 10 days from 23-Dec 2011:"; "15 Oct 2013, 17 Oct 2013 and 1 Nov 2013". Sometimes, a rate can imply duration when expressed as total volume / duration (e.g. 500mL/2 hours implies a duration of 2 hours). However, when rate doesn't imply duration (e.g. 250mL/hour), then the timing.repeat.duration is needed to convey the infuse over time period. This attribute might not always be populated while the Dosage.text is expected to be populated. If both are populated, then the Dosage.text should reflect the content of the Dosage.timing.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
event | Σ | 0..* | dateTime | There are no (further) constraints on this element Element IdMedicationRequest.dosageInstruction.timing.event When the event occurs DefinitionIdentifies specific times when the event occurs. In a Medication Administration Record, for instance, you need to take a general specification, and turn it into a precise specification.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
repeat | Σ I | 0..1 | Element | There are no (further) constraints on this element Element IdMedicationRequest.dosageInstruction.timing.repeat When the event is to occur DefinitionA set of rules that describe when the event is scheduled. Many timing schedules are determined by regular repetitions.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
bounds[x] | Σ | 0..1 | There are no (further) constraints on this element Element IdMedicationRequest.dosageInstruction.timing.repeat.bounds[x] Length/Range of lengths, or (Start and/or end) limits DefinitionEither a duration for the length of the timing schedule, a range of possible length, or outer bounds for start and/or end limits of the timing schedule.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
boundsDuration | Duration | Data Type | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
boundsRange | NHSDigitalRange | Data Type | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
boundsPeriod | Period | Data Type | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
count | Σ | 0..1 | positiveInt | There are no (further) constraints on this element Element IdMedicationRequest.dosageInstruction.timing.repeat.count Number of times to repeat DefinitionA total count of the desired number of repetitions across the duration of the entire timing specification. If countMax is present, this element indicates the lower bound of the allowed range of count values. Repetitions may be limited by end time or total occurrences. If you have both bounds and count, then this should be understood as within the bounds period, until count times happens.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
countMax | Σ | 0..1 | positiveInt | There are no (further) constraints on this element Element IdMedicationRequest.dosageInstruction.timing.repeat.countMax Maximum number of times to repeat DefinitionIf present, indicates that the count is a range - so to perform the action between [count] and [countMax] times. 32 bit number; for values larger than this, use decimal
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
duration | Σ | 0..1 | decimal | There are no (further) constraints on this element Element IdMedicationRequest.dosageInstruction.timing.repeat.duration How long when it happens DefinitionHow long this thing happens for when it happens. If durationMax is present, this element indicates the lower bound of the allowed range of the duration. Some activities are not instantaneous and need to be maintained for a period of time. For some events the duration is part of the definition of the event (e.g. IV infusions, where the duration is implicit in the specified quantity and rate). For others, it's part of the timing specification (e.g. exercise).
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
durationMax | Σ | 0..1 | decimal | There are no (further) constraints on this element Element IdMedicationRequest.dosageInstruction.timing.repeat.durationMax How long when it happens (Max) DefinitionIf present, indicates that the duration is a range - so to perform the action between [duration] and [durationMax] time length. Some activities are not instantaneous and need to be maintained for a period of time. For some events the duration is part of the definition of the event (e.g. IV infusions, where the duration is implicit in the specified quantity and rate). For others, it's part of the timing specification (e.g. exercise).
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
durationUnit | Σ | 0..1 | codeBinding | There are no (further) constraints on this element Element IdMedicationRequest.dosageInstruction.timing.repeat.durationUnit s | min | h | d | wk | mo | a - unit of time (UCUM) DefinitionThe units of time for the duration, in UCUM units. Note that FHIR strings SHALL NOT exceed 1MB in size A unit of time (units from UCUM). UnitsOfTime (required)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
frequency | Σ | 0..1 | positiveInt | There are no (further) constraints on this element Element IdMedicationRequest.dosageInstruction.timing.repeat.frequency Event occurs frequency times per period DefinitionThe number of times to repeat the action within the specified period. If frequencyMax is present, this element indicates the lower bound of the allowed range of the frequency. 32 bit number; for values larger than this, use decimal
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
frequencyMax | Σ | 0..1 | positiveInt | There are no (further) constraints on this element Element IdMedicationRequest.dosageInstruction.timing.repeat.frequencyMax Event occurs up to frequencyMax times per period DefinitionIf present, indicates that the frequency is a range - so to repeat between [frequency] and [frequencyMax] times within the period or period range. 32 bit number; for values larger than this, use decimal
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ | 0..1 | decimal | There are no (further) constraints on this element Element IdMedicationRequest.dosageInstruction.timing.repeat.period Event occurs frequency times per period DefinitionIndicates the duration of time over which repetitions are to occur; e.g. to express "3 times per day", 3 would be the frequency and "1 day" would be the period. If periodMax is present, this element indicates the lower bound of the allowed range of the period length. Do not use an IEEE type floating point type, instead use something that works like a true decimal, with inbuilt precision (e.g. Java BigInteger)
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
periodMax | Σ | 0..1 | decimal | There are no (further) constraints on this element Element IdMedicationRequest.dosageInstruction.timing.repeat.periodMax Upper limit of period (3-4 hours) DefinitionIf present, indicates that the period is a range from [period] to [periodMax], allowing expressing concepts such as "do this once every 3-5 days. Do not use an IEEE type floating point type, instead use something that works like a true decimal, with inbuilt precision (e.g. Java BigInteger)
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
periodUnit | Σ | 0..1 | codeBinding | There are no (further) constraints on this element Element IdMedicationRequest.dosageInstruction.timing.repeat.periodUnit s | min | h | d | wk | mo | a - unit of time (UCUM) DefinitionThe units of time for the period in UCUM units. Note that FHIR strings SHALL NOT exceed 1MB in size A unit of time (units from UCUM). UnitsOfTime (required)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
dayOfWeek | Σ | 0..* | codeBinding | There are no (further) constraints on this element Element IdMedicationRequest.dosageInstruction.timing.repeat.dayOfWeek mon | tue | wed | thu | fri | sat | sun DefinitionIf one or more days of week is provided, then the action happens only on the specified day(s). If no days are specified, the action is assumed to happen every day as otherwise specified. The elements frequency and period cannot be used as well as dayOfWeek.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
timeOfDay | Σ | 0..* | time | There are no (further) constraints on this element Element IdMedicationRequest.dosageInstruction.timing.repeat.timeOfDay Time of day for action DefinitionSpecified time of day for action to take place. When time of day is specified, it is inferred that the action happens every day (as filtered by dayofWeek) on the specified times. The elements when, frequency and period cannot be used as well as timeOfDay.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
when | Σ | 0..* | codeBinding | There are no (further) constraints on this element Element IdMedicationRequest.dosageInstruction.timing.repeat.when Code for time period of occurrence DefinitionAn approximate time period during the day, potentially linked to an event of daily living that indicates when the action should occur. Timings are frequently determined by occurrences such as waking, eating and sleep. When more than one event is listed, the event is tied to the union of the specified events. Real world event relating to the schedule. EventTiming (required)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
offset | Σ | 0..1 | unsignedInt | There are no (further) constraints on this element Element IdMedicationRequest.dosageInstruction.timing.repeat.offset Minutes from event (before or after) DefinitionThe number of minutes from the event. If the event code does not indicate whether the minutes is before or after the event, then the offset is assumed to be after the event. 32 bit number; for values larger than this, use decimal
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
code | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdMedicationRequest.dosageInstruction.timing.code BID | TID | QID | AM | PM | QD | QOD | + DefinitionA code for the timing schedule (or just text in code.text). Some codes such as BID are ubiquitous, but many institutions define their own additional codes. If a code is provided, the code is understood to be a complete statement of whatever is specified in the structured timing data, and either the code or the data may be used to interpret the Timing, with the exception that .repeat.bounds still applies over the code (and is not contained in the code). BID etc. are defined as 'at institutionally specified times'. For example, an institution may choose that BID is "always at 7am and 6pm". If it is inappropriate for this choice to be made, the code BID should not be used. Instead, a distinct organization-specific code should be used in place of the HL7-defined BID code and/or a structured representation should be used (in this case, specifying the two event times). Code for a known / defined timing pattern. TimingAbbreviation (preferred)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
asNeeded[x] | S Σ | 0..1 | Element IdMedicationRequest.dosageInstruction.asNeeded[x] Take "as needed" (for x) DefinitionThe In this case use the The Can express "as needed" without a reason by setting the Boolean = True. In this case the CodeableConcept is not populated. Or you can express "as needed" with a reason by including the CodeableConcept. In this case the Boolean is assumed to be True. If you set the Boolean to False, then the dose is given according to the schedule and is not "prn" or "as needed". A coded concept identifying the precondition that should be met or evaluated prior to consuming or administering a medication dose. For example "pain", "30 minutes prior to sexual intercourse", "on flare-up" etc. SNOMEDCTMedicationAsNeededReasonCodes (example)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
asNeededBoolean | boolean | There are no (further) constraints on this element Data Type | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
asNeededCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data Type | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
site | S Σ | 0..1 | CodeableConcept | Element IdMedicationRequest.dosageInstruction.site Body site to administer to DefinitionAny
A coded specification of the anatomic site where the medication first enters the body. If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension bodySite. May be a summary code, or a reference to a very precise definition of the location, or both. A coded concept describing the site location the medicine enters into or onto the body. SNOMEDCTAnatomicalStructureForAdministrationSiteCodes (example)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
route | S Σ | 0..1 | CodeableConcept | Element IdMedicationRequest.dosageInstruction.route How drug should enter body DefinitionAny
A code specifying the route or physiological path of administration of a therapeutic agent into or onto a patient's body. 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. A coded concept describing the route or physiological path of administration of a therapeutic agent into or onto the body of a subject. SNOMEDCTRouteCodes (example)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
method | S Σ | 0..1 | CodeableConcept | Element IdMedicationRequest.dosageInstruction.method Technique for administering medication DefinitionThe 999000041000001103 ePrescribing method simple reference set (foundation metadata concept) reference set collates the commonly used terms for Whilst a FHIR value-set for method does exist, together with two separate hierarchies within SNOMED-CT (Dose form administration method and Dosing instruction fragment), it is recommended to use the ePrescribing reference set in the first instance.
Use of synonymsIn most instances it is anticipated that the UK Preferred term should be the term applied to SNOMED CT concepts However for some cases, for example the anatomically correct SNOMED-CT term may not be easily understood by the patient or clinician, the use of a synonym may be preferred. Guidance for using terms that are not preferred terms is available within the published document Guidance on the use of CodeableConcept. A coded value indicating the method by which the medication is introduced into or onto the body. Most commonly used for injections. For examples, Slow Push; Deep IV. Terminologies used often pre-coordinate this term with the route and or form of administration. A coded concept describing the technique by which the medicine is administered. SNOMEDCTAdministrationMethodCodes (example)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
doseAndRate | Σ | 0..* | Element | Element IdMedicationRequest.dosageInstruction.doseAndRate Amount of medication administered DefinitionDose and Rate elements within the Dosage structure have been combined within the R4 standard, but their underlying use and purpose is the same as per R4. A dose or rate of medication can be described via one of the following methods. In both instances when considering Units of Measure note that UCUM is preferred. Sub-element:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element IdMedicationRequest.dosageInstruction.doseAndRate.type The kind of dose or rate specified DefinitionThe kind of dose or rate specified, for example, ordered or calculated. If the type is not populated, assume to be "ordered". 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. The kind of dose or rate specified. DoseAndRateType (example)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
dose[x] | Σ | 0..1 | There are no (further) constraints on this element Element IdMedicationRequest.dosageInstruction.doseAndRate.dose[x] Amount of medication per dose DefinitionAmount of medication per dose. The amount of therapeutic or other substance given at one administration event. Note that this specifies the quantity of the specified medication, not the quantity for each active ingredient(s). Each ingredient amount can be communicated in the Medication resource. For example, if one wants to communicate that a tablet was 375 mg, where the dose was one tablet, you can use the Medication resource to document that the tablet was comprised of 375 mg of drug XYZ. Alternatively if the dose was 375 mg, then you may only need to use the Medication resource to indicate this was a tablet. If the example were an IV such as dopamine and you wanted to communicate that 400mg of dopamine was mixed in 500 ml of some IV solution, then this would all be communicated in the Medication resource. If the administration is not intended to be instantaneous (rate is present or timing has a duration), this can be specified to convey the total amount to be administered over the period of time as indicated by the schedule e.g. 500 ml in dose, with timing used to convey that this should be done over 4 hours.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
doseRange | NHSDigitalRange | Data Type | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
doseQuantity | SimpleQuantity | Data Type | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
rate[x] | Σ | 0..1 | There are no (further) constraints on this element Element IdMedicationRequest.dosageInstruction.doseAndRate.rate[x] Amount of medication per unit of time DefinitionAmount of medication per unit of time. Identifies the speed with which the medication was or will be introduced into the patient. Typically the rate for an infusion e.g. 100 ml per 1 hour or 100 ml/hr. May also be expressed as a rate per unit of time e.g. 500 ml per 2 hours. Other examples: 200 mcg/min or 200 mcg/1 minute; 1 liter/8 hours. Sometimes, a rate can imply duration when expressed as total volume / duration (e.g. 500mL/2 hours implies a duration of 2 hours). However, when rate doesn't imply duration (e.g. 250mL/hour), then the timing.repeat.duration is needed to convey the infuse over time period. It is possible to supply both a rate and a doseQuantity to provide full details about how the medication is to be administered and supplied. If the rate is intended to change over time, depending on local rules/regulations, each change should be captured as a new version of the MedicationRequest with an updated rate, or captured with a new MedicationRequest with the new rate. It is possible to specify a rate over time (for example, 100 ml/hour) using either the rateRatio and rateQuantity. The rateQuantity approach requires systems to have the capability to parse UCUM grammer where ml/hour is included rather than a specific ratio where the time is specified as the denominator. Where a rate such as 500ml over 2 hours is specified, the use of rateRatio may be more semantically correct than specifying using a rateQuantity of 250 mg/hour.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
rateRatio | Ratio | There are no (further) constraints on this element Data Type | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
rateRange | Range | There are no (further) constraints on this element Data Type | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
rateQuantity | SimpleQuantity | There are no (further) constraints on this element Data Type | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
maxDosePerPeriod | S Σ I | 0..1 | Ratio | Element IdMedicationRequest.dosageInstruction.maxDosePerPeriod Upper limit on medication per unit of time Definition
Used to define a maxiumum dose over a given time period.
An example would be a Sumatriptan 6mg injection which can be repeated after an hour but not again over a 24 hour period. The The
A real-world example of where this would be required has not yet been identified.
Maximum dose per period of 12mg/24 hour
The maximum total quantity of a therapeutic substance that may be administered to a subject over the period of time. For example, 1000mg in 24 hours. This is intended for use as an adjunct to the dosage when there is an upper cap. For example "2 tablets every 4 hours to a maximum of 8/day".
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
maxDosePerAdministration | Σ I | 0..1 | SimpleQuantity | Element IdMedicationRequest.dosageInstruction.maxDosePerAdministration Upper limit on medication per administration Definition
Used to define a maximum dose for a single administration.
An example would be Anagrelide for which a single dose should not exceed 2.5 mg. The In many scenarios it is expected that the The
A real-world example of where this would be required has not yet been identified.
Maximum dose per administration of 2.5mg
The maximum total quantity of a therapeutic substance that may be administered to a subject per administration. This is intended for use as an adjunct to the dosage when there is an upper cap. For example, a body surface area related dose with a maximum amount, such as 1.5 mg/m2 (maximum 2 mg) IV over 5 – 10 minutes would have doseQuantity of 1.5 mg/m2 and maxDosePerAdministration of 2 mg.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
maxDosePerLifetime | Σ I | 0..1 | SimpleQuantity | Element IdMedicationRequest.dosageInstruction.maxDosePerLifetime Upper limit on medication per lifetime of the patient Definition
Used to define the maximum cumulative dose over the lifetime of a patient.
An example would be Daunorubicin which may have a maximum cumulative dose of 600mg/m2 (based on the size of the patient). The The
Note: If a
maxDosePerLifetime statement is required with a multi-sequence instruction, it is recommended to define it within the last / final sequence to ensure that the information is presented at the end of a the complete instruction, rather than th middle which could be overlooked.
Maximum dose over lifetime of the patient of 600 mg/m2
The maximum total quantity of a therapeutic substance that may be administered per lifetime of the subject. The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
dispenseRequest | S | 1..1 | BackboneElement | There are no (further) constraints on this element Element IdMedicationRequest.dispenseRequest Medication supply authorization DefinitionIndicates the specific details for the dispense or medication supply part of a medication request (also known as a Medication Prescription or Medication Order). Note that this information is not always sent with the order. There may be in some settings (e.g. hospitals) institutional or system support for completing the dispense details in the pharmacy department.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
id | 0..0 | System.String | There are no (further) constraints on this element Element IdMedicationRequest.dispenseRequest.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. System.String Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
extension | I | 1..* | Extension | Element IdMedicationRequest.dispenseRequest.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) Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
performerSiteType | S I | 1..1 | Extension(Coding) | Element IdMedicationRequest.dispenseRequest.extension:performerSiteType type of dispensing organisation Alternate namesextensions, user content DefinitionUsed to indicate type of pharmacist 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. https://fhir.nhs.uk/StructureDefinition/Extension-DM-PerformerSiteType Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
initialFill | 0..1 | BackboneElement | There are no (further) constraints on this element Element IdMedicationRequest.dispenseRequest.initialFill First fill details DefinitionIndicates the quantity or duration for the first dispense of the medication. If populating this element, either the quantity or the duration must be included.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
quantity | I | 0..1 | SimpleQuantity | There are no (further) constraints on this element Element IdMedicationRequest.dispenseRequest.initialFill.quantity First fill quantity DefinitionThe amount or quantity to provide as part of the first dispense. The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
duration | I | 0..1 | DurationBinding | There are no (further) constraints on this element Element IdMedicationRequest.dispenseRequest.initialFill.duration First fill duration DefinitionThe length of time that the first dispense is expected to last. The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator. Appropriate units for Duration. CommonUCUMCodesForDuration (extensible)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
dispenseInterval | I | 0..1 | DurationBinding | There are no (further) constraints on this element Element IdMedicationRequest.dispenseRequest.dispenseInterval Minimum period of time between dispenses DefinitionThe minimum period of time that must occur between dispenses of the medication. The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator. Appropriate units for Duration. CommonUCUMCodesForDuration (extensible)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
validityPeriod | S I | 0..1 | Period | Element IdMedicationRequest.dispenseRequest.validityPeriod Time period supply is authorized for DefinitionThe
Indicates when the Prescription becomes valid, and when it ceases to be a dispensable Prescription. It reflects the prescribers' perspective for the validity of the prescription. Dispenses must not be made against the prescription outside of this period. The lower-bound of the Dispensing Window signifies the earliest date that the prescription can be filled for the first time. If an upper-bound is not specified then the Prescription is open-ended or will default to a stale-date based on regulations.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
start | Σ I | 1..1 | dateTime | There are no (further) constraints on this element Element IdMedicationRequest.dispenseRequest.validityPeriod.start Starting time with inclusive boundary DefinitionThe start of the period. The boundary is inclusive. If the low element is missing, the meaning is that the low boundary is not known.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
end | Σ I | 0..1 | dateTime | There are no (further) constraints on this element Element IdMedicationRequest.dispenseRequest.validityPeriod.end End time with inclusive boundary, if not ongoing DefinitionThe end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time. The high value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has an end value of 2012-02-03.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
numberOfRepeatsAllowed | S | 0..1 | unsignedInt | Element IdMedicationRequest.dispenseRequest.numberOfRepeatsAllowed Number of refills authorized DefinitionAn integer indicating the number of times, in addition to the original dispense, (aka refills or repeats) that the patient can receive the prescribed medication. Usage Notes: This integer does not include the original order dispense. This means that if an order indicates dispense 30 tablets plus "3 repeats", then the order can be dispensed a total of 4 times and the patient can receive a total of 120 tablets. A prescriber may explicitly say that zero refills are permitted after the initial dispense. The number of repeat issues authorised if specified. For Example for a
Example for a
This will result in a total of three issues of the medication. If displaying "number of authorized fills", add 1 to this number.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
quantity | S I | 1..1 | SimpleQuantity | There are no (further) constraints on this element Element IdMedicationRequest.dispenseRequest.quantity Amount of medication to supply per dispense DefinitionThe amount that is to be dispensed for one fill. The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 1..1 | decimal | There are no (further) constraints on this element Element IdMedicationRequest.dispenseRequest.quantity.value Numerical value (with implicit precision) DefinitionThe value of the measured amount. The value includes an implicit precision in the presentation of the value. Precision is handled implicitly in almost all cases of measurement. The implicit precision in the value should always be honored. Monetary values have their own rules for handling precision (refer to standard accounting text books).
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
comparator | Σ ?! | 0..0 | codeBinding | There are no (further) constraints on this element Element IdMedicationRequest.dispenseRequest.quantity.comparator < | <= | >= | > - how to understand the value DefinitionNot allowed to be used in this context Need a framework for handling measures where the value is <5ug/L or >400mg/L due to the limitations of measuring methodology. Note that FHIR strings SHALL NOT exceed 1MB in size How the Quantity should be understood and represented. QuantityComparator (required)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
unit | Σ | 1..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.dispenseRequest.quantity.unit Unit representation DefinitionA human-readable form of the unit. There are many representations for units of measure and in many contexts, particular representations are fixed and required. I.e. mcg for micrograms. Note that FHIR strings SHALL NOT exceed 1MB in size
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ I | 0..1 | uri | There are no (further) constraints on this element Element IdMedicationRequest.dispenseRequest.quantity.system System that defines coded unit form DefinitionThe identification of the system that provides the coded form of the unit. Need to know the system that defines the coded form of the unit. see http://en.wikipedia.org/wiki/Uniform_resource_identifier
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
code | Σ | 1..1 | code | There are no (further) constraints on this element Element IdMedicationRequest.dispenseRequest.quantity.code Coded form of the unit DefinitionA computer processable form of the unit in some unit representation system. Need a computable form of the unit that is fixed across all forms. UCUM provides this for quantities, but SNOMED CT provides many units of interest. The preferred system is UCUM, but SNOMED CT can also be used (for customary units) or ISO 4217 for currency. The context of use may additionally require a code from a particular system.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
expectedSupplyDuration | S I | 0..1 | DurationBinding | Element IdMedicationRequest.dispenseRequest.expectedSupplyDuration Days Supply DefinitionThe The
In some situations, this attribute may be used instead of quantity to identify the amount supplied by how long it is expected to last, rather than the physical quantity issued, e.g. 90 days supply of medication (based on an ordered dosage). When possible, it is always better to specify quantity, as this tends to be more precise. expectedSupplyDuration will always be an estimate that can be influenced by external factors. Appropriate units for Duration. CommonUCUMCodesForDuration (extensible)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 1..1 | decimal | There are no (further) constraints on this element Element IdMedicationRequest.dispenseRequest.expectedSupplyDuration.value Numerical value (with implicit precision) DefinitionThe value of the measured amount. The value includes an implicit precision in the presentation of the value. Precision is handled implicitly in almost all cases of measurement. The implicit precision in the value should always be honored. Monetary values have their own rules for handling precision (refer to standard accounting text books).
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
comparator | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdMedicationRequest.dispenseRequest.expectedSupplyDuration.comparator < | <= | >= | > - how to understand the value DefinitionHow the value should be understood and represented - whether the actual value is greater or less than the stated value due to measurement issues; e.g. if the comparator is "<" , then the real value is < stated value. Need a framework for handling measures where the value is <5ug/L or >400mg/L due to the limitations of measuring methodology. Note that FHIR strings SHALL NOT exceed 1MB in size How the Quantity should be understood and represented. QuantityComparator (required)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
unit | Σ | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.dispenseRequest.expectedSupplyDuration.unit Unit representation DefinitionA human-readable form of the unit. There are many representations for units of measure and in many contexts, particular representations are fixed and required. I.e. mcg for micrograms. Note that FHIR strings SHALL NOT exceed 1MB in size
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ I | 0..1 | uri | There are no (further) constraints on this element Element IdMedicationRequest.dispenseRequest.expectedSupplyDuration.system System that defines coded unit form DefinitionThe identification of the system that provides the coded form of the unit. Need to know the system that defines the coded form of the unit. see http://en.wikipedia.org/wiki/Uniform_resource_identifier
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
code | Σ | 1..1 | codeFixed Value | Element IdMedicationRequest.dispenseRequest.expectedSupplyDuration.code Coded form of the unit DefinitionA computer processable form of the unit in some unit representation system. Need a computable form of the unit that is fixed across all forms. UCUM provides this for quantities, but SNOMED CT provides many units of interest. The preferred system is UCUM, but SNOMED CT can also be used (for customary units) or ISO 4217 for currency. The context of use may additionally require a code from a particular system.
d
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
performer | S I | 0..1 | Reference(NHSDigitalOrganizationODS) | Element IdMedicationRequest.dispenseRequest.performer Intended dispenser DefinitionFor non token based prescriptions the destination pharmacy MUST be recorded in the dispenseRequest.performer.identifier and a identifier reference (not a resource reference) with an ANANA/ODS Code MUST used. The extension https://fhir.nhs.uk/StructureDefinition/Extension-DM-PerformerSiteType MUST be present. Patients pharmacy preferences may be sourced from PDS. Patients pharmacy preferences may be overriden by an 'one-off pharmacy nomination' by populating the dispenseRequest.performer.identifier with the ODS/ANANA code of the destination pharmacy.
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. Reference(NHSDigitalOrganizationODS) Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
extension | I | 0..* | Extension | Element IdMedicationRequest.dispenseRequest.performer.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) Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
dispensingPractitioner | S I | 0..1 | Extension(Reference(NHSDigitalPractitionerRole)) | Element IdMedicationRequest.dispenseRequest.performer.extension:dispensingPractitioner practitioner who released(/downloaded) the prescription Alternate namesextensions, user content DefinitionDetails of the dispenser who is actioning the MedicationRequest
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. Extension(Reference(NHSDigitalPractitionerRole)) Extension URLhttps://fhir.nhs.uk/StructureDefinition/Extension-DM-DispensingPerformer Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
reference | Σ I | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.dispenseRequest.performer.reference Literal reference, Relative, internal or absolute URL DefinitionA 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. 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.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdMedicationRequest.dispenseRequest.performer.type Type the reference refers to (e.g. "Patient") DefinitionThe 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). 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. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
identifier | Σ | 1..1 | Identifier | There are no (further) constraints on this element Element IdMedicationRequest.dispenseRequest.performer.identifier Logical reference, when literal reference is not known DefinitionAn 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. 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).
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdMedicationRequest.dispenseRequest.performer.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdMedicationRequest.dispenseRequest.performer.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 1..1 | uriFixed Value | Element IdMedicationRequest.dispenseRequest.performer.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
https://fhir.nhs.uk/Id/ods-organization-code
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 1..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.dispenseRequest.performer.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdMedicationRequest.dispenseRequest.performer.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdMedicationRequest.dispenseRequest.performer.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.dispenseRequest.performer.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. 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.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
substitution | S | 1..1 | BackboneElement | Element IdMedicationRequest.substitution Any restrictions on medication substitution DefinitionWithin UK healthcare, substitution is not the norm and so this element will normally be set to a default of Substitution being set to false is a mandatory requirement for EPS.. Substituition is a mandatory requirement for EPS. Important Note:Within UK healthcare, substitution is not the norm so the international FHIR definition where "_If nothing is specified substitution may be done._" does not align with UK healthcare prescribing best practice.It could be unwise to assume all UK implementations will prevent substitution if not explicitly stated, especially if the same clinical system has been previously implemented outside the UK. UK Core has profiled this element as MANDATORY and MUST have a default boolean value of Allowing substitutionWhere substitution to be be allowed, set to
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
allowed[x] | 1..1 | There are no (further) constraints on this element Element IdMedicationRequest.substitution.allowed[x] Whether substitution is allowed or not DefinitionThe purpose of this element is to allow the prescriber to dispense a different drug from what was prescribed. This element is labeled as a modifier because whether substitution is allow or not, it cannot be ignored. Identifies the type of substitution allowed. v3.ActSubstanceAdminSubstitutionCode (example)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
allowedBoolean | boolean | Data Type | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
reason | 0..1 | CodeableConcept | There are no (further) constraints on this element Element IdMedicationRequest.substitution.reason Why should (not) substitution be made DefinitionIndicates the reason for the substitution, or why substitution must or must not be performed. 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. A coded concept describing the reason that a different medication should (or should not) be substituted from what was prescribed. v3.SubstanceAdminSubstitutionReason (example)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
priorPrescription | I | 0..1 | Reference(UK Core MedicationRequest) | There are no (further) constraints on this element Element IdMedicationRequest.priorPrescription An order/prescription that is being replaced DefinitionA link to a resource representing an earlier order related order or prescription. 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. Reference(UK Core MedicationRequest) Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
reference | Σ I | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.priorPrescription.reference Literal reference, Relative, internal or absolute URL DefinitionA 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. 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.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdMedicationRequest.priorPrescription.type Type the reference refers to (e.g. "Patient") DefinitionThe 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). 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. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdMedicationRequest.priorPrescription.identifier Logical reference, when literal reference is not known DefinitionAn 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. 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).
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdMedicationRequest.priorPrescription.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdMedicationRequest.priorPrescription.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdMedicationRequest.priorPrescription.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patient Mappings
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.priorPrescription.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdMedicationRequest.priorPrescription.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdMedicationRequest.priorPrescription.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.priorPrescription.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. 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.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
detectedIssue | I | 0..* | Reference(DetectedIssue) | There are no (further) constraints on this element Element IdMedicationRequest.detectedIssue Clinical Issue with action Alternate namesContraindication, Drug Utilization Review (DUR), Alert DefinitionIndicates an actual or potential clinical issue with or between one or more active or proposed clinical actions for a patient; e.g. Drug-drug interaction, duplicate therapy, dosage alert etc. This element can include a detected issue that has been identified either by a decision support system or by a clinician and may include information on the steps that were taken to address the issue.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
reference | Σ I | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.detectedIssue.reference Literal reference, Relative, internal or absolute URL DefinitionA 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. 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.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdMedicationRequest.detectedIssue.type Type the reference refers to (e.g. "Patient") DefinitionThe 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). 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. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdMedicationRequest.detectedIssue.identifier Logical reference, when literal reference is not known DefinitionAn 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. 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).
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdMedicationRequest.detectedIssue.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdMedicationRequest.detectedIssue.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdMedicationRequest.detectedIssue.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patient Mappings
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.detectedIssue.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdMedicationRequest.detectedIssue.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdMedicationRequest.detectedIssue.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.detectedIssue.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. 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.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
eventHistory | I | 0..* | Reference(NHSDigitalProvenance) | Element IdMedicationRequest.eventHistory A list of events of interest in the lifecycle DefinitionLinks to Provenance records for past versions of this resource or fulfilling request or event resources that identify key state transitions or updates that are likely to be relevant to a user looking at the current version of the resource. 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.). Reference(NHSDigitalProvenance) Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
reference | Σ I | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.eventHistory.reference Literal reference, Relative, internal or absolute URL DefinitionA 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. 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.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdMedicationRequest.eventHistory.type Type the reference refers to (e.g. "Patient") DefinitionThe 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). 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. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdMedicationRequest.eventHistory.identifier Logical reference, when literal reference is not known DefinitionAn 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. 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).
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdMedicationRequest.eventHistory.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdMedicationRequest.eventHistory.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdMedicationRequest.eventHistory.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patient Mappings
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.eventHistory.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdMedicationRequest.eventHistory.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdMedicationRequest.eventHistory.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.eventHistory.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. 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.
|
Differential from UK Core MedicationRequest
MedicationRequest | I | MedicationRequest | Element IdMedicationRequest Ordering of medication for patient or group Alternate namesPrescription, Order DefinitionAn order or request for both supply of the medication and the instructions for administration of the medication to a patient. The resource is called "MedicationRequest" rather than "MedicationPrescription" or "MedicationOrder" to generalize the use across inpatient and outpatient settings, including care plans, etc., and to harmonize with workflow patterns.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
extension | I | 1..* | Extension | Element IdMedicationRequest.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 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. 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) Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
medicationRepeatInformation | S I | 0..1 | Extension(Complex) | Element IdMedicationRequest.extension:medicationRepeatInformation Continous and Continuous Repeat Dispensing Alternate namesextensions, user content DefinitionThis extension MUST be present for
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. Extension(Complex) Extension URLhttps://fhir.hl7.org.uk/StructureDefinition/Extension-UKCore-MedicationRepeatInformation Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
responsiblePractitioner | S I | 0..1 | Extension(Reference(NHSDigitalPractitionerRole)) | Element IdMedicationRequest.extension:responsiblePractitioner Responsible Practitioner for the prescription Alternate namesextensions, user content DefinitionMust only be populated if the
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. Extension(Reference(NHSDigitalPractitionerRole)) Extension URLhttps://fhir.nhs.uk/StructureDefinition/Extension-DM-ResponsiblePractitioner Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
prescriptionEndorsement | S I | 0..* | Extension(CodeableConcept) | Element IdMedicationRequest.extension:prescriptionEndorsement NHS BSA Prescription Endorsements Alternate namesextensions, user content DefinitionThe codes are contained in the valueset
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. https://fhir.nhs.uk/StructureDefinition/Extension-DM-PrescriptionEndorsement Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
prescriptionTaskStatusReason | S I | 0..* | Extension(Complex) | Element IdMedicationRequest.extension:prescriptionTaskStatusReason Prescription task status reason Alternate namesextensions, user content DefinitionThe status history within EPS is primarily a technical Status and the statusReason will reflect current clinical status of the order. 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. Extension(Complex) Extension URLhttps://fhir.nhs.uk/StructureDefinition/Extension-DM-PrescriptionStatusHistory Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
NHSBSAprescriptionType | S I | 1..1 | Extension(Coding) | Element IdMedicationRequest.extension:NHSBSAprescriptionType NHS BSA Prescription Type Alternate namesextensions, user content DefinitionThe vocabulary for the ‘PrescriptionType’ vocabulary is defined within the NHSBSA Overprint Specification. The System must populate the ‘PrescriptionType’ attribute for the appropriate combination of prescriber and care setting. Retired codes within this vocabulary must not be used
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. https://fhir.nhs.uk/StructureDefinition/Extension-DM-PrescriptionType Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
controlledDrug | S I | 0..1 | Extension(Complex) | Element IdMedicationRequest.extension:controlledDrug Optional Controlled Drug Extensions Alternate namesextensions, user content DefinitionThe table below summarises the EPS requirements for the CD schedules. The terms “Hand signature” and “Electronic signature” expressed in the table are shortened references to the legal definition of signature requirements within government legislation.
It is a legal requirement to state the prescribed quantity as words in the
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. Extension(Complex) Extension URLhttps://fhir.nhs.uk/StructureDefinition/Extension-DM-ControlledDrug Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
dispensingInformation | S I | 0..1 | Extension(Complex) | Element IdMedicationRequest.extension:dispensingInformation For EPS use only Alternate namesextensions, user content DefinitionThis extension is used in
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. Extension(Complex) Extension URLhttps://fhir.nhs.uk/StructureDefinition/Extension-EPS-DispensingInformation Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
identifier | S | 1..* | Identifier | Element IdMedicationRequest.identifier Each MedicationRequest MUST be identified by an Universal Unique Identifiers (UUIDs) with a system of https://fhir.nhs.uk/Id/prescription-order-item-number DefinitionUUID example (for illustration purposes only); a54219b8-f741-4c47-b662-e4f8dfa49ab6
This is a business identifier, not a resource identifier. Unordered, Open, by system(Value) Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(All Slices) | There are no (further) constraints on this element | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdMedicationRequest.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdMedicationRequest.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdMedicationRequest.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patient Mappings
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 0..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdMedicationRequest.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdMedicationRequest.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
prescriptionOrderItem | 1..1 | Identifier | Element IdMedicationRequest.identifier:prescriptionOrderItem Prescription Order Item DefinitionUnique Id of the MedicationRequest within EPS This is a business identifier, not a resource identifier.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdMedicationRequest.identifier:prescriptionOrderItem.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdMedicationRequest.identifier:prescriptionOrderItem.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 1..1 | uriFixed Value | Element IdMedicationRequest.identifier:prescriptionOrderItem.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
https://fhir.nhs.uk/Id/prescription-order-item-number
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 1..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.identifier:prescriptionOrderItem.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdMedicationRequest.identifier:prescriptionOrderItem.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdMedicationRequest.identifier:prescriptionOrderItem.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
status | S Σ ?! | 1..1 | codeBinding | Element IdMedicationRequest.status active | cancelled | stopped DefinitionA code specifying the current state of the order. Generally, this will be active or completed state.
Logical medicationRequest status transitionsThis state transition diagram is an enhancement over the generic State Machine defined within the FHIR specification. It includes the status values associated with a medication request with transitions applicable to a UK implementation. ![]() This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid. A coded concept specifying the state of the prescribing event. Describes the lifecycle of the prescription. medicationrequest Status (required)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
statusReason | S | 0..1 | CodeableConceptBinding | Element IdMedicationRequest.statusReason Reason for current status DefinitionThis is generally only used for exception statuses such as This is mandatory for 'prescription-order-update' messages.
This is generally only used for "exception" statuses such as "suspended" or "cancelled". The reason why the MedicationRequest was created at all is captured in reasonCode, not here. Identifies the reasons for a given status. MedicationRequestStatusReason (required)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
coding | Σ | 1..1 | Coding | There are no (further) constraints on this element Element IdMedicationRequest.statusReason.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. 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.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 1..1 | uri | There are no (further) constraints on this element Element IdMedicationRequest.statusReason.coding.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 IdMedicationRequest.statusReason.coding.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 | Σ | 1..1 | code | There are no (further) constraints on this element Element IdMedicationRequest.statusReason.coding.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 | Σ | 1..1 | string | There are no (further) constraints on this element Element IdMedicationRequest.statusReason.coding.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 IdMedicationRequest.statusReason.coding.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.
|