Extensions for Using Data Elements from FHIR STU3 in FHIR R4
0.1.0 - STU International flag

Extensions for Using Data Elements from FHIR STU3 in FHIR R4 - Downloaded Version null See the Directory of published versions

ConceptMap: R3DeviceElementMapToR4

Official URL: http://hl7.org/fhir/uv/xver/ConceptMap/R3-Device-element-map-to-R4 Version: 0.1.0
Standards status: Trial-use Maturity Level: 0 Computable Name: R3DeviceElementMapToR4

This ConceptMap represents cross-version mappings for elements from a FHIR STU3 Device to FHIR R4.

Mapping from http://hl7.org/fhir/3.0 to http://hl7.org/fhir/4.0


Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/Device|3.0.2 to Deviceversion: 4.0.1)

Source CodeRelationshipTarget CodeComment
Device.meta (meta)is equivalent toDevice.metaElement `Device.meta` is mapped to FHIR R4 element `Device.meta` as `Equivalent`.
Device.implicitRules (implicitRules)is equivalent toDevice.implicitRulesElement `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. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.
Device.language (language)is equivalent toDevice.languageElement `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 toDevice.textElement `Device.text` is mapped to FHIR R4 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 in formation is added later.
Device.contained (contained)is equivalent toDevice.containedElement `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.
Device.identifier (identifier)is equivalent toDevice.identifierElement `Device.identifier` is mapped to FHIR R4 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. For [UDI](https://hl7.org/fhir/device.html#5.11.3.2.2), this element corresponds to the variable portion of the UDI that identifies the serial number of a specific device. See [UDI mappings](https://hl7.org/fhir/devi.html#udi) for a complete mapping of UDI parts to Device.
Device.udi (udi)is related toDevice.udiCarrierElement `Device.udi` is mapped to FHIR R4 element `Device.udiCarrier` as `SourceIsNarrowerThanTarget`. UDI may identify an unique instance of a device, or it may only identify the type of the device. See [UDI mappings](https://hl7.org/fhir/devi.html#udi) for a complete mapping of UDI parts to Device.
Device.udi.deviceIdentifier (deviceIdentifier)is equivalent toDevice.udiCarrier.deviceIdentifierElement `Device.udi.deviceIdentifier` is mapped to FHIR R4 element `Device.udiCarrier.deviceIdentifier` as `Equivalent`.
Device.udi.jurisdiction (jurisdiction)is equivalent toDevice.udiCarrier.jurisdictionElement `Device.udi.jurisdiction` is mapped to FHIR R4 element `Device.udiCarrier.jurisdiction` as `Equivalent`.
Device.udi.carrierHRF (carrierHRF)is equivalent toDevice.udiCarrier.carrierHRFElement `Device.udi.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.udi.carrierAIDC (carrierAIDC)is equivalent toDevice.udiCarrier.carrierAIDCElement `Device.udi.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.udi.issuer (issuer)is equivalent toDevice.udiCarrier.issuerElement `Device.udi.issuer` is mapped to FHIR R4 element `Device.udiCarrier.issuer` as `Equivalent`.
Device.udi.entryType (entryType)is equivalent toDevice.udiCarrier.entryTypeElement `Device.udi.entryType` is mapped to FHIR R4 element `Device.udiCarrier.entryType` as `Equivalent`.
Device.status (status)is equivalent toDevice.statusElement `Device.status` is mapped to FHIR R4 element `Device.status` as `Equivalent`. This element is labeled as a modifier because the status contains the codes inactive and entered-in-error that mark the device (record)as not currently valid.
Device.type (type)is equivalent toDevice.typeElement `Device.type` is mapped to FHIR R4 element `Device.type` as `Equivalent`.
Device.lotNumber (lotNumber)is equivalent toDevice.lotNumberElement `Device.lotNumber` is mapped to FHIR R4 element `Device.lotNumber` as `Equivalent`.
Device.manufacturer (manufacturer)is equivalent toDevice.manufacturerElement `Device.manufacturer` is mapped to FHIR R4 element `Device.manufacturer` as `Equivalent`.
Device.manufactureDate (manufactureDate)is equivalent toDevice.manufactureDateElement `Device.manufactureDate` is mapped to FHIR R4 element `Device.manufactureDate` as `Equivalent`.
Device.expirationDate (expirationDate)is equivalent toDevice.expirationDateElement `Device.expirationDate` is mapped to FHIR R4 element `Device.expirationDate` as `Equivalent`.
Device.model (model)is equivalent toDevice.modelNumberElement `Device.model` is mapped to FHIR R4 element `Device.modelNumber` as `Equivalent`.
Device.version (version)is equivalent toDevice.version.valueElement `Device.version` is mapped to FHIR R4 element `Device.version.value` as `Equivalent`.
Device.patient (patient)is equivalent toDevice.patientElement `Device.patient` is mapped to FHIR R4 element `Device.patient` as `Equivalent`.
Device.owner (owner)is equivalent toDevice.ownerElement `Device.owner` is mapped to FHIR R4 element `Device.owner` as `Equivalent`.
Device.contact (contact)is equivalent toDevice.contactElement `Device.contact` is mapped to FHIR R4 element `Device.contact` as `Equivalent`. used for troubleshooting etc.
Device.location (location)is equivalent toDevice.locationElement `Device.location` is mapped to FHIR R4 element `Device.location` as `Equivalent`.
Device.url (url)is equivalent toDevice.urlElement `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 toDevice.noteElement `Device.note` is mapped to FHIR R4 element `Device.note` as `Equivalent`.
Device.safety (safety)is equivalent toDevice.safetyElement `Device.safety` is mapped to FHIR R4 element `Device.safety` as `Equivalent`.

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/Device|3.0.2 to STU3: Device Name as appears on UDI label (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Device.udi.name (name)is equivalent toExtension (STU3: Device Name as appears on UDI label (new))Element `Device.udi.name` has a context of Device.udiCarrier based on following the parent source element upwards and mapping to `Device`. Element `Device.udi.name` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Use the `Device.type` for a generic type or kind of device name. Note the [GUDID](http://www.fda.gov/medicaldevices/deviceregulationandguidance/uniquedeviceidentification/globaludidatabasegudid/default.htm) lists the name as the 'Brand Name'.