Extensions for Using Data Elements from FHIR R5 in FHIR R4
0.1.0 - STU
Extensions for Using Data Elements from FHIR R5 in FHIR R4
0.1.0 - STU
Extensions for Using Data Elements from FHIR R5 in FHIR R4 - 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="R5-Device-element-map-to-R4"/>
<text>
<status value="generated"/>
<div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: ConceptMap R5-Device-element-map-to-R4</b></p><a name="R5-Device-element-map-to-R4"> </a><a name="hcR5-Device-element-map-to-R4"> </a><p>Mapping from http://hl7.org/fhir/5.0 to http://hl7.org/fhir/4.0</p><br/><p><b>Group 1 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Device|5.0.0</code> to <a href="http://hl7.org/fhir/R4/device.html">Deviceversion: 4.0.1)</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|5.0.0</td><td/><td colspan="2" title="http://hl7.org/fhir/StructureDefinition/Device|4.0.1"><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="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 R4 element `Device.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="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 R4 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its 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="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 R4 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).</td></tr><tr><td style="border-right-width: 0px">Device.text</td><td style="border-left-width: 0px">text</td><td><a href="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 R4 element `Device.text` as `Equivalent`.
Contained resources do not have a 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="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 R4 element `Device.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="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 R4 element `Device.identifier` as `Equivalent`.
Certain attributes, like serial number and UDI Carrier (the HRF or AIDC barcode string) are not device instance identifiers as they are not consistently able to uniquely identify the instance of a device, thus are not appropriate to be used to value Device.identifier. 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. The identifier is typically valued if the serialNumber or lotNumber is not valued and represents a different type of identifier. However, it is permissible to still include those identifiers in DeviceDefinition.identifier with the appropriate identifier.type.</td></tr><tr><td style="border-right-width: 0px">Device.displayName</td><td style="border-left-width: 0px">displayName</td><td><a href="CodeSystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td style="border-right-width: 0px">Device.deviceName</td><td style="border-left-width: 0px">Device.deviceName</td><td>Element `Device.displayName` is mapped to FHIR R4 element `Device.deviceName` as `RelatedTo`.
The mappings for `Device.displayName` do not cover the following types: string.
The mappings for `Device.displayName` do not cover the following types based on type expansion: value.</td></tr><tr><td style="border-right-width: 0px">Device.definition</td><td style="border-left-width: 0px">definition</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</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 R4 element `Device.definition` as `SourceIsBroaderThanTarget`.
The mappings for `Device.definition` do not cover the following types: CodeableReference.
The mappings for `Device.definition` do not cover the following types based on type expansion: concept.</td></tr><tr><td style="border-right-width: 0px">Device.udiCarrier</td><td style="border-left-width: 0px">udiCarrier</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</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 R4 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="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 R4 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="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 R4 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="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 R4 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="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 R4 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="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 R4 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="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</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 R4 element `Device.udiCarrier.entryType` as `RelatedTo`.
The mappings for `Device.udiCarrier.entryType` do not allow expression of the necessary codes, per the bindings on the source and target.</td></tr><tr><td style="border-right-width: 0px">Device.status</td><td style="border-left-width: 0px">status</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent 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 R4 element `Device.status` as `SourceIsNarrowerThanTarget`.
The mappings for `Device.status` do not allow expression of the necessary codes, per the bindings on the source and target.</td></tr><tr><td style="border-right-width: 0px">Device.manufacturer</td><td style="border-left-width: 0px">manufacturer</td><td><a href="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 R4 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="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 R4 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="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 R4 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="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 R4 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="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 R4 element `Device.serialNumber` as `Equivalent`.
Alphanumeric Maximum 20. While a serial number is a type of identifier, in the context of devices for which a UDI is required, thus a serial number may be part of the production identifier, it is more informative to have the serial number as a dedicated attribute together with the other UDI production identifier. When the device is not subject to including the UDI (e.g., its presence and exchange is not mandated by local regulatory requirements or specific use case at hand), thus the concept of production identifiers is not relevant as a set, it remains helpful for consistency to still use Device.serialNumber rather than using Device.identifier with an appropriate type. Systems that do not realize an identifier is a serial number may place it in Device.identifier or if the identifier.system is known for the serial number, it may also be populated in the Device.identifier as a globally unique id_.</td></tr><tr><td style="border-right-width: 0px">Device.name</td><td style="border-left-width: 0px">name</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">Device.deviceName</td><td style="border-left-width: 0px">Device.deviceName</td><td>Element `Device.name` is mapped to FHIR R4 element `Device.deviceName` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px; border-bottom-style: none">Device.name.value</td><td style="border-left-width: 0px; border-bottom-style: none">value</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">Device.deviceName</td><td style="border-left-width: 0px">Device.deviceName</td><td>Element `Device.name.value` is mapped to FHIR R4 element `Device.deviceName.name` as `Equivalent`.
Element `Device.name.value` is mapped to FHIR R4 element `Device.deviceName` as `SourceIsNarrowerThanTarget`.</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="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">Device.deviceName.name</td><td style="border-left-width: 0px">Device.deviceName.name</td><td>Element `Device.name.value` is mapped to FHIR R4 element `Device.deviceName.name` as `Equivalent`.
Element `Device.name.value` is mapped to FHIR R4 element `Device.deviceName` as `SourceIsNarrowerThanTarget`.</td></tr><tr><td style="border-right-width: 0px">Device.name.type</td><td style="border-left-width: 0px">type</td><td><a href="CodeSystem-concept-map-relationship.html#narrower" title="narrower">narrower</a></td><td style="border-right-width: 0px">Device.deviceName.type</td><td style="border-left-width: 0px">Device.deviceName.type</td><td>Element `Device.name.type` is mapped to FHIR R4 element `Device.deviceName.type` as `SourceIsNarrowerThanTarget`.
The mappings for `Device.name.type` do not allow expression of the necessary codes, per the bindings on the source and target.</td></tr><tr><td style="border-right-width: 0px">Device.name.display</td><td style="border-left-width: 0px">display</td><td><a href="CodeSystem-concept-map-relationship.html#narrower" title="narrower">narrower</a></td><td style="border-right-width: 0px">Device.deviceName</td><td style="border-left-width: 0px">Device.deviceName</td><td>Element `Device.name.display` is mapped to FHIR R4 element `Device.deviceName` as `SourceIsNarrowerThanTarget`.</td></tr><tr><td style="border-right-width: 0px">Device.modelNumber</td><td style="border-left-width: 0px">modelNumber</td><td><a href="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 R4 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="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 R4 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="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 R4 element `Device.type` as `SourceIsBroaderThanTarget`.
Multiple device types are use when a device is categorized in more than one context – for example, hybrid devices in which the device is both of type gateway and sensor.</td></tr><tr><td style="border-right-width: 0px">Device.version</td><td style="border-left-width: 0px">version</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</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 R4 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="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 R4 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="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 R4 element `Device.version.component` as `Equivalent`.
Note that the module of the device would not need to be tracked as a separate device, e.g., using different UDI, thus would typically involve one or more software modules. For example, a device may involve two software modules each on a different version.</td></tr><tr><td style="border-right-width: 0px">Device.version.value</td><td style="border-left-width: 0px">value</td><td><a href="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 R4 element `Device.version.value` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">Device.conformsTo</td><td style="border-left-width: 0px">conformsTo</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">Device.specialization</td><td style="border-left-width: 0px">Device.specialization</td><td>Element `Device.conformsTo` is mapped to FHIR R4 element `Device.specialization` as `Equivalent`.
An externally-defined extension that has been mapped as the representation of FHIR R5 element `Device.conformsTo`: `http://hl7.org/fhir/StructureDefinition/device-conformsTo`.</td></tr><tr><td style="border-right-width: 0px">Device.conformsTo.category</td><td style="border-left-width: 0px">category</td><td><a href="CodeSystem-concept-map-relationship.html#narrower" title="narrower">narrower</a></td><td style="border-right-width: 0px">Device.specialization</td><td style="border-left-width: 0px">Device.specialization</td><td>Element `Device.conformsTo.category` is mapped to FHIR R4 element `Device.specialization` as `SourceIsNarrowerThanTarget`.</td></tr><tr><td style="border-right-width: 0px">Device.conformsTo.specification</td><td style="border-left-width: 0px">specification</td><td><a href="CodeSystem-concept-map-relationship.html#narrower" title="narrower">narrower</a></td><td style="border-right-width: 0px">Device.specialization</td><td style="border-left-width: 0px">Device.specialization</td><td>Element `Device.conformsTo.specification` is mapped to FHIR R4 element `Device.specialization` as `SourceIsNarrowerThanTarget`.</td></tr><tr><td style="border-right-width: 0px">Device.property</td><td style="border-left-width: 0px">property</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</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 R4 element `Device.property` as `Equivalent`.
Dynamic or current properties, such as settings, of an individual device are described using a Device instance-specific [DeviceMetric] and recorded using [Observation]. Static characteristics of a device could also be documented in an associated [DeviceDefinition] instance. The Device instance's properties, and their values, could be, but need not be, the same as those described in an associated DeviceDefinition.</td></tr><tr><td style="border-right-width: 0px">Device.property.type</td><td style="border-left-width: 0px">type</td><td><a href="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 R4 element `Device.property.type` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px; border-bottom-style: none">Device.property.value[x]</td><td style="border-left-width: 0px; border-bottom-style: none">value[x]</td><td><a href="CodeSystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td style="border-right-width: 0px">Device.property.valueCode</td><td style="border-left-width: 0px">Device.property.valueCode</td><td>Element `Device.property.value[x]` is mapped to FHIR R4 element `Device.property.valueQuantity` as `RelatedTo`.
Element `Device.property.value[x]` is mapped to FHIR R4 element `Device.property.valueCode` as `RelatedTo`.
The mappings for `Device.property.value[x]` do not cover the following types: Attachment, boolean, integer, Range, string.
The text element in CodeableConcept.text is used for properties which would usually be coded (such as the size of an implant, or a security classification) but for which there is not currently an appropriate concept in the vocabulary (e.g. a custom implant size, or a security classification which depends on configuration). Otherwise the string choice type is used for descriptive properties, or instructions.</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="CodeSystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td style="border-right-width: 0px">Device.property.valueQuantity</td><td style="border-left-width: 0px">Device.property.valueQuantity</td><td>Element `Device.property.value[x]` is mapped to FHIR R4 element `Device.property.valueQuantity` as `RelatedTo`.
Element `Device.property.value[x]` is mapped to FHIR R4 element `Device.property.valueCode` as `RelatedTo`.
The mappings for `Device.property.value[x]` do not cover the following types: Attachment, boolean, integer, Range, string.
The text element in CodeableConcept.text is used for properties which would usually be coded (such as the size of an implant, or a security classification) but for which there is not currently an appropriate concept in the vocabulary (e.g. a custom implant size, or a security classification which depends on configuration). Otherwise the string choice type is used for descriptive properties, or instructions.</td></tr><tr><td style="border-right-width: 0px">Device.owner</td><td style="border-left-width: 0px">owner</td><td><a href="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 R4 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="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 R4 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="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 R4 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="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 R4 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="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 R4 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="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 R4 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="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 R4 element `Device.parent` as `Equivalent`.
For example a vital signs monitor (parent) where three separate modules can be plugged into such as interchangeable blood pressure, oximeter, temperature modules. These modules are represented as devices with the .parent valued to the vital signs monitor when plugged in.</td></tr></table><hr/><p><b>Group 2 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Device|5.0.0</code> to <a href="StructureDefinition-ext-R5-Device.displayName.html">R5: The name used to display by default when the device is referenced additional typesversion: 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.displayName (displayName)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: The name used to display by default when the device is referenced additional types)</td><td>Element `Device.displayName` is mapped to FHIR R4 element `Device.deviceName` as `RelatedTo`.
The mappings for `Device.displayName` do not cover the following types: string.
The mappings for `Device.displayName` do not cover the following types based on type expansion: value.</td></tr></table><hr/><p><b>Group 3 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Device|5.0.0</code> to <a href="StructureDefinition-ext-R5-Device.definition.html">R5: definition additional typesversion: 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.definition (definition)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (R5: definition additional types)</td><td>Element `Device.definition` is mapped to FHIR R4 element `Device.definition` as `SourceIsBroaderThanTarget`.
The mappings for `Device.definition` do not cover the following types: CodeableReference.
The mappings for `Device.definition` do not cover the following types based on type expansion: concept.</td></tr></table><hr/><p><b>Group 4 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Device|5.0.0</code> to <a href="StructureDefinition-ext-R5-Device.udi.entryType.html">R5: barcode | rfid | manual | card | self-reported | electronic-transmission | unknown 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="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (R5: barcode | rfid | manual | card | self-reported | electronic-transmission | unknown additional codes)</td><td>Element `Device.udiCarrier.entryType` is mapped to FHIR R4 element `Device.udiCarrier.entryType` as `RelatedTo`.
The mappings for `Device.udiCarrier.entryType` do not allow expression of the necessary codes, per the bindings on the source and target.</td></tr></table><hr/><p><b>Group 5 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Device|5.0.0</code> to <a href="StructureDefinition-ext-R5-Device.availabilityStatus.html">R5: lost | damaged | destroyed | available (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.availabilityStatus (availabilityStatus)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: lost | damaged | destroyed | available (new))</td><td>Element `Device.availabilityStatus` has a context of Device based on following the parent source element upwards and mapping to `Device`.
Element `Device.availabilityStatus` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 6 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Device|5.0.0</code> to <a href="StructureDefinition-ext-R5-Device.biologicalSourceEvent.html">R5: An identifier that supports traceability to the event during which material in this product from one or more biological entities was obtained or pooled (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.biologicalSourceEvent (biologicalSourceEvent)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: An identifier that supports traceability to the event during which material in this product from one or more biological entities was obtained or pooled (new))</td><td>Element `Device.biologicalSourceEvent` has a context of Device based on following the parent source element upwards and mapping to `Device`.
Element `Device.biologicalSourceEvent` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Necessary to support mandatory requirements for traceability from donor/source to recipient and vice versa, while also satisfying donor anonymity requirements. The element is defined consistently across BiologicallyDerivedProduct, NutritionProduct, and Device. The identifier references an event that links to a single biological entity such as a blood donor, or to multiple biological entities (e.g. when the product is an embryo or a pooled platelet product). A single biologicalSourceEvent identifier may appear on multiple products of many types derived from a single donation event or source extraction. As an example, a single donation event may provide 2 kidneys and a liver for organ transplantation, 2 corneas for eye surgery, heart valves and arterial tissue for cardiovascular surgery, multiple skin grafts, tendons, multiple shaped bone grafts and a large number of bone putty/paste products; and each of them may be assigned to the same biological source event identifier.</td></tr></table><hr/><p><b>Group 7 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Device|5.0.0</code> to <a href="StructureDefinition-ext-R5-Device.category.html">R5: Indicates a high-level grouping of the device (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.category (category)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: Indicates a high-level grouping of the device (new))</td><td>Element `Device.category` has a context of Device based on following the parent source element upwards and mapping to `Device`.
Element `Device.category` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 8 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Device|5.0.0</code> to <a href="StructureDefinition-ext-R5-Device.ver.installDate.html">R5: The date the version was installed on the device (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.version.installDate (installDate)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: The date the version was installed on the device (new))</td><td>Element `Device.version.installDate` has a context of Device.version based on following the parent source element upwards and mapping to `Device`.
Element `Device.version.installDate` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 9 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Device|5.0.0</code> to <a href="StructureDefinition-ext-R5-Device.con.version.html">R5: Specific form or variant of the standard (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.conformsTo.version (version)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: Specific form or variant of the standard (new))</td><td>Element `Device.conformsTo.version` has a context of Device.specialization based on following the parent source element upwards and mapping to `Device`.
Element `Device.conformsTo.version` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 10 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Device|5.0.0</code> to <a href="StructureDefinition-ext-R5-Device.pro.value.html">R5: Value of the property additional typesversion: 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.value[x] (value[x])</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: Value of the property additional types)</td><td>Element `Device.property.value[x]` is mapped to FHIR R4 element `Device.property.valueQuantity` as `RelatedTo`.
Element `Device.property.value[x]` is mapped to FHIR R4 element `Device.property.valueCode` as `RelatedTo`.
The mappings for `Device.property.value[x]` do not cover the following types: Attachment, boolean, integer, Range, string.
The text element in CodeableConcept.text is used for properties which would usually be coded (such as the size of an implant, or a security classification) but for which there is not currently an appropriate concept in the vocabulary (e.g. a custom implant size, or a security classification which depends on configuration). Otherwise the string choice type is used for descriptive properties, or instructions.</td></tr></table><hr/><p><b>Group 11 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Device|5.0.0</code> to <a href="StructureDefinition-ext-R5-Device.mode.html">R5: The designated condition for performing a task (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.mode (mode)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: The designated condition for performing a task (new))</td><td>Element `Device.mode` has a context of Device based on following the parent source element upwards and mapping to `Device`.
Element `Device.mode` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 12 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Device|5.0.0</code> to <a href="StructureDefinition-ext-R5-Device.cycle.html">R5: The series of occurrences that repeats during the operation of the device (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.cycle (cycle)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: The series of occurrences that repeats during the operation of the device (new))</td><td>Element `Device.cycle` has a context of Device based on following the parent source element upwards and mapping to `Device`.
Element `Device.cycle` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 13 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Device|5.0.0</code> to <a href="StructureDefinition-ext-R5-Device.duration.html">R5: A measurement of time during the device's operation (e.g., days, hours, mins, etc.) (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.duration (duration)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: A measurement of time during the device's operation (e.g., days, hours, mins, etc.) (new))</td><td>Element `Device.duration` has a context of Device based on following the parent source element upwards and mapping to `Device`.
Element `Device.duration` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 14 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Device|5.0.0</code> to <a href="StructureDefinition-ext-R5-Device.endpoint.html">R5: Technical endpoints providing access to electronic services provided by the device (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.endpoint (endpoint)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: Technical endpoints providing access to electronic services provided by the device (new))</td><td>Element `Device.endpoint` has a context of Device based on following the parent source element upwards and mapping to `Device`.
Element `Device.endpoint` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 15 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Device|5.0.0</code> to <a href="StructureDefinition-ext-R5-Device.gateway.html">R5: Linked device acting as a communication/data collector, translator or controller (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.gateway (gateway)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: Linked device acting as a communication/data collector, translator or controller (new))</td><td>Element `Device.gateway` has a context of Device based on following the parent source element upwards and mapping to `Device`.
Element `Device.gateway` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
The Device.gateway may be used when the Device being referenced has a gateway and/or to capture one or more gateways associated with the device. If the Gateway is included in the Observation resource, the Observation.gatewayDevice should be used instead.</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-r5.r4"/>
</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-r5.r4"/>
</extension>
</valueCode>
</extension>
<url
value="http://hl7.org/fhir/uv/xver/ConceptMap/R5-Device-element-map-to-R4"/>
<version value="0.1.0"/>
<name value="R5DeviceElementMapToR4"/>
<title value="Cross-version mapping for FHIR R5 Device to FHIR R4 Device"/>
<status value="active"/>
<experimental value="false"/>
<date value="2026-03-17T16:04:44.9538459-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 R5 Device to FHIR R4."/>
<jurisdiction>
<coding>
<system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
<code value="001"/>
<display value="World"/>
</coding>
</jurisdiction>
<sourceCanonical value="http://hl7.org/fhir/5.0"/>
<targetUri value="http://hl7.org/fhir/4.0"/>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Device"/>
<sourceVersion value="5.0.0"/>
<target value="http://hl7.org/fhir/StructureDefinition/Device"/>
<targetVersion value="4.0.1"/>
<element>
<code value="Device.meta"/>
<display value="meta"/>
<target>
<code value="Device.meta"/>
<display value="Device.meta"/>
<equivalence value="equivalent"/>
<comment
value="Element `Device.meta` is mapped to FHIR R4 element `Device.meta` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Device.implicitRules"/>
<display value="implicitRules"/>
<target>
<code value="Device.implicitRules"/>
<display value="Device.implicitRules"/>
<equivalence value="equivalent"/>
<comment
value="Element `Device.implicitRules` is mapped to FHIR R4 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its 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"/>
<equivalence value="equivalent"/>
<comment
value="Element `Device.language` is mapped to FHIR R4 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)."/>
</target>
</element>
<element>
<code value="Device.text"/>
<display value="text"/>
<target>
<code value="Device.text"/>
<display value="Device.text"/>
<equivalence value="equivalent"/>
<comment
value="Element `Device.text` is mapped to FHIR R4 element `Device.text` as `Equivalent`.
Contained resources do not have a 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"/>
<equivalence value="equivalent"/>
<comment
value="Element `Device.contained` is mapped to FHIR R4 element `Device.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"/>
<equivalence value="equivalent"/>
<comment
value="Element `Device.identifier` is mapped to FHIR R4 element `Device.identifier` as `Equivalent`.
Certain attributes, like serial number and UDI Carrier (the HRF or AIDC barcode string) are not device instance identifiers as they are not consistently able to uniquely identify the instance of a device, thus are not appropriate to be used to value Device.identifier. 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. The identifier is typically valued if the serialNumber or lotNumber is not valued and represents a different type of identifier. However, it is permissible to still include those identifiers in DeviceDefinition.identifier with the appropriate identifier.type."/>
</target>
</element>
<element>
<code value="Device.displayName"/>
<display value="displayName"/>
<target>
<code value="Device.deviceName"/>
<display value="Device.deviceName"/>
<equivalence value="relatedto"/>
<comment
value="Element `Device.displayName` is mapped to FHIR R4 element `Device.deviceName` as `RelatedTo`.
The mappings for `Device.displayName` do not cover the following types: string.
The mappings for `Device.displayName` do not cover the following types based on type expansion: value."/>
</target>
</element>
<element>
<code value="Device.definition"/>
<display value="definition"/>
<target>
<code value="Device.definition"/>
<display value="Device.definition"/>
<equivalence value="wider"/>
<comment
value="Element `Device.definition` is mapped to FHIR R4 element `Device.definition` as `SourceIsBroaderThanTarget`.
The mappings for `Device.definition` do not cover the following types: CodeableReference.
The mappings for `Device.definition` do not cover the following types based on type expansion: concept."/>
</target>
</element>
<element>
<code value="Device.udiCarrier"/>
<display value="udiCarrier"/>
<target>
<code value="Device.udiCarrier"/>
<display value="Device.udiCarrier"/>
<equivalence value="wider"/>
<comment
value="Element `Device.udiCarrier` is mapped to FHIR R4 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"/>
<equivalence value="equivalent"/>
<comment
value="Element `Device.udiCarrier.deviceIdentifier` is mapped to FHIR R4 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"/>
<equivalence value="equivalent"/>
<comment
value="Element `Device.udiCarrier.issuer` is mapped to FHIR R4 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"/>
<equivalence value="equivalent"/>
<comment
value="Element `Device.udiCarrier.jurisdiction` is mapped to FHIR R4 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"/>
<equivalence value="equivalent"/>
<comment
value="Element `Device.udiCarrier.carrierAIDC` is mapped to FHIR R4 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"/>
<equivalence value="equivalent"/>
<comment
value="Element `Device.udiCarrier.carrierHRF` is mapped to FHIR R4 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"/>
<equivalence value="wider"/>
<comment
value="Element `Device.udiCarrier.entryType` is mapped to FHIR R4 element `Device.udiCarrier.entryType` as `RelatedTo`.
The mappings for `Device.udiCarrier.entryType` do not allow expression of the necessary codes, per the bindings on the source and target."/>
</target>
</element>
<element>
<code value="Device.status"/>
<display value="status"/>
<target>
<code value="Device.status"/>
<display value="Device.status"/>
<equivalence value="equivalent"/>
<comment
value="Element `Device.status` is mapped to FHIR R4 element `Device.status` as `SourceIsNarrowerThanTarget`.
The mappings for `Device.status` do not allow expression of the necessary codes, per the bindings on the source and target."/>
</target>
</element>
<element>
<code value="Device.manufacturer"/>
<display value="manufacturer"/>
<target>
<code value="Device.manufacturer"/>
<display value="Device.manufacturer"/>
<equivalence value="equivalent"/>
<comment
value="Element `Device.manufacturer` is mapped to FHIR R4 element `Device.manufacturer` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Device.manufactureDate"/>
<display value="manufactureDate"/>
<target>
<code value="Device.manufactureDate"/>
<display value="Device.manufactureDate"/>
<equivalence value="equivalent"/>
<comment
value="Element `Device.manufactureDate` is mapped to FHIR R4 element `Device.manufactureDate` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Device.expirationDate"/>
<display value="expirationDate"/>
<target>
<code value="Device.expirationDate"/>
<display value="Device.expirationDate"/>
<equivalence value="equivalent"/>
<comment
value="Element `Device.expirationDate` is mapped to FHIR R4 element `Device.expirationDate` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Device.lotNumber"/>
<display value="lotNumber"/>
<target>
<code value="Device.lotNumber"/>
<display value="Device.lotNumber"/>
<equivalence value="equivalent"/>
<comment
value="Element `Device.lotNumber` is mapped to FHIR R4 element `Device.lotNumber` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Device.serialNumber"/>
<display value="serialNumber"/>
<target>
<code value="Device.serialNumber"/>
<display value="Device.serialNumber"/>
<equivalence value="equivalent"/>
<comment
value="Element `Device.serialNumber` is mapped to FHIR R4 element `Device.serialNumber` as `Equivalent`.
Alphanumeric Maximum 20. While a serial number is a type of identifier, in the context of devices for which a UDI is required, thus a serial number may be part of the production identifier, it is more informative to have the serial number as a dedicated attribute together with the other UDI production identifier. When the device is not subject to including the UDI (e.g., its presence and exchange is not mandated by local regulatory requirements or specific use case at hand), thus the concept of production identifiers is not relevant as a set, it remains helpful for consistency to still use Device.serialNumber rather than using Device.identifier with an appropriate type. Systems that do not realize an identifier is a serial number may place it in Device.identifier or if the identifier.system is known for the serial number, it may also be populated in the Device.identifier as a globally unique id_."/>
</target>
</element>
<element>
<code value="Device.name"/>
<display value="name"/>
<target>
<code value="Device.deviceName"/>
<display value="Device.deviceName"/>
<equivalence value="wider"/>
<comment
value="Element `Device.name` is mapped to FHIR R4 element `Device.deviceName` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Device.name.value"/>
<display value="value"/>
<target>
<code value="Device.deviceName"/>
<display value="Device.deviceName"/>
<equivalence value="equivalent"/>
<comment
value="Element `Device.name.value` is mapped to FHIR R4 element `Device.deviceName.name` as `Equivalent`.
Element `Device.name.value` is mapped to FHIR R4 element `Device.deviceName` as `SourceIsNarrowerThanTarget`."/>
</target>
<target>
<code value="Device.deviceName.name"/>
<display value="Device.deviceName.name"/>
<equivalence value="equivalent"/>
<comment
value="Element `Device.name.value` is mapped to FHIR R4 element `Device.deviceName.name` as `Equivalent`.
Element `Device.name.value` is mapped to FHIR R4 element `Device.deviceName` as `SourceIsNarrowerThanTarget`."/>
</target>
</element>
<element>
<code value="Device.name.type"/>
<display value="type"/>
<target>
<code value="Device.deviceName.type"/>
<display value="Device.deviceName.type"/>
<equivalence value="narrower"/>
<comment
value="Element `Device.name.type` is mapped to FHIR R4 element `Device.deviceName.type` as `SourceIsNarrowerThanTarget`.
The mappings for `Device.name.type` do not allow expression of the necessary codes, per the bindings on the source and target."/>
</target>
</element>
<element>
<code value="Device.name.display"/>
<display value="display"/>
<target>
<code value="Device.deviceName"/>
<display value="Device.deviceName"/>
<equivalence value="narrower"/>
<comment
value="Element `Device.name.display` is mapped to FHIR R4 element `Device.deviceName` as `SourceIsNarrowerThanTarget`."/>
</target>
</element>
<element>
<code value="Device.modelNumber"/>
<display value="modelNumber"/>
<target>
<code value="Device.modelNumber"/>
<display value="Device.modelNumber"/>
<equivalence value="equivalent"/>
<comment
value="Element `Device.modelNumber` is mapped to FHIR R4 element `Device.modelNumber` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Device.partNumber"/>
<display value="partNumber"/>
<target>
<code value="Device.partNumber"/>
<display value="Device.partNumber"/>
<equivalence value="equivalent"/>
<comment
value="Element `Device.partNumber` is mapped to FHIR R4 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"/>
<equivalence value="equivalent"/>
<comment
value="Element `Device.type` is mapped to FHIR R4 element `Device.type` as `SourceIsBroaderThanTarget`.
Multiple device types are use when a device is categorized in more than one context – for example, hybrid devices in which the device is both of type gateway and sensor."/>
</target>
</element>
<element>
<code value="Device.version"/>
<display value="version"/>
<target>
<code value="Device.version"/>
<display value="Device.version"/>
<equivalence value="wider"/>
<comment
value="Element `Device.version` is mapped to FHIR R4 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"/>
<equivalence value="equivalent"/>
<comment
value="Element `Device.version.type` is mapped to FHIR R4 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"/>
<equivalence value="equivalent"/>
<comment
value="Element `Device.version.component` is mapped to FHIR R4 element `Device.version.component` as `Equivalent`.
Note that the module of the device would not need to be tracked as a separate device, e.g., using different UDI, thus would typically involve one or more software modules. For example, a device may involve two software modules each on a different version."/>
</target>
</element>
<element>
<code value="Device.version.value"/>
<display value="value"/>
<target>
<code value="Device.version.value"/>
<display value="Device.version.value"/>
<equivalence value="equivalent"/>
<comment
value="Element `Device.version.value` is mapped to FHIR R4 element `Device.version.value` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Device.conformsTo"/>
<display value="conformsTo"/>
<target>
<code value="Device.specialization"/>
<display value="Device.specialization"/>
<equivalence value="wider"/>
<comment
value="Element `Device.conformsTo` is mapped to FHIR R4 element `Device.specialization` as `Equivalent`.
An externally-defined extension that has been mapped as the representation of FHIR R5 element `Device.conformsTo`: `http://hl7.org/fhir/StructureDefinition/device-conformsTo`."/>
</target>
</element>
<element>
<code value="Device.conformsTo.category"/>
<display value="category"/>
<target>
<code value="Device.specialization"/>
<display value="Device.specialization"/>
<equivalence value="narrower"/>
<comment
value="Element `Device.conformsTo.category` is mapped to FHIR R4 element `Device.specialization` as `SourceIsNarrowerThanTarget`."/>
</target>
</element>
<element>
<code value="Device.conformsTo.specification"/>
<display value="specification"/>
<target>
<code value="Device.specialization"/>
<display value="Device.specialization"/>
<equivalence value="narrower"/>
<comment
value="Element `Device.conformsTo.specification` is mapped to FHIR R4 element `Device.specialization` as `SourceIsNarrowerThanTarget`."/>
</target>
</element>
<element>
<code value="Device.property"/>
<display value="property"/>
<target>
<code value="Device.property"/>
<display value="Device.property"/>
<equivalence value="wider"/>
<comment
value="Element `Device.property` is mapped to FHIR R4 element `Device.property` as `Equivalent`.
Dynamic or current properties, such as settings, of an individual device are described using a Device instance-specific [DeviceMetric] and recorded using [Observation]. Static characteristics of a device could also be documented in an associated [DeviceDefinition] instance. The Device instance's properties, and their values, could be, but need not be, the same as those described in an associated DeviceDefinition."/>
</target>
</element>
<element>
<code value="Device.property.type"/>
<display value="type"/>
<target>
<code value="Device.property.type"/>
<display value="Device.property.type"/>
<equivalence value="equivalent"/>
<comment
value="Element `Device.property.type` is mapped to FHIR R4 element `Device.property.type` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Device.property.value[x]"/>
<display value="value[x]"/>
<target>
<code value="Device.property.valueCode"/>
<display value="Device.property.valueCode"/>
<equivalence value="relatedto"/>
<comment
value="Element `Device.property.value[x]` is mapped to FHIR R4 element `Device.property.valueQuantity` as `RelatedTo`.
Element `Device.property.value[x]` is mapped to FHIR R4 element `Device.property.valueCode` as `RelatedTo`.
The mappings for `Device.property.value[x]` do not cover the following types: Attachment, boolean, integer, Range, string.
The text element in CodeableConcept.text is used for properties which would usually be coded (such as the size of an implant, or a security classification) but for which there is not currently an appropriate concept in the vocabulary (e.g. a custom implant size, or a security classification which depends on configuration). Otherwise the string choice type is used for descriptive properties, or instructions."/>
</target>
<target>
<code value="Device.property.valueQuantity"/>
<display value="Device.property.valueQuantity"/>
<equivalence value="relatedto"/>
<comment
value="Element `Device.property.value[x]` is mapped to FHIR R4 element `Device.property.valueQuantity` as `RelatedTo`.
Element `Device.property.value[x]` is mapped to FHIR R4 element `Device.property.valueCode` as `RelatedTo`.
The mappings for `Device.property.value[x]` do not cover the following types: Attachment, boolean, integer, Range, string.
The text element in CodeableConcept.text is used for properties which would usually be coded (such as the size of an implant, or a security classification) but for which there is not currently an appropriate concept in the vocabulary (e.g. a custom implant size, or a security classification which depends on configuration). Otherwise the string choice type is used for descriptive properties, or instructions."/>
</target>
</element>
<element>
<code value="Device.owner"/>
<display value="owner"/>
<target>
<code value="Device.owner"/>
<display value="Device.owner"/>
<equivalence value="equivalent"/>
<comment
value="Element `Device.owner` is mapped to FHIR R4 element `Device.owner` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Device.contact"/>
<display value="contact"/>
<target>
<code value="Device.contact"/>
<display value="Device.contact"/>
<equivalence value="equivalent"/>
<comment
value="Element `Device.contact` is mapped to FHIR R4 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"/>
<equivalence value="equivalent"/>
<comment
value="Element `Device.location` is mapped to FHIR R4 element `Device.location` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Device.url"/>
<display value="url"/>
<target>
<code value="Device.url"/>
<display value="Device.url"/>
<equivalence value="equivalent"/>
<comment
value="Element `Device.url` is mapped to FHIR R4 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"/>
<equivalence value="equivalent"/>
<comment
value="Element `Device.note` is mapped to FHIR R4 element `Device.note` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Device.safety"/>
<display value="safety"/>
<target>
<code value="Device.safety"/>
<display value="Device.safety"/>
<equivalence value="equivalent"/>
<comment
value="Element `Device.safety` is mapped to FHIR R4 element `Device.safety` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Device.parent"/>
<display value="parent"/>
<target>
<code value="Device.parent"/>
<display value="Device.parent"/>
<equivalence value="equivalent"/>
<comment
value="Element `Device.parent` is mapped to FHIR R4 element `Device.parent` as `Equivalent`.
For example a vital signs monitor (parent) where three separate modules can be plugged into such as interchangeable blood pressure, oximeter, temperature modules. These modules are represented as devices with the .parent valued to the vital signs monitor when plugged in."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Device"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.displayName"/>
<targetVersion value="0.1.0"/>
<element>
<code value="Device.displayName"/>
<display value="displayName"/>
<target>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `Device.displayName` is mapped to FHIR R4 element `Device.deviceName` as `RelatedTo`.
The mappings for `Device.displayName` do not cover the following types: string.
The mappings for `Device.displayName` do not cover the following types based on type expansion: value."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Device"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.definition"/>
<targetVersion value="0.1.0"/>
<element>
<code value="Device.definition"/>
<display value="definition"/>
<target>
<code value="Extension"/>
<equivalence value="equivalent"/>
<comment
value="Element `Device.definition` is mapped to FHIR R4 element `Device.definition` as `SourceIsBroaderThanTarget`.
The mappings for `Device.definition` do not cover the following types: CodeableReference.
The mappings for `Device.definition` do not cover the following types based on type expansion: concept."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Device"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.udiCarrier.entryType"/>
<targetVersion value="0.1.0"/>
<element>
<code value="Device.udiCarrier.entryType"/>
<display value="entryType"/>
<target>
<code value="Extension"/>
<equivalence value="equivalent"/>
<comment
value="Element `Device.udiCarrier.entryType` is mapped to FHIR R4 element `Device.udiCarrier.entryType` as `RelatedTo`.
The mappings for `Device.udiCarrier.entryType` do not allow expression of the necessary codes, per the bindings on the source and target."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Device"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.availabilityStatus"/>
<targetVersion value="0.1.0"/>
<element>
<code value="Device.availabilityStatus"/>
<display value="availabilityStatus"/>
<target>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `Device.availabilityStatus` has a context of Device based on following the parent source element upwards and mapping to `Device`.
Element `Device.availabilityStatus` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Device"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.biologicalSourceEvent"/>
<targetVersion value="0.1.0"/>
<element>
<code value="Device.biologicalSourceEvent"/>
<display value="biologicalSourceEvent"/>
<target>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `Device.biologicalSourceEvent` has a context of Device based on following the parent source element upwards and mapping to `Device`.
Element `Device.biologicalSourceEvent` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Necessary to support mandatory requirements for traceability from donor/source to recipient and vice versa, while also satisfying donor anonymity requirements. The element is defined consistently across BiologicallyDerivedProduct, NutritionProduct, and Device. The identifier references an event that links to a single biological entity such as a blood donor, or to multiple biological entities (e.g. when the product is an embryo or a pooled platelet product). A single biologicalSourceEvent identifier may appear on multiple products of many types derived from a single donation event or source extraction. As an example, a single donation event may provide 2 kidneys and a liver for organ transplantation, 2 corneas for eye surgery, heart valves and arterial tissue for cardiovascular surgery, multiple skin grafts, tendons, multiple shaped bone grafts and a large number of bone putty/paste products; and each of them may be assigned to the same biological source event identifier."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Device"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.category"/>
<targetVersion value="0.1.0"/>
<element>
<code value="Device.category"/>
<display value="category"/>
<target>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `Device.category` has a context of Device based on following the parent source element upwards and mapping to `Device`.
Element `Device.category` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Device"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.version.installDate"/>
<targetVersion value="0.1.0"/>
<element>
<code value="Device.version.installDate"/>
<display value="installDate"/>
<target>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `Device.version.installDate` has a context of Device.version based on following the parent source element upwards and mapping to `Device`.
Element `Device.version.installDate` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Device"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.conformsTo.version"/>
<targetVersion value="0.1.0"/>
<element>
<code value="Device.conformsTo.version"/>
<display value="version"/>
<target>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `Device.conformsTo.version` has a context of Device.specialization based on following the parent source element upwards and mapping to `Device`.
Element `Device.conformsTo.version` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Device"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.property.value"/>
<targetVersion value="0.1.0"/>
<element>
<code value="Device.property.value[x]"/>
<display value="value[x]"/>
<target>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `Device.property.value[x]` is mapped to FHIR R4 element `Device.property.valueQuantity` as `RelatedTo`.
Element `Device.property.value[x]` is mapped to FHIR R4 element `Device.property.valueCode` as `RelatedTo`.
The mappings for `Device.property.value[x]` do not cover the following types: Attachment, boolean, integer, Range, string.
The text element in CodeableConcept.text is used for properties which would usually be coded (such as the size of an implant, or a security classification) but for which there is not currently an appropriate concept in the vocabulary (e.g. a custom implant size, or a security classification which depends on configuration). Otherwise the string choice type is used for descriptive properties, or instructions."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Device"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.mode"/>
<targetVersion value="0.1.0"/>
<element>
<code value="Device.mode"/>
<display value="mode"/>
<target>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `Device.mode` has a context of Device based on following the parent source element upwards and mapping to `Device`.
Element `Device.mode` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Device"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.cycle"/>
<targetVersion value="0.1.0"/>
<element>
<code value="Device.cycle"/>
<display value="cycle"/>
<target>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `Device.cycle` has a context of Device based on following the parent source element upwards and mapping to `Device`.
Element `Device.cycle` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Device"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.duration"/>
<targetVersion value="0.1.0"/>
<element>
<code value="Device.duration"/>
<display value="duration"/>
<target>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `Device.duration` has a context of Device based on following the parent source element upwards and mapping to `Device`.
Element `Device.duration` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Device"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.endpoint"/>
<targetVersion value="0.1.0"/>
<element>
<code value="Device.endpoint"/>
<display value="endpoint"/>
<target>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `Device.endpoint` has a context of Device based on following the parent source element upwards and mapping to `Device`.
Element `Device.endpoint` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Device"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.gateway"/>
<targetVersion value="0.1.0"/>
<element>
<code value="Device.gateway"/>
<display value="gateway"/>
<target>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `Device.gateway` has a context of Device based on following the parent source element upwards and mapping to `Device`.
Element `Device.gateway` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
The Device.gateway may be used when the Device being referenced has a gateway and/or to capture one or more gateways associated with the device. If the Gateway is included in the Observation resource, the Observation.gatewayDevice should be used instead."/>
</target>
</element>
</group>
</ConceptMap>
IG © 2025+ FHIR Infrastructure. Package hl7.fhir.uv.xver-r5.r4#0.1.0 based on FHIR 4.0.1. Generated 2026-03-20
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change