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

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

Lookup for Profile_R5_DeviceAssociation_R4_Device

Lookup for FHIR R5 DeviceAssociation for use in FHIR R4

The FHIR R5 resource is represented in FHIR R4 via the Device resource.

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

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

Source Element (FHIR R5) Target(s) Comments
DeviceAssociation    
DeviceAssociation.meta Device.meta Element DeviceAssociation.meta is mapped to FHIR R4 element Device.meta as Equivalent.
DeviceAssociation.implicitRules Device.implicitRules Element DeviceAssociation.implicitRules is mapped to FHIR R4 element Device.implicitRules as Equivalent.
DeviceAssociation.language Device.language Element DeviceAssociation.language is mapped to FHIR R4 element Device.language as Equivalent.
DeviceAssociation.text Device.text Element DeviceAssociation.text is mapped to FHIR R4 element Device.text as Equivalent.
DeviceAssociation.contained Device.contained Element DeviceAssociation.contained is mapped to FHIR R4 element Device.contained as Equivalent.
DeviceAssociation.identifier Device.identifier Element DeviceAssociation.identifier is mapped to FHIR R4 element Device.identifier as Equivalent.
DeviceAssociation.device Extension: ExtensionDeviceAssociation_Device Element DeviceAssociation.device has a context of Device based on following the parent source element upwards and mapping to Device.
Element DeviceAssociation.device has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
DeviceAssociation.category Extension: ExtensionDeviceAssociation_Category Element DeviceAssociation.category has a context of Device based on following the parent source element upwards and mapping to Device.
Element DeviceAssociation.category has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
DeviceAssociation.status Extension: ExtensionDeviceAssociation_Status Element DeviceAssociation.status has a context of Device based on following the parent source element upwards and mapping to Device.
Element DeviceAssociation.status has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
DeviceAssociation.statusReason Device.statusReason
Extension: ExtensionDeviceAssociation_StatusReason		 Element DeviceAssociation.statusReason is mapped to FHIR R4 element Device.statusReason as Equivalent.
DeviceAssociation.subject Device.patient
Standard Extension: alternate-reference		 Element DeviceAssociation.subject is mapped to FHIR R4 element Device.patient as SourceIsBroaderThanTarget.
The standard extension alternate-reference has been mapped as the representation of FHIR R5 element DeviceAssociation.subject with unmapped reference targets: Device, Group, Practitioner, RelatedPerson.
DeviceAssociation.bodyStructure Extension: ExtensionDeviceAssociation_BodyStructure Element DeviceAssociation.bodyStructure has a context of Device based on following the parent source element upwards and mapping to Device.
Element DeviceAssociation.bodyStructure has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
DeviceAssociation.period Extension: ExtensionDeviceAssociation_Period Element DeviceAssociation.period has a context of Device based on following the parent source element upwards and mapping to Device.
Element DeviceAssociation.period has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
DeviceAssociation.operation Extension: ExtensionDeviceAssociation_Operation Element DeviceAssociation.operation has a context of Device based on following the parent source element upwards and mapping to Device.
Element DeviceAssociation.operation has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
DeviceAssociation.operation.status Extension: ExtensionDeviceAssociation_Operation Slice:status Element DeviceAssociation.operation.status is part of an existing definition because parent element DeviceAssociation.operation requires a cross-version extension.
Element DeviceAssociation.operation.status has a context of Device based on following the parent source element upwards and mapping to Device.
Element DeviceAssociation.operation.status has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
DeviceAssociation.operation.operator Extension: ExtensionDeviceAssociation_Operation Slice:operator Element DeviceAssociation.operation.operator is part of an existing definition because parent element DeviceAssociation.operation requires a cross-version extension.
Element DeviceAssociation.operation.operator has a context of Device based on following the parent source element upwards and mapping to Device.
Element DeviceAssociation.operation.operator has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
DeviceAssociation.operation.period Extension: ExtensionDeviceAssociation_Operation Slice:period Element DeviceAssociation.operation.period is part of an existing definition because parent element DeviceAssociation.operation requires a cross-version extension.
Element DeviceAssociation.operation.period has a context of Device based on following the parent source element upwards and mapping to Device.
Element DeviceAssociation.operation.period has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).