Extensions for Using Data Elements from FHIR R4B in FHIR R5
0.1.0 - STU
Extensions for Using Data Elements from FHIR R4B in FHIR R5
0.1.0 - STU
Extensions for Using Data Elements from FHIR R4B in FHIR R5 - Downloaded Version null See the Directory of published versions
| Page standards status: Trial-use | Maturity Level: 0 |
<ConceptMap xmlns="http://hl7.org/fhir">
<id value="R4B-Device-element-map-to-R5"/>
<text>
<status value="generated"/>
<div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: ConceptMap R4B-Device-element-map-to-R5</b></p><a name="R4B-Device-element-map-to-R5"> </a><a name="hcR4B-Device-element-map-to-R5"> </a><p>Mapping from http://hl7.org/fhir/4.3 to http://hl7.org/fhir/5.0</p><br/><p><b>Group 1 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Device|4.3.0</code> to <a href="http://hl7.org/fhir/R5/device.html">Deviceversion: 5.0.0)</a></p><table class="grid"><tr><td colspan="2"><b>Source Concept Details</b></td><td><b>Relationship</b></td><td colspan="2"><b>Target Concept Details</b></td><td><b>Comment</b></td></tr><tr><td colspan="2"><b>Codes</b> from http://hl7.org/fhir/StructureDefinition/Device|4.3.0</td><td/><td colspan="2" title="http://hl7.org/fhir/StructureDefinition/Device|5.0.0"><b>Codes</b> from Device</td><td/></tr><tr><td style="border-right-width: 0px">Device.meta</td><td style="border-left-width: 0px">meta</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">Device.meta</td><td style="border-left-width: 0px">Device.meta</td><td>Element `Device.meta` is mapped to FHIR R5 element `Device.meta` as `Equivalent`.
Element `Device.meta` is mapped to FHIR R5 element `DeviceAssociation.meta` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">Device.implicitRules</td><td style="border-left-width: 0px">implicitRules</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">Device.implicitRules</td><td style="border-left-width: 0px">Device.implicitRules</td><td>Element `Device.implicitRules` is mapped to FHIR R5 element `Device.implicitRules` as `Equivalent`.
Element `Device.implicitRules` is mapped to FHIR R5 element `DeviceAssociation.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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.</td></tr><tr><td style="border-right-width: 0px">Device.language</td><td style="border-left-width: 0px">language</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">Device.language</td><td style="border-left-width: 0px">Device.language</td><td>Element `Device.language` is mapped to FHIR R5 element `Device.language` as `Equivalent`.
Element `Device.language` is mapped to FHIR R5 element `DeviceAssociation.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).</td></tr><tr><td style="border-right-width: 0px">Device.text</td><td style="border-left-width: 0px">text</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">Device.text</td><td style="border-left-width: 0px">Device.text</td><td>Element `Device.text` is mapped to FHIR R5 element `Device.text` as `Equivalent`.
Element `Device.text` is mapped to FHIR R5 element `DeviceAssociation.text` as `Equivalent`.
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 information is added later.</td></tr><tr><td style="border-right-width: 0px">Device.contained</td><td style="border-left-width: 0px">contained</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">Device.contained</td><td style="border-left-width: 0px">Device.contained</td><td>Element `Device.contained` is mapped to FHIR R5 element `Device.contained` as `Equivalent`.
Element `Device.contained` is mapped to FHIR R5 element `DeviceAssociation.contained` as `Equivalent`.
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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.</td></tr><tr><td style="border-right-width: 0px">Device.identifier</td><td style="border-left-width: 0px">identifier</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">Device.identifier</td><td style="border-left-width: 0px">Device.identifier</td><td>Element `Device.identifier` is mapped to FHIR R5 element `Device.identifier` as `Equivalent`.
Element `Device.identifier` is mapped to FHIR R5 element `DeviceAssociation.identifier` as `Equivalent`.
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.</td></tr><tr><td style="border-right-width: 0px">Device.definition</td><td style="border-left-width: 0px">definition</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">Device.definition</td><td style="border-left-width: 0px">Device.definition</td><td>Element `Device.definition` is mapped to FHIR R5 element `Device.definition` as `SourceIsNarrowerThanTarget`.</td></tr><tr><td style="border-right-width: 0px">Device.udiCarrier</td><td style="border-left-width: 0px">udiCarrier</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#related-to" title="related-to">is related to</a></td><td style="border-right-width: 0px">Device.udiCarrier</td><td style="border-left-width: 0px">Device.udiCarrier</td><td>Element `Device.udiCarrier` is mapped to FHIR R5 element `Device.udiCarrier` as `Equivalent`.
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.</td></tr><tr><td style="border-right-width: 0px">Device.udiCarrier.deviceIdentifier</td><td style="border-left-width: 0px">deviceIdentifier</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">Device.udiCarrier.deviceIdentifier</td><td style="border-left-width: 0px">Device.udiCarrier.deviceIdentifier</td><td>Element `Device.udiCarrier.deviceIdentifier` is mapped to FHIR R5 element `Device.udiCarrier.deviceIdentifier` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">Device.udiCarrier.issuer</td><td style="border-left-width: 0px">issuer</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">Device.udiCarrier.issuer</td><td style="border-left-width: 0px">Device.udiCarrier.issuer</td><td>Element `Device.udiCarrier.issuer` is mapped to FHIR R5 element `Device.udiCarrier.issuer` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">Device.udiCarrier.jurisdiction</td><td style="border-left-width: 0px">jurisdiction</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">Device.udiCarrier.jurisdiction</td><td style="border-left-width: 0px">Device.udiCarrier.jurisdiction</td><td>Element `Device.udiCarrier.jurisdiction` is mapped to FHIR R5 element `Device.udiCarrier.jurisdiction` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">Device.udiCarrier.carrierAIDC</td><td style="border-left-width: 0px">carrierAIDC</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">Device.udiCarrier.carrierAIDC</td><td style="border-left-width: 0px">Device.udiCarrier.carrierAIDC</td><td>Element `Device.udiCarrier.carrierAIDC` is mapped to FHIR R5 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.</td></tr><tr><td style="border-right-width: 0px">Device.udiCarrier.carrierHRF</td><td style="border-left-width: 0px">carrierHRF</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">Device.udiCarrier.carrierHRF</td><td style="border-left-width: 0px">Device.udiCarrier.carrierHRF</td><td>Element `Device.udiCarrier.carrierHRF` is mapped to FHIR R5 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.</td></tr><tr><td style="border-right-width: 0px">Device.udiCarrier.entryType</td><td style="border-left-width: 0px">entryType</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#related-to" title="related-to">is related to</a></td><td style="border-right-width: 0px">Device.udiCarrier.entryType</td><td style="border-left-width: 0px">Device.udiCarrier.entryType</td><td>Element `Device.udiCarrier.entryType` is mapped to FHIR R5 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.</td></tr><tr><td style="border-right-width: 0px">Device.status</td><td style="border-left-width: 0px">status</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#related-to" title="related-to">is related to</a></td><td style="border-right-width: 0px">Device.status</td><td style="border-left-width: 0px">Device.status</td><td>Element `Device.status` is mapped to FHIR R5 element `Device.status` as `SourceIsBroaderThanTarget`.
Element `Device.status` is mapped to FHIR R5 element `DeviceAssociation.status` as `SourceIsNarrowerThanTarget`.
The mappings for `Device.status` do not allow expression of the necessary codes, per the bindings on the source and target.
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.</td></tr><tr><td style="border-right-width: 0px">Device.manufacturer</td><td style="border-left-width: 0px">manufacturer</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">Device.manufacturer</td><td style="border-left-width: 0px">Device.manufacturer</td><td>Element `Device.manufacturer` is mapped to FHIR R5 element `Device.manufacturer` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">Device.manufactureDate</td><td style="border-left-width: 0px">manufactureDate</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">Device.manufactureDate</td><td style="border-left-width: 0px">Device.manufactureDate</td><td>Element `Device.manufactureDate` is mapped to FHIR R5 element `Device.manufactureDate` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">Device.expirationDate</td><td style="border-left-width: 0px">expirationDate</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">Device.expirationDate</td><td style="border-left-width: 0px">Device.expirationDate</td><td>Element `Device.expirationDate` is mapped to FHIR R5 element `Device.expirationDate` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">Device.lotNumber</td><td style="border-left-width: 0px">lotNumber</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">Device.lotNumber</td><td style="border-left-width: 0px">Device.lotNumber</td><td>Element `Device.lotNumber` is mapped to FHIR R5 element `Device.lotNumber` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">Device.serialNumber</td><td style="border-left-width: 0px">serialNumber</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">Device.serialNumber</td><td style="border-left-width: 0px">Device.serialNumber</td><td>Element `Device.serialNumber` is mapped to FHIR R5 element `Device.serialNumber` as `Equivalent`.
Alphanumeric Maximum 20.</td></tr><tr><td style="border-right-width: 0px; border-bottom-style: none">Device.deviceName</td><td style="border-left-width: 0px; border-bottom-style: none">deviceName</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#related-to" title="related-to">is related to</a></td><td style="border-right-width: 0px">Device.displayName</td><td style="border-left-width: 0px">Device.displayName</td><td>Element `Device.deviceName` is mapped to FHIR R5 element `Device.displayName` as `RelatedTo`.
Element `Device.deviceName` is mapped to FHIR R5 element `Device.name` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px; border-top-style: none"/><td style="border-top-style: none; border-left-width: 0px"/><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#related-to" title="related-to">is related to</a></td><td style="border-right-width: 0px">Device.name</td><td style="border-left-width: 0px">Device.name</td><td>Element `Device.deviceName` is mapped to FHIR R5 element `Device.displayName` as `RelatedTo`.
Element `Device.deviceName` is mapped to FHIR R5 element `Device.name` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">Device.deviceName.name</td><td style="border-left-width: 0px">name</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">Device.name.value</td><td style="border-left-width: 0px">Device.name.value</td><td>Element `Device.deviceName.name` is mapped to FHIR R5 element `Device.name.value` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">Device.deviceName.type</td><td style="border-left-width: 0px">type</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#related-to" title="related-to">is related to</a></td><td style="border-right-width: 0px">Device.name.type</td><td style="border-left-width: 0px">Device.name.type</td><td>Element `Device.deviceName.type` is mapped to FHIR R5 element `Device.name.type` as `SourceIsBroaderThanTarget`.</td></tr><tr><td style="border-right-width: 0px">Device.modelNumber</td><td style="border-left-width: 0px">modelNumber</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">Device.modelNumber</td><td style="border-left-width: 0px">Device.modelNumber</td><td>Element `Device.modelNumber` is mapped to FHIR R5 element `Device.modelNumber` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">Device.partNumber</td><td style="border-left-width: 0px">partNumber</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">Device.partNumber</td><td style="border-left-width: 0px">Device.partNumber</td><td>Element `Device.partNumber` is mapped to FHIR R5 element `Device.partNumber` as `Equivalent`.
Alphanumeric Maximum 20.</td></tr><tr><td style="border-right-width: 0px">Device.type</td><td style="border-left-width: 0px">type</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">Device.type</td><td style="border-left-width: 0px">Device.type</td><td>Element `Device.type` is mapped to FHIR R5 element `Device.type` as `SourceIsNarrowerThanTarget`.</td></tr><tr><td style="border-right-width: 0px">Device.specialization</td><td style="border-left-width: 0px">specialization</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#related-to" title="related-to">is related to</a></td><td style="border-right-width: 0px">Device.conformsTo</td><td style="border-left-width: 0px">Device.conformsTo</td><td>Element `Device.specialization` is mapped to FHIR R5 element `Device.conformsTo` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">Device.version</td><td style="border-left-width: 0px">version</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#related-to" title="related-to">is related to</a></td><td style="border-right-width: 0px">Device.version</td><td style="border-left-width: 0px">Device.version</td><td>Element `Device.version` is mapped to FHIR R5 element `Device.version` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">Device.version.type</td><td style="border-left-width: 0px">type</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">Device.version.type</td><td style="border-left-width: 0px">Device.version.type</td><td>Element `Device.version.type` is mapped to FHIR R5 element `Device.version.type` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">Device.version.component</td><td style="border-left-width: 0px">component</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">Device.version.component</td><td style="border-left-width: 0px">Device.version.component</td><td>Element `Device.version.component` is mapped to FHIR R5 element `Device.version.component` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">Device.version.value</td><td style="border-left-width: 0px">value</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">Device.version.value</td><td style="border-left-width: 0px">Device.version.value</td><td>Element `Device.version.value` is mapped to FHIR R5 element `Device.version.value` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">Device.property</td><td style="border-left-width: 0px">property</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#related-to" title="related-to">is related to</a></td><td style="border-right-width: 0px">Device.property</td><td style="border-left-width: 0px">Device.property</td><td>Element `Device.property` is mapped to FHIR R5 element `Device.property` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">Device.property.type</td><td style="border-left-width: 0px">type</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">Device.property.type</td><td style="border-left-width: 0px">Device.property.type</td><td>Element `Device.property.type` is mapped to FHIR R5 element `Device.property.type` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">Device.owner</td><td style="border-left-width: 0px">owner</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">Device.owner</td><td style="border-left-width: 0px">Device.owner</td><td>Element `Device.owner` is mapped to FHIR R5 element `Device.owner` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">Device.contact</td><td style="border-left-width: 0px">contact</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">Device.contact</td><td style="border-left-width: 0px">Device.contact</td><td>Element `Device.contact` is mapped to FHIR R5 element `Device.contact` as `Equivalent`.
used for troubleshooting etc.</td></tr><tr><td style="border-right-width: 0px">Device.location</td><td style="border-left-width: 0px">location</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">Device.location</td><td style="border-left-width: 0px">Device.location</td><td>Element `Device.location` is mapped to FHIR R5 element `Device.location` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">Device.url</td><td style="border-left-width: 0px">url</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">Device.url</td><td style="border-left-width: 0px">Device.url</td><td>Element `Device.url` is mapped to FHIR R5 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.</td></tr><tr><td style="border-right-width: 0px">Device.note</td><td style="border-left-width: 0px">note</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">Device.note</td><td style="border-left-width: 0px">Device.note</td><td>Element `Device.note` is mapped to FHIR R5 element `Device.note` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">Device.safety</td><td style="border-left-width: 0px">safety</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">Device.safety</td><td style="border-left-width: 0px">Device.safety</td><td>Element `Device.safety` is mapped to FHIR R5 element `Device.safety` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">Device.parent</td><td style="border-left-width: 0px">parent</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">Device.parent</td><td style="border-left-width: 0px">Device.parent</td><td>Element `Device.parent` is mapped to FHIR R5 element `Device.parent` as `Equivalent`.</td></tr></table><hr/><p><b>Group 2 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Device|4.3.0</code> to <a href="http://hl7.org/fhir/R5/deviceassociation.html">DeviceAssociationversion: 5.0.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Device.meta (meta)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>DeviceAssociation.meta</td><td>Element `Device.meta` is mapped to FHIR R5 element `Device.meta` as `Equivalent`.
Element `Device.meta` is mapped to FHIR R5 element `DeviceAssociation.meta` as `Equivalent`.</td></tr><tr><td>Device.implicitRules (implicitRules)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>DeviceAssociation.implicitRules</td><td>Element `Device.implicitRules` is mapped to FHIR R5 element `Device.implicitRules` as `Equivalent`.
Element `Device.implicitRules` is mapped to FHIR R5 element `DeviceAssociation.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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.</td></tr><tr><td>Device.language (language)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>DeviceAssociation.language</td><td>Element `Device.language` is mapped to FHIR R5 element `Device.language` as `Equivalent`.
Element `Device.language` is mapped to FHIR R5 element `DeviceAssociation.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).</td></tr><tr><td>Device.text (text)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>DeviceAssociation.text</td><td>Element `Device.text` is mapped to FHIR R5 element `Device.text` as `Equivalent`.
Element `Device.text` is mapped to FHIR R5 element `DeviceAssociation.text` as `Equivalent`.
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 information is added later.</td></tr><tr><td>Device.contained (contained)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>DeviceAssociation.contained</td><td>Element `Device.contained` is mapped to FHIR R5 element `Device.contained` as `Equivalent`.
Element `Device.contained` is mapped to FHIR R5 element `DeviceAssociation.contained` as `Equivalent`.
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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.</td></tr><tr><td>Device.identifier (identifier)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>DeviceAssociation.identifier</td><td>Element `Device.identifier` is mapped to FHIR R5 element `Device.identifier` as `Equivalent`.
Element `Device.identifier` is mapped to FHIR R5 element `DeviceAssociation.identifier` as `Equivalent`.
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.</td></tr><tr><td>Device.status (status)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>DeviceAssociation.status</td><td>Element `Device.status` is mapped to FHIR R5 element `Device.status` as `SourceIsBroaderThanTarget`.
Element `Device.status` is mapped to FHIR R5 element `DeviceAssociation.status` as `SourceIsNarrowerThanTarget`.
The mappings for `Device.status` do not allow expression of the necessary codes, per the bindings on the source and target.
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.</td></tr><tr><td>Device.statusReason (statusReason)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>DeviceAssociation.statusReason</td><td>Element `Device.statusReason` is mapped to FHIR R5 element `DeviceAssociation.statusReason` as `Equivalent`.</td></tr><tr><td>Device.patient (patient)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>DeviceAssociation.subject</td><td>Element `Device.patient` is mapped to FHIR R5 element `DeviceAssociation.subject` as `SourceIsNarrowerThanTarget`.</td></tr></table><hr/><p><b>Group 3 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Device|4.3.0</code> to <a href="StructureDefinition-ext-R4B-Device.udi.entryType.html">R4B: barcode | rfid | manual + additional codesversion: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Device.udiCarrier.entryType (entryType)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#source-is-broader-than-target" title="source-is-broader-than-target">is broader than</a></td><td>Extension (R4B: barcode | rfid | manual + additional codes)</td><td>Element `Device.udiCarrier.entryType` is mapped to FHIR R5 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.</td></tr></table><hr/><p><b>Group 4 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Device|4.3.0</code> to <a href="StructureDefinition-ext-R4B-Device.distinctIdentifier.html">R4B: The distinct identification string (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Device.distinctIdentifier (distinctIdentifier)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#source-is-broader-than-target" title="source-is-broader-than-target">is broader than</a></td><td>Extension (R4B: The distinct identification string (new))</td><td>Element `Device.distinctIdentifier` has a context of Device based on following the parent source element upwards and mapping to `Device`.
Element `Device.distinctIdentifier` has a context of DeviceAssociation based on following the parent source element upwards and mapping to `DeviceAssociation`.
Element `Device.distinctIdentifier` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
For example, this applies to devices in the United States regulated under *Code of Federal Regulation 21CFR1271.290(c)*.</td></tr></table><hr/><p><b>Group 5 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Device|4.3.0</code> to <a href="StructureDefinition-ext-R4B-Device.dev.type.html">R4B: udi-label-name | user-friendly-name | patient-reported-name | manufacturer-name | model-name | otherversion: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Device.deviceName.type (type)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#source-is-broader-than-target" title="source-is-broader-than-target">is broader than</a></td><td>Extension (R4B: udi-label-name | user-friendly-name | patient-reported-name | manufacturer-name | model-name | other)</td><td>Element `Device.deviceName.type` is mapped to FHIR R5 element `Device.name.type` as `SourceIsBroaderThanTarget`.</td></tr></table><hr/><p><b>Group 6 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Device|4.3.0</code> to <a href="StructureDefinition-ext-R4B-Device.spe.systemType.html">R4B: The standard that is used to operate and communicate (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Device.specialization.systemType (systemType)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#source-is-broader-than-target" title="source-is-broader-than-target">is broader than</a></td><td>Extension (R4B: The standard that is used to operate and communicate (new))</td><td>Element `Device.specialization.systemType` has a context of Device.conformsTo based on following the parent source element upwards and mapping to `Device`.
Element `Device.specialization.systemType` has a context of DeviceAssociation based on following the parent source element upwards and mapping to `DeviceAssociation`.
Element `Device.specialization.systemType` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 7 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Device|4.3.0</code> to <a href="StructureDefinition-ext-R4B-Device.spe.version.html">R4B: The version of the standard that is used to operate and communicate (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Device.specialization.version (version)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#source-is-broader-than-target" title="source-is-broader-than-target">is broader than</a></td><td>Extension (R4B: The version of the standard that is used to operate and communicate (new))</td><td>Element `Device.specialization.version` has a context of Device.conformsTo based on following the parent source element upwards and mapping to `Device`.
Element `Device.specialization.version` has a context of DeviceAssociation based on following the parent source element upwards and mapping to `DeviceAssociation`.
Element `Device.specialization.version` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 8 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Device|4.3.0</code> to <a href="StructureDefinition-ext-R4B-Device.pro.valueQuantity.html">R4B: Property value as a quantity (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Device.property.valueQuantity (valueQuantity)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#source-is-broader-than-target" title="source-is-broader-than-target">is broader than</a></td><td>Extension (R4B: Property value as a quantity (new))</td><td>Element `Device.property.valueQuantity` has a context of Device.property based on following the parent source element upwards and mapping to `Device`.
Element `Device.property.valueQuantity` has a context of DeviceAssociation based on following the parent source element upwards and mapping to `DeviceAssociation`.
Element `Device.property.valueQuantity` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 9 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Device|4.3.0</code> to <a href="StructureDefinition-ext-R4B-Device.pro.valueCode.html">R4B: Property value as a code, e.g., NTP4 (synced to NTP) (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Device.property.valueCode (valueCode)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#source-is-broader-than-target" title="source-is-broader-than-target">is broader than</a></td><td>Extension (R4B: Property value as a code, e.g., NTP4 (synced to NTP) (new))</td><td>Element `Device.property.valueCode` has a context of Device.property based on following the parent source element upwards and mapping to `Device`.
Element `Device.property.valueCode` has a context of DeviceAssociation based on following the parent source element upwards and mapping to `DeviceAssociation`.
Element `Device.property.valueCode` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).</td></tr></table></div>
</text>
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
<valueCode value="fhir"/>
</extension>
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
<valueInteger value="0">
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom">
<valueCanonical
value="http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4b.r5"/>
</extension>
</valueInteger>
</extension>
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
<valueCode value="trial-use">
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom">
<valueCanonical
value="http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4b.r5"/>
</extension>
</valueCode>
</extension>
<url
value="http://hl7.org/fhir/uv/xver/ConceptMap/R4B-Device-element-map-to-R5"/>
<version value="0.1.0"/>
<name value="R4BDeviceElementMapToR5"/>
<title value="Cross-version mapping for FHIR R4B Device to FHIR R5 Device"/>
<status value="active"/>
<experimental value="false"/>
<date value="2026-03-17T16:03:51.3076028-05:00"/>
<contact>
<name value="FHIR Infrastructure"/>
<telecom>
<system value="url"/>
<value value="http://www.hl7.org/Special/committees/fiwg"/>
</telecom>
</contact>
<description
value="This ConceptMap represents cross-version mappings for elements from a FHIR R4B Device to FHIR R5."/>
<jurisdiction>
<coding>
<system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
<code value="001"/>
<display value="World"/>
</coding>
</jurisdiction>
<sourceScopeCanonical value="http://hl7.org/fhir/4.3"/>
<targetScopeUri value="http://hl7.org/fhir/5.0"/>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Device|4.3.0"/>
<target value="http://hl7.org/fhir/StructureDefinition/Device|5.0.0"/>
<element>
<code value="Device.meta"/>
<display value="meta"/>
<target>
<code value="Device.meta"/>
<display value="Device.meta"/>
<relationship value="equivalent"/>
<comment
value="Element `Device.meta` is mapped to FHIR R5 element `Device.meta` as `Equivalent`.
Element `Device.meta` is mapped to FHIR R5 element `DeviceAssociation.meta` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Device.implicitRules"/>
<display value="implicitRules"/>
<target>
<code value="Device.implicitRules"/>
<display value="Device.implicitRules"/>
<relationship value="equivalent"/>
<comment
value="Element `Device.implicitRules` is mapped to FHIR R5 element `Device.implicitRules` as `Equivalent`.
Element `Device.implicitRules` is mapped to FHIR R5 element `DeviceAssociation.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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc."/>
</target>
</element>
<element>
<code value="Device.language"/>
<display value="language"/>
<target>
<code value="Device.language"/>
<display value="Device.language"/>
<relationship value="equivalent"/>
<comment
value="Element `Device.language` is mapped to FHIR R5 element `Device.language` as `Equivalent`.
Element `Device.language` is mapped to FHIR R5 element `DeviceAssociation.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)."/>
</target>
</element>
<element>
<code value="Device.text"/>
<display value="text"/>
<target>
<code value="Device.text"/>
<display value="Device.text"/>
<relationship value="equivalent"/>
<comment
value="Element `Device.text` is mapped to FHIR R5 element `Device.text` as `Equivalent`.
Element `Device.text` is mapped to FHIR R5 element `DeviceAssociation.text` as `Equivalent`.
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 information is added later."/>
</target>
</element>
<element>
<code value="Device.contained"/>
<display value="contained"/>
<target>
<code value="Device.contained"/>
<display value="Device.contained"/>
<relationship value="equivalent"/>
<comment
value="Element `Device.contained` is mapped to FHIR R5 element `Device.contained` as `Equivalent`.
Element `Device.contained` is mapped to FHIR R5 element `DeviceAssociation.contained` as `Equivalent`.
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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels."/>
</target>
</element>
<element>
<code value="Device.identifier"/>
<display value="identifier"/>
<target>
<code value="Device.identifier"/>
<display value="Device.identifier"/>
<relationship value="equivalent"/>
<comment
value="Element `Device.identifier` is mapped to FHIR R5 element `Device.identifier` as `Equivalent`.
Element `Device.identifier` is mapped to FHIR R5 element `DeviceAssociation.identifier` as `Equivalent`.
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."/>
</target>
</element>
<element>
<code value="Device.definition"/>
<display value="definition"/>
<target>
<code value="Device.definition"/>
<display value="Device.definition"/>
<relationship value="equivalent"/>
<comment
value="Element `Device.definition` is mapped to FHIR R5 element `Device.definition` as `SourceIsNarrowerThanTarget`."/>
</target>
</element>
<element>
<code value="Device.udiCarrier"/>
<display value="udiCarrier"/>
<target>
<code value="Device.udiCarrier"/>
<display value="Device.udiCarrier"/>
<relationship value="related-to"/>
<comment
value="Element `Device.udiCarrier` is mapped to FHIR R5 element `Device.udiCarrier` as `Equivalent`.
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."/>
</target>
</element>
<element>
<code value="Device.udiCarrier.deviceIdentifier"/>
<display value="deviceIdentifier"/>
<target>
<code value="Device.udiCarrier.deviceIdentifier"/>
<display value="Device.udiCarrier.deviceIdentifier"/>
<relationship value="equivalent"/>
<comment
value="Element `Device.udiCarrier.deviceIdentifier` is mapped to FHIR R5 element `Device.udiCarrier.deviceIdentifier` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Device.udiCarrier.issuer"/>
<display value="issuer"/>
<target>
<code value="Device.udiCarrier.issuer"/>
<display value="Device.udiCarrier.issuer"/>
<relationship value="equivalent"/>
<comment
value="Element `Device.udiCarrier.issuer` is mapped to FHIR R5 element `Device.udiCarrier.issuer` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Device.udiCarrier.jurisdiction"/>
<display value="jurisdiction"/>
<target>
<code value="Device.udiCarrier.jurisdiction"/>
<display value="Device.udiCarrier.jurisdiction"/>
<relationship value="equivalent"/>
<comment
value="Element `Device.udiCarrier.jurisdiction` is mapped to FHIR R5 element `Device.udiCarrier.jurisdiction` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Device.udiCarrier.carrierAIDC"/>
<display value="carrierAIDC"/>
<target>
<code value="Device.udiCarrier.carrierAIDC"/>
<display value="Device.udiCarrier.carrierAIDC"/>
<relationship value="equivalent"/>
<comment
value="Element `Device.udiCarrier.carrierAIDC` is mapped to FHIR R5 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."/>
</target>
</element>
<element>
<code value="Device.udiCarrier.carrierHRF"/>
<display value="carrierHRF"/>
<target>
<code value="Device.udiCarrier.carrierHRF"/>
<display value="Device.udiCarrier.carrierHRF"/>
<relationship value="equivalent"/>
<comment
value="Element `Device.udiCarrier.carrierHRF` is mapped to FHIR R5 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."/>
</target>
</element>
<element>
<code value="Device.udiCarrier.entryType"/>
<display value="entryType"/>
<target>
<code value="Device.udiCarrier.entryType"/>
<display value="Device.udiCarrier.entryType"/>
<relationship value="related-to"/>
<comment
value="Element `Device.udiCarrier.entryType` is mapped to FHIR R5 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."/>
</target>
</element>
<element>
<code value="Device.status"/>
<display value="status"/>
<target>
<code value="Device.status"/>
<display value="Device.status"/>
<relationship value="related-to"/>
<comment
value="Element `Device.status` is mapped to FHIR R5 element `Device.status` as `SourceIsBroaderThanTarget`.
Element `Device.status` is mapped to FHIR R5 element `DeviceAssociation.status` as `SourceIsNarrowerThanTarget`.
The mappings for `Device.status` do not allow expression of the necessary codes, per the bindings on the source and target.
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."/>
</target>
</element>
<element>
<code value="Device.manufacturer"/>
<display value="manufacturer"/>
<target>
<code value="Device.manufacturer"/>
<display value="Device.manufacturer"/>
<relationship value="equivalent"/>
<comment
value="Element `Device.manufacturer` is mapped to FHIR R5 element `Device.manufacturer` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Device.manufactureDate"/>
<display value="manufactureDate"/>
<target>
<code value="Device.manufactureDate"/>
<display value="Device.manufactureDate"/>
<relationship value="equivalent"/>
<comment
value="Element `Device.manufactureDate` is mapped to FHIR R5 element `Device.manufactureDate` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Device.expirationDate"/>
<display value="expirationDate"/>
<target>
<code value="Device.expirationDate"/>
<display value="Device.expirationDate"/>
<relationship value="equivalent"/>
<comment
value="Element `Device.expirationDate` is mapped to FHIR R5 element `Device.expirationDate` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Device.lotNumber"/>
<display value="lotNumber"/>
<target>
<code value="Device.lotNumber"/>
<display value="Device.lotNumber"/>
<relationship value="equivalent"/>
<comment
value="Element `Device.lotNumber` is mapped to FHIR R5 element `Device.lotNumber` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Device.serialNumber"/>
<display value="serialNumber"/>
<target>
<code value="Device.serialNumber"/>
<display value="Device.serialNumber"/>
<relationship value="equivalent"/>
<comment
value="Element `Device.serialNumber` is mapped to FHIR R5 element `Device.serialNumber` as `Equivalent`.
Alphanumeric Maximum 20."/>
</target>
</element>
<element>
<code value="Device.deviceName"/>
<display value="deviceName"/>
<target>
<code value="Device.displayName"/>
<display value="Device.displayName"/>
<relationship value="related-to"/>
<comment
value="Element `Device.deviceName` is mapped to FHIR R5 element `Device.displayName` as `RelatedTo`.
Element `Device.deviceName` is mapped to FHIR R5 element `Device.name` as `Equivalent`."/>
</target>
<target>
<code value="Device.name"/>
<display value="Device.name"/>
<relationship value="related-to"/>
<comment
value="Element `Device.deviceName` is mapped to FHIR R5 element `Device.displayName` as `RelatedTo`.
Element `Device.deviceName` is mapped to FHIR R5 element `Device.name` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Device.deviceName.name"/>
<display value="name"/>
<target>
<code value="Device.name.value"/>
<display value="Device.name.value"/>
<relationship value="equivalent"/>
<comment
value="Element `Device.deviceName.name` is mapped to FHIR R5 element `Device.name.value` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Device.deviceName.type"/>
<display value="type"/>
<target>
<code value="Device.name.type"/>
<display value="Device.name.type"/>
<relationship value="related-to"/>
<comment
value="Element `Device.deviceName.type` is mapped to FHIR R5 element `Device.name.type` as `SourceIsBroaderThanTarget`."/>
</target>
</element>
<element>
<code value="Device.modelNumber"/>
<display value="modelNumber"/>
<target>
<code value="Device.modelNumber"/>
<display value="Device.modelNumber"/>
<relationship value="equivalent"/>
<comment
value="Element `Device.modelNumber` is mapped to FHIR R5 element `Device.modelNumber` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Device.partNumber"/>
<display value="partNumber"/>
<target>
<code value="Device.partNumber"/>
<display value="Device.partNumber"/>
<relationship value="equivalent"/>
<comment
value="Element `Device.partNumber` is mapped to FHIR R5 element `Device.partNumber` as `Equivalent`.
Alphanumeric Maximum 20."/>
</target>
</element>
<element>
<code value="Device.type"/>
<display value="type"/>
<target>
<code value="Device.type"/>
<display value="Device.type"/>
<relationship value="equivalent"/>
<comment
value="Element `Device.type` is mapped to FHIR R5 element `Device.type` as `SourceIsNarrowerThanTarget`."/>
</target>
</element>
<element>
<code value="Device.specialization"/>
<display value="specialization"/>
<target>
<code value="Device.conformsTo"/>
<display value="Device.conformsTo"/>
<relationship value="related-to"/>
<comment
value="Element `Device.specialization` is mapped to FHIR R5 element `Device.conformsTo` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Device.version"/>
<display value="version"/>
<target>
<code value="Device.version"/>
<display value="Device.version"/>
<relationship value="related-to"/>
<comment
value="Element `Device.version` is mapped to FHIR R5 element `Device.version` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Device.version.type"/>
<display value="type"/>
<target>
<code value="Device.version.type"/>
<display value="Device.version.type"/>
<relationship value="equivalent"/>
<comment
value="Element `Device.version.type` is mapped to FHIR R5 element `Device.version.type` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Device.version.component"/>
<display value="component"/>
<target>
<code value="Device.version.component"/>
<display value="Device.version.component"/>
<relationship value="equivalent"/>
<comment
value="Element `Device.version.component` is mapped to FHIR R5 element `Device.version.component` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Device.version.value"/>
<display value="value"/>
<target>
<code value="Device.version.value"/>
<display value="Device.version.value"/>
<relationship value="equivalent"/>
<comment
value="Element `Device.version.value` is mapped to FHIR R5 element `Device.version.value` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Device.property"/>
<display value="property"/>
<target>
<code value="Device.property"/>
<display value="Device.property"/>
<relationship value="related-to"/>
<comment
value="Element `Device.property` is mapped to FHIR R5 element `Device.property` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Device.property.type"/>
<display value="type"/>
<target>
<code value="Device.property.type"/>
<display value="Device.property.type"/>
<relationship value="equivalent"/>
<comment
value="Element `Device.property.type` is mapped to FHIR R5 element `Device.property.type` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Device.owner"/>
<display value="owner"/>
<target>
<code value="Device.owner"/>
<display value="Device.owner"/>
<relationship value="equivalent"/>
<comment
value="Element `Device.owner` is mapped to FHIR R5 element `Device.owner` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Device.contact"/>
<display value="contact"/>
<target>
<code value="Device.contact"/>
<display value="Device.contact"/>
<relationship value="equivalent"/>
<comment
value="Element `Device.contact` is mapped to FHIR R5 element `Device.contact` as `Equivalent`.
used for troubleshooting etc."/>
</target>
</element>
<element>
<code value="Device.location"/>
<display value="location"/>
<target>
<code value="Device.location"/>
<display value="Device.location"/>
<relationship value="equivalent"/>
<comment
value="Element `Device.location` is mapped to FHIR R5 element `Device.location` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Device.url"/>
<display value="url"/>
<target>
<code value="Device.url"/>
<display value="Device.url"/>
<relationship value="equivalent"/>
<comment
value="Element `Device.url` is mapped to FHIR R5 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."/>
</target>
</element>
<element>
<code value="Device.note"/>
<display value="note"/>
<target>
<code value="Device.note"/>
<display value="Device.note"/>
<relationship value="equivalent"/>
<comment
value="Element `Device.note` is mapped to FHIR R5 element `Device.note` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Device.safety"/>
<display value="safety"/>
<target>
<code value="Device.safety"/>
<display value="Device.safety"/>
<relationship value="equivalent"/>
<comment
value="Element `Device.safety` is mapped to FHIR R5 element `Device.safety` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Device.parent"/>
<display value="parent"/>
<target>
<code value="Device.parent"/>
<display value="Device.parent"/>
<relationship value="equivalent"/>
<comment
value="Element `Device.parent` is mapped to FHIR R5 element `Device.parent` as `Equivalent`."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Device|4.3.0"/>
<target
value="http://hl7.org/fhir/StructureDefinition/DeviceAssociation|5.0.0"/>
<element>
<code value="Device.meta"/>
<display value="meta"/>
<target>
<code value="DeviceAssociation.meta"/>
<display value="DeviceAssociation.meta"/>
<relationship value="equivalent"/>
<comment
value="Element `Device.meta` is mapped to FHIR R5 element `Device.meta` as `Equivalent`.
Element `Device.meta` is mapped to FHIR R5 element `DeviceAssociation.meta` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Device.implicitRules"/>
<display value="implicitRules"/>
<target>
<code value="DeviceAssociation.implicitRules"/>
<display value="DeviceAssociation.implicitRules"/>
<relationship value="equivalent"/>
<comment
value="Element `Device.implicitRules` is mapped to FHIR R5 element `Device.implicitRules` as `Equivalent`.
Element `Device.implicitRules` is mapped to FHIR R5 element `DeviceAssociation.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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc."/>
</target>
</element>
<element>
<code value="Device.language"/>
<display value="language"/>
<target>
<code value="DeviceAssociation.language"/>
<display value="DeviceAssociation.language"/>
<relationship value="equivalent"/>
<comment
value="Element `Device.language` is mapped to FHIR R5 element `Device.language` as `Equivalent`.
Element `Device.language` is mapped to FHIR R5 element `DeviceAssociation.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)."/>
</target>
</element>
<element>
<code value="Device.text"/>
<display value="text"/>
<target>
<code value="DeviceAssociation.text"/>
<display value="DeviceAssociation.text"/>
<relationship value="equivalent"/>
<comment
value="Element `Device.text` is mapped to FHIR R5 element `Device.text` as `Equivalent`.
Element `Device.text` is mapped to FHIR R5 element `DeviceAssociation.text` as `Equivalent`.
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 information is added later."/>
</target>
</element>
<element>
<code value="Device.contained"/>
<display value="contained"/>
<target>
<code value="DeviceAssociation.contained"/>
<display value="DeviceAssociation.contained"/>
<relationship value="equivalent"/>
<comment
value="Element `Device.contained` is mapped to FHIR R5 element `Device.contained` as `Equivalent`.
Element `Device.contained` is mapped to FHIR R5 element `DeviceAssociation.contained` as `Equivalent`.
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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels."/>
</target>
</element>
<element>
<code value="Device.identifier"/>
<display value="identifier"/>
<target>
<code value="DeviceAssociation.identifier"/>
<display value="DeviceAssociation.identifier"/>
<relationship value="equivalent"/>
<comment
value="Element `Device.identifier` is mapped to FHIR R5 element `Device.identifier` as `Equivalent`.
Element `Device.identifier` is mapped to FHIR R5 element `DeviceAssociation.identifier` as `Equivalent`.
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."/>
</target>
</element>
<element>
<code value="Device.status"/>
<display value="status"/>
<target>
<code value="DeviceAssociation.status"/>
<display value="DeviceAssociation.status"/>
<relationship value="equivalent"/>
<comment
value="Element `Device.status` is mapped to FHIR R5 element `Device.status` as `SourceIsBroaderThanTarget`.
Element `Device.status` is mapped to FHIR R5 element `DeviceAssociation.status` as `SourceIsNarrowerThanTarget`.
The mappings for `Device.status` do not allow expression of the necessary codes, per the bindings on the source and target.
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."/>
</target>
</element>
<element>
<code value="Device.statusReason"/>
<display value="statusReason"/>
<target>
<code value="DeviceAssociation.statusReason"/>
<display value="DeviceAssociation.statusReason"/>
<relationship value="equivalent"/>
<comment
value="Element `Device.statusReason` is mapped to FHIR R5 element `DeviceAssociation.statusReason` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Device.patient"/>
<display value="patient"/>
<target>
<code value="DeviceAssociation.subject"/>
<display value="DeviceAssociation.subject"/>
<relationship value="equivalent"/>
<comment
value="Element `Device.patient` is mapped to FHIR R5 element `DeviceAssociation.subject` as `SourceIsNarrowerThanTarget`."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Device|4.3.0"/>
<target
value="http://hl7.org/fhir/4.3/StructureDefinition/extension-Device.udiCarrier.entryType|0.1.0"/>
<element>
<code value="Device.udiCarrier.entryType"/>
<display value="entryType"/>
<target>
<code value="Extension"/>
<relationship value="source-is-broader-than-target"/>
<comment
value="Element `Device.udiCarrier.entryType` is mapped to FHIR R5 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."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Device|4.3.0"/>
<target
value="http://hl7.org/fhir/4.3/StructureDefinition/extension-Device.distinctIdentifier|0.1.0"/>
<element>
<code value="Device.distinctIdentifier"/>
<display value="distinctIdentifier"/>
<target>
<code value="Extension"/>
<relationship value="source-is-broader-than-target"/>
<comment
value="Element `Device.distinctIdentifier` has a context of Device based on following the parent source element upwards and mapping to `Device`.
Element `Device.distinctIdentifier` has a context of DeviceAssociation based on following the parent source element upwards and mapping to `DeviceAssociation`.
Element `Device.distinctIdentifier` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
For example, this applies to devices in the United States regulated under *Code of Federal Regulation 21CFR1271.290(c)*."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Device|4.3.0"/>
<target
value="http://hl7.org/fhir/4.3/StructureDefinition/extension-Device.deviceName.type|0.1.0"/>
<element>
<code value="Device.deviceName.type"/>
<display value="type"/>
<target>
<code value="Extension"/>
<relationship value="source-is-broader-than-target"/>
<comment
value="Element `Device.deviceName.type` is mapped to FHIR R5 element `Device.name.type` as `SourceIsBroaderThanTarget`."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Device|4.3.0"/>
<target
value="http://hl7.org/fhir/4.3/StructureDefinition/extension-Device.specialization.systemType|0.1.0"/>
<element>
<code value="Device.specialization.systemType"/>
<display value="systemType"/>
<target>
<code value="Extension"/>
<relationship value="source-is-broader-than-target"/>
<comment
value="Element `Device.specialization.systemType` has a context of Device.conformsTo based on following the parent source element upwards and mapping to `Device`.
Element `Device.specialization.systemType` has a context of DeviceAssociation based on following the parent source element upwards and mapping to `DeviceAssociation`.
Element `Device.specialization.systemType` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Device|4.3.0"/>
<target
value="http://hl7.org/fhir/4.3/StructureDefinition/extension-Device.specialization.version|0.1.0"/>
<element>
<code value="Device.specialization.version"/>
<display value="version"/>
<target>
<code value="Extension"/>
<relationship value="source-is-broader-than-target"/>
<comment
value="Element `Device.specialization.version` has a context of Device.conformsTo based on following the parent source element upwards and mapping to `Device`.
Element `Device.specialization.version` has a context of DeviceAssociation based on following the parent source element upwards and mapping to `DeviceAssociation`.
Element `Device.specialization.version` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Device|4.3.0"/>
<target
value="http://hl7.org/fhir/4.3/StructureDefinition/extension-Device.property.valueQuantity|0.1.0"/>
<element>
<code value="Device.property.valueQuantity"/>
<display value="valueQuantity"/>
<target>
<code value="Extension"/>
<relationship value="source-is-broader-than-target"/>
<comment
value="Element `Device.property.valueQuantity` has a context of Device.property based on following the parent source element upwards and mapping to `Device`.
Element `Device.property.valueQuantity` has a context of DeviceAssociation based on following the parent source element upwards and mapping to `DeviceAssociation`.
Element `Device.property.valueQuantity` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Device|4.3.0"/>
<target
value="http://hl7.org/fhir/4.3/StructureDefinition/extension-Device.property.valueCode|0.1.0"/>
<element>
<code value="Device.property.valueCode"/>
<display value="valueCode"/>
<target>
<code value="Extension"/>
<relationship value="source-is-broader-than-target"/>
<comment
value="Element `Device.property.valueCode` has a context of Device.property based on following the parent source element upwards and mapping to `Device`.
Element `Device.property.valueCode` has a context of DeviceAssociation based on following the parent source element upwards and mapping to `DeviceAssociation`.
Element `Device.property.valueCode` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
</ConceptMap>
IG © 2025+ FHIR Infrastructure. Package hl7.fhir.uv.xver-r4b.r5#0.1.0 based on FHIR 5.0.0. Generated 2026-03-20
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change