R4DeviceElementMapToR5 - Extensions for Using Data Elements from FHIR R4 in FHIR R5 v0.1.0

Device.meta

Element `Device.meta` is mapped to FHIR R5 element `Device.meta` as `Equivalent`. Element `Device.meta` is mapped to FHIR R5 element `DeviceAssociation.meta` as `Equivalent`.

Device.implicitRules

implicitRules

Device.implicitRules

Element `Device.implicitRules` is mapped to FHIR R5 element `Device.implicitRules` as `Equivalent`. Element `Device.implicitRules` is mapped to FHIR R5 element `DeviceAssociation.implicitRules` as `Equivalent`. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.

Device.language

language

Device.language

Element `Device.language` is mapped to FHIR R5 element `Device.language` as `Equivalent`. Element `Device.language` is mapped to FHIR R5 element `DeviceAssociation.language` as `Equivalent`. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).

Device.text

text

Device.text

Element `Device.text` is mapped to FHIR R5 element `Device.text` as `Equivalent`. Element `Device.text` is mapped to FHIR R5 element `DeviceAssociation.text` as `Equivalent`. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.

Device.contained

contained

Device.contained

Element `Device.contained` is mapped to FHIR R5 element `Device.contained` as `Equivalent`. Element `Device.contained` is mapped to FHIR R5 element `DeviceAssociation.contained` as `Equivalent`. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.

Device.identifier

identifier

Device.identifier

Element `Device.identifier` is mapped to FHIR R5 element `Device.identifier` as `Equivalent`. Element `Device.identifier` is mapped to FHIR R5 element `DeviceAssociation.identifier` as `Equivalent`. The barcode string from a barcode present on a device label or package may identify the instance, include names given to the device in local usage, or may identify the type of device. If the identifier identifies the type of device, Device.type element should be used.

Device.definition

definition

Device.definition

Element `Device.definition` is mapped to FHIR R5 element `Device.definition` as `SourceIsNarrowerThanTarget`.

Device.udiCarrier

udiCarrier

Device.udiCarrier

Element `Device.udiCarrier` is mapped to FHIR R5 element `Device.udiCarrier` as `Equivalent`. UDI may identify an unique instance of a device, or it may only identify the type of the device. See [UDI mappings](https://hl7.org/fhir/devi.html#udi) for a complete mapping of UDI parts to Device.

Device.udiCarrier.deviceIdentifier

deviceIdentifier

Device.udiCarrier.deviceIdentifier

Element `Device.udiCarrier.deviceIdentifier` is mapped to FHIR R5 element `Device.udiCarrier.deviceIdentifier` as `Equivalent`.

Device.udiCarrier.issuer

issuer

Device.udiCarrier.issuer

Element `Device.udiCarrier.issuer` is mapped to FHIR R5 element `Device.udiCarrier.issuer` as `Equivalent`.

Device.udiCarrier.jurisdiction

jurisdiction

Device.udiCarrier.jurisdiction

Element `Device.udiCarrier.jurisdiction` is mapped to FHIR R5 element `Device.udiCarrier.jurisdiction` as `Equivalent`.

Device.udiCarrier.carrierAIDC

carrierAIDC

Device.udiCarrier.carrierAIDC

Element `Device.udiCarrier.carrierAIDC` is mapped to FHIR R5 element `Device.udiCarrier.carrierAIDC` as `Equivalent`. The AIDC form of UDIs should be scanned or otherwise used for the identification of the device whenever possible to minimize errors in records resulting from manual transcriptions. If separate barcodes for DI and PI are present, concatenate the string with DI first and in order of human readable expression on label.

Device.udiCarrier.carrierHRF

carrierHRF

Device.udiCarrier.carrierHRF

Element `Device.udiCarrier.carrierHRF` is mapped to FHIR R5 element `Device.udiCarrier.carrierHRF` as `Equivalent`. If separate barcodes for DI and PI are present, concatenate the string with DI first and in order of human readable expression on label.

Device.udiCarrier.entryType

entryType

Device.udiCarrier.entryType

Element `Device.udiCarrier.entryType` is mapped to FHIR R5 element `Device.udiCarrier.entryType` as `RelatedTo`. The mappings for `Device.udiCarrier.entryType` do not allow expression of the necessary codes, per the bindings on the source and target.

Device.status

status

Device.status

Element `Device.status` is mapped to FHIR R5 element `Device.status` as `SourceIsBroaderThanTarget`. Element `Device.status` is mapped to FHIR R5 element `DeviceAssociation.status` as `SourceIsNarrowerThanTarget`. The mappings for `Device.status` do not allow expression of the necessary codes, per the bindings on the source and target. This element is labeled as a modifier because the status contains the codes inactive and entered-in-error that mark the device (record)as not currently valid.

Device.manufacturer

manufacturer

Device.manufacturer

Element `Device.manufacturer` is mapped to FHIR R5 element `Device.manufacturer` as `Equivalent`.

Device.manufactureDate

manufactureDate

Device.manufactureDate

Element `Device.manufactureDate` is mapped to FHIR R5 element `Device.manufactureDate` as `Equivalent`.

Device.expirationDate

expirationDate

Device.expirationDate

Element `Device.expirationDate` is mapped to FHIR R5 element `Device.expirationDate` as `Equivalent`.

Device.lotNumber

lotNumber

Device.lotNumber

Element `Device.lotNumber` is mapped to FHIR R5 element `Device.lotNumber` as `Equivalent`.

Device.serialNumber

serialNumber

Device.serialNumber

Element `Device.serialNumber` is mapped to FHIR R5 element `Device.serialNumber` as `Equivalent`. Alphanumeric Maximum 20.

Device.deviceName

deviceName

Device.displayName

Element `Device.deviceName` is mapped to FHIR R5 element `Device.displayName` as `RelatedTo`. Element `Device.deviceName` is mapped to FHIR R5 element `Device.name` as `Equivalent`.

Device.name

Element `Device.deviceName` is mapped to FHIR R5 element `Device.displayName` as `RelatedTo`. Element `Device.deviceName` is mapped to FHIR R5 element `Device.name` as `Equivalent`.

Device.deviceName.name

name

Device.name.value

Element `Device.deviceName.name` is mapped to FHIR R5 element `Device.name.value` as `Equivalent`.

Device.deviceName.type

type

Device.name.type

Element `Device.deviceName.type` is mapped to FHIR R5 element `Device.name.type` as `SourceIsBroaderThanTarget`.

Device.modelNumber

modelNumber

Device.modelNumber

Element `Device.modelNumber` is mapped to FHIR R5 element `Device.modelNumber` as `Equivalent`.

Device.partNumber

partNumber

Device.partNumber

Element `Device.partNumber` is mapped to FHIR R5 element `Device.partNumber` as `Equivalent`. Alphanumeric Maximum 20.

Device.type

type

Device.type

Element `Device.type` is mapped to FHIR R5 element `Device.type` as `SourceIsNarrowerThanTarget`.

Device.specialization

specialization

Device.conformsTo

Element `Device.specialization` is mapped to FHIR R5 element `Device.conformsTo` as `Equivalent`.

Device.version

version

Device.version

Element `Device.version` is mapped to FHIR R5 element `Device.version` as `Equivalent`.

Device.version.type

type

Device.version.type

Element `Device.version.type` is mapped to FHIR R5 element `Device.version.type` as `Equivalent`.

Device.version.component

component

Device.version.component

Element `Device.version.component` is mapped to FHIR R5 element `Device.version.component` as `Equivalent`.

Device.version.value

value

Device.version.value

Element `Device.version.value` is mapped to FHIR R5 element `Device.version.value` as `Equivalent`.

Device.property

property

Device.property

Element `Device.property` is mapped to FHIR R5 element `Device.property` as `Equivalent`.

Device.property.type

type

Device.property.type

Element `Device.property.type` is mapped to FHIR R5 element `Device.property.type` as `Equivalent`.

Device.owner

owner

Device.owner

Element `Device.owner` is mapped to FHIR R5 element `Device.owner` as `Equivalent`.

Device.contact

contact

Device.contact

Element `Device.contact` is mapped to FHIR R5 element `Device.contact` as `Equivalent`. used for troubleshooting etc.

Device.location

location

Device.location

Element `Device.location` is mapped to FHIR R5 element `Device.location` as `Equivalent`.

Device.url

url

Device.url

Element `Device.url` is mapped to FHIR R5 element `Device.url` as `Equivalent`. If the device is running a FHIR server, the network address should be the Base URL from which a conformance statement may be retrieved.

Device.note

note

Device.note

Element `Device.note` is mapped to FHIR R5 element `Device.note` as `Equivalent`.

Device.safety

safety

Device.safety

Element `Device.safety` is mapped to FHIR R5 element `Device.safety` as `Equivalent`.

Device.parent

parent

Device.parent

Element `Device.parent` is mapped to FHIR R5 element `Device.parent` as `Equivalent`.

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/Device|4.0.1 to DeviceAssociationversion: 5.0.0)

Source Code

Relationship

Target Code

Comment

Device.meta (meta)

DeviceAssociation.meta

Element `Device.meta` is mapped to FHIR R5 element `Device.meta` as `Equivalent`. Element `Device.meta` is mapped to FHIR R5 element `DeviceAssociation.meta` as `Equivalent`.

Device.implicitRules (implicitRules)

DeviceAssociation.implicitRules

Element `Device.implicitRules` is mapped to FHIR R5 element `Device.implicitRules` as `Equivalent`. Element `Device.implicitRules` is mapped to FHIR R5 element `DeviceAssociation.implicitRules` as `Equivalent`. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.

Device.language (language)

DeviceAssociation.language

Element `Device.language` is mapped to FHIR R5 element `Device.language` as `Equivalent`. Element `Device.language` is mapped to FHIR R5 element `DeviceAssociation.language` as `Equivalent`. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).

Device.text (text)

DeviceAssociation.text

Element `Device.text` is mapped to FHIR R5 element `Device.text` as `Equivalent`. Element `Device.text` is mapped to FHIR R5 element `DeviceAssociation.text` as `Equivalent`. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.

Device.contained (contained)

DeviceAssociation.contained

Element `Device.contained` is mapped to FHIR R5 element `Device.contained` as `Equivalent`. Element `Device.contained` is mapped to FHIR R5 element `DeviceAssociation.contained` as `Equivalent`. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.

Device.identifier (identifier)

DeviceAssociation.identifier

Element `Device.identifier` is mapped to FHIR R5 element `Device.identifier` as `Equivalent`. Element `Device.identifier` is mapped to FHIR R5 element `DeviceAssociation.identifier` as `Equivalent`. The barcode string from a barcode present on a device label or package may identify the instance, include names given to the device in local usage, or may identify the type of device. If the identifier identifies the type of device, Device.type element should be used.

Device.status (status)

DeviceAssociation.status

Element `Device.status` is mapped to FHIR R5 element `Device.status` as `SourceIsBroaderThanTarget`. Element `Device.status` is mapped to FHIR R5 element `DeviceAssociation.status` as `SourceIsNarrowerThanTarget`. The mappings for `Device.status` do not allow expression of the necessary codes, per the bindings on the source and target. This element is labeled as a modifier because the status contains the codes inactive and entered-in-error that mark the device (record)as not currently valid.

Device.statusReason (statusReason)

DeviceAssociation.statusReason

Element `Device.statusReason` is mapped to FHIR R5 element `DeviceAssociation.statusReason` as `Equivalent`.

Device.patient (patient)

DeviceAssociation.subject

Element `Device.patient` is mapped to FHIR R5 element `DeviceAssociation.subject` as `SourceIsNarrowerThanTarget`.

Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/Device|4.0.1 to R4: barcode | rfid | manual + additional codesversion: 0.1.0)

Source Code

Relationship

Target Code

Comment

Device.udiCarrier.entryType (entryType)

Extension (R4: barcode | rfid | manual + additional codes)

Element `Device.udiCarrier.entryType` is mapped to FHIR R5 element `Device.udiCarrier.entryType` as `RelatedTo`. The mappings for `Device.udiCarrier.entryType` do not allow expression of the necessary codes, per the bindings on the source and target.

Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/Device|4.0.1 to R4: The distinct identification string (new)version: 0.1.0)

Source Code

Relationship

Target Code

Comment

Device.distinctIdentifier (distinctIdentifier)

Extension (R4: The distinct identification string (new))

Element `Device.distinctIdentifier` has a context of Device based on following the parent source element upwards and mapping to `Device`. Element `Device.distinctIdentifier` has a context of DeviceAssociation based on following the parent source element upwards and mapping to `DeviceAssociation`. Element `Device.distinctIdentifier` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). For example, this applies to devices in the United States regulated under *Code of Federal Regulation 21CFR§1271.290(c)*.

Source Code

Relationship

Target Code

Comment

Device.deviceName.type (type)

Element `Device.deviceName.type` is mapped to FHIR R5 element `Device.name.type` as `SourceIsBroaderThanTarget`.

Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/Device|4.0.1 to R4: The standard that is used to operate and communicate (new)version: 0.1.0)

Source Code

Relationship

Target Code

Comment

Device.specialization.systemType (systemType)

Extension (R4: The standard that is used to operate and communicate (new))

Element `Device.specialization.systemType` has a context of Device.conformsTo based on following the parent source element upwards and mapping to `Device`. Element `Device.specialization.systemType` has a context of DeviceAssociation based on following the parent source element upwards and mapping to `DeviceAssociation`. Element `Device.specialization.systemType` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/Device|4.0.1 to R4: The version of the standard that is used to operate and communicate (new)version: 0.1.0)

Source Code

Relationship

Target Code

Comment

Device.specialization.version (version)

Extension (R4: The version of the standard that is used to operate and communicate (new))

Element `Device.specialization.version` has a context of Device.conformsTo based on following the parent source element upwards and mapping to `Device`. Element `Device.specialization.version` has a context of DeviceAssociation based on following the parent source element upwards and mapping to `DeviceAssociation`. Element `Device.specialization.version` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/Device|4.0.1 to R4: Property value as a quantity (new)version: 0.1.0)

Source Code

Relationship

Target Code

Comment

Device.property.valueQuantity (valueQuantity)

Extension (R4: Property value as a quantity (new))

Element `Device.property.valueQuantity` has a context of Device.property based on following the parent source element upwards and mapping to `Device`. Element `Device.property.valueQuantity` has a context of DeviceAssociation based on following the parent source element upwards and mapping to `DeviceAssociation`. Element `Device.property.valueQuantity` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/Device|4.0.1 to R4: Property value as a code, e.g., NTP4 (synced to NTP) (new)version: 0.1.0)

Source Code

Relationship

Target Code

Comment

Device.property.valueCode (valueCode)