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_Device_R4

Lookup for FHIR R5 Device 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: Device

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

Source Element (FHIR R5) Target(s) Comments
Device    
Device.meta Device.meta Element Device.meta is mapped to FHIR R4 element Device.meta as Equivalent.
Device.implicitRules Device.implicitRules Element Device.implicitRules is mapped to FHIR R4 element Device.implicitRules as Equivalent.
Device.language Device.language Element Device.language is mapped to FHIR R4 element Device.language as Equivalent.
Device.text Device.text Element Device.text is mapped to FHIR R4 element Device.text as Equivalent.
Device.contained Device.contained Element Device.contained is mapped to FHIR R4 element Device.contained as Equivalent.
Device.identifier Device.identifier Element Device.identifier is mapped to FHIR R4 element Device.identifier as Equivalent.
Device.displayName Device.deviceName
Extension: ExtensionDevice_DisplayName		 Element Device.displayName is mapped to FHIR R4 element Device.deviceName as RelatedTo.
The mappings for Device.displayName do not cover the following types: string.
The mappings for Device.displayName do not cover the following types based on type expansion: value.
Device.definition Device.definition
Extension: ExtensionDevice_Definition		 Element Device.definition is mapped to FHIR R4 element Device.definition as SourceIsBroaderThanTarget.
The mappings for Device.definition do not cover the following types: CodeableReference.
The mappings for Device.definition do not cover the following types based on type expansion: concept.
Device.udiCarrier Device.udiCarrier Element Device.udiCarrier is mapped to FHIR R4 element Device.udiCarrier as Equivalent.
Device.udiCarrier.deviceIdentifier Device.udiCarrier.deviceIdentifier Element Device.udiCarrier.deviceIdentifier is mapped to FHIR R4 element Device.udiCarrier.deviceIdentifier as Equivalent.
Device.udiCarrier.issuer Device.udiCarrier.issuer Element Device.udiCarrier.issuer is mapped to FHIR R4 element Device.udiCarrier.issuer as Equivalent.
Device.udiCarrier.jurisdiction Device.udiCarrier.jurisdiction Element Device.udiCarrier.jurisdiction is mapped to FHIR R4 element Device.udiCarrier.jurisdiction as Equivalent.
Device.udiCarrier.carrierAIDC Device.udiCarrier.carrierAIDC Element Device.udiCarrier.carrierAIDC is mapped to FHIR R4 element Device.udiCarrier.carrierAIDC as Equivalent.
Device.udiCarrier.carrierHRF Device.udiCarrier.carrierHRF Element Device.udiCarrier.carrierHRF is mapped to FHIR R4 element Device.udiCarrier.carrierHRF as Equivalent.
Device.udiCarrier.entryType Device.udiCarrier.entryType
Extension: ExtensionDevice_UdiCarrier_EntryType		 Element Device.udiCarrier.entryType is mapped to FHIR R4 element Device.udiCarrier.entryType as RelatedTo.
The mappings for Device.udiCarrier.entryType do not allow expression of the necessary codes, per the bindings on the source and target.
Device.status Device.status Element Device.status is mapped to FHIR R4 element Device.status as SourceIsNarrowerThanTarget.
The mappings for Device.status do not allow expression of the necessary codes, per the bindings on the source and target.
Device.availabilityStatus Extension: ExtensionDevice_AvailabilityStatus Element Device.availabilityStatus has a context of Device based on following the parent source element upwards and mapping to Device.
Element Device.availabilityStatus has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Device.biologicalSourceEvent Extension: ExtensionDevice_BiologicalSourceEvent Element Device.biologicalSourceEvent has a context of Device based on following the parent source element upwards and mapping to Device.
Element Device.biologicalSourceEvent has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Device.manufacturer Device.manufacturer Element Device.manufacturer is mapped to FHIR R4 element Device.manufacturer as Equivalent.
Device.manufactureDate Device.manufactureDate Element Device.manufactureDate is mapped to FHIR R4 element Device.manufactureDate as Equivalent.
Device.expirationDate Device.expirationDate Element Device.expirationDate is mapped to FHIR R4 element Device.expirationDate as Equivalent.
Device.lotNumber Device.lotNumber Element Device.lotNumber is mapped to FHIR R4 element Device.lotNumber as Equivalent.
Device.serialNumber Device.serialNumber Element Device.serialNumber is mapped to FHIR R4 element Device.serialNumber as Equivalent.
Device.name Device.deviceName Element Device.name is mapped to FHIR R4 element Device.deviceName as Equivalent.
Device.name.value Device.deviceName
Device.deviceName.name		 Element Device.name.value is mapped to FHIR R4 element Device.deviceName.name as Equivalent.
Element Device.name.value is mapped to FHIR R4 element Device.deviceName as SourceIsNarrowerThanTarget.
Device.name.type Device.deviceName.type Element Device.name.type is mapped to FHIR R4 element Device.deviceName.type as SourceIsNarrowerThanTarget.
The mappings for Device.name.type do not allow expression of the necessary codes, per the bindings on the source and target.
Device.name.display Device.deviceName Element Device.name.display is mapped to FHIR R4 element Device.deviceName as SourceIsNarrowerThanTarget.
Device.modelNumber Device.modelNumber Element Device.modelNumber is mapped to FHIR R4 element Device.modelNumber as Equivalent.
Device.partNumber Device.partNumber Element Device.partNumber is mapped to FHIR R4 element Device.partNumber as Equivalent.
Device.category Extension: ExtensionDevice_Category Element Device.category has a context of Device based on following the parent source element upwards and mapping to Device.
Element Device.category has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Device.type Device.type Element Device.type is mapped to FHIR R4 element Device.type as SourceIsBroaderThanTarget.
Device.version Device.version Element Device.version is mapped to FHIR R4 element Device.version as Equivalent.
Device.version.type Device.version.type Element Device.version.type is mapped to FHIR R4 element Device.version.type as Equivalent.
Device.version.component Device.version.component Element Device.version.component is mapped to FHIR R4 element Device.version.component as Equivalent.
Device.version.installDate Extension: ExtensionDevice_Version_InstallDate Element Device.version.installDate has a context of Device.version based on following the parent source element upwards and mapping to Device.
Element Device.version.installDate has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Device.version.value Device.version.value Element Device.version.value is mapped to FHIR R4 element Device.version.value as Equivalent.
Device.conformsTo Device.specialization
Standard Extension: device-conformsTo		 Element Device.conformsTo is mapped to FHIR R4 element Device.specialization as Equivalent.
An externally-defined extension that has been mapped as the representation of FHIR R5 element Device.conformsTo: http://hl7.org/fhir/StructureDefinition/device-conformsTo.
Device.conformsTo.category Device.specialization Element Device.conformsTo.category is mapped to FHIR R4 element Device.specialization as SourceIsNarrowerThanTarget.
Device.conformsTo.specification Device.specialization Element Device.conformsTo.specification is mapped to FHIR R4 element Device.specialization as SourceIsNarrowerThanTarget.
Device.conformsTo.version Extension: ExtensionDevice_ConformsTo_Version Element Device.conformsTo.version has a context of Device.specialization based on following the parent source element upwards and mapping to Device.
Element Device.conformsTo.version has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Device.property Device.property Element Device.property is mapped to FHIR R4 element Device.property as Equivalent.
Device.property.type Device.property.type Element Device.property.type is mapped to FHIR R4 element Device.property.type as Equivalent.
Device.property.value[x] Device.property.valueCode
Device.property.valueQuantity
Extension: ExtensionDevice_Property_Value		 Element Device.property.value[x] is mapped to FHIR R4 element Device.property.valueQuantity as RelatedTo.
Element Device.property.value[x] is mapped to FHIR R4 element Device.property.valueCode as RelatedTo.
The mappings for Device.property.value[x] do not cover the following types: Attachment, boolean, integer, Range, string.
Device.mode Extension: ExtensionDevice_Mode Element Device.mode has a context of Device based on following the parent source element upwards and mapping to Device.
Element Device.mode has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Device.cycle Extension: ExtensionDevice_Cycle Element Device.cycle has a context of Device based on following the parent source element upwards and mapping to Device.
Element Device.cycle has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Device.duration Extension: ExtensionDevice_Duration Element Device.duration has a context of Device based on following the parent source element upwards and mapping to Device.
Element Device.duration has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Device.owner Device.owner Element Device.owner is mapped to FHIR R4 element Device.owner as Equivalent.
Device.contact Device.contact Element Device.contact is mapped to FHIR R4 element Device.contact as Equivalent.
Device.location Device.location Element Device.location is mapped to FHIR R4 element Device.location as Equivalent.
Device.url Device.url Element Device.url is mapped to FHIR R4 element Device.url as Equivalent.
Device.endpoint Extension: ExtensionDevice_Endpoint Element Device.endpoint has a context of Device based on following the parent source element upwards and mapping to Device.
Element Device.endpoint has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Device.gateway Extension: ExtensionDevice_Gateway Element Device.gateway has a context of Device based on following the parent source element upwards and mapping to Device.
Element Device.gateway has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Device.note Device.note Element Device.note is mapped to FHIR R4 element Device.note as Equivalent.
Device.safety Device.safety Element Device.safety is mapped to FHIR R4 element Device.safety as Equivalent.
Device.parent Device.parent Element Device.parent is mapped to FHIR R4 element Device.parent as Equivalent.