Extensions for Using Data Elements from FHIR R5 in FHIR STU3
0.1.0 - STU International flag

Extensions for Using Data Elements from FHIR R5 in FHIR STU3 - Downloaded Version null See the Directory of published versions

Lookup for Profile_R5_DeviceDispense_R3

Lookup for FHIR R5 DeviceDispense for use in FHIR STU3

The FHIR R5 resource is represented in FHIR STU3 via the Basic resource.

Note that there is a profile defined to simplify use of this cross-version resource representation:Profile: DeviceDispense

A computable version of the following element information is available in: R5DeviceDispenseElementMapToR3

Source Element (FHIR R5) Target(s) Comments
DeviceDispense    
DeviceDispense.meta Basic.meta Element matches Basic element path Basic.meta (Resource.meta), use that element instead.
Element DeviceDispense.meta is not mapped to FHIR STU3, since FHIR R5 DeviceDispense is not mapped.
Element DeviceDispense.meta has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDispense.implicitRules Basic.implicitRules Element matches Basic element path Basic.implicitRules (Resource.implicitRules), use that element instead.
Element DeviceDispense.implicitRules is not mapped to FHIR STU3, since FHIR R5 DeviceDispense is not mapped.
Element DeviceDispense.implicitRules has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDispense.language Basic.language Element matches Basic element path Basic.language (Resource.language), use that element instead.
Element DeviceDispense.language is not mapped to FHIR STU3, since FHIR R5 DeviceDispense is not mapped.
Element DeviceDispense.language has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDispense.text Basic.text Element matches Basic element path Basic.text (DomainResource.text), use that element instead.
Element DeviceDispense.text is not mapped to FHIR STU3, since FHIR R5 DeviceDispense is not mapped.
Element DeviceDispense.text has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDispense.contained Basic.contained Element matches Basic element path Basic.contained (DomainResource.contained), use that element instead.
Element DeviceDispense.contained is not mapped to FHIR STU3, since FHIR R5 DeviceDispense is not mapped.
Element DeviceDispense.contained has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDispense.identifier Basic.identifier Element matches Basic element path Basic.identifier (Basic.identifier), use that element instead.
Element DeviceDispense.identifier is not mapped to FHIR STU3, since FHIR R5 DeviceDispense is not mapped.
Element DeviceDispense.identifier has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDispense.basedOn Extension: ExtensionDeviceDispense_BasedOn Element DeviceDispense.basedOn is not mapped to FHIR STU3, since FHIR R5 DeviceDispense is not mapped.
Element DeviceDispense.basedOn has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDispense.partOf Extension: ExtensionDeviceDispense_PartOf Element DeviceDispense.partOf is not mapped to FHIR STU3, since FHIR R5 DeviceDispense is not mapped.
Element DeviceDispense.partOf has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDispense.status Modifier Extension: ExtensionDeviceDispense_Status Element DeviceDispense.status is not mapped to FHIR STU3, since FHIR R5 DeviceDispense is not mapped.
Element DeviceDispense.status has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDispense.statusReason Extension: ExtensionDeviceDispense_StatusReason Element DeviceDispense.statusReason is not mapped to FHIR STU3, since FHIR R5 DeviceDispense is not mapped.
Element DeviceDispense.statusReason has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDispense.category Extension: ExtensionDeviceDispense_Category Element DeviceDispense.category is not mapped to FHIR STU3, since FHIR R5 DeviceDispense is not mapped.
Element DeviceDispense.category has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDispense.device Extension: ExtensionDeviceDispense_Device Element DeviceDispense.device is not mapped to FHIR STU3, since FHIR R5 DeviceDispense is not mapped.
Element DeviceDispense.device has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDispense.subject Basic.subject Element matches Basic element path Basic.subject (Basic.subject), use that element instead.
Element DeviceDispense.subject is not mapped to FHIR STU3, since FHIR R5 DeviceDispense is not mapped.
Element DeviceDispense.subject has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDispense.receiver Extension: ExtensionDeviceDispense_Receiver Element DeviceDispense.receiver is not mapped to FHIR STU3, since FHIR R5 DeviceDispense is not mapped.
Element DeviceDispense.receiver has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDispense.encounter Extension: ExtensionDeviceDispense_Encounter Element DeviceDispense.encounter is not mapped to FHIR STU3, since FHIR R5 DeviceDispense is not mapped.
Element DeviceDispense.encounter has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDispense.supportingInformation Extension: ExtensionDeviceDispense_SupportingInformation Element DeviceDispense.supportingInformation is not mapped to FHIR STU3, since FHIR R5 DeviceDispense is not mapped.
Element DeviceDispense.supportingInformation has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDispense.performer Extension: ExtensionDeviceDispense_Performer Element DeviceDispense.performer is not mapped to FHIR STU3, since FHIR R5 DeviceDispense is not mapped.
Element DeviceDispense.performer has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDispense.performer.function Extension: ExtensionDeviceDispense_Performer Slice:function Element DeviceDispense.performer.function is part of an existing definition because parent element DeviceDispense.performer requires a cross-version extension.
Element DeviceDispense.performer.function is not mapped to FHIR STU3, since FHIR R5 DeviceDispense is not mapped.
Element DeviceDispense.performer.function has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDispense.performer.actor Extension: ExtensionDeviceDispense_Performer Slice:actor Element DeviceDispense.performer.actor is part of an existing definition because parent element DeviceDispense.performer requires a cross-version extension.
Element DeviceDispense.performer.actor is not mapped to FHIR STU3, since FHIR R5 DeviceDispense is not mapped.
Element DeviceDispense.performer.actor has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDispense.location Extension: ExtensionDeviceDispense_Location Element DeviceDispense.location is not mapped to FHIR STU3, since FHIR R5 DeviceDispense is not mapped.
Element DeviceDispense.location has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDispense.type Extension: ExtensionDeviceDispense_Type Element DeviceDispense.type is not mapped to FHIR STU3, since FHIR R5 DeviceDispense is not mapped.
Element DeviceDispense.type has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDispense.quantity Extension: ExtensionDeviceDispense_Quantity Element DeviceDispense.quantity is not mapped to FHIR STU3, since FHIR R5 DeviceDispense is not mapped.
Element DeviceDispense.quantity has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDispense.preparedDate Extension: ExtensionDeviceDispense_PreparedDate Element DeviceDispense.preparedDate is not mapped to FHIR STU3, since FHIR R5 DeviceDispense is not mapped.
Element DeviceDispense.preparedDate has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDispense.whenHandedOver Extension: ExtensionDeviceDispense_WhenHandedOver Element DeviceDispense.whenHandedOver is not mapped to FHIR STU3, since FHIR R5 DeviceDispense is not mapped.
Element DeviceDispense.whenHandedOver has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDispense.destination Extension: ExtensionDeviceDispense_Destination Element DeviceDispense.destination is not mapped to FHIR STU3, since FHIR R5 DeviceDispense is not mapped.
Element DeviceDispense.destination has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDispense.note Extension: ExtensionDeviceDispense_Note Element DeviceDispense.note is not mapped to FHIR STU3, since FHIR R5 DeviceDispense is not mapped.
Element DeviceDispense.note has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDispense.usageInstruction Extension: ExtensionDeviceDispense_UsageInstruction Element DeviceDispense.usageInstruction is not mapped to FHIR STU3, since FHIR R5 DeviceDispense is not mapped.
Element DeviceDispense.usageInstruction has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDispense.eventHistory Extension: ExtensionDeviceDispense_EventHistory Element DeviceDispense.eventHistory is not mapped to FHIR STU3, since FHIR R5 DeviceDispense is not mapped.
Element DeviceDispense.eventHistory has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).