Extensions for Using Data Elements from FHIR DSTU2 in FHIR R4B
0.1.0 - STU
Extensions for Using Data Elements from FHIR DSTU2 in FHIR R4B
0.1.0 - STU
Extensions for Using Data Elements from FHIR DSTU2 in FHIR R4B - Downloaded Version null See the Directory of published versions
| Official URL: http://hl7.org/fhir/uv/xver/ConceptMap/R2-Device-element-map-to-R4B | Version: 0.1.0 | |||
| Standards status: Trial-use | Maturity Level: 0 | Computable Name: R2DeviceElementMapToR4B | ||
This ConceptMap represents cross-version mappings for elements from a FHIR DSTU2 Device to FHIR R4B.
Mapping from http://hl7.org/fhir/1.0 to http://hl7.org/fhir/4.3
Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/Device|1.0.2 to Deviceversion: 4.3.0)
| Source Code | Relationship | Target Code | Comment |
| Device.meta (meta) | maps to wider concept | Device.meta | Element `Device.meta` is mapped to FHIR R4B element `Device.meta` as `SourceIsBroaderThanTarget`. The mappings for `Device.meta` do not cover the following types: Meta. The mappings for `Device.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId. |
| Device.implicitRules (implicitRules) | is equivalent to | Device.implicitRules | Element `Device.implicitRules` is mapped to FHIR R4B element `Device.implicitRules` as `Equivalent`. 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 as much as possible. |
| Device.language (language) | is equivalent to | Device.language | Element `Device.language` is mapped to FHIR R4B element `Device.language` as `Equivalent`. 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). |
| Device.text (text) | maps to wider concept | Device.text | Element `Device.text` is mapped to FHIR R4B element `Device.text` as `SourceIsBroaderThanTarget`. The mappings for `Device.text` do not cover the following types: Narrative. The mappings for `Device.text` do not cover the following types based on type expansion: div, status. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. |
| Device.contained (contained) | is equivalent to | Device.contained | Element `Device.contained` is mapped to FHIR R4B element `Device.contained` as `SourceIsBroaderThanTarget`. 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. |
| Device.identifier (identifier) | maps to wider concept | Device.identifier | Element `Device.identifier` is mapped to FHIR R4B element `Device.identifier` as `SourceIsBroaderThanTarget`. The mappings for `Device.identifier` do not cover the following types: Identifier. The mappings for `Device.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value. Often fixed to the device as a barcode and may include names given to the device in local usage. Note that some of the barcodes affixed to the device identify its type, not its instance. For the FDA mandated Unique Device Identifier (UDI) use the Device.udi element. |
| Device.type (type) | is equivalent to | Device.type | Element `Device.type` is mapped to FHIR R4B element `Device.type` as `Equivalent`. For the FDA mandated Unique Device Identifier (UDI) use the Device.udi element. |
| Device.note (note) | maps to wider concept | Device.note | Element `Device.note` is mapped to FHIR R4B element `Device.note` as `SourceIsBroaderThanTarget`. The mappings for `Device.note` do not cover the following types: Annotation. The mappings for `Device.note` do not cover the following types based on type expansion: author[x], text, time. |
| Device.status (status) | is equivalent to | Device.status | Element `Device.status` is mapped to FHIR R4B 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.manufacturer (manufacturer) | is equivalent to | Device.manufacturer | Element `Device.manufacturer` is mapped to FHIR R4B element `Device.manufacturer` as `Equivalent`. |
| Device.model (model) | is equivalent to | Device.modelNumber | Element `Device.model` is mapped to FHIR R4B element `Device.modelNumber` as `Equivalent`. |
| Device.version (version) | is equivalent to | Device.version.value | Element `Device.version` is mapped to FHIR R4B element `Device.version.value` as `Equivalent`. |
| Device.manufactureDate (manufactureDate) | is equivalent to | Device.manufactureDate | Element `Device.manufactureDate` is mapped to FHIR R4B element `Device.manufactureDate` as `Equivalent`. |
| Device.expiry (expiry) | is equivalent to | Device.expirationDate | Element `Device.expiry` is mapped to FHIR R4B element `Device.expirationDate` as `Equivalent`. |
| Device.udi (udi) | is equivalent to | Device.udiCarrier.deviceIdentifier | Element `Device.udi` is mapped to FHIR R4B element `Device.udiCarrier.deviceIdentifier` as `Equivalent`. The unique identifier may identify an instance of a device uniquely, or it may only identify the type of the device. A portion of the UDI - the DI part - can be extracted from the UDI when required, and used to look up information about the device through the GUDID. |
| Device.lotNumber (lotNumber) | is equivalent to | Device.lotNumber | Element `Device.lotNumber` is mapped to FHIR R4B element `Device.lotNumber` as `Equivalent`. Alphanumeric Maximum 20. |
| Device.owner (owner) | maps to wider concept | Device.owner | Element `Device.owner` is mapped to FHIR R4B element `Device.owner` as `SourceIsBroaderThanTarget`. The mappings for `Device.owner` do not cover the following types based on type expansion: display, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `Device.owner` with unmapped reference targets: Organization. |
| Device.location (location) | maps to wider concept | Device.location | Element `Device.location` is mapped to FHIR R4B element `Device.location` as `SourceIsBroaderThanTarget`. The mappings for `Device.location` do not cover the following types based on type expansion: display, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `Device.location` with unmapped reference targets: Location. |
| Device.patient (patient) | maps to wider concept | Device.patient | Element `Device.patient` is mapped to FHIR R4B element `Device.patient` as `SourceIsBroaderThanTarget`. The mappings for `Device.patient` do not cover the following types based on type expansion: display, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `Device.patient` with unmapped reference targets: Patient. |
| Device.contact (contact) | maps to wider concept | Device.contact | Element `Device.contact` is mapped to FHIR R4B element `Device.contact` as `SourceIsBroaderThanTarget`. The mappings for `Device.contact` do not cover the following types: ContactPoint. The mappings for `Device.contact` do not cover the following types based on type expansion: period, rank, system, use, value. used for troubleshooting etc. |
| Device.url (url) | is equivalent to | Device.url | Element `Device.url` is mapped to FHIR R4B element `Device.url` as `Equivalent`. If the device is running a FHIR server, the network address should be the root URL from which a conformance statement may be retrieved. |
Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/Device|1.0.2 to DSTU2: meta additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| Device.meta (meta) | is equivalent to | Extension (DSTU2: meta additional types) | Element `Device.meta` is mapped to FHIR R4B element `Device.meta` as `SourceIsBroaderThanTarget`. The mappings for `Device.meta` do not cover the following types: Meta. The mappings for `Device.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId. |
Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/Device|1.0.2 to DSTU2: text additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| Device.text (text) | is equivalent to | Extension (DSTU2: text additional types) | Element `Device.text` is mapped to FHIR R4B element `Device.text` as `SourceIsBroaderThanTarget`. The mappings for `Device.text` do not cover the following types: Narrative. The mappings for `Device.text` do not cover the following types based on type expansion: div, status. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. |
Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/Device|1.0.2 to DSTU2: Instance id from manufacturer, owner, and others additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| Device.identifier (identifier) | is equivalent to | Extension (DSTU2: Instance id from manufacturer, owner, and others additional types) | Element `Device.identifier` is mapped to FHIR R4B element `Device.identifier` as `SourceIsBroaderThanTarget`. The mappings for `Device.identifier` do not cover the following types: Identifier. The mappings for `Device.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value. Often fixed to the device as a barcode and may include names given to the device in local usage. Note that some of the barcodes affixed to the device identify its type, not its instance. For the FDA mandated Unique Device Identifier (UDI) use the Device.udi element. |
Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/Device|1.0.2 to DSTU2: note additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| Device.note (note) | is equivalent to | Extension (DSTU2: note additional types) | Element `Device.note` is mapped to FHIR R4B element `Device.note` as `SourceIsBroaderThanTarget`. The mappings for `Device.note` do not cover the following types: Annotation. The mappings for `Device.note` do not cover the following types based on type expansion: author[x], text, time. |
Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/Device|1.0.2 to DSTU2: contact additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| Device.contact (contact) | is equivalent to | Extension (DSTU2: contact additional types) | Element `Device.contact` is mapped to FHIR R4B element `Device.contact` as `SourceIsBroaderThanTarget`. The mappings for `Device.contact` do not cover the following types: ContactPoint. The mappings for `Device.contact` do not cover the following types based on type expansion: period, rank, system, use, value. used for troubleshooting etc. |
IG © 2025+ FHIR Infrastructure. Package hl7.fhir.uv.xver-r2.r4b#0.1.0 based on FHIR 4.3.0. Generated 2026-03-20
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change