Generated Narrative: ConceptMap R5-Device-element-map-to-R4 Mapping from http://hl7.org/fhir/5.0 to http://hl7.org/fhir/4.0 Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/Device|5.0.0 to Deviceversion: 4.0.1) Source Concept Details Relationship Target Concept Details Comment Codes from http://hl7.org/fhir/StructureDefinition/Device|5.0.0 Codes from Device Device.meta meta is equivalent to Device.meta Device.meta Element `Device.meta` is mapped to FHIR R4 element `Device.meta` as `Equivalent`. Device.implicitRules implicitRules is equivalent to Device.implicitRules Device.implicitRules 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. Device.language language is equivalent to Device.language Device.language 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). Device.text text is equivalent to Device.text Device.text 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. Device.contained contained is equivalent to Device.contained Device.contained 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. Device.identifier identifier is equivalent to Device.identifier Device.identifier 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. Device.displayName displayName is related to Device.deviceName Device.deviceName Element `Device.displayName` is mapped to FHIR R4 element `Device.deviceName` as `RelatedTo`. The mappings for `Device.displayName` do not cover the following types: string. The mappings for `Device.displayName` do not cover the following types based on type expansion: value. Device.definition definition maps to wider concept Device.definition Device.definition Element `Device.definition` is mapped to FHIR R4 element `Device.definition` as `SourceIsBroaderThanTarget`. The mappings for `Device.definition` do not cover the following types: CodeableReference. The mappings for `Device.definition` do not cover the following types based on type expansion: concept. Device.udiCarrier udiCarrier maps to wider concept Device.udiCarrier Device.udiCarrier 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. Device.udiCarrier.deviceIdentifier deviceIdentifier is equivalent to Device.udiCarrier.deviceIdentifier Device.udiCarrier.deviceIdentifier Element `Device.udiCarrier.deviceIdentifier` is mapped to FHIR R4 element `Device.udiCarrier.deviceIdentifier` as `Equivalent`. Device.udiCarrier.issuer issuer is equivalent to Device.udiCarrier.issuer Device.udiCarrier.issuer Element `Device.udiCarrier.issuer` is mapped to FHIR R4 element `Device.udiCarrier.issuer` as `Equivalent`. Device.udiCarrier.jurisdiction jurisdiction is equivalent to Device.udiCarrier.jurisdiction Device.udiCarrier.jurisdiction Element `Device.udiCarrier.jurisdiction` is mapped to FHIR R4 element `Device.udiCarrier.jurisdiction` as `Equivalent`. Device.udiCarrier.carrierAIDC carrierAIDC is equivalent to Device.udiCarrier.carrierAIDC Device.udiCarrier.carrierAIDC 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. Device.udiCarrier.carrierHRF carrierHRF is equivalent to Device.udiCarrier.carrierHRF Device.udiCarrier.carrierHRF 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. Device.udiCarrier.entryType entryType maps to wider concept Device.udiCarrier.entryType Device.udiCarrier.entryType Element `Device.udiCarrier.entryType` is mapped to FHIR R4 element `Device.udiCarrier.entryType` as `RelatedTo`. The mappings for `Device.udiCarrier.entryType` do not allow expression of the necessary codes, per the bindings on the source and target. Device.status status is equivalent to Device.status Device.status Element `Device.status` is mapped to FHIR R4 element `Device.status` as `SourceIsNarrowerThanTarget`. The mappings for `Device.status` do not allow expression of the necessary codes, per the bindings on the source and target. Device.manufacturer manufacturer is equivalent to Device.manufacturer Device.manufacturer Element `Device.manufacturer` is mapped to FHIR R4 element `Device.manufacturer` as `Equivalent`. Device.manufactureDate manufactureDate is equivalent to Device.manufactureDate Device.manufactureDate Element `Device.manufactureDate` is mapped to FHIR R4 element `Device.manufactureDate` as `Equivalent`. Device.expirationDate expirationDate is equivalent to Device.expirationDate Device.expirationDate Element `Device.expirationDate` is mapped to FHIR R4 element `Device.expirationDate` as `Equivalent`. Device.lotNumber lotNumber is equivalent to Device.lotNumber Device.lotNumber Element `Device.lotNumber` is mapped to FHIR R4 element `Device.lotNumber` as `Equivalent`. Device.serialNumber serialNumber is equivalent to Device.serialNumber Device.serialNumber 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_. Device.name name maps to wider concept Device.deviceName Device.deviceName Element `Device.name` is mapped to FHIR R4 element `Device.deviceName` as `Equivalent`. Device.name.value value is equivalent to Device.deviceName Device.deviceName 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`. is equivalent to Device.deviceName.name Device.deviceName.name Element `Device.name.value` is mapped to FHIR R4 element `Device.deviceName.name` as `Equivalent`. Element `Device.name.value` is mapped to FHIR R4 element `Device.deviceName` as `SourceIsNarrowerThanTarget`. Device.name.type type narrower Device.deviceName.type Device.deviceName.type Element `Device.name.type` is mapped to FHIR R4 element `Device.deviceName.type` as `SourceIsNarrowerThanTarget`. The mappings for `Device.name.type` do not allow expression of the necessary codes, per the bindings on the source and target. Device.name.display display narrower Device.deviceName Device.deviceName Element `Device.name.display` is mapped to FHIR R4 element `Device.deviceName` as `SourceIsNarrowerThanTarget`. Device.modelNumber modelNumber is equivalent to Device.modelNumber Device.modelNumber Element `Device.modelNumber` is mapped to FHIR R4 element `Device.modelNumber` as `Equivalent`. Device.partNumber partNumber is equivalent to Device.partNumber Device.partNumber Element `Device.partNumber` is mapped to FHIR R4 element `Device.partNumber` as `Equivalent`. Alphanumeric Maximum 20. Device.type type is equivalent to Device.type Device.type 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. Device.version version maps to wider concept Device.version Device.version Element `Device.version` is mapped to FHIR R4 element `Device.version` as `Equivalent`. Device.version.type type is equivalent to Device.version.type Device.version.type Element `Device.version.type` is mapped to FHIR R4 element `Device.version.type` as `Equivalent`. Device.version.component component is equivalent to Device.version.component Device.version.component 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. Device.version.value value is equivalent to Device.version.value Device.version.value Element `Device.version.value` is mapped to FHIR R4 element `Device.version.value` as `Equivalent`. Device.conformsTo conformsTo maps to wider concept Device.specialization Device.specialization Element `Device.conformsTo` is mapped to FHIR R4 element `Device.specialization` as `Equivalent`. An externally-defined extension that has been mapped as the representation of FHIR R5 element `Device.conformsTo`: `http://hl7.org/fhir/StructureDefinition/device-conformsTo`. Device.conformsTo.category category narrower Device.specialization Device.specialization Element `Device.conformsTo.category` is mapped to FHIR R4 element `Device.specialization` as `SourceIsNarrowerThanTarget`. Device.conformsTo.specification specification narrower Device.specialization Device.specialization Element `Device.conformsTo.specification` is mapped to FHIR R4 element `Device.specialization` as `SourceIsNarrowerThanTarget`. Device.property property maps to wider concept Device.property Device.property 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. Device.property.type type is equivalent to Device.property.type Device.property.type Element `Device.property.type` is mapped to FHIR R4 element `Device.property.type` as `Equivalent`. Device.property.value[x] value[x] is related to Device.property.valueCode Device.property.valueCode 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. is related to Device.property.valueQuantity Device.property.valueQuantity 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. Device.owner owner is equivalent to Device.owner Device.owner Element `Device.owner` is mapped to FHIR R4 element `Device.owner` as `Equivalent`. Device.contact contact is equivalent to Device.contact Device.contact Element `Device.contact` is mapped to FHIR R4 element `Device.contact` as `Equivalent`. used for troubleshooting etc. Device.location location is equivalent to Device.location Device.location Element `Device.location` is mapped to FHIR R4 element `Device.location` as `Equivalent`. Device.url url is equivalent to Device.url Device.url 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. Device.note note is equivalent to Device.note Device.note Element `Device.note` is mapped to FHIR R4 element `Device.note` as `Equivalent`. Device.safety safety is equivalent to Device.safety Device.safety Element `Device.safety` is mapped to FHIR R4 element `Device.safety` as `Equivalent`. Device.parent parent is equivalent to Device.parent Device.parent 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. Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/Device|5.0.0 to R5: The name used to display by default when the device is referenced additional typesversion: 0.1.0) Source Code Relationship Target Code Comment Device.displayName (displayName) maps to wider concept Extension (R5: The name used to display by default when the device is referenced additional types) 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. Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/Device|5.0.0 to R5: definition additional typesversion: 0.1.0) Source Code Relationship Target Code Comment Device.definition (definition) is equivalent to Extension (R5: definition additional types) 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. Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/Device|5.0.0 to R5: barcode | rfid | manual | card | self-reported | electronic-transmission | unknown additional codesversion: 0.1.0) Source Code Relationship Target Code Comment Device.udiCarrier.entryType (entryType) is equivalent to Extension (R5: barcode | rfid | manual | card | self-reported | electronic-transmission | unknown additional codes) 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. Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/Device|5.0.0 to R5: lost | damaged | destroyed | available (new)version: 0.1.0) Source Code Relationship Target Code Comment Device.availabilityStatus (availabilityStatus) maps to wider concept Extension (R5: lost | damaged | destroyed | available (new)) 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). Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/Device|5.0.0 to 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) Source Code Relationship Target Code Comment Device.biologicalSourceEvent (biologicalSourceEvent) maps to wider concept 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)) 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. Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/Device|5.0.0 to R5: Indicates a high-level grouping of the device (new)version: 0.1.0) Source Code Relationship Target Code Comment Device.category (category) maps to wider concept Extension (R5: Indicates a high-level grouping of the device (new)) 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). Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/Device|5.0.0 to R5: The date the version was installed on the device (new)version: 0.1.0) Source Code Relationship Target Code Comment Device.version.installDate (installDate) maps to wider concept Extension (R5: The date the version was installed on the device (new)) 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). Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/Device|5.0.0 to R5: Specific form or variant of the standard (new)version: 0.1.0) Source Code Relationship Target Code Comment Device.conformsTo.version (version) maps to wider concept Extension (R5: Specific form or variant of the standard (new)) 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). Group 10 Mapping from http://hl7.org/fhir/StructureDefinition/Device|5.0.0 to R5: Value of the property additional typesversion: 0.1.0) Source Code Relationship Target Code Comment Device.property.value[x] (value[x]) maps to wider concept Extension (R5: Value of the property additional types) 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. Group 11 Mapping from http://hl7.org/fhir/StructureDefinition/Device|5.0.0 to R5: The designated condition for performing a task (new)version: 0.1.0) Source Code Relationship Target Code Comment Device.mode (mode) maps to wider concept Extension (R5: The designated condition for performing a task (new)) 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). Group 12 Mapping from http://hl7.org/fhir/StructureDefinition/Device|5.0.0 to R5: The series of occurrences that repeats during the operation of the device (new)version: 0.1.0) Source Code Relationship Target Code Comment Device.cycle (cycle) maps to wider concept Extension (R5: The series of occurrences that repeats during the operation of the device (new)) 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). Group 13 Mapping from http://hl7.org/fhir/StructureDefinition/Device|5.0.0 to R5: A measurement of time during the device's operation (e.g., days, hours, mins, etc.) (new)version: 0.1.0) Source Code Relationship Target Code Comment Device.duration (duration) maps to wider concept Extension (R5: A measurement of time during the device's operation (e.g., days, hours, mins, etc.) (new)) 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). Group 14 Mapping from http://hl7.org/fhir/StructureDefinition/Device|5.0.0 to R5: Technical endpoints providing access to electronic services provided by the device (new)version: 0.1.0) Source Code Relationship Target Code Comment Device.endpoint (endpoint) maps to wider concept Extension (R5: Technical endpoints providing access to electronic services provided by the device (new)) 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). Group 15 Mapping from http://hl7.org/fhir/StructureDefinition/Device|5.0.0 to R5: Linked device acting as a communication/data collector, translator or controller (new)version: 0.1.0) Source Code Relationship Target Code Comment Device.gateway (gateway) maps to wider concept Extension (R5: Linked device acting as a communication/data collector, translator or controller (new)) 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.
Cross-version mapping for FHIR R5 Device to FHIR R4 Device
This ConceptMap represents cross-version mappings for elements from a FHIR R5 Device to FHIR R4.
Element `Device.meta` is mapped to FHIR R4 element `Device.meta` as `Equivalent`.
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.
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).
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.
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.
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.
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.
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.
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.
Element `Device.udiCarrier.deviceIdentifier` is mapped to FHIR R4 element `Device.udiCarrier.deviceIdentifier` as `Equivalent`.
Element `Device.udiCarrier.issuer` is mapped to FHIR R4 element `Device.udiCarrier.issuer` as `Equivalent`.
Element `Device.udiCarrier.jurisdiction` is mapped to FHIR R4 element `Device.udiCarrier.jurisdiction` as `Equivalent`.
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.
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.
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.
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.
Element `Device.manufacturer` is mapped to FHIR R4 element `Device.manufacturer` as `Equivalent`.
Element `Device.manufactureDate` is mapped to FHIR R4 element `Device.manufactureDate` as `Equivalent`.
Element `Device.expirationDate` is mapped to FHIR R4 element `Device.expirationDate` as `Equivalent`.
Element `Device.lotNumber` is mapped to FHIR R4 element `Device.lotNumber` as `Equivalent`.
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_.
Element `Device.name` is mapped to FHIR R4 element `Device.deviceName` as `Equivalent`.
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`.
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.
Element `Device.name.display` is mapped to FHIR R4 element `Device.deviceName` as `SourceIsNarrowerThanTarget`.
Element `Device.modelNumber` is mapped to FHIR R4 element `Device.modelNumber` as `Equivalent`.
Element `Device.partNumber` is mapped to FHIR R4 element `Device.partNumber` as `Equivalent`. Alphanumeric Maximum 20.
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.
Element `Device.version` is mapped to FHIR R4 element `Device.version` as `Equivalent`.
Element `Device.version.type` is mapped to FHIR R4 element `Device.version.type` as `Equivalent`.
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.
Element `Device.version.value` is mapped to FHIR R4 element `Device.version.value` as `Equivalent`.
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`.
Element `Device.conformsTo.category` is mapped to FHIR R4 element `Device.specialization` as `SourceIsNarrowerThanTarget`.
Element `Device.conformsTo.specification` is mapped to FHIR R4 element `Device.specialization` as `SourceIsNarrowerThanTarget`.
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.
Element `Device.property.type` is mapped to FHIR R4 element `Device.property.type` as `Equivalent`.
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.
Element `Device.owner` is mapped to FHIR R4 element `Device.owner` as `Equivalent`.
Element `Device.contact` is mapped to FHIR R4 element `Device.contact` as `Equivalent`. used for troubleshooting etc.
Element `Device.location` is mapped to FHIR R4 element `Device.location` as `Equivalent`.
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.
Element `Device.note` is mapped to FHIR R4 element `Device.note` as `Equivalent`.
Element `Device.safety` is mapped to FHIR R4 element `Device.safety` as `Equivalent`.
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.
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).
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.
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).
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).
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).
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).
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).
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).
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).
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.