Extensions for Using Data Elements from FHIR STU3 in FHIR R4B
0.1.0 - STU
Extensions for Using Data Elements from FHIR STU3 in FHIR R4B
0.1.0 - STU
Extensions for Using Data Elements from FHIR STU3 in FHIR R4B - Downloaded Version null See the Directory of published versions
| Official URL: http://hl7.org/fhir/uv/xver/ConceptMap/R3-Device-element-map-to-R4B | Version: 0.1.0 | |||
| Standards status: Trial-use | Maturity Level: 0 | Computable Name: R3DeviceElementMapToR4B | ||
This ConceptMap represents cross-version mappings for elements from a FHIR STU3 Device to FHIR R4B.
Mapping from http://hl7.org/fhir/3.0 to http://hl7.org/fhir/4.3
Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/Device|3.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. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation. |
| 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. 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 in formation is added later. |
| 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. The barcode string from a barcode present on a device label or package may identify the instance, include names given to the device in local usage, or may identify the type of device. If the identifier identifies the type of device, Device.type element should be used. For [UDI](https://hl7.org/fhir/device.html#5.11.3.2.2), this element corresponds to the variable portion of the UDI that identifies the serial number of a specific device. See [UDI mappings](https://hl7.org/fhir/devi.html#udi) for a complete mapping of UDI parts to Device. |
| Device.udi (udi) | is related to | Device.udiCarrier | Element `Device.udi` is mapped to FHIR R4B element `Device.udiCarrier` as `SourceIsNarrowerThanTarget`. UDI may identify an unique instance of a device, or it may only identify the type of the device. See [UDI mappings](https://hl7.org/fhir/devi.html#udi) for a complete mapping of UDI parts to Device. |
| Device.udi.deviceIdentifier (deviceIdentifier) | is equivalent to | Device.udiCarrier.deviceIdentifier | Element `Device.udi.deviceIdentifier` is mapped to FHIR R4B element `Device.udiCarrier.deviceIdentifier` as `Equivalent`. |
| Device.udi.jurisdiction (jurisdiction) | is equivalent to | Device.udiCarrier.jurisdiction | Element `Device.udi.jurisdiction` is mapped to FHIR R4B element `Device.udiCarrier.jurisdiction` as `Equivalent`. |
| Device.udi.carrierHRF (carrierHRF) | is equivalent to | Device.udiCarrier.carrierHRF | Element `Device.udi.carrierHRF` is mapped to FHIR R4B element `Device.udiCarrier.carrierHRF` as `Equivalent`. If separate barcodes for DI and PI are present, concatenate the string with DI first and in order of human readable expression on label. |
| Device.udi.carrierAIDC (carrierAIDC) | is equivalent to | Device.udiCarrier.carrierAIDC | Element `Device.udi.carrierAIDC` is mapped to FHIR R4B element `Device.udiCarrier.carrierAIDC` as `Equivalent`. The AIDC form of UDIs should be scanned or otherwise used for the identification of the device whenever possible to minimize errors in records resulting from manual transcriptions. If separate barcodes for DI and PI are present, concatenate the string with DI first and in order of human readable expression on label. |
| Device.udi.issuer (issuer) | is equivalent to | Device.udiCarrier.issuer | Element `Device.udi.issuer` is mapped to FHIR R4B element `Device.udiCarrier.issuer` as `Equivalent`. |
| Device.udi.entryType (entryType) | is equivalent to | Device.udiCarrier.entryType | Element `Device.udi.entryType` is mapped to FHIR R4B element `Device.udiCarrier.entryType` as `Equivalent`. |
| Device.status (status) | is equivalent to | Device.status | Element `Device.status` is mapped to FHIR R4B element `Device.status` as `Equivalent`. This element is labeled as a modifier because the status contains the codes inactive and entered-in-error that mark the device (record)as not currently valid. |
| Device.type (type) | is equivalent to | Device.type | Element `Device.type` is mapped to FHIR R4B element `Device.type` as `Equivalent`. |
| Device.lotNumber (lotNumber) | is equivalent to | Device.lotNumber | Element `Device.lotNumber` is mapped to FHIR R4B element `Device.lotNumber` as `Equivalent`. |
| Device.manufacturer (manufacturer) | is equivalent to | Device.manufacturer | Element `Device.manufacturer` is mapped to FHIR R4B element `Device.manufacturer` as `Equivalent`. |
| Device.manufactureDate (manufactureDate) | is equivalent to | Device.manufactureDate | Element `Device.manufactureDate` is mapped to FHIR R4B element `Device.manufactureDate` as `Equivalent`. |
| Device.expirationDate (expirationDate) | is equivalent to | Device.expirationDate | Element `Device.expirationDate` is mapped to FHIR R4B element `Device.expirationDate` 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.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, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `Device.patient` with unmapped reference targets: Patient. |
| 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, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `Device.owner` with unmapped reference targets: Organization. |
| 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.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, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `Device.location` with unmapped reference targets: Location. |
| 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 Base URL from which a conformance statement may be retrieved. |
| 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.safety (safety) | is equivalent to | Device.safety | Element `Device.safety` is mapped to FHIR R4B element `Device.safety` as `Equivalent`. |
Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/Device|3.0.2 to STU3: meta additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| Device.meta (meta) | is equivalent to | Extension (STU3: 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|3.0.2 to STU3: text additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| Device.text (text) | is equivalent to | Extension (STU3: 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. 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 in formation is added later. |
Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/Device|3.0.2 to STU3: identifier additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| Device.identifier (identifier) | is equivalent to | Extension (STU3: identifier 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. The barcode string from a barcode present on a device label or package may identify the instance, include names given to the device in local usage, or may identify the type of device. If the identifier identifies the type of device, Device.type element should be used. For [UDI](https://hl7.org/fhir/device.html#5.11.3.2.2), this element corresponds to the variable portion of the UDI that identifies the serial number of a specific device. See [UDI mappings](https://hl7.org/fhir/devi.html#udi) for a complete mapping of UDI parts to Device. |
Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/Device|3.0.2 to STU3: Device Name as appears on UDI label (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| Device.udi.name (name) | is equivalent to | Extension (STU3: Device Name as appears on UDI label (new)) | Element `Device.udi.name` has a context of Device.udiCarrier based on following the parent source element upwards and mapping to `Device`. Element `Device.udi.name` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). Use the `Device.type` for a generic type or kind of device name. Note the [GUDID](http://www.fda.gov/medicaldevices/deviceregulationandguidance/uniquedeviceidentification/globaludidatabasegudid/default.htm) lists the name as the 'Brand Name'. |
Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/Device|3.0.2 to STU3: contact additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| Device.contact (contact) | is equivalent to | Extension (STU3: 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. |
Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/Device|3.0.2 to STU3: note additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| Device.note (note) | is equivalent to | Extension (STU3: 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. |
IG © 2025+ FHIR Infrastructure. Package hl7.fhir.uv.xver-r3.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