OrderedMedications
| Canonical URL | https://fhir.synapxe.sg/StructureDefinition/profile-bundle-medicationrequest |
|---|---|
| Version | 1.2.3 |
| Published by | Synapxe |
| Status | Active |
| Description | A Bundle of MedicationRequest resources will be used to store one or more medication orders or requests for both supply of the medication and the instructions for administration of the medication to a patient. The resource is represented as a Bundle containing multiple MedicationRequest resources. |
| Bundle | C | Bundle | |
| id | Σ | 0..1 | id |
| meta | Σ | 0..1 | Meta |
| implicitRules | Σ ?! | 0..1 | uri |
| language | 0..1 | codeBinding | |
| identifier | Σ C | 0..0 | Identifier |
| type | Σ C | 1..1 | codeBindingPattern |
| timestamp | Σ C | 0..0 | instant |
| total | Σ C | 0..0 | unsignedInt |
| link | Σ C | 0..0 | BackboneElement |
| entry | Σ C | 1..* | BackboneElement |
| id | 0..0 | string | |
| extension | C | 0..0 | Extension |
| modifierExtension | Σ ?! C | 0..0 | Extension |
| link | Σ | 0..0 | see (link) |
| fullUrl | Σ C | 1..1 | uri |
| resource | Σ C | 1..1 | MedicationRequest |
| id | Σ | 0..1 | id |
| meta | Σ | 0..1 | Meta |
| implicitRules | Σ ?! | 0..1 | uri |
| language | 0..1 | codeBinding | |
| text | C | 0..1 | Narrative |
| contained | C | 0..* | Resource |
| medication | C | 0..1 | Medication |
| extension | C | 0..* | Extension |
| orderingLocation | C | 0..1 | Extension(CodeableConcept) |
| orderSetConnectingTerm | C | 0..1 | Extension(CodeableConcept) |
| changesMade | C | 0..* | Extension(Complex) |
| authorizer | C | 0..* | Extension(Reference(Practitioner)) |
| orderingInstitution | C | 0..1 | Extension(Reference(Organization)) |
| modifierExtension | Σ ?! C | 0..0 | Extension |
| identifier | C | 1..* | Identifier |
| (All Slices) | |||
| id | 0..0 | string | |
| extension | C | 0..0 | Extension |
| use | Σ ?! | 0..0 | codeBinding |
| type | Σ | 0..0 | CodeableConceptBinding |
| system | Σ | 1..1 | uri |
| value | Σ C | 1..1 | string |
| period | Σ C | 0..0 | Period |
| assigner | Σ C | 0..0 | Reference(Organization) |
| recordIdentifier | C | 0..1 | IdentifierRecordID |
| orderID | C | 1..1 | IdentifierOrderNo |
| sourceGroupingID | C | 1..1 | IdentifierSourceGroupingID |
| sequenceNo | C | 0..1 | IdentifierSequenceNo |
| basedOn | Σ C | 0..0 | Reference(Encounter) |
| priorPrescription | C | 0..0 | Reference(MedicationRequest) |
| groupIdentifier | Σ C | 0..1 | Identifier |
| id | 0..0 | string | |
| extension | C | 0..0 | Extension |
| use | Σ ?! | 0..0 | codeBinding |
| type | Σ | 0..0 | CodeableConceptBinding |
| system | Σ | 1..1 | uriPattern |
| value | Σ C | 1..1 | string |
| period | Σ C | 0..0 | Period |
| assigner | Σ C | 0..0 | Reference(Organization) |
| status | Σ ?! | 1..1 | codeBinding |
| statusReason | 0..1 | CodeableConceptBinding | |
| id | 0..0 | string | |
| extension | C | 0..0 | Extension |
| coding | Σ C | 1..* | Coding |
| id | 0..0 | string | |
| extension | C | 0..0 | Extension |
| system | Σ | 1..1 | uri |
| version | Σ | 0..1 | string |
| code | Σ C | 1..1 | code |
| display | Σ C | 1..1 | string |
| userSelected | Σ | 0..0 | boolean |
| text | Σ | 0..1 | string |
| statusChanged | 0..1 | dateTime | |
| intent | Σ ?! | 1..1 | codeBindingPattern |
| category | 1..1 | CodeableConceptBinding | |
| id | 0..0 | string | |
| extension | C | 0..0 | Extension |
| coding | Σ C | 1..* | Coding |
| id | 0..0 | string | |
| extension | C | 0..0 | Extension |
| system | Σ | 1..1 | uri |
| version | Σ | 0..1 | string |
| code | Σ C | 1..1 | code |
| display | Σ C | 1..1 | string |
| userSelected | Σ | 0..0 | boolean |
| text | Σ | 0..1 | string |
| priority | Σ | 0..0 | codeBinding |
| doNotPerform | Σ ?! | 0..0 | boolean |
| medication | Σ | 1..1 | CodeableReference(Medication) |
| id | 0..0 | string | |
| extension | C | 0..0 | Extension |
| concept | Σ | 0..0 | CodeableConcept |
| reference | Σ C | 1..1 | Reference(Medication) |
| id | 0..0 | string | |
| extension | C | 0..0 | Extension |
| reference | Σ C | 0..1 | string |
| type | Σ | 0..0 | uriBinding |
| identifier | Σ C | 0..1 | Identifier |
| id | 0..0 | string | |
| extension | C | 0..0 | Extension |
| use | Σ ?! | 0..0 | codeBinding |
| type | Σ | 0..0 | CodeableConceptBinding |
| system | Σ | 1..1 | uri |
| value | Σ C | 1..1 | string |
| period | Σ C | 0..0 | Period |
| assigner | Σ C | 0..0 | Reference(Organization) |
| display | Σ C | 0..1 | string |
| subject | Σ C | 1..1 | Reference(Patient) |
| id | 0..0 | string | |
| extension | C | 0..0 | Extension |
| reference | Σ C | 0..0 | string |
| type | Σ | 1..1 | uriBindingPattern |
| identifier | Σ C | 1..1 | Identifier |
| id | 0..0 | string | |
| extension | C | 0..0 | Extension |
| use | Σ ?! | 0..0 | codeBinding |
| type | Σ | 0..0 | CodeableConceptBinding |
| system | Σ | 1..1 | uri |
| value | Σ C | 1..1 | string |
| period | Σ C | 0..0 | Period |
| assigner | Σ C | 0..0 | Reference(Organization) |
| display | Σ C | 0..0 | string |
| informationSource | C | 0..0 | Reference(Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) |
| encounter | C | 0..1 | Reference(Encounter) |
| supportingInformation | C | 0..0 | Reference(Resource) |
| authoredOn | Σ | 1..1 | dateTime |
| requester | Σ C | 1..1 | Reference(Practitioner) |
| id | 0..0 | string | |
| extension | C | 0..0 | Extension |
| reference | Σ C | 0..0 | string |
| type | Σ | 1..1 | uriBindingPattern |
| identifier | Σ C | 1..1 | IdentifierDCR, IdentifierMCR, IdentifierPRN, IdentifierSNB |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| use | Σ ?! | 0..1 | codeBinding |
| type | Σ | 0..1 | CodeableConceptBinding |
| system | Σ | 0..1 | uri |
| value | Σ C | 0..1 | string |
| period | Σ C | 0..1 | Period |
| assigner | Σ C | 0..1 | Reference(Organization) |
| display | Σ C | 0..1 | string |
| reported | Σ | 0..0 | boolean |
| performerType | Σ | 0..0 | CodeableConceptBinding |
| performer | C | 0..0 | Reference(Practitioner) |
| device | 0..0 | CodeableReference(DeviceDefinition) | |
| recorder | C | 0..0 | Reference(Practitioner) |
| reason | 0..1 | CodeableReference(Condition | Observation) | |
| id | 0..0 | string | |
| extension | C | 0..0 | Extension |
| concept | Σ | 1..1 | CodeableConceptBinding |
| id | 0..0 | string | |
| extension | C | 0..0 | Extension |
| coding | Σ C | 1..* | Coding |
| id | 0..0 | string | |
| extension | C | 0..0 | Extension |
| system | Σ | 1..1 | uri |
| version | Σ | 0..0 | string |
| code | Σ C | 1..1 | code |
| display | Σ C | 1..1 | string |
| userSelected | Σ | 0..0 | boolean |
| text | Σ | 0..1 | string |
| reference | Σ C | 0..1 | Reference |
| courseOfTherapyType | 0..0 | CodeableConceptBinding | |
| insurance | C | 0..0 | Reference(ClaimResponse | Coverage) |
| note | 0..1 | Annotation | |
| renderedDosageInstruction | 0..0 | markdown | |
| effectiveDosePeriod | C | 0..1 | Period |
| id | 0..0 | string | |
| extension | C | 0..0 | Extension |
| start | Σ C | 1..1 | dateTime |
| end | Σ C | 0..1 | dateTime |
| dosageInstruction | C | 1..1 | Dosage |
| id | 0..0 | string | |
| extension | C | 0..0 | Extension |
| modifierExtension | Σ ?! C | 0..0 | Extension |
| sequence | Σ | 0..1 | integer |
| text | Σ | 0..1 | string |
| additionalInstruction | Σ | 0..1 | CodeableConcept |
| id | 0..0 | string | |
| extension | C | 0..0 | Extension |
| coding | Σ C | 0..0 | Coding |
| text | Σ | 1..1 | string |
| patientInstruction | Σ | 0..0 | string |
| timing | Σ | 0..1 | Timing |
| id | 0..0 | string | |
| extension | C | 0..0 | Extension |
| modifierExtension | Σ ?! C | 0..0 | Extension |
| event | Σ | 0..1 | dateTime |
| repeat | Σ C | 0..1 | Element |
| id | 0..0 | string | |
| extension | C | 0..0 | Extension |
| bounds[x] | Σ | 0..1 | |
| boundsPeriod | Period | ||
| count | Σ C | 0..1 | positiveInt |
| countMax | Σ C | 0..1 | positiveInt |
| duration | Σ C | 0..1 | decimal |
| durationMax | Σ C | 0..1 | decimal |
| durationUnit | Σ C | 0..1 | codeBinding |
| frequency | Σ | 0..1 | positiveInt |
| frequencyMax | Σ | 0..1 | positiveInt |
| period | Σ C | 0..1 | decimal |
| periodMax | Σ C | 0..1 | decimal |
| periodUnit | Σ C | 0..1 | codeBinding |
| dayOfWeek | Σ | 0..1 | codeBinding |
| timeOfDay | Σ C | 0..1 | time |
| when | Σ C | 0..1 | codeBinding |
| offset | Σ C | 0..1 | unsignedInt |
| code | Σ | 0..1 | CodeableConceptBinding |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| coding | Σ C | 0..* | Coding |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| system | Σ | 0..1 | uri |
| version | Σ | 0..1 | string |
| code | Σ C | 0..1 | code |
| display | Σ C | 0..1 | string |
| userSelected | Σ | 0..0 | boolean |
| text | Σ | 0..1 | string |
| asNeeded | Σ C | 0..0 | boolean |
| asNeededFor | Σ C | 0..1 | CodeableConcept |
| id | 0..1 | string | |
| extension | C | 0..0 | Extension |
| coding | Σ C | 0..0 | Coding |
| text | Σ | 1..1 | string |
| site | Σ | 0..0 | CodeableConcept |
| route | Σ | 0..1 | CodeableConceptBinding |
| id | 0..0 | string | |
| extension | C | 0..0 | Extension |
| coding | Σ C | 1..* | Coding |
| id | 0..0 | string | |
| extension | C | 0..0 | Extension |
| system | Σ | 1..1 | uri |
| version | Σ | 0..1 | string |
| code | Σ C | 1..1 | code |
| display | Σ C | 1..1 | string |
| userSelected | Σ | 0..0 | boolean |
| text | Σ | 0..1 | string |
| method | Σ | 0..0 | CodeableConcept |
| doseAndRate | Σ | 0..* | Element |
| id | 0..0 | string | |
| extension | C | 0..0 | Extension |
| type | Σ | 0..0 | CodeableConcept |
| dose[x] | Σ | 1..1 | |
| doseQuantity | SimpleQuantity | ||
| doseRange | Range | ||
| rate[x] | Σ | 0..1 | |
| rateQuantity | SimpleQuantity | ||
| rateRange | Range | ||
| rateRatio | Ratio | ||
| maxDosePerPeriod | Σ C | 0..0 | Ratio |
| maxDosePerAdministration | Σ C | 0..0 | SimpleQuantity |
| maxDosePerLifetime | Σ C | 0..0 | SimpleQuantity |
| dispenseRequest | 0..1 | BackboneElement | |
| id | 0..0 | string | |
| extension | C | 0..0 | Extension |
| modifierExtension | Σ ?! C | 0..0 | Extension |
| initialFill | 0..0 | BackboneElement | |
| dispenseInterval | C | 0..0 | Duration |
| validityPeriod | C | 0..0 | Period |
| numberOfRepeatsAllowed | 0..0 | unsignedInt | |
| quantity | C | 0..1 | SimpleQuantity |
| id | 0..0 | string | |
| extension | C | 0..0 | Extension |
| value | Σ | 1..1 | decimal |
| comparator | Σ ?! | 0..0 | codeBinding |
| unit | Σ | 1..1 | string |
| system | Σ C | 1..1 | uri |
| code | Σ C | 1..1 | code |
| expectedSupplyDuration | C | 0..0 | Duration |
| dispenser | C | 0..1 | Reference(Location) |
| id | 0..0 | string | |
| extension | C | 0..0 | Extension |
| reference | Σ C | 0..0 | string |
| type | Σ | 1..1 | uriBindingPattern |
| identifier | Σ C | 1..1 | Identifier |
| id | 0..0 | string | |
| extension | C | 0..0 | Extension |
| use | Σ ?! | 0..0 | codeBinding |
| type | Σ | 0..0 | CodeableConceptBinding |
| system | Σ | 1..1 | uri |
| value | Σ C | 1..1 | string |
| period | Σ C | 0..0 | Period |
| assigner | Σ C | 0..0 | Reference(Organization) |
| display | Σ C | 1..1 | string |
| dispenserInstruction | 0..0 | Annotation | |
| doseAdministrationAid | 0..0 | CodeableConcept | |
| substitution | 0..0 | BackboneElement | |
| eventHistory | C | 0..0 | Reference(Provenance) |
| search | Σ C | 0..0 | BackboneElement |
| request | Σ C | 0..1 | BackboneElement |
| id | 0..0 | string | |
| extension | C | 0..0 | Extension |
| modifierExtension | Σ ?! C | 0..0 | Extension |
| method | Σ C | 1..1 | codeBinding |
| url | Σ | 1..1 | uri |
| ifNoneMatch | Σ | 0..1 | string |
| ifModifiedSince | Σ | 0..1 | instant |
| ifMatch | Σ | 0..1 | string |
| ifNoneExist | Σ | 0..1 | string |
| response | Σ C | 0..1 | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| status | Σ | 1..1 | string |
| location | Σ | 0..1 | uri |
| etag | Σ | 0..1 | string |
| lastModified | Σ | 0..1 | instant |
| outcome | Σ | 0..1 | Resource |
| signature | Σ | 0..0 | Signature |
| issues | Σ C | 0..0 | OperationOutcome |
| Bundle | C | |
| Short | Contains a collection of resources | |
| Definition | A container for a collection of resources. | |
| Cardinality | 0..* | |
| Constraints |
| |
| Mappings |
| |
| Bundle.id | Σ | |
| Short | Logical id of this artifact | |
| Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. | |
| Cardinality | 0..1 | |
| Type | id | |
| Summary | True | |
| Comments | Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.meta | Σ | |
| Short | Metadata about a resource | |
| Definition | The metadata about a resource. This is content in the resource that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource. | |
| Cardinality | 0..1 | |
| Type | Meta | |
| Summary | True | |
| Constraints |
| |
| Mappings |
| |
| Bundle.implicitRules | Σ ?! | |
| Short | A set of rules under which this content was created | |
| Definition | A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. | |
| Cardinality | 0..1 | |
| Type | uri | |
| Modifier | True | |
| Summary | True | |
| Comments | Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.language | ||
| Short | Language of the resource content | |
| Definition | The base language in which the resource is written. | |
| Cardinality | 0..1 | |
| Type | code | |
| Binding | IETF language tag for a human language | |
| Comments | Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). | |
| Constraints |
| |
| Mappings |
| |
| Bundle.identifier | Σ C | |
| Short | Persistent identifier for the bundle | |
| Definition | A persistent identifier for the bundle that won't change as a bundle is copied from server to server. | |
| Cardinality | 0..0 | |
| Type | Identifier | |
| Summary | True | |
| Comments | Persistent identity generally only matters for batches of type Document, Message, and Collection. It would not normally be populated for search and history results and servers ignore Bundle.identifier when processing batches and transactions. For Documents the .identifier SHALL be populated such that the .identifier is globally unique. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: bdl-9 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.type | Σ C | |
| Short | document | message | transaction | transaction-response | batch | batch-response | history | searchset | collection | subscription-notification | |
| Definition | Indicates the purpose of this bundle - how it is intended to be used. | |
| Cardinality | 1..1 | |
| Type | code | |
| Binding | Indicates the purpose of a bundle - how it is intended to be used. | |
| Summary | True | |
| Comments | It's possible to use a bundle for other purposes (e.g. a document can be accepted as a transaction). This is primarily defined so that there can be specific rules for some of the bundle types. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: bdl-1, bdl-2, bdl-3a, bdl-3b, bdl-3c, bdl-3d, bdl-7, bdl-9, bdl-10, bdl-11, bdl-12, bdl-13, bdl-14, bdl-15, bdl-17, bdl-18 | |
| Constraints |
| |
| Pattern | transaction | |
| Mappings |
| |
| Bundle.timestamp | Σ C | |
| Short | When the bundle was assembled | |
| Definition | The date/time that the bundle was assembled - i.e. when the resources were placed in the bundle. | |
| Cardinality | 0..0 | |
| Type | instant | |
| Summary | True | |
| Comments | For many bundles, the timestamp is equal to .meta.lastUpdated, because they are not stored (e.g. search results). When a bundle is placed in a persistent store, .meta.lastUpdated will be usually be changed by the server. When the bundle is a message, a middleware agent altering the message (even if not stored) SHOULD update .meta.lastUpdated. .timestamp is used to track the original time of the Bundle, and SHOULD be populated. Usage:
The timestamp value should be greater than the lastUpdated and other timestamps in the resources in the bundle, and it should be equal or earlier than the .meta.lastUpdated on the Bundle itself. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: bdl-10 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.total | Σ C | |
| Short | If search, the total number of matches | |
| Definition | If a set of search matches, this is the (potentially estimated) total number of entries of type 'match' across all pages in the search. It does not include search.mode = 'include' or 'outcome' entries and it does not provide a count of the number of entries in the Bundle. | |
| Cardinality | 0..0 | |
| Type | unsignedInt | |
| Summary | True | |
| Comments | Only used if the bundle is a search result set. The total does not include resources such as OperationOutcome and included resources, only the total number of matching resources. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: bdl-1 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.link | Σ C | |
| Short | Links related to this Bundle | |
| Definition | A series of links that provide context to this bundle. | |
| Cardinality | 0..0 | |
| Type | BackboneElement | |
| Summary | True | |
| Comments | Both Bundle.link and Bundle.entry.link are defined to support providing additional context when Bundles are used (e.g. HATEOAS). Bundle.entry.link corresponds to links found in the HTTP header if the resource in the entry was read directly. This specification defines some specific uses of Bundle.link for searching and paging, but no specific uses for Bundle.entry.link, and no defined function in a transaction - the meaning is implementation specific. The behavior of navigation link types (next/prev/first/last) are well defined for searchset and history Bundles but are not currently defined for other types. Implementers who choose to use such link relationships for other bundle types will need to negotiate behavior with their interoperability partners. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: bdl-18 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.link.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..1 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.link.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..* | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.link.modifierExtension | Σ ?! C | |
| Short | Extensions that cannot be ignored even if unrecognized | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | |
| Cardinality | 0..* | |
| Type | Extension | |
| Modifier | True | |
| Summary | True | |
| Alias | extensions, user content, modifiers | |
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.link.relation | Σ C | |
| Short | See http://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1 | |
| Definition | A name which details the functional use for this link - see http://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1. | |
| Cardinality | 1..1 | |
| Type | code | |
| Binding | ||
| Summary | True | |
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |
| Conditions | The cardinality or value of this element may be affected by these constraints: bdl-18 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.link.url | Σ C | |
| Short | Reference details for the link | |
| Definition | The reference details for the link. | |
| Cardinality | 1..1 | |
| Type | uri | |
| Summary | True | |
| Comments | see http://en.wikipedia.org/wiki/Uniform_resource_identifier | |
| Conditions | The cardinality or value of this element may be affected by these constraints: bdl-18 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry | Σ C | |
| Short | Entry in the bundle - will have a resource or information | |
| Definition | An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only). | |
| Cardinality | 1..* | |
| Type | BackboneElement | |
| Summary | True | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..0 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.modifierExtension | Σ ?! C | |
| Short | Extensions that cannot be ignored even if unrecognized | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Modifier | True | |
| Summary | True | |
| Alias | extensions, user content, modifiers | |
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.link | Σ | |
| Short | Links related to this entry | |
| Definition | A series of links that provide context to this entry. | |
| Cardinality | 0..0 | |
| Type | see (link) | |
| Summary | True | |
| Bundle.entry.fullUrl | Σ C | |
| Short | URI for resource (e.g. the absolute URL server address, URI for UUID/OID, etc.) | |
| Definition | The Absolute URL for the resource. Except for transactions and batches, each entry in a Bundle must have a fullUrl. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. Even when not required, fullUrl MAY be set to a urn:uuid to allow referencing entries in a transaction. The fullUrl can be an arbitrary URI and is not limited to urn:uuid, urn:oid, http, and https. The fullUrl element SHALL have a value except when:
| |
| Cardinality | 1..1 | |
| Type | uri | |
| Summary | True | |
| Comments | fullUrl might not be unique in the context of a resource. Note that since FHIR resources do not need to be served through the FHIR API, the fullURL might be a URN or an absolute URL that does not end with the logical id of the resource (Resource.id). However, but if the fullUrl does look like a RESTful server URL (e.g. meets the regex, then the 'id' portion of the fullUrl SHALL end with the Resource.id. Note that the fullUrl is not the same as the canonical URL - it's an absolute url for an endpoint serving the resource (these will happen to have the same value on the canonical server for the resource with the canonical URL). | |
| Conditions | The cardinality or value of this element may be affected by these constraints: bdl-7, bdl-15, bdl-8 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource | Σ C | |
| Short | Ordering of medication for patient or group | |
| Definition | An 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. | |
| Cardinality | 1..1 | |
| Type | MedicationRequest | |
| Summary | True | |
| Alias | Prescription, Order | |
| Conditions | The cardinality or value of this element may be affected by these constraints: bdl-3a, bdl-3b, bdl-3c, bdl-7, bdl-11, bdl-12, bdl-13, bdl-5 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.id | Σ | |
| Short | Logical id of this artifact | |
| Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. | |
| Cardinality | 0..1 | |
| Type | id | |
| Summary | True | |
| Comments | Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.meta | Σ | |
| Short | Metadata about the resource | |
| Definition | The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource. | |
| Cardinality | 0..1 | |
| Type | Meta | |
| Summary | True | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.implicitRules | Σ ?! | |
| Short | A set of rules under which this content was created | |
| Definition | A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. | |
| Cardinality | 0..1 | |
| Type | uri | |
| Modifier | True | |
| Summary | True | |
| Comments | Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.language | ||
| Short | Language of the resource content | |
| Definition | The base language in which the resource is written. | |
| Cardinality | 0..1 | |
| Type | code | |
| Binding | IETF language tag for a human language | |
| Comments | Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.text | C | |
| Short | Text summary of the resource, for human interpretation | |
| Definition | A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. | |
| Cardinality | 0..1 | |
| Type | Narrative | |
| Alias | narrative, html, xhtml, display | |
| Comments | Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: dom-6 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.contained | C | |
| Short | Contained, inline Resources | |
| Definition | These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning. | |
| Cardinality | 0..* | |
| Type | Resource | |
| Alias | inline resources, anonymous resources, contained resources | |
| Comments | This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels. | |
| Slicing | Unordered, Open, by $this(Profile) | |
| Conditions | The cardinality or value of this element may be affected by these constraints: dom-2, dom-4, dom-3, dom-5 | |
| Mappings |
| |
| Bundle.entry.resource.contained:medication | C | |
| Short | Definition of a Medication | |
| Definition | This resource is primarily used for the identification and definition of a medication, including ingredients, for the purposes of prescribing, dispensing, and administering a medication as well as for making statements about medication use. | |
| Cardinality | 0..1 | |
| Type | Medication | |
| Alias | inline resources, anonymous resources, contained resources | |
| Comments | This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: dom-2, dom-4, dom-3, dom-5 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..* | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.extension:orderingLocation | C | |
| Short | Ordering Location Information | |
| Definition | Extension for capturing ordering location information in MedicationRequest | |
| Cardinality | 0..1 | |
| Type | Extension(CodeableConcept) | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.extension:orderSetConnectingTerm | C | |
| Short | Order Set Connecting Term Information | |
| Definition | Extension for capturing order set connecting term information in MedicationRequest | |
| Cardinality | 0..1 | |
| Type | Extension(CodeableConcept) | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.extension:changesMade | C | |
| Short | Changes Made Information | |
| Definition | Extension for capturing changes made information in MedicationRequest | |
| Cardinality | 0..* | |
| Type | Extension(Complex) | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.extension:authorizer | C | |
| Short | Authorizer Information | |
| Definition | Extension for capturing authorizer information in MedicationRequest | |
| Cardinality | 0..* | |
| Type | Extension(Reference(Practitioner)) | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.extension:orderingInstitution | C | |
| Short | Ordering Institution Information | |
| Definition | Extension for capturing ordering institution information in ServiceRequest | |
| Cardinality | 0..1 | |
| Type | Extension(Reference(Organization)) | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.modifierExtension | Σ ?! C | |
| Short | Extensions that cannot be ignored | |
| Definition | May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Modifier | True | |
| Summary | True | |
| Alias | extensions, user content | |
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.identifier | C | |
| Short | External ids for this request | |
| Definition | Identifiers associated with this medication request that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate. They are business identifiers assigned to this resource by the performer or other systems and remain constant as the resource is updated and propagates from server to server. | |
| Cardinality | 1..* | |
| Type | Identifier | |
| Comments | This is a business identifier, not a resource identifier. | |
| Slicing | Unordered, Open, by system(Value) | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.identifier.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..0 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.resource.identifier.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.identifier.use | Σ ?! | |
| Short | usual | official | temp | secondary | old (If known) | |
| Definition | The purpose of this identifier. | |
| Cardinality | 0..0 | |
| Type | code | |
| Binding | Identifies the purpose for this identifier, if known . | |
| Modifier | True | |
| Summary | True | |
| Requirements | Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. | |
| Comments | Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.identifier.type | Σ | |
| Short | Description of identifier | |
| Definition | A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. | |
| Cardinality | 0..0 | |
| Type | CodeableConcept | |
| Binding | A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. | |
| Summary | True | |
| Requirements | Allows users to make use of identifiers when the identifier system is not known. | |
| Comments | 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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.identifier.system | Σ | |
| Short | The namespace for the identifier value | |
| Definition | Establishes the namespace for the value - that is, an absolute URL that describes a set values that are unique. | |
| Cardinality | 1..1 | |
| Type | uri | |
| Summary | True | |
| Requirements | 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. | |
| Comments | Identifier.system is always case sensitive. | |
| Constraints |
| |
| Examples | Generalhttp://www.acme.com/identifiers/patient | |
| Mappings |
| |
| Bundle.entry.resource.identifier.value | Σ C | |
| Short | The value that is unique | |
| Definition | The portion of the identifier typically relevant to the user and which is unique within the context of the system. | |
| Cardinality | 1..1 | |
| Type | string | |
| Summary | True | |
| Comments | 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 http://hl7.org/fhir/StructureDefinition/rendered-value). 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. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ident-1 | |
| Constraints |
| |
| Examples | General123456 | |
| Mappings |
| |
| Bundle.entry.resource.identifier.period | Σ C | |
| Short | Time period when id is/was valid for use | |
| Definition | Time period during which identifier is/was valid for use. | |
| Cardinality | 0..0 | |
| Type | Period | |
| Summary | True | |
| Comments | 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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.identifier.assigner | Σ C | |
| Short | Organization that issued id (may be just text) | |
| Definition | Organization that issued/manages the identifier. | |
| Cardinality | 0..0 | |
| Type | Reference(Organization) | |
| Summary | True | |
| Comments | 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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.identifier:recordIdentifier | C | |
| Short | An identifier intended for computation | |
| Definition | An identifier - identifies some entity uniquely and unambiguously. Typically this is used for business identifiers. | |
| Cardinality | 0..1 | |
| Type | IdentifierRecordID | |
| Comments | The rules of the identifier.type determine if a check digit is part of the ID value or sent separately, such as through the checkDigit extension. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.identifier:orderID | C | |
| Short | An identifier intended for computation | |
| Definition | An identifier - identifies some entity uniquely and unambiguously. Typically this is used for business identifiers. | |
| Cardinality | 1..1 | |
| Type | IdentifierOrderNo | |
| Comments | The rules of the identifier.type determine if a check digit is part of the ID value or sent separately, such as through the checkDigit extension. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.identifier:sourceGroupingID | C | |
| Short | An identifier intended for computation | |
| Definition | An identifier - identifies some entity uniquely and unambiguously. Typically this is used for business identifiers. | |
| Cardinality | 1..1 | |
| Type | IdentifierSourceGroupingID | |
| Comments | The rules of the identifier.type determine if a check digit is part of the ID value or sent separately, such as through the checkDigit extension. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.identifier:sequenceNo | C | |
| Short | An identifier intended for computation | |
| Definition | An identifier - identifies some entity uniquely and unambiguously. Typically this is used for business identifiers. | |
| Cardinality | 0..1 | |
| Type | IdentifierSequenceNo | |
| Comments | The rules of the identifier.type determine if a check digit is part of the ID value or sent separately, such as through the checkDigit extension. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.basedOn | Σ C | |
| Short | A plan or request that is fulfilled in whole or in part by this medication request | |
| Definition | A plan or request that is fulfilled in whole or in part by this medication request. | |
| Cardinality | 0..0 | |
| Type | Reference(Encounter) | |
| Summary | True | |
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolvable (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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.basedOn.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..0 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.resource.basedOn.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.basedOn.reference | Σ C | |
| Short | Literal reference, Relative, internal or absolute URL | |
| Definition | A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. | |
| Cardinality | 0..0 | |
| Type | string | |
| Summary | True | |
| Comments | Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ref-2, ref-1 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.basedOn.type | Σ | |
| Short | Type the reference refers to (e.g. "Patient") - must be a resource in resources | |
| Definition | The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). | |
| Cardinality | 1..1 | |
| Type | uri | |
| Binding | Aa resource (or, for logical models, the URI of the logical model). | |
| Summary | True | |
| Comments | This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a known RESTful URL) or by resolving the target of the reference. | |
| Constraints |
| |
| Pattern | Encounter | |
| Mappings |
| |
| Bundle.entry.resource.basedOn.identifier | Σ C | |
| Short | An identifier intended for computation | |
| Definition | An identifier - identifies some entity uniquely and unambiguously. Typically this is used for business identifiers. | |
| Cardinality | 1..1 | |
| Type | IdentifierRecordID | |
| Summary | True | |
| Comments | The rules of the identifier.type determine if a check digit is part of the ID value or sent separately, such as through the checkDigit extension. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ref-2 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.basedOn.display | Σ C | |
| Short | Text alternative for the resource | |
| Definition | Plain text narrative that identifies the resource in addition to the resource reference. | |
| Cardinality | 0..0 | |
| Type | string | |
| Summary | True | |
| Comments | This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ref-2 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.priorPrescription | C | |
| Short | Reference to an order/prescription that is being replaced by this MedicationRequest | |
| Definition | Reference to an order/prescription that is being replaced by this MedicationRequest. | |
| Cardinality | 0..0 | |
| Type | Reference(MedicationRequest) | |
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolvable (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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.groupIdentifier | Σ C | |
| Short | An identifier intended for computation | |
| Definition | An identifier - identifies some entity uniquely and unambiguously. Typically this is used for business identifiers. | |
| Cardinality | 0..1 | |
| Type | Identifier | |
| Summary | True | |
| Requirements | 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. | |
| Comments | The rules of the identifier.type determine if a check digit is part of the ID value or sent separately, such as through the checkDigit extension. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.groupIdentifier.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..0 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.resource.groupIdentifier.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.groupIdentifier.use | Σ ?! | |
| Short | usual | official | temp | secondary | old (If known) | |
| Definition | The purpose of this identifier. | |
| Cardinality | 0..0 | |
| Type | code | |
| Binding | Identifies the purpose for this identifier, if known . | |
| Modifier | True | |
| Summary | True | |
| Requirements | Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. | |
| Comments | Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.groupIdentifier.type | Σ | |
| Short | Description of identifier | |
| Definition | A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. | |
| Cardinality | 0..0 | |
| Type | CodeableConcept | |
| Binding | A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. | |
| Summary | True | |
| Requirements | Allows users to make use of identifiers when the identifier system is not known. | |
| Comments | 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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.groupIdentifier.system | Σ | |
| Short | The namespace for the identifier value | |
| Definition | Establishes the namespace for the value - that is, an absolute URL that describes a set values that are unique. | |
| Cardinality | 1..1 | |
| Type | uri | |
| Summary | True | |
| Requirements | 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. | |
| Comments | Identifier.system is always case sensitive. | |
| Constraints |
| |
| Pattern | https://fhir.synapxe.sg/NamingSystem/group-no | |
| Examples | Generalhttp://www.acme.com/identifiers/patient | |
| Mappings |
| |
| Bundle.entry.resource.groupIdentifier.value | Σ C | |
| Short | The value that is unique | |
| Definition | The portion of the identifier typically relevant to the user and which is unique within the context of the system. | |
| Cardinality | 1..1 | |
| Type | string | |
| Summary | True | |
| Comments | 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 http://hl7.org/fhir/StructureDefinition/rendered-value). 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. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ident-1 | |
| Constraints |
| |
| Examples | General123456 | |
| Mappings |
| |
| Bundle.entry.resource.groupIdentifier.period | Σ C | |
| Short | Time period when id is/was valid for use | |
| Definition | Time period during which identifier is/was valid for use. | |
| Cardinality | 0..0 | |
| Type | Period | |
| Summary | True | |
| Comments | 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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.groupIdentifier.assigner | Σ C | |
| Short | Organization that issued id (may be just text) | |
| Definition | Organization that issued/manages the identifier. | |
| Cardinality | 0..0 | |
| Type | Reference(Organization) | |
| Summary | True | |
| Comments | 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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.status | Σ ?! | |
| Short | active | on-hold | ended | stopped | completed | cancelled | entered-in-error | draft | unknown | |
| Definition | A code specifying the current state of the order. Generally, this will be active or completed state. | |
| Cardinality | 1..1 | |
| Type | code | |
| Binding | A coded concept specifying the state of the prescribing event. Describes the lifecycle of the prescription. | |
| Modifier | True | |
| Summary | True | |
| Comments | This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid. Clinical decision support systems should take the status into account when determining which medications to include in their algorithms. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.statusReason | ||
| Short | Reason for cancellation, if it is cancelled | |
| Definition | A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text. | |
| Cardinality | 0..1 | |
| Type | CodeableConcept | |
| Binding | Identifies the reasons for a given status. | |
| Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.statusReason.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..0 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.resource.statusReason.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.statusReason.coding | Σ C | |
| Short | Code defined by a terminology system | |
| Definition | A reference to a code defined by a terminology system. | |
| Cardinality | 1..* | |
| Type | Coding | |
| Summary | True | |
| Requirements | Allows for alternative encodings within a code system, and translations to other code systems. | |
| Comments | Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.statusReason.coding.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..0 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.resource.statusReason.coding.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.statusReason.coding.system | Σ | |
| Short | Identity of the terminology system | |
| Definition | The identification of the code system that defines the meaning of the symbol in the code. | |
| Cardinality | 1..1 | |
| Type | uri | |
| Summary | True | |
| Requirements | Need to be unambiguous about the source of the definition of the symbol. | |
| Comments | The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should be an absolute reference to some definition that establishes the system clearly and unambiguously. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.statusReason.coding.version | Σ | |
| Short | Version of the system - if relevant | |
| Definition | The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. | |
| Cardinality | 0..1 | |
| Type | string | |
| Summary | True | |
| Comments | Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.statusReason.coding.code | Σ C | |
| Short | Symbol in syntax defined by the system | |
| Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). | |
| Cardinality | 1..1 | |
| Type | code | |
| Summary | True | |
| Requirements | Need to refer to a particular code in the system. | |
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |
| Conditions | The cardinality or value of this element may be affected by these constraints: cod-1 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.statusReason.coding.display | Σ C | |
| Short | Representation defined by the system | |
| Definition | A representation of the meaning of the code in the system, following the rules of the system. | |
| Cardinality | 1..1 | |
| Type | string | |
| Summary | True | |
| Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. | |
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |
| Conditions | The cardinality or value of this element may be affected by these constraints: cod-1 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.statusReason.coding.userSelected | Σ | |
| Short | If this coding was chosen directly by the user | |
| Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). | |
| Cardinality | 0..0 | |
| Type | boolean | |
| Summary | True | |
| Requirements | This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. | |
| Comments | Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.statusReason.text | Σ | |
| Short | Plain text representation of the concept | |
| Definition | A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. | |
| Cardinality | 0..1 | |
| Type | string | |
| Summary | True | |
| Requirements | The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. | |
| Comments | Very often the text is the same as a displayName of one of the codings. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.statusChanged | ||
| Short | if status is Discontinued, this is the discontinued date time | |
| Definition | if status is Discontinued, this is the discontinued date time | |
| Cardinality | 0..1 | |
| Type | dateTime | |
| Comments | UTC offset is allowed for dates and partial dates | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.intent | Σ ?! | |
| Short | proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option | |
| Definition | Whether the request is a proposal, plan, or an original order. | |
| Cardinality | 1..1 | |
| Type | code | |
| Binding | The kind of medication order. | |
| Modifier | True | |
| Summary | True | |
| Comments | It is expected that the type of requester will be restricted for different stages of a MedicationRequest. For example, Proposals can be created by a patient, relatedPerson, Practitioner or Device. Plans can be created by Practitioners, Patients, RelatedPersons and Devices. Original orders can be created by a Practitioner only. An instance-order is an instantiation of a request or order and may be used to populate Medication Administration Record. This element is labeled as a modifier because the intent alters when and how the resource is actually applicable. | |
| Constraints |
| |
| Pattern | order | |
| Mappings |
| |
| Bundle.entry.resource.category | ||
| Short | The specific clinical setting when this medication is ordered | |
| Definition | The specific clinical setting when this medication is ordered | |
| Cardinality | 1..1 | |
| Type | CodeableConcept | |
| Binding | A coded concept identifying where the medication is to be consumed or administered. | |
| Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.category.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..0 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.resource.category.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.category.coding | Σ C | |
| Short | Code defined by a terminology system | |
| Definition | A reference to a code defined by a terminology system. | |
| Cardinality | 1..* | |
| Type | Coding | |
| Summary | True | |
| Requirements | Allows for alternative encodings within a code system, and translations to other code systems. | |
| Comments | Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.category.coding.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..0 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.resource.category.coding.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.category.coding.system | Σ | |
| Short | Identity of the terminology system | |
| Definition | The identification of the code system that defines the meaning of the symbol in the code. | |
| Cardinality | 1..1 | |
| Type | uri | |
| Summary | True | |
| Requirements | Need to be unambiguous about the source of the definition of the symbol. | |
| Comments | The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should be an absolute reference to some definition that establishes the system clearly and unambiguously. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.category.coding.version | Σ | |
| Short | Version of the system - if relevant | |
| Definition | The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. | |
| Cardinality | 0..1 | |
| Type | string | |
| Summary | True | |
| Comments | Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.category.coding.code | Σ C | |
| Short | Symbol in syntax defined by the system | |
| Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). | |
| Cardinality | 1..1 | |
| Type | code | |
| Summary | True | |
| Requirements | Need to refer to a particular code in the system. | |
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |
| Conditions | The cardinality or value of this element may be affected by these constraints: cod-1 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.category.coding.display | Σ C | |
| Short | Representation defined by the system | |
| Definition | A representation of the meaning of the code in the system, following the rules of the system. | |
| Cardinality | 1..1 | |
| Type | string | |
| Summary | True | |
| Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. | |
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |
| Conditions | The cardinality or value of this element may be affected by these constraints: cod-1 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.category.coding.userSelected | Σ | |
| Short | If this coding was chosen directly by the user | |
| Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). | |
| Cardinality | 0..0 | |
| Type | boolean | |
| Summary | True | |
| Requirements | This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. | |
| Comments | Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.category.text | Σ | |
| Short | Plain text representation of the concept | |
| Definition | A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. | |
| Cardinality | 0..1 | |
| Type | string | |
| Summary | True | |
| Requirements | The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. | |
| Comments | Very often the text is the same as a displayName of one of the codings. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.priority | Σ | |
| Short | routine | urgent | asap | stat | |
| Definition | Indicates how quickly the Medication Request should be addressed with respect to other requests. | |
| Cardinality | 0..0 | |
| Type | code | |
| Binding | Identifies the level of importance to be assigned to actioning the request. | |
| Summary | True | |
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.doNotPerform | Σ ?! | |
| Short | True if patient is to stop taking or not to start taking the medication | |
| Definition | If true, indicates that the provider is asking for the patient to either stop taking or to not start taking the specified medication. For example, the patient is taking an existing medication and the provider is changing their medication. They want to create two seperate requests: one to stop using the current medication and another to start the new medication. | |
| Cardinality | 0..0 | |
| Type | boolean | |
| Modifier | True | |
| Summary | True | |
| Comments | If do not perform is not specified, the request is a positive request e.g. "do perform". | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.medication | Σ | |
| Short | Medication to be taken | |
| Definition | Identifies the medication being requested. This is a link to a resource that represents the medication which may be the details of the medication or simply an attribute carrying a code that identifies the medication from a known list of medications. | |
| Cardinality | 1..1 | |
| Type | CodeableReference(Medication) | |
| Binding | A coded concept identifying substance or product that can be ordered. | |
| Summary | True | |
| Comments | If only a code is specified, then it needs to be a code for a specific product. If more information is required, then the use of the Medication resource is recommended. For example, if you require form or lot number or if the medication is compounded or extemporaneously prepared, then you must reference the Medication resource. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.medication.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..0 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.resource.medication.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.medication.concept | Σ | |
| Short | Concept - reference to a terminology or just text | |
| Definition | A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text. | |
| Cardinality | 0..0 | |
| Type | CodeableConcept | |
| Summary | True | |
| Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.medication.concept.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..0 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.resource.medication.concept.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.medication.concept.coding | Σ C | |
| Short | Code defined by a terminology system | |
| Definition | A reference to a code defined by a terminology system. | |
| Cardinality | 1..* | |
| Type | Coding | |
| Summary | True | |
| Requirements | Allows for alternative encodings within a code system, and translations to other code systems. | |
| Comments | Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.medication.concept.coding.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..0 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.resource.medication.concept.coding.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.medication.concept.coding.system | Σ | |
| Short | Identity of the terminology system | |
| Definition | The identification of the code system that defines the meaning of the symbol in the code. | |
| Cardinality | 1..1 | |
| Type | uri | |
| Summary | True | |
| Requirements | Need to be unambiguous about the source of the definition of the symbol. | |
| Comments | The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should be an absolute reference to some definition that establishes the system clearly and unambiguously. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.medication.concept.coding.version | Σ | |
| Short | Version of the system - if relevant | |
| Definition | The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. | |
| Cardinality | 0..0 | |
| Type | string | |
| Summary | True | |
| Comments | Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.medication.concept.coding.code | Σ C | |
| Short | Symbol in syntax defined by the system | |
| Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). | |
| Cardinality | 1..1 | |
| Type | code | |
| Summary | True | |
| Requirements | Need to refer to a particular code in the system. | |
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |
| Conditions | The cardinality or value of this element may be affected by these constraints: cod-1 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.medication.concept.coding.display | Σ C | |
| Short | Representation defined by the system | |
| Definition | A representation of the meaning of the code in the system, following the rules of the system. | |
| Cardinality | 1..1 | |
| Type | string | |
| Summary | True | |
| Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. | |
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |
| Conditions | The cardinality or value of this element may be affected by these constraints: cod-1 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.medication.concept.coding.userSelected | Σ | |
| Short | If this coding was chosen directly by the user | |
| Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). | |
| Cardinality | 0..0 | |
| Type | boolean | |
| Summary | True | |
| Requirements | This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. | |
| Comments | Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.medication.concept.text | Σ | |
| Short | Plain text representation of the concept | |
| Definition | A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. | |
| Cardinality | 0..1 | |
| Type | string | |
| Summary | True | |
| Requirements | The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. | |
| Comments | Very often the text is the same as a displayName of one of the codings. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.medication.reference | Σ C | |
| Short | Reference to a resource (by instance) | |
| Definition | A reference to a resource the provides exact details about the information being referenced. | |
| Cardinality | 1..1 | |
| Type | Reference(Medication) | |
| Summary | True | |
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolvable (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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.medication.reference.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..0 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.resource.medication.reference.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.medication.reference.reference | Σ C | |
| Short | Literal reference, Relative, internal or absolute URL | |
| Definition | A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. | |
| Cardinality | 0..1 | |
| Type | string | |
| Summary | True | |
| Comments | Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ref-2, ref-1 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.medication.reference.type | Σ | |
| Short | Type the reference refers to (e.g. "Patient") - must be a resource in resources | |
| Definition | The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). | |
| Cardinality | 0..0 | |
| Type | uri | |
| Binding | Aa resource (or, for logical models, the URI of the logical model). | |
| Summary | True | |
| Comments | This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a known RESTful URL) or by resolving the target of the reference. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.medication.reference.identifier | Σ C | |
| Short | Logical reference, when literal reference is not known | |
| Definition | An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. | |
| Cardinality | 0..1 | |
| Type | Identifier | |
| Summary | True | |
| Comments | When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). This element only allows for a single identifier. In the case where additional identifers are required, use the http://hl7.org/fhir/StructureDefinition/additionalIdentifier extension. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ref-2 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.medication.reference.identifier.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..0 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.resource.medication.reference.identifier.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.medication.reference.identifier.use | Σ ?! | |
| Short | usual | official | temp | secondary | old (If known) | |
| Definition | The purpose of this identifier. | |
| Cardinality | 0..0 | |
| Type | code | |
| Binding | Identifies the purpose for this identifier, if known . | |
| Modifier | True | |
| Summary | True | |
| Requirements | Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. | |
| Comments | Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.medication.reference.identifier.type | Σ | |
| Short | Description of identifier | |
| Definition | A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. | |
| Cardinality | 0..0 | |
| Type | CodeableConcept | |
| Binding | A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. | |
| Summary | True | |
| Requirements | Allows users to make use of identifiers when the identifier system is not known. | |
| Comments | 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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.medication.reference.identifier.system | Σ | |
| Short | The namespace for the identifier value | |
| Definition | Establishes the namespace for the value - that is, an absolute URL that describes a set values that are unique. | |
| Cardinality | 1..1 | |
| Type | uri | |
| Summary | True | |
| Requirements | 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. | |
| Comments | Identifier.system is always case sensitive. | |
| Constraints |
| |
| Examples | Generalhttp://www.acme.com/identifiers/patient | |
| Mappings |
| |
| Bundle.entry.resource.medication.reference.identifier.value | Σ C | |
| Short | The value that is unique | |
| Definition | The portion of the identifier typically relevant to the user and which is unique within the context of the system. | |
| Cardinality | 1..1 | |
| Type | string | |
| Summary | True | |
| Comments | 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 http://hl7.org/fhir/StructureDefinition/rendered-value). 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. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ident-1 | |
| Constraints |
| |
| Examples | General123456 | |
| Mappings |
| |
| Bundle.entry.resource.medication.reference.identifier.period | Σ C | |
| Short | Time period when id is/was valid for use | |
| Definition | Time period during which identifier is/was valid for use. | |
| Cardinality | 0..0 | |
| Type | Period | |
| Summary | True | |
| Comments | 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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.medication.reference.identifier.assigner | Σ C | |
| Short | Organization that issued id (may be just text) | |
| Definition | Organization that issued/manages the identifier. | |
| Cardinality | 0..0 | |
| Type | Reference(Organization) | |
| Summary | True | |
| Comments | 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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.medication.reference.display | Σ C | |
| Short | Text alternative for the resource | |
| Definition | Plain text narrative that identifies the resource in addition to the resource reference. | |
| Cardinality | 0..1 | |
| Type | string | |
| Summary | True | |
| Comments | This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ref-2 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.subject | Σ C | |
| Short | A reference from one resource to another | |
| Definition | A reference from one resource to another. | |
| Cardinality | 1..1 | |
| Type | Reference(Patient) | |
| Summary | True | |
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolvable (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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.subject.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..0 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.resource.subject.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.subject.reference | Σ C | |
| Short | Literal reference, Relative, internal or absolute URL | |
| Definition | A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. | |
| Cardinality | 0..0 | |
| Type | string | |
| Summary | True | |
| Comments | Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ref-2, ref-1 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.subject.type | Σ | |
| Short | Type the reference refers to (e.g. "Patient") - must be a resource in resources | |
| Definition | The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). | |
| Cardinality | 1..1 | |
| Type | uri | |
| Binding | Aa resource (or, for logical models, the URI of the logical model). | |
| Summary | True | |
| Comments | This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a known RESTful URL) or by resolving the target of the reference. | |
| Constraints |
| |
| Pattern | Patient | |
| Mappings |
| |
| Bundle.entry.resource.subject.identifier | Σ C | |
| Short | An identifier intended for computation | |
| Definition | An identifier - identifies some entity uniquely and unambiguously. Typically this is used for business identifiers. | |
| Cardinality | 1..1 | |
| Type | Identifier | |
| Summary | True | |
| Comments | The rules of the identifier.type determine if a check digit is part of the ID value or sent separately, such as through the checkDigit extension. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ref-2 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.subject.identifier.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..0 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.resource.subject.identifier.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.subject.identifier.use | Σ ?! | |
| Short | usual | official | temp | secondary | old (If known) | |
| Definition | The purpose of this identifier. | |
| Cardinality | 0..0 | |
| Type | code | |
| Binding | Identifies the purpose for this identifier, if known . | |
| Modifier | True | |
| Summary | True | |
| Requirements | Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. | |
| Comments | Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.subject.identifier.type | Σ | |
| Short | Description of identifier | |
| Definition | A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. | |
| Cardinality | 0..0 | |
| Type | CodeableConcept | |
| Binding | A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. | |
| Summary | True | |
| Requirements | Allows users to make use of identifiers when the identifier system is not known. | |
| Comments | 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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.subject.identifier.system | Σ | |
| Short | https://fhir.synapxe.sg/NamingSystem/nric or https://fhir.synapxe.sg/NamingSystem/mrn | |
| Definition | Use the NRIC naming system when the patient's identification type is NRIC; otherwise use the MRN naming system (e.g. for identification type OT). | |
| Cardinality | 1..1 | |
| Type | uri | |
| Summary | True | |
| Requirements | 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. | |
| Comments | Identifier.system is always case sensitive. | |
| Constraints |
| |
| Examples | Generalhttp://www.acme.com/identifiers/patientNRIC https://fhir.synapxe.sg/NamingSystem/nricMRN https://fhir.synapxe.sg/NamingSystem/mrn | |
| Mappings |
| |
| Bundle.entry.resource.subject.identifier.value | Σ C | |
| Short | The value that is unique | |
| Definition | The portion of the identifier typically relevant to the user and which is unique within the context of the system. | |
| Cardinality | 1..1 | |
| Type | string | |
| Summary | True | |
| Comments | 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 http://hl7.org/fhir/StructureDefinition/rendered-value). 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. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ident-1 | |
| Constraints |
| |
| Examples | General123456 | |
| Mappings |
| |
| Bundle.entry.resource.subject.identifier.period | Σ C | |
| Short | Time period when id is/was valid for use | |
| Definition | Time period during which identifier is/was valid for use. | |
| Cardinality | 0..0 | |
| Type | Period | |
| Summary | True | |
| Comments | 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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.subject.identifier.assigner | Σ C | |
| Short | Organization that issued id (may be just text) | |
| Definition | Organization that issued/manages the identifier. | |
| Cardinality | 0..0 | |
| Type | Reference(Organization) | |
| Summary | True | |
| Comments | 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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.subject.display | Σ C | |
| Short | Text alternative for the resource | |
| Definition | Plain text narrative that identifies the resource in addition to the resource reference. | |
| Cardinality | 0..0 | |
| Type | string | |
| Summary | True | |
| Comments | This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ref-2 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.informationSource | C | |
| Short | The person or organization who provided the information about this request, if the source is someone other than the requestor | |
| Definition | The person or organization who provided the information about this request, if the source is someone other than the requestor. This is often used when the MedicationRequest is reported by another person. | |
| Cardinality | 0..0 | |
| Type | Reference(Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | |
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolvable (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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.encounter | C | |
| Short | A reference from one resource to another | |
| Definition | A reference from one resource to another. | |
| Cardinality | 0..1 | |
| Type | Reference(Encounter) | |
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolvable (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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.supportingInformation | C | |
| Short | Information to support fulfilling of the medication | |
| Definition | Information to support fulfilling (i.e. dispensing or administering) of the medication, for example, patient height and weight, a MedicationStatement for the patient). | |
| Cardinality | 0..0 | |
| Type | Reference(Resource) | |
| Comments | This attribute can be used to reference a MedicationStatement about the patients' medication use. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.authoredOn | Σ | |
| Short | medication order date time | |
| Definition | The date (and perhaps time) when the prescription was initially written or authored on. | |
| Cardinality | 1..1 | |
| Type | dateTime | |
| Summary | True | |
| Comments | UTC offset is allowed for dates and partial dates | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.requester | Σ C | |
| Short | A reference from one resource to another | |
| Definition | A reference from one resource to another. | |
| Cardinality | 1..1 | |
| Type | Reference(Practitioner) | |
| Summary | True | |
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolvable (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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.requester.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..0 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.resource.requester.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.requester.reference | Σ C | |
| Short | Literal reference, Relative, internal or absolute URL | |
| Definition | A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. | |
| Cardinality | 0..0 | |
| Type | string | |
| Summary | True | |
| Comments | Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ref-2, ref-1 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.requester.type | Σ | |
| Short | Type the reference refers to (e.g. "Patient") - must be a resource in resources | |
| Definition | The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). | |
| Cardinality | 1..1 | |
| Type | uri | |
| Binding | Aa resource (or, for logical models, the URI of the logical model). | |
| Summary | True | |
| Comments | This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a known RESTful URL) or by resolving the target of the reference. | |
| Constraints |
| |
| Pattern | Practitioner | |
| Mappings |
| |
| Bundle.entry.resource.requester.identifier | Σ C | |
| Short | Logical reference, when literal reference is not known | |
| Definition | An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. | |
| Cardinality | 1..1 | |
| Type | IdentifierDCR, IdentifierMCR, IdentifierPRN, IdentifierSNB | |
| Summary | True | |
| Comments | When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). This element only allows for a single identifier. In the case where additional identifers are required, use the http://hl7.org/fhir/StructureDefinition/additionalIdentifier extension. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ref-2 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.requester.identifier.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..1 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.resource.requester.identifier.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..* | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.requester.identifier.use | Σ ?! | |
| Short | usual | official | temp | secondary | old (If known) | |
| Definition | The purpose of this identifier. | |
| Cardinality | 0..1 | |
| Type | code | |
| Binding | Identifies the purpose for this identifier, if known . | |
| Modifier | True | |
| Summary | True | |
| Requirements | Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. | |
| Comments | Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.requester.identifier.type | Σ | |
| Short | Description of identifier | |
| Definition | A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. | |
| Cardinality | 0..1 | |
| Type | CodeableConcept | |
| Binding | A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. | |
| Summary | True | |
| Requirements | Allows users to make use of identifiers when the identifier system is not known. | |
| Comments | 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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.requester.identifier.system | Σ | |
| Short | The namespace for the identifier value | |
| Definition | Allowed requester identifier systems: https://fhir.synapxe.sg/NamingSystem/mcr, https://fhir.synapxe.sg/NamingSystem/dcr, https://fhir.synapxe.sg/NamingSystem/prn, or https://fhir.synapxe.sg/NamingSystem/snb. | |
| Cardinality | 0..1 | |
| Type | uri | |
| Summary | True | |
| Requirements | 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. | |
| Comments | Identifier.system is always case sensitive. | |
| Constraints |
| |
| Examples | Generalhttp://www.acme.com/identifiers/patient | |
| Mappings |
| |
| Bundle.entry.resource.requester.identifier.value | Σ C | |
| Short | The value that is unique | |
| Definition | The portion of the identifier typically relevant to the user and which is unique within the context of the system. | |
| Cardinality | 0..1 | |
| Type | string | |
| Summary | True | |
| Comments | 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 http://hl7.org/fhir/StructureDefinition/rendered-value). 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. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ident-1 | |
| Constraints |
| |
| Examples | General123456 | |
| Mappings |
| |
| Bundle.entry.resource.requester.identifier.period | Σ C | |
| Short | Time period when id is/was valid for use | |
| Definition | Time period during which identifier is/was valid for use. | |
| Cardinality | 0..1 | |
| Type | Period | |
| Summary | True | |
| Comments | 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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.requester.identifier.assigner | Σ C | |
| Short | Organization that issued id (may be just text) | |
| Definition | Organization that issued/manages the identifier. | |
| Cardinality | 0..1 | |
| Type | Reference(Organization) | |
| Summary | True | |
| Comments | 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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.requester.display | Σ C | |
| Short | Text alternative for the resource | |
| Definition | Plain text narrative that identifies the resource in addition to the resource reference. | |
| Cardinality | 0..1 | |
| Type | string | |
| Summary | True | |
| Comments | This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ref-2 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.reported | Σ | |
| Short | Reported rather than primary record | |
| Definition | Indicates 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. | |
| Cardinality | 0..0 | |
| Type | boolean | |
| Summary | True | |
| Comments | If not populated, then assume that this is the original record and not reported | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.performerType | Σ | |
| Short | Desired kind of performer of the medication administration | |
| Definition | Indicates the type of performer of the administration of the medication. | |
| Cardinality | 0..0 | |
| Type | CodeableConcept | |
| Binding | Identifies the type of individual that is desired to administer the medication. | |
| Summary | True | |
| Comments | 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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.performer | C | |
| Short | Intended performer of administration | |
| Definition | The specified desired performer of the medication treatment (e.g. the performer of the medication administration). For devices, this is the device that is intended to perform the administration of the medication. An IV Pump would be an example of a device that is performing the administration. Both the IV Pump and the practitioner that set the rate or bolus on the pump can be listed as performers. | |
| Cardinality | 0..0 | |
| Type | Reference(Practitioner) | |
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolvable (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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.performer.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..0 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.resource.performer.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.performer.reference | Σ C | |
| Short | Literal reference, Relative, internal or absolute URL | |
| Definition | A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. | |
| Cardinality | 0..0 | |
| Type | string | |
| Summary | True | |
| Comments | Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ref-2, ref-1 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.performer.type | Σ | |
| Short | Type the reference refers to (e.g. "Patient") - must be a resource in resources | |
| Definition | The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). | |
| Cardinality | 0..0 | |
| Type | uri | |
| Binding | Aa resource (or, for logical models, the URI of the logical model). | |
| Summary | True | |
| Comments | This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a known RESTful URL) or by resolving the target of the reference. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.performer.identifier | Σ C | |
| Short | Logical reference, when literal reference is not known | |
| Definition | An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. | |
| Cardinality | 1..1 | |
| Type | Identifier | |
| Summary | True | |
| Comments | When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). This element only allows for a single identifier. In the case where additional identifers are required, use the http://hl7.org/fhir/StructureDefinition/additionalIdentifier extension. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ref-2 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.performer.identifier.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..0 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.resource.performer.identifier.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.performer.identifier.use | Σ ?! | |
| Short | usual | official | temp | secondary | old (If known) | |
| Definition | The purpose of this identifier. | |
| Cardinality | 0..0 | |
| Type | code | |
| Binding | Identifies the purpose for this identifier, if known . | |
| Modifier | True | |
| Summary | True | |
| Requirements | Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. | |
| Comments | Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.performer.identifier.type | Σ | |
| Short | Description of identifier | |
| Definition | A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. | |
| Cardinality | 0..0 | |
| Type | CodeableConcept | |
| Binding | A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. | |
| Summary | True | |
| Requirements | Allows users to make use of identifiers when the identifier system is not known. | |
| Comments | 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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.performer.identifier.system | Σ | |
| Short | The namespace for the identifier value | |
| Definition | Establishes the namespace for the value - that is, an absolute URL that describes a set values that are unique. | |
| Cardinality | 1..1 | |
| Type | uri | |
| Summary | True | |
| Requirements | 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. | |
| Comments | Identifier.system is always case sensitive. | |
| Constraints |
| |
| Examples | Generalhttp://www.acme.com/identifiers/patientMedical Council Registration https://fhir.synapxe.sg/NamingSystem/mcrDental Council Registration https://fhir.synapxe.sg/NamingSystem/dcr | |
| Mappings |
| |
| Bundle.entry.resource.performer.identifier.value | Σ C | |
| Short | The value that is unique | |
| Definition | The portion of the identifier typically relevant to the user and which is unique within the context of the system. | |
| Cardinality | 1..1 | |
| Type | string | |
| Summary | True | |
| Comments | 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 http://hl7.org/fhir/StructureDefinition/rendered-value). 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. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ident-1 | |
| Constraints |
| |
| Examples | General123456 | |
| Mappings |
| |
| Bundle.entry.resource.performer.identifier.period | Σ C | |
| Short | Time period when id is/was valid for use | |
| Definition | Time period during which identifier is/was valid for use. | |
| Cardinality | 0..0 | |
| Type | Period | |
| Summary | True | |
| Comments | 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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.performer.identifier.assigner | Σ C | |
| Short | Organization that issued id (may be just text) | |
| Definition | Organization that issued/manages the identifier. | |
| Cardinality | 0..0 | |
| Type | Reference(Organization) | |
| Summary | True | |
| Comments | 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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.performer.display | Σ C | |
| Short | Text alternative for the resource | |
| Definition | Plain text narrative that identifies the resource in addition to the resource reference. | |
| Cardinality | 1..1 | |
| Type | string | |
| Summary | True | |
| Comments | This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ref-2 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.device | ||
| Short | Intended type of device for the administration | |
| Definition | The intended type of device that is to be used for the administration of the medication (for example, PCA Pump). | |
| Cardinality | 0..0 | |
| Type | CodeableReference(DeviceDefinition) | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.recorder | C | |
| Short | The healthcare professional responsible for prescribing this medication order | |
| Definition | The healthcare professional responsible for prescribing this medication order | |
| Cardinality | 0..0 | |
| Type | Reference(Practitioner) | |
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolvable (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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.recorder.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..0 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.resource.recorder.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.recorder.reference | Σ C | |
| Short | Literal reference, Relative, internal or absolute URL | |
| Definition | A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. | |
| Cardinality | 0..0 | |
| Type | string | |
| Summary | True | |
| Comments | Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ref-2, ref-1 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.recorder.type | Σ | |
| Short | Type the reference refers to (e.g. "Patient") - must be a resource in resources | |
| Definition | The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). | |
| Cardinality | 0..1 | |
| Type | uri | |
| Binding | Aa resource (or, for logical models, the URI of the logical model). | |
| Summary | True | |
| Comments | This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a known RESTful URL) or by resolving the target of the reference. | |
| Constraints |
| |
| Pattern | Practitioner | |
| Mappings |
| |
| Bundle.entry.resource.recorder.identifier | Σ C | |
| Short | Logical reference, when literal reference is not known | |
| Definition | An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. | |
| Cardinality | 1..1 | |
| Type | Identifier | |
| Summary | True | |
| Comments | When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). This element only allows for a single identifier. In the case where additional identifers are required, use the http://hl7.org/fhir/StructureDefinition/additionalIdentifier extension. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ref-2 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.recorder.identifier.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..0 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.resource.recorder.identifier.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.recorder.identifier.use | Σ ?! | |
| Short | usual | official | temp | secondary | old (If known) | |
| Definition | The purpose of this identifier. | |
| Cardinality | 0..0 | |
| Type | code | |
| Binding | Identifies the purpose for this identifier, if known . | |
| Modifier | True | |
| Summary | True | |
| Requirements | Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. | |
| Comments | Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.recorder.identifier.type | Σ | |
| Short | Description of identifier | |
| Definition | A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. | |
| Cardinality | 0..0 | |
| Type | CodeableConcept | |
| Binding | A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. | |
| Summary | True | |
| Requirements | Allows users to make use of identifiers when the identifier system is not known. | |
| Comments | 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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.recorder.identifier.system | Σ | |
| Short | The namespace for the identifier value | |
| Definition | Establishes the namespace for the value - that is, an absolute URL that describes a set values that are unique. | |
| Cardinality | 1..1 | |
| Type | uri | |
| Summary | True | |
| Requirements | 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. | |
| Comments | Identifier.system is always case sensitive. | |
| Constraints |
| |
| Examples | Generalhttp://www.acme.com/identifiers/patientMedical Council Registration https://fhir.synapxe.sg/NamingSystem/mcrPharmacist Registration Number https://fhir.synapxe.sg/NamingSystem/prnDental Council Registration https://fhir.synapxe.sg/NamingSystem/dcrSingapore Nursing Board https://fhir.synapxe.sg/NamingSystem/snb | |
| Mappings |
| |
| Bundle.entry.resource.recorder.identifier.value | Σ C | |
| Short | The value that is unique | |
| Definition | The portion of the identifier typically relevant to the user and which is unique within the context of the system. | |
| Cardinality | 1..1 | |
| Type | string | |
| Summary | True | |
| Comments | 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 http://hl7.org/fhir/StructureDefinition/rendered-value). 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. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ident-1 | |
| Constraints |
| |
| Examples | General123456 | |
| Mappings |
| |
| Bundle.entry.resource.recorder.identifier.period | Σ C | |
| Short | Time period when id is/was valid for use | |
| Definition | Time period during which identifier is/was valid for use. | |
| Cardinality | 0..0 | |
| Type | Period | |
| Summary | True | |
| Comments | 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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.recorder.identifier.assigner | Σ C | |
| Short | Organization that issued id (may be just text) | |
| Definition | Organization that issued/manages the identifier. | |
| Cardinality | 0..0 | |
| Type | Reference(Organization) | |
| Summary | True | |
| Comments | 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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.recorder.display | Σ C | |
| Short | Text alternative for the resource | |
| Definition | Plain text narrative that identifies the resource in addition to the resource reference. | |
| Cardinality | 1..1 | |
| Type | string | |
| Summary | True | |
| Comments | This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ref-2 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.reason | ||
| Short | Reason or indication for ordering or not ordering the medication | |
| Definition | The reason or the indication for ordering or not ordering the medication. | |
| Cardinality | 0..1 | |
| Type | CodeableReference(Condition | Observation) | |
| Binding | A coded concept indicating why the medication was ordered. | |
| Comments | This could be a diagnosis code. If a full condition record exists or additional detail is needed, use reasonReference. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.reason.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..0 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.resource.reason.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.reason.concept | Σ | |
| Short | Concept - reference to a terminology or just text | |
| Definition | A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text. | |
| Cardinality | 1..1 | |
| Type | CodeableConcept | |
| Binding | ||
| Summary | True | |
| Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.reason.concept.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..0 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.resource.reason.concept.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.reason.concept.coding | Σ C | |
| Short | Code defined by a terminology system | |
| Definition | A reference to a code defined by a terminology system. | |
| Cardinality | 1..* | |
| Type | Coding | |
| Summary | True | |
| Requirements | Allows for alternative encodings within a code system, and translations to other code systems. | |
| Comments | Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.reason.concept.coding.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..0 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.resource.reason.concept.coding.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.reason.concept.coding.system | Σ | |
| Short | Identity of the terminology system | |
| Definition | The identification of the code system that defines the meaning of the symbol in the code. | |
| Cardinality | 1..1 | |
| Type | uri | |
| Summary | True | |
| Requirements | Need to be unambiguous about the source of the definition of the symbol. | |
| Comments | The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should be an absolute reference to some definition that establishes the system clearly and unambiguously. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.reason.concept.coding.version | Σ | |
| Short | Version of the system - if relevant | |
| Definition | The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. | |
| Cardinality | 0..0 | |
| Type | string | |
| Summary | True | |
| Comments | Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.reason.concept.coding.code | Σ C | |
| Short | Symbol in syntax defined by the system | |
| Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). | |
| Cardinality | 1..1 | |
| Type | code | |
| Summary | True | |
| Requirements | Need to refer to a particular code in the system. | |
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |
| Conditions | The cardinality or value of this element may be affected by these constraints: cod-1 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.reason.concept.coding.display | Σ C | |
| Short | Representation defined by the system | |
| Definition | A representation of the meaning of the code in the system, following the rules of the system. | |
| Cardinality | 1..1 | |
| Type | string | |
| Summary | True | |
| Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. | |
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |
| Conditions | The cardinality or value of this element may be affected by these constraints: cod-1 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.reason.concept.coding.userSelected | Σ | |
| Short | If this coding was chosen directly by the user | |
| Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). | |
| Cardinality | 0..0 | |
| Type | boolean | |
| Summary | True | |
| Requirements | This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. | |
| Comments | Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.reason.concept.text | Σ | |
| Short | Plain text representation of the concept | |
| Definition | A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. | |
| Cardinality | 0..1 | |
| Type | string | |
| Summary | True | |
| Requirements | The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. | |
| Comments | Very often the text is the same as a displayName of one of the codings. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.reason.reference | Σ C | |
| Short | Reference to a resource (by instance) | |
| Definition | A reference to a resource the provides exact details about the information being referenced. | |
| Cardinality | 0..1 | |
| Type | Reference | |
| Summary | True | |
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolvable (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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.courseOfTherapyType | ||
| Short | Overall pattern of medication administration | |
| Definition | The description of the overall pattern of the administration of the medication to the patient. | |
| Cardinality | 0..0 | |
| Type | CodeableConcept | |
| Binding | Identifies the overall pattern of medication administratio. | |
| Comments | This attribute should not be confused with the protocol of the medication. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.insurance | C | |
| Short | Associated insurance coverage | |
| Definition | Insurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be required for delivering the requested service. | |
| Cardinality | 0..0 | |
| Type | Reference(ClaimResponse | Coverage) | |
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolvable (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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.note | ||
| Short | Text node with attribution | |
| Definition | A text note which also contains information about who made the statement and when. | |
| Cardinality | 0..1 | |
| Type | Annotation | |
| Comments | 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). | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.renderedDosageInstruction | ||
| Short | Full representation of the dosage instructions | |
| Definition | The full representation of the dose of the medication included in all dosage instructions. To be used when multiple dosage instructions are included to represent complex dosing such as increasing or tapering doses. | |
| Cardinality | 0..0 | |
| Type | markdown | |
| Requirements | The content of the renderedDosageInstructions must not be different than the dose represented in the dosageInstruction content. | |
| Comments | Systems are not required to have markdown support, so the text should be readable without markdown processing. The markdown syntax is GFM - see https://github.github.com/gfm/ | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.effectiveDosePeriod | C | |
| Short | Period over which the medication is to be taken | |
| Definition | The period over which the medication is to be taken. Where there are multiple dosageInstruction lines (for example, tapering doses), this is the earliest date and the latest end date of the dosageInstructions. | |
| Cardinality | 0..1 | |
| Type | Period | |
| Comments | 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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.effectiveDosePeriod.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..0 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.resource.effectiveDosePeriod.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.effectiveDosePeriod.start | Σ C | |
| Short | Starting time with inclusive boundary | |
| Definition | The start of the period. The boundary is inclusive. | |
| Cardinality | 1..1 | |
| Type | dateTime | |
| Summary | True | |
| Comments | If the low element is missing, the meaning is that the low boundary is not known. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: per-1 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.effectiveDosePeriod.end | Σ C | |
| Short | End time with inclusive boundary, if not ongoing | |
| Definition | The 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. | |
| Cardinality | 0..1 | |
| Type | dateTime | |
| Summary | True | |
| Comments | The end 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. | |
| Meaning when missing | If the end of the period is missing, it means that the period is ongoing | |
| Conditions | The cardinality or value of this element may be affected by these constraints: per-1 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction | C | |
| Short | Specific instructions for how the medication should be taken | |
| Definition | Specific instructions for how the medication is to be used by the patient. | |
| Cardinality | 1..1 | |
| Type | Dosage | |
| Comments | 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. In general, each prescribed drug will be a separate Medication Request. When drug orders are grouped together at the time of order entry, but each of the drugs can be manipulated independently e.g. changing the status of one order to "completed" or "cancelled", changing another order status to "on-hold", the method to "group" all of the medication requests together is to use MedicationRequest.groupIdentifier element. All of the orders grouped together in this manner will have the same groupIdentifier, and separately, each order in the group may have a unique identifier. There are cases that require grouping of Medication orders together when it is necessary to specify optionality e.g. order two drugs at one time, but stating either of these drugs may be used to treat the patient. The use of a RequestOrchestration should be used as a parent for the Medication orders that require this type of grouping. An example when it may be necessary to group medication orders together is when you specify timing relationships e.g. order drug "xyz" with dose 123, then taper the same drug to a different dose after some interval of time precedence: e.g. give drug "abc" followed by drug "def" e.g. give drug 30 minutes before some procedure was performed more generically this supports - hierarchical groups of actions, where each specific action references the action to be performed (in terms of a Request resource), and each group describes additional behavior, relationships, and applicable conditions between the actions in the overall group. Note that one should NOT use the List or Composition resource to accomplish the above requirements. You may use List or Composition for other business requirements, but not to address the specific requirements of grouping medication orders. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..0 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.modifierExtension | Σ ?! C | |
| Short | Extensions that cannot be ignored even if unrecognized | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Modifier | True | |
| Summary | True | |
| Alias | extensions, user content, modifiers | |
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.sequence | Σ | |
| Short | The sequence number of the dosage instructions for step or variable dose | |
| Definition | The sequence number of the dosage instructions for step or variable dose | |
| Cardinality | 0..1 | |
| Type | integer | |
| Summary | True | |
| Requirements | 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. | |
| Comments | 32 bit number; for values larger than this, use decimal | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.text | Σ | |
| Short | Free text dosage instructions e.g. SIG | |
| Definition | Free text dosage instructions e.g. SIG. | |
| Cardinality | 0..1 | |
| Type | string | |
| Summary | True | |
| Requirements | 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. | |
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.additionalInstruction | Σ | |
| Short | Supplemental instruction or warnings to the patient - e.g. "with meals", "may cause drowsiness" | |
| Definition | Supplemental instructions to the patient on how to take the medication (e.g. "with meals" or"take half to one hour before food") or warnings for the patient about the medication (e.g. "may cause drowsiness" or "avoid exposure of skin to direct sunlight or sunlamps"). | |
| Cardinality | 0..1 | |
| Type | CodeableConcept | |
| Binding | A coded concept identifying additional instructions such as "take with water" or "avoid operating heavy machinery". | |
| Summary | True | |
| Requirements | 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. | |
| Comments | Information about administration or preparation of the medication (e.g. "infuse as rapidly as possibly via intraperitoneal port" or take "immediately following drug x") should be populated in dosage.text. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.additionalInstruction.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..0 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.additionalInstruction.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.additionalInstruction.coding | Σ C | |
| Short | Code defined by a terminology system | |
| Definition | A reference to a code defined by a terminology system. | |
| Cardinality | 0..0 | |
| Type | Coding | |
| Summary | True | |
| Requirements | Allows for alternative encodings within a code system, and translations to other code systems. | |
| Comments | Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.additionalInstruction.text | Σ | |
| Short | Plain text representation of the concept | |
| Definition | A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. | |
| Cardinality | 1..1 | |
| Type | string | |
| Summary | True | |
| Requirements | The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. | |
| Comments | Very often the text is the same as a displayName of one of the codings. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.patientInstruction | Σ | |
| Short | Patient or consumer oriented instructions | |
| Definition | Instructions in terms that are understood by the patient or consumer. | |
| Cardinality | 0..0 | |
| Type | string | |
| Summary | True | |
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.timing | Σ | |
| Short | When medication should be administered | |
| Definition | When medication should be administered. Frequency code, duration and durationUnits. Refer to https://hl7.org/fhir/datatypes.html#timing on how to populate timing. For example duration code "1 week" and frquency code "every morning" will map to period "1", periodUnit "week" and when "MORN" | |
| Cardinality | 0..1 | |
| Type | Timing | |
| Summary | True | |
| Requirements | 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. | |
| Comments | 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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.timing.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..0 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.timing.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.timing.modifierExtension | Σ ?! C | |
| Short | Extensions that cannot be ignored even if unrecognized | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Modifier | True | |
| Summary | True | |
| Alias | extensions, user content, modifiers | |
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.timing.event | Σ | |
| Short | When the event occurs | |
| Definition | Identifies specific times when the event occurs. | |
| Cardinality | 0..1 | |
| Type | dateTime | |
| Summary | True | |
| Requirements | In a Medication Administration Record, for instance, you need to take a general specification, and turn it into a precise specification. | |
| Comments | UTC offset is allowed for dates and partial dates | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.timing.repeat | Σ C | |
| Short | When the event is to occur | |
| Definition | A set of rules that describe when the event is scheduled. | |
| Cardinality | 0..1 | |
| Type | Element | |
| Summary | True | |
| Requirements | Many timing schedules are determined by regular repetitions. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.timing.repeat.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..0 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.timing.repeat.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.timing.repeat.bounds[x] | Σ | |
| Short | Length/Range of lengths, or (Start and/or end) limits | |
| Definition | Either 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. | |
| Cardinality | 0..1 | |
| Type | Period | |
| Summary | True | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.timing.repeat.count | Σ C | |
| Short | Number of times to repeat | |
| Definition | A 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. | |
| Cardinality | 0..1 | |
| Type | positiveInt | |
| Summary | True | |
| Requirements | Repetitions may be limited by end time or total occurrences. | |
| Comments | If you have both bounds and count, then this should be understood as within the bounds period, until count times happens. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: tim-8 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.timing.repeat.countMax | Σ C | |
| Short | Maximum number of times to repeat | |
| Definition | If present, indicates that the count is a range - so to perform the action between [count] and [countMax] times. | |
| Cardinality | 0..1 | |
| Type | positiveInt | |
| Summary | True | |
| Comments | 32 bit number; for values larger than this, use decimal | |
| Conditions | The cardinality or value of this element may be affected by these constraints: tim-8 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.timing.repeat.duration | Σ C | |
| Short | How long when it happens | |
| Definition | How 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. | |
| Cardinality | 0..1 | |
| Type | decimal | |
| Summary | True | |
| Requirements | Some activities are not instantaneous and need to be maintained for a period of time. | |
| Comments | 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). | |
| Conditions | The cardinality or value of this element may be affected by these constraints: tim-7, tim-1, tim-4 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.timing.repeat.durationMax | Σ C | |
| Short | How long when it happens (Max) | |
| Definition | If present, indicates that the duration is a range - so to perform the action between [duration] and [durationMax] time length. | |
| Cardinality | 0..1 | |
| Type | decimal | |
| Summary | True | |
| Requirements | Some activities are not instantaneous and need to be maintained for a period of time. | |
| Comments | 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). | |
| Conditions | The cardinality or value of this element may be affected by these constraints: tim-7 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.timing.repeat.durationUnit | Σ C | |
| Short | s | min | h | d | wk | mo | a - unit of time (UCUM) | |
| Definition | The units of time for the duration, in UCUM units Normal practice is to use the 'mo' code as a calendar month when calculating the next occurrence. | |
| Cardinality | 0..1 | |
| Type | code | |
| Binding | A unit of time (units from UCUM). | |
| Summary | True | |
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |
| Conditions | The cardinality or value of this element may be affected by these constraints: tim-1 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.timing.repeat.frequency | Σ | |
| Short | Indicates the number of repetitions that should occur within a period. I.e. Event occurs frequency times per period | |
| Definition | The 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. | |
| Cardinality | 0..1 | |
| Type | positiveInt | |
| Summary | True | |
| Comments | 32 bit number; for values larger than this, use decimal | |
| Meaning when missing | If no frequency is stated, the assumption is that the event occurs once per period, but systems SHOULD always be specific about this | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.timing.repeat.frequencyMax | Σ | |
| Short | Event occurs up to frequencyMax times per period | |
| Definition | If present, indicates that the frequency is a range - so to repeat between [frequency] and [frequencyMax] times within the period or period range. | |
| Cardinality | 0..1 | |
| Type | positiveInt | |
| Summary | True | |
| Comments | 32 bit number; for values larger than this, use decimal | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.timing.repeat.period | Σ C | |
| Short | The duration to which the frequency applies. I.e. Event occurs frequency times per period | |
| Definition | Indicates 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. | |
| Cardinality | 0..1 | |
| Type | decimal | |
| Summary | True | |
| Comments | 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) | |
| Conditions | The cardinality or value of this element may be affected by these constraints: tim-6, tim-5, tim-2 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.timing.repeat.periodMax | Σ C | |
| Short | Upper limit of period (3-4 hours) | |
| Definition | If present, indicates that the period is a range from [period] to [periodMax], allowing expressing concepts such as "do this once every 3-5 days. | |
| Cardinality | 0..1 | |
| Type | decimal | |
| Summary | True | |
| Comments | 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) | |
| Conditions | The cardinality or value of this element may be affected by these constraints: tim-6 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.timing.repeat.periodUnit | Σ C | |
| Short | s | min | h | d | wk | mo | a - unit of time (UCUM) | |
| Definition | The units of time for the period in UCUM units Normal practice is to use the 'mo' code as a calendar month when calculating the next occurrence. | |
| Cardinality | 0..1 | |
| Type | code | |
| Binding | A unit of time (units from UCUM). | |
| Summary | True | |
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |
| Conditions | The cardinality or value of this element may be affected by these constraints: tim-2 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.timing.repeat.dayOfWeek | Σ | |
| Short | mon | tue | wed | thu | fri | sat | sun | |
| Definition | If one or more days of week is provided, then the action happens only on the specified day(s). | |
| Cardinality | 0..1 | |
| Type | code | |
| Binding | ||
| Summary | True | |
| Comments | If no days are specified, the action is assumed to happen every day as otherwise specified. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.timing.repeat.timeOfDay | Σ C | |
| Short | Time of day for action | |
| Definition | Specified time of day for action to take place. | |
| Cardinality | 0..1 | |
| Type | time | |
| Summary | True | |
| Comments | When time of day is specified, it is inferred that the action happens every day (as filtered by dayofWeek) on the specified times. If there's a timeOfDay, there cannot be a when, or vice versa. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: tim-10 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.timing.repeat.when | Σ C | |
| Short | Code for time period of occurrence | |
| Definition | An approximate time period during the day, potentially linked to an event of daily living that indicates when the action should occur. | |
| Cardinality | 0..1 | |
| Type | code | |
| Binding | Real-world event relating to the schedule. | |
| Summary | True | |
| Requirements | Timings are frequently determined by occurrences such as waking, eating and sleep. | |
| Comments | When more than one event is listed, the event is tied to the union of the specified events. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: tim-9, tim-10 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.timing.repeat.offset | Σ C | |
| Short | Minutes from event (before or after) | |
| Definition | The 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. | |
| Cardinality | 0..1 | |
| Type | unsignedInt | |
| Summary | True | |
| Comments | 32 bit number; for values larger than this, use decimal | |
| Conditions | The cardinality or value of this element may be affected by these constraints: tim-9 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.timing.code | Σ | |
| Short | C | BID | TID | QID | AM | PM | QD | QOD | + | |
| Definition | A 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). | |
| Cardinality | 0..1 | |
| Type | CodeableConcept | |
| Binding | Code for a known / defined timing pattern. | |
| Summary | True | |
| Comments | 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). | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.timing.code.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..1 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.timing.code.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..* | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.timing.code.coding | Σ C | |
| Short | Code defined by a terminology system | |
| Definition | A reference to a code defined by a terminology system. | |
| Cardinality | 0..* | |
| Type | Coding | |
| Summary | True | |
| Requirements | Allows for alternative encodings within a code system, and translations to other code systems. | |
| Comments | Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.timing.code.coding.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..1 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.timing.code.coding.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..* | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.timing.code.coding.system | Σ | |
| Short | Identity of the terminology system | |
| Definition | The identification of the code system that defines the meaning of the symbol in the code. | |
| Cardinality | 0..1 | |
| Type | uri | |
| Summary | True | |
| Requirements | Need to be unambiguous about the source of the definition of the symbol. | |
| Comments | The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should be an absolute reference to some definition that establishes the system clearly and unambiguously. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.timing.code.coding.version | Σ | |
| Short | Version of the system - if relevant | |
| Definition | The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. | |
| Cardinality | 0..1 | |
| Type | string | |
| Summary | True | |
| Comments | Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.timing.code.coding.code | Σ C | |
| Short | Symbol in syntax defined by the system | |
| Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). | |
| Cardinality | 0..1 | |
| Type | code | |
| Summary | True | |
| Requirements | Need to refer to a particular code in the system. | |
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |
| Conditions | The cardinality or value of this element may be affected by these constraints: cod-1 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.timing.code.coding.display | Σ C | |
| Short | Representation defined by the system | |
| Definition | A representation of the meaning of the code in the system, following the rules of the system. | |
| Cardinality | 0..1 | |
| Type | string | |
| Summary | True | |
| Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. | |
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |
| Conditions | The cardinality or value of this element may be affected by these constraints: cod-1 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.timing.code.coding.userSelected | Σ | |
| Short | If this coding was chosen directly by the user | |
| Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). | |
| Cardinality | 0..0 | |
| Type | boolean | |
| Summary | True | |
| Requirements | This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. | |
| Comments | Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.timing.code.text | Σ | |
| Short | Plain text representation of the concept | |
| Definition | A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. | |
| Cardinality | 0..1 | |
| Type | string | |
| Summary | True | |
| Requirements | The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. | |
| Comments | Very often the text is the same as a displayName of one of the codings. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.asNeeded | Σ C | |
| Short | Take "as needed" | |
| Definition | Indicates whether the Medication is only taken when needed within a specific dosing schedule (Boolean option). | |
| Cardinality | 0..0 | |
| Type | boolean | |
| Summary | True | |
| Comments | Can express "as needed" without a reason by setting the Boolean = True. In this case the CodeableConcept is not populated. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: dos-1 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.asNeededFor | Σ C | |
| Short | Frequency qualifier. Take "as needed" (for x) | |
| Definition | A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text. | |
| Cardinality | 0..1 | |
| Type | CodeableConcept | |
| Binding | 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. | |
| Summary | True | |
| Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: dos-1 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.asNeededFor.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..1 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.asNeededFor.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.asNeededFor.coding | Σ C | |
| Short | Code defined by a terminology system | |
| Definition | A reference to a code defined by a terminology system. | |
| Cardinality | 0..0 | |
| Type | Coding | |
| Summary | True | |
| Requirements | Allows for alternative encodings within a code system, and translations to other code systems. | |
| Comments | Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.asNeededFor.text | Σ | |
| Short | Plain text representation of the concept | |
| Definition | A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. | |
| Cardinality | 1..1 | |
| Type | string | |
| Summary | True | |
| Requirements | The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. | |
| Comments | Very often the text is the same as a displayName of one of the codings. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.site | Σ | |
| Short | Body site to administer to | |
| Definition | Body site to administer to. | |
| Cardinality | 0..0 | |
| Type | CodeableConcept | |
| Binding | A coded concept describing the site location the medicine enters into or onto the body. | |
| Summary | True | |
| Requirements | A coded specification of the anatomic site where the medication first enters the body. | |
| Comments | If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension http://hl7.org/fhir/StructureDefinition/bodySite. May be a summary code, or a reference to a very precise definition of the location, or both. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.route | Σ | |
| Short | Concept - reference to a terminology or just text | |
| Definition | A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text. | |
| Cardinality | 0..1 | |
| Type | CodeableConcept | |
| Binding | A coded concept describing the route or physiological path of administration of a therapeutic agent into or onto the body of a subject. | |
| Summary | True | |
| Requirements | A code specifying the route or physiological path of administration of a therapeutic agent into or onto a patient's body. | |
| Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.route.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..0 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.route.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.route.coding | Σ C | |
| Short | Code defined by a terminology system | |
| Definition | A reference to a code defined by a terminology system. | |
| Cardinality | 1..* | |
| Type | Coding | |
| Summary | True | |
| Requirements | Allows for alternative encodings within a code system, and translations to other code systems. | |
| Comments | Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.route.coding.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..0 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.route.coding.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.route.coding.system | Σ | |
| Short | Identity of the terminology system | |
| Definition | The identification of the code system that defines the meaning of the symbol in the code. | |
| Cardinality | 1..1 | |
| Type | uri | |
| Summary | True | |
| Requirements | Need to be unambiguous about the source of the definition of the symbol. | |
| Comments | The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should be an absolute reference to some definition that establishes the system clearly and unambiguously. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.route.coding.version | Σ | |
| Short | Version of the system - if relevant | |
| Definition | The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. | |
| Cardinality | 0..1 | |
| Type | string | |
| Summary | True | |
| Comments | Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.route.coding.code | Σ C | |
| Short | Symbol in syntax defined by the system | |
| Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). | |
| Cardinality | 1..1 | |
| Type | code | |
| Summary | True | |
| Requirements | Need to refer to a particular code in the system. | |
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |
| Conditions | The cardinality or value of this element may be affected by these constraints: cod-1 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.route.coding.display | Σ C | |
| Short | Representation defined by the system | |
| Definition | A representation of the meaning of the code in the system, following the rules of the system. | |
| Cardinality | 1..1 | |
| Type | string | |
| Summary | True | |
| Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. | |
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |
| Conditions | The cardinality or value of this element may be affected by these constraints: cod-1 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.route.coding.userSelected | Σ | |
| Short | If this coding was chosen directly by the user | |
| Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). | |
| Cardinality | 0..0 | |
| Type | boolean | |
| Summary | True | |
| Requirements | This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. | |
| Comments | Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.route.text | Σ | |
| Short | Plain text representation of the concept | |
| Definition | A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. | |
| Cardinality | 0..1 | |
| Type | string | |
| Summary | True | |
| Requirements | The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. | |
| Comments | Very often the text is the same as a displayName of one of the codings. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.method | Σ | |
| Short | Technique for administering medication | |
| Definition | Technique for administering medication. | |
| Cardinality | 0..0 | |
| Type | CodeableConcept | |
| Binding | A coded concept describing the technique by which the medicine is administered. | |
| Summary | True | |
| Requirements | 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. | |
| Comments | Terminologies used often pre-coordinate this term with the route and or form of administration. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.doseAndRate | Σ | |
| Short | Amount of medication administered, to be administered or typical amount to be administered | |
| Definition | Depending on the resource,this is the amount of medication administered, to be administered or typical amount to be administered. | |
| Cardinality | 0..* | |
| Type | Element | |
| Summary | True | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.doseAndRate.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..0 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.doseAndRate.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.doseAndRate.type | Σ | |
| Short | The kind of dose or rate specified | |
| Definition | The kind of dose or rate specified, for example, ordered or calculated. | |
| Cardinality | 0..0 | |
| Type | CodeableConcept | |
| Binding | The kind of dose or rate specified. | |
| Summary | True | |
| Requirements | If the type is not populated, assume to be "ordered". | |
| Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.doseAndRate.dose[x] | Σ | |
| Short | Amount of medication per dose | |
| Definition | Amount of medication per dose. | |
| Cardinality | 1..1 | |
| Type | SimpleQuantity | Range | |
| Summary | True | |
| Requirements | The amount of therapeutic or other substance given at one administration event. | |
| Comments | 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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.doseAndRate.rate[x] | Σ | |
| Short | Amount of medication per unit of time | |
| Definition | Amount of medication per unit of time. | |
| Cardinality | 0..1 | |
| Type | SimpleQuantity | Range | Ratio | |
| Summary | True | |
| Requirements | 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. | |
| Comments | 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 grammar 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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.maxDosePerPeriod | Σ C | |
| Short | Upper limit on medication per unit of time | |
| Definition | Upper limit on medication per unit of time. | |
| Cardinality | 0..0 | |
| Type | Ratio | |
| Summary | True | |
| Requirements | 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. | |
| Comments | 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". | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.maxDosePerAdministration | Σ C | |
| Short | Upper limit on medication per administration | |
| Definition | Upper limit on medication per administration. | |
| Cardinality | 0..0 | |
| Type | SimpleQuantity | |
| Summary | True | |
| Requirements | The maximum total quantity of a therapeutic substance that may be administered to a subject per administration. | |
| Comments | 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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dosageInstruction.maxDosePerLifetime | Σ C | |
| Short | Upper limit on medication per lifetime of the patient | |
| Definition | Upper limit on medication per lifetime of the patient. | |
| Cardinality | 0..0 | |
| Type | SimpleQuantity | |
| Summary | True | |
| Requirements | The maximum total quantity of a therapeutic substance that may be administered per lifetime of the subject. | |
| Comments | 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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest | ||
| Short | Medication supply authorization | |
| Definition | Indicates 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. | |
| Cardinality | 0..1 | |
| Type | BackboneElement | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..0 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.modifierExtension | Σ ?! C | |
| Short | Extensions that cannot be ignored even if unrecognized | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Modifier | True | |
| Summary | True | |
| Alias | extensions, user content, modifiers | |
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.initialFill | ||
| Short | First fill details | |
| Definition | Indicates the quantity or duration for the first dispense of the medication. | |
| Cardinality | 0..0 | |
| Type | BackboneElement | |
| Comments | If populating this element, either the quantity or the duration must be included. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.initialFill.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..1 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.initialFill.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..* | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.initialFill.modifierExtension | Σ ?! C | |
| Short | Extensions that cannot be ignored even if unrecognized | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | |
| Cardinality | 0..* | |
| Type | Extension | |
| Modifier | True | |
| Summary | True | |
| Alias | extensions, user content, modifiers | |
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.initialFill.quantity | C | |
| Short | First fill quantity | |
| Definition | The amount or quantity to provide as part of the first dispense. | |
| Cardinality | 0..1 | |
| Type | SimpleQuantity | |
| Comments | 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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.initialFill.duration | C | |
| Short | First fill duration | |
| Definition | The length of time that the first dispense is expected to last. | |
| Cardinality | 0..1 | |
| Type | Duration | |
| Comments | 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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.dispenseInterval | C | |
| Short | Minimum period of time between dispenses | |
| Definition | The minimum period of time that must occur between dispenses of the medication. | |
| Cardinality | 0..0 | |
| Type | Duration | |
| Comments | 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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.validityPeriod | C | |
| Short | Time period supply is authorized for | |
| Definition | This indicates the validity period of a prescription (stale dating the Prescription). | |
| Cardinality | 0..0 | |
| Type | Period | |
| Requirements | Indicates when the Prescription becomes valid, and when it ceases to be a dispensable Prescription. | |
| Comments | 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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.numberOfRepeatsAllowed | ||
| Short | Number of refills authorized | |
| Definition | 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. | |
| Cardinality | 0..0 | |
| Type | unsignedInt | |
| Comments | If displaying "number of authorized fills", add 1 to this number. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.quantity | C | |
| Short | Amount of medication to supply per dispense | |
| Definition | The amount that is to be dispensed for one fill. | |
| Cardinality | 0..1 | |
| Type | SimpleQuantity | |
| Comments | 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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.quantity.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..0 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.quantity.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.quantity.value | Σ | |
| Short | Numerical value (with implicit precision) | |
| Definition | The value of the measured amount. The value includes an implicit precision in the presentation of the value. | |
| Cardinality | 1..1 | |
| Type | decimal | |
| Summary | True | |
| Requirements | Precision is handled implicitly in almost all cases of measurement. | |
| Comments | 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). | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.quantity.comparator | Σ ?! | |
| Short | < | <= | >= | > | ad - how to understand the value | |
| Definition | Not allowed to be used in this context | |
| Cardinality | 0..0 | |
| Type | code | |
| Binding | How the Quantity should be understood and represented. | |
| Modifier | True | |
| Summary | True | |
| Requirements | Need a framework for handling measures where the value is <5ug/L or >400mg/L due to the limitations of measuring methodology. | |
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |
| Meaning when missing | If there is no comparator, then there is no modification of the value | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.quantity.unit | Σ | |
| Short | Unit representation | |
| Definition | A human-readable form of the unit. | |
| Cardinality | 1..1 | |
| Type | string | |
| Summary | True | |
| Requirements | There are many representations for units of measure and in many contexts, particular representations are fixed and required. I.e. mcg for micrograms. | |
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.quantity.system | Σ C | |
| Short | System that defines coded unit form | |
| Definition | The identification of the system that provides the coded form of the unit. | |
| Cardinality | 1..1 | |
| Type | uri | |
| Summary | True | |
| Requirements | Need to know the system that defines the coded form of the unit. | |
| Comments | see http://en.wikipedia.org/wiki/Uniform_resource_identifier | |
| Conditions | The cardinality or value of this element may be affected by these constraints: qty-3 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.quantity.code | Σ C | |
| Short | Coded form of the unit | |
| Definition | A computer processable form of the unit in some unit representation system. | |
| Cardinality | 1..1 | |
| Type | code | |
| Summary | True | |
| Requirements | 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. | |
| Comments | 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. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: qty-3 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.expectedSupplyDuration | C | |
| Short | Number of days supply per dispense | |
| Definition | Identifies the period time over which the supplied product is expected to be used, or the length of time the dispense is expected to last. | |
| Cardinality | 0..0 | |
| Type | Duration | |
| Comments | 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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.expectedSupplyDuration.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..0 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.expectedSupplyDuration.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.expectedSupplyDuration.value | Σ | |
| Short | Numerical value (with implicit precision) | |
| Definition | The value of the measured amount. The value includes an implicit precision in the presentation of the value. | |
| Cardinality | 1..1 | |
| Type | decimal | |
| Summary | True | |
| Requirements | Precision is handled implicitly in almost all cases of measurement. | |
| Comments | 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). | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.expectedSupplyDuration.comparator | Σ ?! | |
| Short | < | <= | >= | > | ad - how to understand the value | |
| Definition | How 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. | |
| Cardinality | 0..0 | |
| Type | code | |
| Binding | How the Quantity should be understood and represented. | |
| Modifier | True | |
| Summary | True | |
| Requirements | Need a framework for handling measures where the value is <5ug/L or >400mg/L due to the limitations of measuring methodology. | |
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |
| Meaning when missing | If there is no comparator, then there is no modification of the value | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.expectedSupplyDuration.unit | Σ | |
| Short | Unit representation | |
| Definition | A human-readable form of the unit. | |
| Cardinality | 1..1 | |
| Type | string | |
| Summary | True | |
| Requirements | There are many representations for units of measure and in many contexts, particular representations are fixed and required. I.e. mcg for micrograms. | |
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.expectedSupplyDuration.system | Σ C | |
| Short | System that defines coded unit form | |
| Definition | The identification of the system that provides the coded form of the unit. | |
| Cardinality | 1..1 | |
| Type | uri | |
| Summary | True | |
| Requirements | Need to know the system that defines the coded form of the unit. | |
| Comments | see http://en.wikipedia.org/wiki/Uniform_resource_identifier | |
| Conditions | The cardinality or value of this element may be affected by these constraints: qty-3 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.expectedSupplyDuration.code | Σ C | |
| Short | Coded form of the unit | |
| Definition | A computer processable form of the unit in some unit representation system. | |
| Cardinality | 1..1 | |
| Type | code | |
| Summary | True | |
| Requirements | 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. | |
| Comments | 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. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: qty-3 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.dispenser | C | |
| Short | Intended performer of dispense | |
| Definition | Indicates the intended performing Organization that will dispense the medication as specified by the prescriber. | |
| Cardinality | 0..1 | |
| Type | Reference(Location) | |
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolvable (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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.dispenser.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..0 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.dispenser.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.dispenser.reference | Σ C | |
| Short | Literal reference, Relative, internal or absolute URL | |
| Definition | A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. | |
| Cardinality | 0..0 | |
| Type | string | |
| Summary | True | |
| Comments | Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ref-2, ref-1 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.dispenser.type | Σ | |
| Short | Type the reference refers to (e.g. "Patient") - must be a resource in resources | |
| Definition | The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). | |
| Cardinality | 1..1 | |
| Type | uri | |
| Binding | Aa resource (or, for logical models, the URI of the logical model). | |
| Summary | True | |
| Comments | This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a known RESTful URL) or by resolving the target of the reference. | |
| Constraints |
| |
| Pattern | Location | |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.dispenser.identifier | Σ C | |
| Short | Logical reference, when literal reference is not known | |
| Definition | An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. | |
| Cardinality | 1..1 | |
| Type | Identifier | |
| Summary | True | |
| Comments | When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). This element only allows for a single identifier. In the case where additional identifers are required, use the http://hl7.org/fhir/StructureDefinition/additionalIdentifier extension. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ref-2 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.dispenser.identifier.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..0 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.dispenser.identifier.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.dispenser.identifier.use | Σ ?! | |
| Short | usual | official | temp | secondary | old (If known) | |
| Definition | The purpose of this identifier. | |
| Cardinality | 0..0 | |
| Type | code | |
| Binding | Identifies the purpose for this identifier, if known . | |
| Modifier | True | |
| Summary | True | |
| Requirements | Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. | |
| Comments | Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.dispenser.identifier.type | Σ | |
| Short | Description of identifier | |
| Definition | A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. | |
| Cardinality | 0..0 | |
| Type | CodeableConcept | |
| Binding | A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. | |
| Summary | True | |
| Requirements | Allows users to make use of identifiers when the identifier system is not known. | |
| Comments | 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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.dispenser.identifier.system | Σ | |
| Short | The namespace for the identifier value | |
| Definition | Establishes the namespace for the value - that is, an absolute URL that describes a set values that are unique. | |
| Cardinality | 1..1 | |
| Type | uri | |
| Summary | True | |
| Requirements | 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. | |
| Comments | Identifier.system is always case sensitive. | |
| Constraints |
| |
| Examples | Generalhttp://www.acme.com/identifiers/patient | |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.dispenser.identifier.value | Σ C | |
| Short | The value that is unique | |
| Definition | The portion of the identifier typically relevant to the user and which is unique within the context of the system. | |
| Cardinality | 1..1 | |
| Type | string | |
| Summary | True | |
| Comments | 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 http://hl7.org/fhir/StructureDefinition/rendered-value). 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. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ident-1 | |
| Constraints |
| |
| Examples | General123456 | |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.dispenser.identifier.period | Σ C | |
| Short | Time period when id is/was valid for use | |
| Definition | Time period during which identifier is/was valid for use. | |
| Cardinality | 0..0 | |
| Type | Period | |
| Summary | True | |
| Comments | 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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.dispenser.identifier.assigner | Σ C | |
| Short | Organization that issued id (may be just text) | |
| Definition | Organization that issued/manages the identifier. | |
| Cardinality | 0..0 | |
| Type | Reference(Organization) | |
| Summary | True | |
| Comments | 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. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.dispenser.display | Σ C | |
| Short | Text alternative for the resource | |
| Definition | Plain text narrative that identifies the resource in addition to the resource reference. | |
| Cardinality | 1..1 | |
| Type | string | |
| Summary | True | |
| Comments | This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ref-2 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.dispenserInstruction | ||
| Short | Additional information for the dispenser | |
| Definition | Provides additional information to the dispenser, for example, counselling to be provided to the patient. | |
| Cardinality | 0..0 | |
| Type | Annotation | |
| Comments | 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). | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.dispenseRequest.doseAdministrationAid | ||
| Short | Type of adherence packaging to use for the dispense | |
| Definition | Provides information about the type of adherence packaging to be supplied for the medication dispense. | |
| Cardinality | 0..0 | |
| Type | CodeableConcept | |
| Binding | ||
| Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.substitution | ||
| Short | Any restrictions on medication substitution | |
| Definition | Indicates whether or not substitution can or should be part of the dispense. In some cases, substitution must happen, in other cases substitution must not happen. This block explains the prescriber's intent. If nothing is specified substitution may be done. | |
| Cardinality | 0..0 | |
| Type | BackboneElement | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.substitution.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..1 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.resource.substitution.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..* | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.substitution.modifierExtension | Σ ?! C | |
| Short | Extensions that cannot be ignored even if unrecognized | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | |
| Cardinality | 0..* | |
| Type | Extension | |
| Modifier | True | |
| Summary | True | |
| Alias | extensions, user content, modifiers | |
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.substitution.allowed[x] | ||
| Short | Whether substitution is allowed or not | |
| Definition | True if the prescriber allows a different drug to be dispensed from what was prescribed. | |
| Cardinality | 1..1 | |
| Type | boolean | CodeableConcept | |
| Binding | Identifies the type of substitution allowed. | |
| Comments | This element is labeled as a modifier because whether substitution is allow or not, it cannot be ignored. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.substitution.reason | ||
| Short | Why should (not) substitution be made | |
| Definition | Indicates the reason for the substitution, or why substitution must or must not be performed. | |
| Cardinality | 0..1 | |
| Type | CodeableConcept | |
| Binding | SubstanceAdminSubstitutionReason | |
| Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.resource.eventHistory | C | |
| Short | A list of events of interest in the lifecycle | |
| Definition | Links 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. | |
| Cardinality | 0..0 | |
| Type | Reference(Provenance) | |
| Comments | This might not include provenances for all versions of the request – only those deemed "relevant" or important. This SHALL NOT include the provenance associated with this current version of the resource. (If that provenance is deemed to be a "relevant" change, it will need to be added as part of a later update. Until then, it can be queried directly as the provenance that points to this version using _revinclude All Provenances should have some historical version of this Request as their subject.). | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.search | Σ C | |
| Short | Search related information | |
| Definition | Information about the search process that lead to the creation of this entry. | |
| Cardinality | 0..0 | |
| Type | BackboneElement | |
| Summary | True | |
| Conditions | The cardinality or value of this element may be affected by these constraints: bdl-2 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.search.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..1 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.search.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..* | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.search.modifierExtension | Σ ?! C | |
| Short | Extensions that cannot be ignored even if unrecognized | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | |
| Cardinality | 0..* | |
| Type | Extension | |
| Modifier | True | |
| Summary | True | |
| Alias | extensions, user content, modifiers | |
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.search.mode | Σ | |
| Short | match | include - why this is in the result set | |
| Definition | Why this entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process. | |
| Cardinality | 0..1 | |
| Type | code | |
| Binding | Why an entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process. | |
| Summary | True | |
| Comments | There is only one mode. In some corner cases, a resource may be included because it is both a match and an include. In these circumstances, 'match' takes precedence. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.search.score | Σ | |
| Short | Search ranking (between 0 and 1) | |
| Definition | When searching, the server's search ranking score for the entry. | |
| Cardinality | 0..1 | |
| Type | decimal | |
| Summary | True | |
| Comments | Servers are not required to return a ranking score. 1 is most relevant, and 0 is least relevant. Often, search results are sorted by score, but the client may specify a different sort order. See Patient Match for the EMPI search which relates to this element. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.request | Σ C | |
| Short | Additional execution information (transaction/batch/history) | |
| Definition | Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry. | |
| Cardinality | 0..1 | |
| Type | BackboneElement | |
| Summary | True | |
| Conditions | The cardinality or value of this element may be affected by these constraints: bdl-3a, bdl-3b, bdl-5 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.request.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..0 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.request.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.request.modifierExtension | Σ ?! C | |
| Short | Extensions that cannot be ignored even if unrecognized | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Modifier | True | |
| Summary | True | |
| Alias | extensions, user content, modifiers | |
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.request.method | Σ C | |
| Short | GET | HEAD | POST | PUT | DELETE | PATCH | |
| Definition | In a transaction or batch, this is the HTTP action to be executed for this entry. In a history bundle, this indicates the HTTP action that occurred. | |
| Cardinality | 1..1 | |
| Type | code | |
| Binding | HTTP verbs (in the HTTP command line). See HTTP rfc for details. | |
| Summary | True | |
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |
| Conditions | The cardinality or value of this element may be affected by these constraints: bdl-3b, bdl-3c, bdl-14, bdl-15 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.request.url | Σ | |
| Short | URL for HTTP equivalent of this entry | |
| Definition | The URL for this entry, relative to the root (the address to which the request is posted). | |
| Cardinality | 1..1 | |
| Type | uri | |
| Summary | True | |
| Comments | E.g. for a Patient Create, the method would be "POST" and the URL would be "Patient". For a Patient Update, the method would be PUT and the URL would be "Patient/[id]". | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.request.ifNoneMatch | Σ | |
| Short | For managing cache validation | |
| Definition | If the ETag values match, return a 304 Not Modified status. See the API documentation for "Conditional Read". | |
| Cardinality | 0..1 | |
| Type | string | |
| Summary | True | |
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.request.ifModifiedSince | Σ | |
| Short | For managing cache currency | |
| Definition | Only perform the operation if the last updated date matches. See the API documentation for "Conditional Read". | |
| Cardinality | 0..1 | |
| Type | instant | |
| Summary | True | |
| Comments | Note: This is intended for where precisely observed times are required, typically system logs etc., and not human-reported times - for them, see date and dateTime (which can be as precise as instant, but is not required to be) below. UTC offset is always required | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.request.ifMatch | Σ | |
| Short | For managing update contention | |
| Definition | Only perform the operation if the Etag value matches. For more information, see the API section "Managing Resource Contention". | |
| Cardinality | 0..1 | |
| Type | string | |
| Summary | True | |
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.request.ifNoneExist | Σ | |
| Short | For conditional creates | |
| Definition | Instruct the server not to perform the create if a specified resource already exists. For further information, see the API documentation for "Conditional Create". This is just the query portion of the URL - what follows the "?" (not including the "?"). | |
| Cardinality | 0..1 | |
| Type | string | |
| Summary | True | |
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.response | Σ C | |
| Short | Results of execution (transaction/batch/history) | |
| Definition | Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history. | |
| Cardinality | 0..1 | |
| Type | BackboneElement | |
| Summary | True | |
| Conditions | The cardinality or value of this element may be affected by these constraints: bdl-3a, bdl-3b, bdl-3d, bdl-5 | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.response.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..1 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Bundle.entry.response.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | |
| Cardinality | 0..* | |
| Type | Extension | |
| Alias | extensions, user content | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.response.modifierExtension | Σ ?! C | |
| Short | Extensions that cannot be ignored even if unrecognized | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | |
| Cardinality | 0..* | |
| Type | Extension | |
| Modifier | True | |
| Summary | True | |
| Alias | extensions, user content, modifiers | |
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | |
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.response.status | Σ | |
| Short | Status response code (text optional) | |
| Definition | The status code returned by processing this entry. The status SHALL start with a 3 digit HTTP code (e.g. 404) and may contain the standard HTTP description associated with the status code. | |
| Cardinality | 1..1 | |
| Type | string | |
| Summary | True | |
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.response.location | Σ | |
| Short | The location (if the operation returns a location) | |
| Definition | The location header created by processing this operation, populated if the operation returns a location. | |
| Cardinality | 0..1 | |
| Type | uri | |
| Summary | True | |
| Comments | see http://en.wikipedia.org/wiki/Uniform_resource_identifier | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.response.etag | Σ | |
| Short | The Etag for the resource (if relevant) | |
| Definition | The Etag for the resource, if the operation for the entry produced a versioned resource (see Resource Metadata and Versioning and Managing Resource Contention). | |
| Cardinality | 0..1 | |
| Type | string | |
| Summary | True | |
| Comments | Etags match the Resource.meta.versionId. The ETag has to match the version id in the header if a resource is included. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.response.lastModified | Σ | |
| Short | Server's date time modified | |
| Definition | The date/time that the resource was modified on the server. | |
| Cardinality | 0..1 | |
| Type | instant | |
| Summary | True | |
| Comments | This has to match the same time in the meta header (meta.lastUpdated) if a resource is included. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.entry.response.outcome | Σ | |
| Short | OperationOutcome with hints and warnings (for batch/transaction) | |
| Definition | An OperationOutcome containing hints and warnings produced as part of processing this entry in a batch or transaction. | |
| Cardinality | 0..1 | |
| Type | Resource | |
| Summary | True | |
| Comments | For a POST/PUT operation, this is the equivalent outcome that would be returned for prefer = operationoutcome - except that the resource is always returned whether or not the outcome is returned. This outcome is not used for error responses in batch/transaction, only for hints and warnings. In a batch operation, the error will be in Bundle.entry.response, and for transaction, there will be a single OperationOutcome instead of a bundle in the case of an error. | |
| Mappings |
| |
| Bundle.signature | Σ | |
| Short | Digital Signature | |
| Definition | Digital Signature - base64 encoded. XML-DSig or a JWS. | |
| Cardinality | 0..0 | |
| Type | Signature | |
| Summary | True | |
| Requirements | A Signature holds an electronic representation of a signature and its supporting context in a FHIR accessible form. The signature may either be a cryptographic type (XML DigSig or a JWS), which is able to provide non-repudiation proof, or it may be a graphical image that represents a signature or a signature process. This element allows capturing signatures on documents, messages, transactions or even search responses, to support content-authentication, non-repudiation or other business cases. This is primarily relevant where the bundle may travel through multiple hops or via other mechanisms where HTTPS non-repudiation is insufficient. | |
| Comments | The signature could be created by the "author" of the bundle or by the originating device. Requirements around inclusion of a signature, verification of signatures and treatment of signed/non-signed bundles is implementation-environment specific. | |
| Constraints |
| |
| Mappings |
| |
| Bundle.issues | Σ C | |
| Short | Issues with the Bundle | |
| Definition | Captures issues and warnings that relate to the construction of the Bundle and the content within it. | |
| Cardinality | 0..0 | |
| Type | OperationOutcome | |
| Summary | True | |
| Comments | Usage notes: These issues and warnings must apply to the Bundle as a whole, not to individual entries.Messages relating to the processing of individual entries (e.g. in a batch or transaction) SHALL be reported in the entry.response.outcome for that entry. If there are errors that arise in the creation of the Bundle, then that should be handled by an OperationOutcome being returned instead of the Bundle. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: bdl-16, bdl-17 | |
| Constraints |
| |
| Mappings |
| |
Business Information Model
Key Design Considerations
There are various identifiers used in the MedicationRequest resource.
- sequenceNo: A number/text that identifies the sequence of this medication item within this medication list. It is modelled using
identifierwith thesystemashttps://fhir.synapxe.sg/NamingSystem/sequence-no. - groupNo: the identifier of the group that this medication item belongs to within this medication list. It is modelled using
identifierwith thesystemashttps://fhir.synapxe.sg/NamingSystem/group-no. - groupSequenceNo: A number/text that identifies the sequence of this medication item within the group derived based on the groupNo. It is modelled using
dosingInstruction.sequence. - orderSetConnectingTerm: The term used to connect this medication item and another medication item within the same order set (i.e. derived using sequenceNo, groupNo, groupSequenceNo) for variable/step doses. It is modelled using
extension:orderSetConnectingTerm.
An example is shown below for a patient's medication order containing two medication items (Prednisolone and Paracetamol) and their administration doses.
Step Dose
- Prednisolone 10 mg for 3 days
- Prednisolone 5 mg for 5 days
- Prednisolone 2 mg for 8 days
Variable Dose
- Paracetamol 1000 mg – Morning
- Paracetamol 500 mg – Afternoon
- Paracetamol 100 mg – Night
Medication Request Details
For step doses (Prednisolone), medications share the same group number (SDSGH103599) and use the "THEN" connecting term, indicating sequential administration where each dose follows the previous one. The group sequence numbers (1, 2, 3) define the order of progression within the group number. In contrast, variable doses (Paracetamol), share the group number (SDSGH103588) and use the "AND" connecting term, indicating concurrent administration at different times of day. The sequence numbers (1.1, 1.2, etc.) provide overall ordering across all medication requests.
| Medication Request | Sequence No. | Group No. | Group Sequence No. | Order Set Connecting Term |
|---|---|---|---|---|
| Prednisolone 10 mg – 3 days | 1.1 | SDSGH103599 | 1 | THEN |
| Prednisolone 5 mg – 5 days | 1.2 | SDSGH103599 | 2 | THEN |
| Prednisolone 2 mg – 8 days | 1.3 | SDSGH103599 | 3 | |
| Paracetamol 1000 mg – Morning | 1.4 | SDSGH103588 | 1 | AND |
| Paracetamol 500 mg – Afternoon | 1.5 | SDSGH103588 | 2 | AND |
| Paracetamol 100 mg – Night | 1.6 | SDSGH103588 | 3 |
API Specification
See MedicationRequest.$submit and MedicationRequest.$retrieve for the API specification to submit and retrieve ordered medications.
Terminology Bindings
| title | Path | Binding Strength | Value Set (Code System) | Description |
|---|---|---|---|---|
| Medication Request Bundle Profile | Bundle.language | required | http://hl7.org/fhir/ValueSet/all-languages|5.0.0 | IETF language tag for a human language |
| Medication Request Bundle Profile | Bundle.type | required | http://hl7.org/fhir/ValueSet/bundle-type|5.0.0 | Indicates the purpose of a bundle - how it is intended to be used. |
| Medication Request Bundle Profile | Bundle.link.relation | required | http://hl7.org/fhir/ValueSet/iana-link-relations|5.0.0 | |
| Medication Request Bundle Profile | Bundle.entry.resource.language | required | http://hl7.org/fhir/ValueSet/all-languages|5.0.0 | IETF language tag for a human language |
| Medication Request Bundle Profile | Bundle.entry.resource.basedOn.type | extensible | http://hl7.org/fhir/ValueSet/resource-types | Aa resource (or, for logical models, the URI of the logical model). |
| Medication Request Bundle Profile | Bundle.entry.resource.status | required | https://fhir.synapxe.sg/ValueSet/medicationrequest-status | A coded concept specifying the state of the prescribing event. Describes the lifecycle of the prescription. |
| Medication Request Bundle Profile | Bundle.entry.resource.statusReason | required | https://fhir.synapxe.sg/ValueSet/status-reason | Identifies the reasons for a given status. |
| Medication Request Bundle Profile | Bundle.entry.resource.intent | required | http://hl7.org/fhir/ValueSet/medicationrequest-intent|5.0.0 | The kind of medication order. |
| Medication Request Bundle Profile | Bundle.entry.resource.category | required | https://fhir.synapxe.sg/ValueSet/order-type | A coded concept identifying where the medication is to be consumed or administered. |
| Medication Request Bundle Profile | Bundle.entry.resource.medication | example | http://hl7.org/fhir/ValueSet/medication-codes | A coded concept identifying substance or product that can be ordered. |
| Medication Request Bundle Profile | Bundle.entry.resource.subject.type | extensible | http://hl7.org/fhir/ValueSet/resource-types | Aa resource (or, for logical models, the URI of the logical model). |
| Medication Request Bundle Profile | Bundle.entry.resource.requester.type | extensible | http://hl7.org/fhir/ValueSet/resource-types | Aa resource (or, for logical models, the URI of the logical model). |
| Medication Request Bundle Profile | Bundle.entry.resource.requester.identifier.use | required | http://hl7.org/fhir/ValueSet/identifier-use|5.0.0 | Identifies the purpose for this identifier, if known . |
| Medication Request Bundle Profile | Bundle.entry.resource.requester.identifier.type | extensible | http://hl7.org/fhir/ValueSet/identifier-type | A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. |
| Medication Request Bundle Profile | Bundle.entry.resource.recorder.type | extensible | http://hl7.org/fhir/ValueSet/resource-types | Aa resource (or, for logical models, the URI of the logical model). |
| Medication Request Bundle Profile | Bundle.entry.resource.reason | example | http://hl7.org/fhir/ValueSet/condition-code | A coded concept indicating why the medication was ordered. |
| Medication Request Bundle Profile | Bundle.entry.resource.reason.concept | required | https://fhir.synapxe.sg/ValueSet/reason-for-medication | |
| Medication Request Bundle Profile | Bundle.entry.resource.dosageInstruction.additionalInstruction | example | http://hl7.org/fhir/ValueSet/additional-instruction-codes | A coded concept identifying additional instructions such as "take with water" or "avoid operating heavy machinery". |
| Medication Request Bundle Profile | Bundle.entry.resource.dosageInstruction.timing.repeat.durationUnit | required | http://hl7.org/fhir/ValueSet/units-of-time|5.0.0 | A unit of time (units from UCUM). |
| Medication Request Bundle Profile | Bundle.entry.resource.dosageInstruction.timing.repeat.periodUnit | required | http://hl7.org/fhir/ValueSet/units-of-time|5.0.0 | A unit of time (units from UCUM). |
| Medication Request Bundle Profile | Bundle.entry.resource.dosageInstruction.timing.repeat.dayOfWeek | required | http://hl7.org/fhir/ValueSet/days-of-week|5.0.0 | |
| Medication Request Bundle Profile | Bundle.entry.resource.dosageInstruction.timing.repeat.when | required | http://hl7.org/fhir/ValueSet/event-timing|5.0.0 | Real-world event relating to the schedule. |
| Medication Request Bundle Profile | Bundle.entry.resource.dosageInstruction.timing.code | preferred | https://fhir.synapxe.sg/ValueSet/medication-frequency | Code for a known / defined timing pattern. |
| Medication Request Bundle Profile | Bundle.entry.resource.dosageInstruction.asNeededFor | example | http://hl7.org/fhir/ValueSet/medication-as-needed-reason | 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. |
| Medication Request Bundle Profile | Bundle.entry.resource.dosageInstruction.route | required | https://fhir.synapxe.sg/ValueSet/medication-route | A coded concept describing the route or physiological path of administration of a therapeutic agent into or onto the body of a subject. |
| Medication Request Bundle Profile | Bundle.entry.resource.dispenseRequest.dispenser.type | extensible | http://hl7.org/fhir/ValueSet/resource-types | Aa resource (or, for logical models, the URI of the logical model). |
| Medication Request Bundle Profile | Bundle.entry.resource.substitution.allowed[x] | preferred | http://terminology.hl7.org/ValueSet/v3-ActSubstanceAdminSubstitutionCode | Identifies the type of substitution allowed. |
| Medication Request Bundle Profile | Bundle.entry.resource.substitution.reason | example | http://terminology.hl7.org/ValueSet/v3-SubstanceAdminSubstitutionReason | SubstanceAdminSubstitutionReason |
| Medication Request Bundle Profile | Bundle.entry.search.mode | required | http://hl7.org/fhir/ValueSet/search-entry-mode|5.0.0 | Why an entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process. |
| Medication Request Bundle Profile | Bundle.entry.request.method | required | http://hl7.org/fhir/ValueSet/http-verb|5.0.0 | HTTP verbs (in the HTTP command line). See HTTP rfc for details. |
Constraints
XML to FHIR Mapping
| XML element | FHIR mapping |
|---|---|
controlHeader/srcInstitution |
Bundle(type=transaction).meta.tag.code |
controlHeader/licenseeNumber |
|
controlHeader/srcApplication |
Bundle(type=transaction).meta.source |
controlHeader/msgID |
Bundle(type=transaction).meta.extension:artifact.extension:msgId.valueIdentifier(system=https://fhir.synapxe.sg/NamingSystem/msg-id).value |
controlHeader/msgSequenceID |
Bundle(type=transaction).meta.extension:artifact.extension:msgSequenceId.valueIdentifier(system=https://fhir.synapxe.sg/NamingSystem/msg-sequence-id).value |
controlHeader/msgDateTime |
Bundle(type=transaction).meta.extension:artifact.extension:date.valueDateTime |
medicationOrder/recordIdentifier |
Bundle(type=transaction).entry.resource → MedicationRequest.identifier(system=https://fhir.synapxe.sg/NamingSystem/record-id).value |
medicationOrder/eventID |
Bundle(type=transaction).entry.resource → MedicationRequest.encounter.identifier(system=https://fhir.synapxe.sg/NamingSystem/event-id).value |
medicationOrder/orderID |
Bundle(type=transaction).entry.resource → MedicationRequest.identifier(system=https://fhir.synapxe.sg/NamingSystem/order-id).value |
medicationOrder/sourceGroupingID |
Bundle(type=transaction).entry.resource → MedicationRequest.identifier(system=https://fhir.synapxe.sg/NamingSystem/source-grouping-id).value |
medicationOrder/orderingInstitution |
Bundle(type=transaction).entry.resource → MedicationRequest.extensions:orderingInstitution.identifier.value |
medicationOrder/orderingLocation/code |
Bundle(type=transaction).entry.resource → MedicationRequest.extensions:orderingLocation.valueCodeableConcept.coding.code |
medicationOrder/orderingLocation/codingSchemeName |
Bundle(type=transaction).entry.resource → MedicationRequest.extensions:orderingLocation.valueCodeableConcept.coding.system |
medicationOrder/orderingLocation/codingSchemeVersion |
Bundle(type=transaction).entry.resource → MedicationRequest.extensions:orderingLocation.valueCodeableConcept.coding.version |
medicationOrder/orderingLocation/textDescription |
Bundle(type=transaction).entry.resource → MedicationRequest.extensions:orderingLocation.valueCodeableConcept.text |
medicationOrder/orderType/code |
Bundle(type=transaction).entry.resource → MedicationRequest.category.coding.code |
medicationOrder/orderType/codingSchemeName |
Bundle(type=transaction).entry.resource → MedicationRequest.category.coding.system |
medicationOrder/orderType/codingSchemeVersion |
Bundle(type=transaction).entry.resource → MedicationRequest.category.coding.version |
medicationOrder/orderType/textDescription |
Bundle(type=transaction).entry.resource → MedicationRequest.category.coding.display |
medicationOrder/orderDateTime |
Bundle(type=transaction).entry.resource → MedicationRequest.authoredOn |
medicationOrder/reasonForCancellation/code |
Bundle(type=transaction).entry.resource → MedicationRequest.statusReason.coding.code |
medicationOrder/reasonForCancellation/codingSchemeName |
Bundle(type=transaction).entry.resource → MedicationRequest.statusReason.coding.system |
medicationOrder/reasonForCancellation/codingSchemeVersion |
Bundle(type=transaction).entry.resource → MedicationRequest.statusReason.coding.version |
medicationOrder/reasonForCancellation/textDescription |
Bundle(type=transaction).entry.resource → MedicationRequest.statusReason.coding.display |
medicationOrder/orderStatus/code |
Bundle(type=transaction).entry.resource → MedicationRequest.status.coding.code |
medicationOrder/orderStatus/codingSchemeName |
Bundle(type=transaction).entry.resource → MedicationRequest.status.coding.system |
medicationOrder/orderStatus/codingSchemeVersion |
Bundle(type=transaction).entry.resource → MedicationRequest.status.coding.version |
medicationOrder/orderStatus/textDescription |
Bundle(type=transaction).entry.resource → MedicationRequest.status.coding.display |
medicationOrder/orderedBy/id |
Bundle(type=transaction).entry.resource → MedicationRequest.requester.identifier.value |
medicationOrder/orderedBy/name |
Bundle(type=transaction).entry.resource → MedicationRequest.requester.display |
medicationOrder/authorizedBy/id |
Bundle(type=transaction).entry.resource → MedicationRequest.extensions:authorizer.identifier.value |
medicationOrder/authorizedBy/name |
Bundle(type=transaction).entry.resource → MedicationRequest.extensions:authorizer.display |
medicationOrder/medicationItem/itemId |
Bundle(type=transaction).entry.resource → MedicationRequest.medication → Medication.identifier(system=https://fhir.synapxe.sg/NamingSystem/item-id).value |
medicationOrder/medicationItem/sequenceNo |
Bundle(type=transaction).entry.resource → MedicationRequest.identifier(system=https://fhir.synapxe.sg/NamingSystem/sequence-no).value |
medicationOrder/medicationItem/groupNo |
Bundle(type=transaction).entry.resource → MedicationRequest.groupIdentifier(system=https://fhir.synapxe.sg/NamingSystem/group-no).value |
medicationOrder/medicationItem/groupSequenceNo |
Bundle(type=transaction).entry.resource → MedicationRequest.dosageInstruction.sequence |
medicationOrder/medicationItem/orderSetConnectingTerm |
Bundle(type=transaction).entry.resource → MedicationRequest.extension:orderSetConnectingTerm |
medicationOrder/medicationItem/frequencyQualifier |
Bundle(type=transaction).entry.resource → MedicationRequest.dosageInstruction.asNeededFor.text |
medicationOrder/medicationItem/dosageInstruction |
Bundle(type=transaction).entry.resource → MedicationRequest.dosageInstruction.text |
medicationOrder/medicationItem/doseQuantity/lowValue |
Bundle(type=transaction).entry.resource → MedicationRequest.dosageInstruction.doseAndRate.doseQuantity.lowValue |
medicationOrder/medicationItem/doseQuantity/lowUnit |
Bundle(type=transaction).entry.resource → MedicationRequest.dosageInstruction.doseAndRate.doseQuantity.lowUnit |
medicationOrder/medicationItem/doseQuantity/highValue |
Bundle(type=transaction).entry.resource → MedicationRequest.dosageInstruction.doseAndRate.doseQuantity.highValue |
medicationOrder/medicationItem/doseQuantity/highUnit |
Bundle(type=transaction).entry.resource → MedicationRequest.dosageInstruction.doseAndRate.doseQuantity.highUnit |
medicationOrder/medicationItem/medicationItemOrderedDate |
Bundle(type=transaction).entry.resource → MedicationRequest.authoredOn |
medicationOrder/medicationItem/medicationStartDateTime |
Bundle(type=transaction).entry.resource → MedicationRequest.effectiveDosePeriod.start |
medicationOrder/medicationItem/medicationEndDateTime |
Bundle(type=transaction).entry.resource → MedicationRequest.effectiveDosePeriod.end |
medicationOrder/medicationItem/medicationDiscontinuedDateTime |
Bundle(type=transaction).entry.resource → MedicationRequest.statusChanged |
medicationOrder/medicationItem/medicationItemStatus/code |
Bundle(type=transaction).entry.resource → MedicationRequest.medication → Medication.status.coding.code |
medicationOrder/medicationItem/medicationItemStatus/codingSchemeName |
Bundle(type=transaction).entry.resource → MedicationRequest.medication → Medication.status.coding.system |
medicationOrder/medicationItem/medicationItemStatus/codingSchemeVersion |
Bundle(type=transaction).entry.resource → MedicationRequest.medication → Medication.status.coding.version |
medicationOrder/medicationItem/medicationItemStatus/textDescription |
Bundle(type=transaction).entry.resource → MedicationRequest.medication → Medication.status.coding.display |
medicationOrder/medicationItem/reasonForMedication/code |
Bundle(type=transaction).entry.resource → MedicationRequest.reason.concept.coding.code |
medicationOrder/medicationItem/reasonForMedication/codingSchemeName |
Bundle(type=transaction).entry.resource → MedicationRequest.reason.concept.coding.system |
medicationOrder/medicationItem/reasonForMedication/codingSchemeVersion |
Bundle(type=transaction).entry.resource → MedicationRequest.reason.concept.coding.version |
medicationOrder/medicationItem/reasonForMedication/textDescription |
Bundle(type=transaction).entry.resource → MedicationRequest.reason.concept.coding.display |
medicationOrder/medicationItem/changesMade/code |
Bundle(type=transaction).entry.resource → MedicationRequest.extension:changesMade.code |
medicationOrder/medicationItem/changesMade/codingSchemeName |
Bundle(type=transaction).entry.resource → MedicationRequest.extension:changesMade.system |
medicationOrder/medicationItem/changesMade/codingSchemeVersion |
Bundle(type=transaction).entry.resource → MedicationRequest.extension:changesMade.version |
medicationOrder/medicationItem/changesMade/textDescription |
Bundle(type=transaction).entry.resource → MedicationRequest.extension:changesMade.display |
medicationOrder/medicationItem/reasonForChanges/code |
Bundle(type=transaction).entry.resource → MedicationRequest.statusReason.coding.code |
medicationOrder/medicationItem/reasonForChanges/codingSchemeName |
Bundle(type=transaction).entry.resource → MedicationRequest.statusReason.coding.system |
medicationOrder/medicationItem/reasonForChanges/codingSchemeVersion |
Bundle(type=transaction).entry.resource → MedicationRequest.statusReason.coding.version |
medicationOrder/medicationItem/reasonForChanges/textDescription |
Bundle(type=transaction).entry.resource → MedicationRequest.statusReason.coding.display |
medicationOrder/medicationItem/quantityOrdered |
Bundle(type=transaction).entry.resource → MedicationRequest.dispenseRequest.quantity.value |
medicationOrder/medicationItem/quantityOrderedUnits |
Bundle(type=transaction).entry.resource → MedicationRequest.dispenseRequest.quantity.unit |
medicationOrder/medicationItem/duration/code |
Bundle(type=transaction).entry.resource → MedicationRequest.dosageInstruction.timing.repeat.period |
medicationOrder/medicationItem/durationUnits |
Bundle(type=transaction).entry.resource → MedicationRequest.dosageInstruction.timing.repeat.periodUnit |
medicationOrder/medicationItem/medicationName/code |
Bundle(type=transaction).entry.resource → MedicationRequest.medication → Medication.code.coding.code |
medicationOrder/medicationItem/medicationName/codingSchemeName |
Bundle(type=transaction).entry.resource → MedicationRequest.medication → Medication.code.coding.system |
medicationOrder/medicationItem/medicationName/codingSchemeVersion |
Bundle(type=transaction).entry.resource → MedicationRequest.medication → Medication.code.coding.version |
medicationOrder/medicationItem/medicationName/textDescription |
Bundle(type=transaction).entry.resource → MedicationRequest.medication → Medication.code.coding.display |
medicationOrder/medicationItem/frequency/code |
Bundle(type=transaction).entry.resource → MedicationRequest.dosageInstruction.timing.code.coding.code |
medicationOrder/medicationItem/frequency/codingSchemeName |
Bundle(type=transaction).entry.resource → MedicationRequest.dosageInstruction.timing.code.coding.system |
medicationOrder/medicationItem/frequency/codingSchemeVersion |
Bundle(type=transaction).entry.resource → MedicationRequest.dosageInstruction.timing.code.coding.version |
medicationOrder/medicationItem/frequency/textDescription |
Bundle(type=transaction).entry.resource → MedicationRequest.dosageInstruction.timing.code.text |
medicationOrder/medicationItem/routeOfAdministration/code |
Bundle(type=transaction).entry.resource → MedicationRequest.dosageInstruction.route.coding.code |
medicationOrder/medicationItem/routeOfAdministration/codingSchemeName |
Bundle(type=transaction).entry.resource → MedicationRequest.dosageInstruction.route.coding.system |
medicationOrder/medicationItem/routeOfAdministration/codingSchemeVersion |
Bundle(type=transaction).entry.resource → MedicationRequest.dosageInstruction.route.coding.version |
medicationOrder/medicationItem/routeOfAdministration/textDescription |
Bundle(type=transaction).entry.resource → MedicationRequest.dosageInstruction.route.coding.display |
medicationOrder/medicationItem/medicationStrength |
Bundle(type=transaction).entry.resource → MedicationRequest.medication → Medication.ingredient.strengthQuantity.value |
medicationOrder/medicationItem/medicationStrengthUnit |
Bundle(type=transaction).entry.resource → MedicationRequest.medication → Medication.ingredient.strengthQuantity.unit |
medicationOrder/medicationItem/additionalDosageInstruction |
Bundle(type=transaction).entry.resource → MedicationRequest.dosageInstruction.additionalInstruction.text |
medicationOrder/medicationItem/doseForm/code |
Bundle(type=transaction).entry.resource → MedicationRequest.medication → Medication.doseForm.coding.code |
medicationOrder/medicationItem/doseForm/codingSchemeName |
Bundle(type=transaction).entry.resource → MedicationRequest.medication → Medication.doseForm.coding.system |
medicationOrder/medicationItem/doseForm/codingSchemeVersion |
Bundle(type=transaction).entry.resource → MedicationRequest.medication → Medication.doseForm.coding.version |
medicationOrder/medicationItem/doseForm/textDescription |
Bundle(type=transaction).entry.resource → MedicationRequest.medication → Medication.doseForm.coding.display |