Generated Narrative: ConceptMap R4-Device-element-map-to-R4B Mapping from http://hl7.org/fhir/4.0 to http://hl7.org/fhir/4.3 Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/Device|4.0.1 to Deviceversion: 4.3.0) Source Code Relationship Target Code Comment Device.meta (meta) is equivalent to Device.meta Element `Device.meta` is mapped to FHIR R4B element `Device.meta` as `Equivalent`. Device.implicitRules (implicitRules) is equivalent to Device.implicitRules Element `Device.implicitRules` is mapped to FHIR R4B element `Device.implicitRules` as `Equivalent`. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc. Device.language (language) is equivalent to Device.language Element `Device.language` is mapped to FHIR R4B element `Device.language` as `Equivalent`. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). Device.text (text) is equivalent to Device.text Element `Device.text` is mapped to FHIR R4B element `Device.text` as `Equivalent`. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later. Device.contained (contained) is equivalent to Device.contained Element `Device.contained` is mapped to FHIR R4B 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 Element `Device.identifier` is mapped to FHIR R4B element `Device.identifier` as `Equivalent`. The barcode string from a barcode present on a device label or package may identify the instance, include names given to the device in local usage, or may identify the type of device. If the identifier identifies the type of device, Device.type element should be used. Device.definition (definition) is equivalent to Device.definition Element `Device.definition` is mapped to FHIR R4B element `Device.definition` as `Equivalent`. Device.udiCarrier (udiCarrier) maps to wider concept Device.udiCarrier Element `Device.udiCarrier` is mapped to FHIR R4B 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 Element `Device.udiCarrier.deviceIdentifier` is mapped to FHIR R4B element `Device.udiCarrier.deviceIdentifier` as `Equivalent`. Device.udiCarrier.issuer (issuer) is equivalent to Device.udiCarrier.issuer Element `Device.udiCarrier.issuer` is mapped to FHIR R4B element `Device.udiCarrier.issuer` as `Equivalent`. Device.udiCarrier.jurisdiction (jurisdiction) is equivalent to Device.udiCarrier.jurisdiction Element `Device.udiCarrier.jurisdiction` is mapped to FHIR R4B element `Device.udiCarrier.jurisdiction` as `Equivalent`. Device.udiCarrier.carrierAIDC (carrierAIDC) is equivalent to Device.udiCarrier.carrierAIDC Element `Device.udiCarrier.carrierAIDC` is mapped to FHIR R4B element `Device.udiCarrier.carrierAIDC` as `Equivalent`. The AIDC form of UDIs should be scanned or otherwise used for the identification of the device whenever possible to minimize errors in records resulting from manual transcriptions. If separate barcodes for DI and PI are present, concatenate the string with DI first and in order of human readable expression on label. Device.udiCarrier.carrierHRF (carrierHRF) is equivalent to Device.udiCarrier.carrierHRF Element `Device.udiCarrier.carrierHRF` is mapped to FHIR R4B element `Device.udiCarrier.carrierHRF` as `Equivalent`. If separate barcodes for DI and PI are present, concatenate the string with DI first and in order of human readable expression on label. Device.udiCarrier.entryType (entryType) is equivalent to Device.udiCarrier.entryType Element `Device.udiCarrier.entryType` is mapped to FHIR R4B element `Device.udiCarrier.entryType` as `Equivalent`. Device.status (status) is equivalent to Device.status Element `Device.status` is mapped to FHIR R4B element `Device.status` as `Equivalent`. This element is labeled as a modifier because the status contains the codes inactive and entered-in-error that mark the device (record)as not currently valid. Device.statusReason (statusReason) is equivalent to Device.statusReason Element `Device.statusReason` is mapped to FHIR R4B element `Device.statusReason` as `Equivalent`. Device.distinctIdentifier (distinctIdentifier) is equivalent to Device.distinctIdentifier Element `Device.distinctIdentifier` is mapped to FHIR R4B element `Device.distinctIdentifier` as `Equivalent`. For example, this applies to devices in the United States regulated under *Code of Federal Regulation 21CFR§1271.290(c)*. Device.manufacturer (manufacturer) is equivalent to Device.manufacturer Element `Device.manufacturer` is mapped to FHIR R4B element `Device.manufacturer` as `Equivalent`. Device.manufactureDate (manufactureDate) is equivalent to Device.manufactureDate Element `Device.manufactureDate` is mapped to FHIR R4B element `Device.manufactureDate` as `Equivalent`. Device.expirationDate (expirationDate) is equivalent to Device.expirationDate Element `Device.expirationDate` is mapped to FHIR R4B element `Device.expirationDate` as `Equivalent`. Device.lotNumber (lotNumber) is equivalent to Device.lotNumber Element `Device.lotNumber` is mapped to FHIR R4B element `Device.lotNumber` as `Equivalent`. Device.serialNumber (serialNumber) is equivalent to Device.serialNumber Element `Device.serialNumber` is mapped to FHIR R4B element `Device.serialNumber` as `Equivalent`. Alphanumeric Maximum 20. Device.deviceName (deviceName) maps to wider concept Device.deviceName Element `Device.deviceName` is mapped to FHIR R4B element `Device.deviceName` as `Equivalent`. Device.deviceName.name (name) is equivalent to Device.deviceName.name Element `Device.deviceName.name` is mapped to FHIR R4B element `Device.deviceName.name` as `Equivalent`. Device.deviceName.type (type) is equivalent to Device.deviceName.type Element `Device.deviceName.type` is mapped to FHIR R4B element `Device.deviceName.type` as `Equivalent`. Device.modelNumber (modelNumber) is equivalent to Device.modelNumber Element `Device.modelNumber` is mapped to FHIR R4B element `Device.modelNumber` as `Equivalent`. Device.partNumber (partNumber) is equivalent to Device.partNumber Element `Device.partNumber` is mapped to FHIR R4B element `Device.partNumber` as `Equivalent`. Alphanumeric Maximum 20. Device.type (type) is equivalent to Device.type Element `Device.type` is mapped to FHIR R4B element `Device.type` as `Equivalent`. Device.specialization (specialization) maps to wider concept Device.specialization Element `Device.specialization` is mapped to FHIR R4B element `Device.specialization` as `Equivalent`. Device.specialization.systemType (systemType) is equivalent to Device.specialization.systemType Element `Device.specialization.systemType` is mapped to FHIR R4B element `Device.specialization.systemType` as `Equivalent`. Device.specialization.version (version) is equivalent to Device.specialization.version Element `Device.specialization.version` is mapped to FHIR R4B element `Device.specialization.version` as `Equivalent`. Device.version (version) maps to wider concept Device.version Element `Device.version` is mapped to FHIR R4B element `Device.version` as `Equivalent`. Device.version.type (type) is equivalent to Device.version.type Element `Device.version.type` is mapped to FHIR R4B element `Device.version.type` as `Equivalent`. Device.version.component (component) is equivalent to Device.version.component Element `Device.version.component` is mapped to FHIR R4B element `Device.version.component` as `Equivalent`. Device.version.value (value) is equivalent to Device.version.value Element `Device.version.value` is mapped to FHIR R4B element `Device.version.value` as `Equivalent`. Device.property (property) maps to wider concept Device.property Element `Device.property` is mapped to FHIR R4B element `Device.property` as `Equivalent`. Device.property.type (type) is equivalent to Device.property.type Element `Device.property.type` is mapped to FHIR R4B element `Device.property.type` as `Equivalent`. Device.property.valueQuantity (valueQuantity) is equivalent to Device.property.valueQuantity Element `Device.property.valueQuantity` is mapped to FHIR R4B element `Device.property.valueQuantity` as `Equivalent`. Device.property.valueCode (valueCode) is equivalent to Device.property.valueCode Element `Device.property.valueCode` is mapped to FHIR R4B element `Device.property.valueCode` as `Equivalent`. Device.patient (patient) is equivalent to Device.patient Element `Device.patient` is mapped to FHIR R4B element `Device.patient` as `Equivalent`. Device.owner (owner) is equivalent to Device.owner Element `Device.owner` is mapped to FHIR R4B element `Device.owner` as `Equivalent`. Device.contact (contact) is equivalent to Device.contact Element `Device.contact` is mapped to FHIR R4B element `Device.contact` as `Equivalent`. used for troubleshooting etc. Device.location (location) is equivalent to Device.location Element `Device.location` is mapped to FHIR R4B element `Device.location` as `Equivalent`. Device.url (url) is equivalent to Device.url Element `Device.url` is mapped to FHIR R4B element `Device.url` as `Equivalent`. If the device is running a FHIR server, the network address should be the Base URL from which a conformance statement may be retrieved. Device.note (note) is equivalent to Device.note Element `Device.note` is mapped to FHIR R4B element `Device.note` as `Equivalent`. Device.safety (safety) is equivalent to Device.safety Element `Device.safety` is mapped to FHIR R4B element `Device.safety` as `Equivalent`. Device.parent (parent) is equivalent to Device.parent Element `Device.parent` is mapped to FHIR R4B element `Device.parent` as `Equivalent`.
Cross-version mapping for FHIR R4 Device to FHIR R4B Device
This ConceptMap represents cross-version mappings for elements from a FHIR R4 Device to FHIR R4B.
Element `Device.meta` is mapped to FHIR R4B element `Device.meta` as `Equivalent`.
Element `Device.implicitRules` is mapped to FHIR R4B element `Device.implicitRules` as `Equivalent`. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.
Element `Device.language` is mapped to FHIR R4B element `Device.language` as `Equivalent`. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
Element `Device.text` is mapped to FHIR R4B element `Device.text` as `Equivalent`. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
Element `Device.contained` is mapped to FHIR R4B 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 R4B element `Device.identifier` as `Equivalent`. The barcode string from a barcode present on a device label or package may identify the instance, include names given to the device in local usage, or may identify the type of device. If the identifier identifies the type of device, Device.type element should be used.
Element `Device.definition` is mapped to FHIR R4B element `Device.definition` as `Equivalent`.
Element `Device.udiCarrier` is mapped to FHIR R4B 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 R4B element `Device.udiCarrier.deviceIdentifier` as `Equivalent`.
Element `Device.udiCarrier.issuer` is mapped to FHIR R4B element `Device.udiCarrier.issuer` as `Equivalent`.
Element `Device.udiCarrier.jurisdiction` is mapped to FHIR R4B element `Device.udiCarrier.jurisdiction` as `Equivalent`.
Element `Device.udiCarrier.carrierAIDC` is mapped to FHIR R4B element `Device.udiCarrier.carrierAIDC` as `Equivalent`. The AIDC form of UDIs should be scanned or otherwise used for the identification of the device whenever possible to minimize errors in records resulting from manual transcriptions. If separate barcodes for DI and PI are present, concatenate the string with DI first and in order of human readable expression on label.
Element `Device.udiCarrier.carrierHRF` is mapped to FHIR R4B element `Device.udiCarrier.carrierHRF` as `Equivalent`. If separate barcodes for DI and PI are present, concatenate the string with DI first and in order of human readable expression on label.
Element `Device.udiCarrier.entryType` is mapped to FHIR R4B element `Device.udiCarrier.entryType` as `Equivalent`.
Element `Device.status` is mapped to FHIR R4B element `Device.status` as `Equivalent`. This element is labeled as a modifier because the status contains the codes inactive and entered-in-error that mark the device (record)as not currently valid.
Element `Device.statusReason` is mapped to FHIR R4B element `Device.statusReason` as `Equivalent`.
Element `Device.distinctIdentifier` is mapped to FHIR R4B element `Device.distinctIdentifier` as `Equivalent`. For example, this applies to devices in the United States regulated under *Code of Federal Regulation 21CFR§1271.290(c)*.
Element `Device.manufacturer` is mapped to FHIR R4B element `Device.manufacturer` as `Equivalent`.
Element `Device.manufactureDate` is mapped to FHIR R4B element `Device.manufactureDate` as `Equivalent`.
Element `Device.expirationDate` is mapped to FHIR R4B element `Device.expirationDate` as `Equivalent`.
Element `Device.lotNumber` is mapped to FHIR R4B element `Device.lotNumber` as `Equivalent`.
Element `Device.serialNumber` is mapped to FHIR R4B element `Device.serialNumber` as `Equivalent`. Alphanumeric Maximum 20.
Element `Device.deviceName` is mapped to FHIR R4B element `Device.deviceName` as `Equivalent`.
Element `Device.deviceName.name` is mapped to FHIR R4B element `Device.deviceName.name` as `Equivalent`.
Element `Device.deviceName.type` is mapped to FHIR R4B element `Device.deviceName.type` as `Equivalent`.
Element `Device.modelNumber` is mapped to FHIR R4B element `Device.modelNumber` as `Equivalent`.
Element `Device.partNumber` is mapped to FHIR R4B element `Device.partNumber` as `Equivalent`. Alphanumeric Maximum 20.
Element `Device.type` is mapped to FHIR R4B element `Device.type` as `Equivalent`.
Element `Device.specialization` is mapped to FHIR R4B element `Device.specialization` as `Equivalent`.
Element `Device.specialization.systemType` is mapped to FHIR R4B element `Device.specialization.systemType` as `Equivalent`.
Element `Device.specialization.version` is mapped to FHIR R4B element `Device.specialization.version` as `Equivalent`.
Element `Device.version` is mapped to FHIR R4B element `Device.version` as `Equivalent`.
Element `Device.version.type` is mapped to FHIR R4B element `Device.version.type` as `Equivalent`.
Element `Device.version.component` is mapped to FHIR R4B element `Device.version.component` as `Equivalent`.
Element `Device.version.value` is mapped to FHIR R4B element `Device.version.value` as `Equivalent`.
Element `Device.property` is mapped to FHIR R4B element `Device.property` as `Equivalent`.
Element `Device.property.type` is mapped to FHIR R4B element `Device.property.type` as `Equivalent`.
Element `Device.property.valueQuantity` is mapped to FHIR R4B element `Device.property.valueQuantity` as `Equivalent`.
Element `Device.property.valueCode` is mapped to FHIR R4B element `Device.property.valueCode` as `Equivalent`.
Element `Device.patient` is mapped to FHIR R4B element `Device.patient` as `Equivalent`.
Element `Device.owner` is mapped to FHIR R4B element `Device.owner` as `Equivalent`.
Element `Device.contact` is mapped to FHIR R4B element `Device.contact` as `Equivalent`. used for troubleshooting etc.
Element `Device.location` is mapped to FHIR R4B element `Device.location` as `Equivalent`.
Element `Device.url` is mapped to FHIR R4B element `Device.url` as `Equivalent`. If the device is running a FHIR server, the network address should be the Base URL from which a conformance statement may be retrieved.
Element `Device.note` is mapped to FHIR R4B element `Device.note` as `Equivalent`.
Element `Device.safety` is mapped to FHIR R4B element `Device.safety` as `Equivalent`.
Element `Device.parent` is mapped to FHIR R4B element `Device.parent` as `Equivalent`.