R5-Device-element-map-to-R4
type: ConceptMap
node role: treeRoot
id:
  v: R5-Device-element-map-to-R4
text:
  status:
    v: generated
  div:
    v: 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 …
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-wg
    l: structuredefinition-wg
  value: Code
    v: fhir
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm
    l: structuredefinition-fmm
  value: Integer
    v: 0
    extension:
      url:
        v: http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom
        l: structuredefinition-conformance-derivedFrom
      value: Canonical
        v: http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4
        l: hl7.fhir.uv.xver-r5.r4
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status
    l: structuredefinition-standards-status
  value: Code
    v: trial-use
    extension:
      url:
        v: http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom
        l: structuredefinition-conformance-derivedFrom
      value: Canonical
        v: http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4
        l: hl7.fhir.uv.xver-r5.r4
url:
  v: http://hl7.org/fhir/uv/xver/ConceptMap/R5-Device-element-map-to-R4
  l: R5-Device-element-map-to-R4
version:
  v: 0.1.0
name:
  v: R5DeviceElementMapToR4
title:
  v: Cross-version mapping for FHIR R5 Device to FHIR R4 Device
status:
  v: active
experimental:
  v: false
date:
  v: 2026-03-17T16:04:44.9538459-05:00
contact:
  name:
    v: FHIR Infrastructure
  telecom:
    system:
      v: url
    value:
      v: http://www.hl7.org/Special/committees/fiwg
description:
  v: This ConceptMap represents cross-version mappings for elements from a FHIR R5 Device to FHIR R4.
jurisdiction:
  coding:
    system:
      v: http://unstats.un.org/unsd/methods/m49/m49.htm
      l: m49.htm
    code:
      v: 001
    display:
      v: World
source: Canonical
  v: http://hl7.org/fhir/5.0
  l: http://hl7.org/fhir/5.0
target: Uri
  v: http://hl7.org/fhir/4.0
  l: http://hl7.org/fhir/4.0
group:
  source:
    v: http://hl7.org/fhir/StructureDefinition/Device
    l: Device
  source version:
    v: 5.0.0
  target:
    v: http://hl7.org/fhir/StructureDefinition/Device
    l: Device
  target version:
    v: 4.0.1
  element:
    code:
      v: Device.meta
    display:
      v: meta
    target:
      code:
        v: Device.meta
      display:
        v: Device.meta
      equivalence:
        v: equivalent
      comment:
        v: Element `Device.meta` is mapped to FHIR R4 element `Device.meta` as `Equivalent`.
  element:
    code:
      v: Device.implicitRules
    display:
      v: implicitRules
    target:
      code:
        v: Device.implicitRules
      display:
        v: Device.implicitRules
      equivalence:
        v: equivalent
      comment:
        v: 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:
    code:
      v: Device.language
    display:
      v: language
    target:
      code:
        v: Device.language
      display:
        v: Device.language
      equivalence:
        v: equivalent
      comment:
        v: 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:
    code:
      v: Device.text
    display:
      v: text
    target:
      code:
        v: Device.text
      display:
        v: Device.text
      equivalence:
        v: equivalent
      comment:
        v: 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:
    code:
      v: Device.contained
    display:
      v: contained
    target:
      code:
        v: Device.contained
      display:
        v: Device.contained
      equivalence:
        v: equivalent
      comment:
        v: 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:
    code:
      v: Device.identifier
    display:
      v: identifier
    target:
      code:
        v: Device.identifier
      display:
        v: Device.identifier
      equivalence:
        v: equivalent
      comment:
        v: 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:
    code:
      v: Device.displayName
    display:
      v: displayName
    target:
      code:
        v: Device.deviceName
      display:
        v: Device.deviceName
      equivalence:
        v: relatedto
      comment:
        v: 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:
    code:
      v: Device.definition
    display:
      v: definition
    target:
      code:
        v: Device.definition
      display:
        v: Device.definition
      equivalence:
        v: wider
      comment:
        v: 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.

code:
  v: Device.udiCarrier
display:
  v: udiCarrier
target:
  code:
    v: Device.udiCarrier
  display:
    v: Device.udiCarrier
  equivalence:
    v: wider
  comment:
    v: 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.

code:
  v: Device.udiCarrier.deviceIdentifier
display:
  v: deviceIdentifier
target:
  code:
    v: Device.udiCarrier.deviceIdentifier
  display:
    v: Device.udiCarrier.deviceIdentifier
  equivalence:
    v: equivalent
  comment:
    v: Element `Device.udiCarrier.deviceIdentifier` is mapped to FHIR R4 element `Device.udiCarrier.deviceIdentifier` as `Equivalent`.

code:
  v: Device.udiCarrier.issuer
display:
  v: issuer
target:
  code:
    v: Device.udiCarrier.issuer
  display:
    v: Device.udiCarrier.issuer
  equivalence:
    v: equivalent
  comment:
    v: Element `Device.udiCarrier.issuer` is mapped to FHIR R4 element `Device.udiCarrier.issuer` as `Equivalent`.

code:
  v: Device.udiCarrier.jurisdiction
display:
  v: jurisdiction
target:
  code:
    v: Device.udiCarrier.jurisdiction
  display:
    v: Device.udiCarrier.jurisdiction
  equivalence:
    v: equivalent
  comment:
    v: Element `Device.udiCarrier.jurisdiction` is mapped to FHIR R4 element `Device.udiCarrier.jurisdiction` as `Equivalent`.

code:
  v: Device.udiCarrier.carrierAIDC
display:
  v: carrierAIDC
target:
  code:
    v: Device.udiCarrier.carrierAIDC
  display:
    v: Device.udiCarrier.carrierAIDC
  equivalence:
    v: equivalent
  comment:
    v: 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.

code:
  v: Device.udiCarrier.carrierHRF
display:
  v: carrierHRF
target:
  code:
    v: Device.udiCarrier.carrierHRF
  display:
    v: Device.udiCarrier.carrierHRF
  equivalence:
    v: equivalent
  comment:
    v: 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.

code:
  v: Device.udiCarrier.entryType
display:
  v: entryType
target:
  code:
    v: Device.udiCarrier.entryType
  display:
    v: Device.udiCarrier.entryType
  equivalence:
    v: wider
  comment:
    v: 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.

code:
  v: Device.status
display:
  v: status
target:
  code:
    v: Device.status
  display:
    v: Device.status
  equivalence:
    v: equivalent
  comment:
    v: 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.

code:
  v: Device.manufacturer
display:
  v: manufacturer
target:
  code:
    v: Device.manufacturer
  display:
    v: Device.manufacturer
  equivalence:
    v: equivalent
  comment:
    v: Element `Device.manufacturer` is mapped to FHIR R4 element `Device.manufacturer` as `Equivalent`.

code:
  v: Device.manufactureDate
display:
  v: manufactureDate
target:
  code:
    v: Device.manufactureDate
  display:
    v: Device.manufactureDate
  equivalence:
    v: equivalent
  comment:
    v: Element `Device.manufactureDate` is mapped to FHIR R4 element `Device.manufactureDate` as `Equivalent`.

code:
  v: Device.expirationDate
display:
  v: expirationDate
target:
  code:
    v: Device.expirationDate
  display:
    v: Device.expirationDate
  equivalence:
    v: equivalent
  comment:
    v: Element `Device.expirationDate` is mapped to FHIR R4 element `Device.expirationDate` as `Equivalent`.

code:
  v: Device.lotNumber
display:
  v: lotNumber
target:
  code:
    v: Device.lotNumber
  display:
    v: Device.lotNumber
  equivalence:
    v: equivalent
  comment:
    v: Element `Device.lotNumber` is mapped to FHIR R4 element `Device.lotNumber` as `Equivalent`.

code:
  v: Device.serialNumber
display:
  v: serialNumber
target:
  code:
    v: Device.serialNumber
  display:
    v: Device.serialNumber
  equivalence:
    v: equivalent
  comment:
    v: 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_.

code:
  v: Device.name
display:
  v: name
target:
  code:
    v: Device.deviceName
  display:
    v: Device.deviceName
  equivalence:
    v: wider
  comment:
    v: Element `Device.name` is mapped to FHIR R4 element `Device.deviceName` as `Equivalent`.

code:
  v: Device.name.value
display:
  v: value
target:
  code:
    v: Device.deviceName
  display:
    v: Device.deviceName
  equivalence:
    v: equivalent
  comment:
    v: Element `Device.name.value` is mapped to FHIR R4 element `Device.deviceName.name` as `Equivalent`. Element `Device.name.value` is mapped to FHIR R4 element `Device.deviceName` as `SourceIsNarrowerThanTarget`.
target:
  code:
    v: Device.deviceName.name
  display:
    v: Device.deviceName.name
  equivalence:
    v: equivalent
  comment:
    v: 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`.

code:
  v: Device.name.type
display:
  v: type
target:
  code:
    v: Device.deviceName.type
  display:
    v: Device.deviceName.type
  equivalence:
    v: narrower
  comment:
    v: 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.

code:
  v: Device.name.display
display:
  v: display
target:
  code:
    v: Device.deviceName
  display:
    v: Device.deviceName
  equivalence:
    v: narrower
  comment:
    v: Element `Device.name.display` is mapped to FHIR R4 element `Device.deviceName` as `SourceIsNarrowerThanTarget`.

code:
  v: Device.modelNumber
display:
  v: modelNumber
target:
  code:
    v: Device.modelNumber
  display:
    v: Device.modelNumber
  equivalence:
    v: equivalent
  comment:
    v: Element `Device.modelNumber` is mapped to FHIR R4 element `Device.modelNumber` as `Equivalent`.

code:
  v: Device.partNumber
display:
  v: partNumber
target:
  code:
    v: Device.partNumber
  display:
    v: Device.partNumber
  equivalence:
    v: equivalent
  comment:
    v: Element `Device.partNumber` is mapped to FHIR R4 element `Device.partNumber` as `Equivalent`. Alphanumeric Maximum 20.

code:
  v: Device.type
display:
  v: type
target:
  code:
    v: Device.type
  display:
    v: Device.type
  equivalence:
    v: equivalent
  comment:
    v: 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.

code:
  v: Device.version
display:
  v: version
target:
  code:
    v: Device.version
  display:
    v: Device.version
  equivalence:
    v: wider
  comment:
    v: Element `Device.version` is mapped to FHIR R4 element `Device.version` as `Equivalent`.

code:
  v: Device.version.type
display:
  v: type
target:
  code:
    v: Device.version.type
  display:
    v: Device.version.type
  equivalence:
    v: equivalent
  comment:
    v: Element `Device.version.type` is mapped to FHIR R4 element `Device.version.type` as `Equivalent`.

code:
  v: Device.version.component
display:
  v: component
target:
  code:
    v: Device.version.component
  display:
    v: Device.version.component
  equivalence:
    v: equivalent
  comment:
    v: 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.

code:
  v: Device.version.value
display:
  v: value
target:
  code:
    v: Device.version.value
  display:
    v: Device.version.value
  equivalence:
    v: equivalent
  comment:
    v: Element `Device.version.value` is mapped to FHIR R4 element `Device.version.value` as `Equivalent`.

code:
  v: Device.conformsTo
display:
  v: conformsTo
target:
  code:
    v: Device.specialization
  display:
    v: Device.specialization
  equivalence:
    v: wider
  comment:
    v: 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`.

code:
  v: Device.conformsTo.category
display:
  v: category
target:
  code:
    v: Device.specialization
  display:
    v: Device.specialization
  equivalence:
    v: narrower
  comment:
    v: Element `Device.conformsTo.category` is mapped to FHIR R4 element `Device.specialization` as `SourceIsNarrowerThanTarget`.

code:
  v: Device.conformsTo.specification
display:
  v: specification
target:
  code:
    v: Device.specialization
  display:
    v: Device.specialization
  equivalence:
    v: narrower
  comment:
    v: Element `Device.conformsTo.specification` is mapped to FHIR R4 element `Device.specialization` as `SourceIsNarrowerThanTarget`.

code:
  v: Device.property
display:
  v: property
target:
  code:
    v: Device.property
  display:
    v: Device.property
  equivalence:
    v: wider
  comment:
    v: 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.

code:
  v: Device.property.type
display:
  v: type
target:
  code:
    v: Device.property.type
  display:
    v: Device.property.type
  equivalence:
    v: equivalent
  comment:
    v: Element `Device.property.type` is mapped to FHIR R4 element `Device.property.type` as `Equivalent`.

code:
  v: Device.property.value[x]
display:
  v: value[x]
target:
  code:
    v: Device.property.valueCode
  display:
    v: Device.property.valueCode
  equivalence:
    v: relatedto
  comment:
    v: Element `Device.property.value[x]` is mapped to FHIR R4 element `Device.property.valueQuantity` as `RelatedTo`. Element `Device.property.value[x]` is mapped to FHIR R4 element `Device.property.valueCode` as `RelatedTo`. The mappings for `Device.property.value[x]` do not cover the following types: Attachment, boolean, integer, Range, string. The text element in CodeableConcept.text is used for properties which would usually be coded (such as the size of an implant, or a security classification) but for which there is not currently an appropriate concept in the vocabulary (e.g. a custom implant size, or a security classification which depends on configuration). Otherwise the string choice type is used for descriptive properties, or instructions.
target:
  code:
    v: Device.property.valueQuantity
  display:
    v: Device.property.valueQuantity
  equivalence:
    v: relatedto
  comment:
    v: 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.

code:
  v: Device.owner
display:
  v: owner
target:
  code:
    v: Device.owner
  display:
    v: Device.owner
  equivalence:
    v: equivalent
  comment:
    v: Element `Device.owner` is mapped to FHIR R4 element `Device.owner` as `Equivalent`.

code:
  v: Device.contact
display:
  v: contact
target:
  code:
    v: Device.contact
  display:
    v: Device.contact
  equivalence:
    v: equivalent
  comment:
    v: Element `Device.contact` is mapped to FHIR R4 element `Device.contact` as `Equivalent`. used for troubleshooting etc.

code:
  v: Device.location
display:
  v: location
target:
  code:
    v: Device.location
  display:
    v: Device.location
  equivalence:
    v: equivalent
  comment:
    v: Element `Device.location` is mapped to FHIR R4 element `Device.location` as `Equivalent`.

code:
  v: Device.url
display:
  v: url
target:
  code:
    v: Device.url
  display:
    v: Device.url
  equivalence:
    v: equivalent
  comment:
    v: 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.

code:
  v: Device.note
display:
  v: note
target:
  code:
    v: Device.note
  display:
    v: Device.note
  equivalence:
    v: equivalent
  comment:
    v: Element `Device.note` is mapped to FHIR R4 element `Device.note` as `Equivalent`.

code:
  v: Device.safety
display:
  v: safety
target:
  code:
    v: Device.safety
  display:
    v: Device.safety
  equivalence:
    v: equivalent
  comment:
    v: Element `Device.safety` is mapped to FHIR R4 element `Device.safety` as `Equivalent`.

code:
  v: Device.parent
display:
  v: parent
target:
  code:
    v: Device.parent
  display:
    v: Device.parent
  equivalence:
    v: equivalent
  comment:
    v: 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.

source:
  v: http://hl7.org/fhir/StructureDefinition/Device
  l: Device
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.displayName
  l: extension-Device.displayName
target version:
  v: 0.1.0
element:
  code:
    v: Device.displayName
  display:
    v: displayName
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: 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.

source:
  v: http://hl7.org/fhir/StructureDefinition/Device
  l: Device
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.definition
  l: extension-Device.definition
target version:
  v: 0.1.0
element:
  code:
    v: Device.definition
  display:
    v: definition
  target:
    code:
      v: Extension
    equivalence:
      v: equivalent
    comment:
      v: 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.

source:
  v: http://hl7.org/fhir/StructureDefinition/Device
  l: Device
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.udiCarrier.entryType
  l: extension-Device.udiCarrier.entryType
target version:
  v: 0.1.0
element:
  code:
    v: Device.udiCarrier.entryType
  display:
    v: entryType
  target:
    code:
      v: Extension
    equivalence:
      v: equivalent
    comment:
      v: 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.

source:
  v: http://hl7.org/fhir/StructureDefinition/Device
  l: Device
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.availabilityStatus
  l: extension-Device.availabilityStatus
target version:
  v: 0.1.0
element:
  code:
    v: Device.availabilityStatus
  display:
    v: availabilityStatus
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: 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).

source:
  v: http://hl7.org/fhir/StructureDefinition/Device
  l: Device
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.biologicalSourceEvent
  l: extension-Device.biologicalSourceEvent
target version:
  v: 0.1.0
element:
  code:
    v: Device.biologicalSourceEvent
  display:
    v: biologicalSourceEvent
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: 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.

source:
  v: http://hl7.org/fhir/StructureDefinition/Device
  l: Device
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.category
  l: extension-Device.category
target version:
  v: 0.1.0
element:
  code:
    v: Device.category
  display:
    v: category
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: 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).

source:
  v: http://hl7.org/fhir/StructureDefinition/Device
  l: Device
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.version.installDate
  l: extension-Device.version.installDate
target version:
  v: 0.1.0
element:
  code:
    v: Device.version.installDate
  display:
    v: installDate
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: 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).

source:
  v: http://hl7.org/fhir/StructureDefinition/Device
  l: Device
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.conformsTo.version
  l: extension-Device.conformsTo.version
target version:
  v: 0.1.0
element:
  code:
    v: Device.conformsTo.version
  display:
    v: version
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: 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).

source:
  v: http://hl7.org/fhir/StructureDefinition/Device
  l: Device
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.property.value
  l: extension-Device.property.value
target version:
  v: 0.1.0
element:
  code:
    v: Device.property.value[x]
  display:
    v: value[x]
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: 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.

source:
  v: http://hl7.org/fhir/StructureDefinition/Device
  l: Device
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.mode
  l: extension-Device.mode
target version:
  v: 0.1.0
element:
  code:
    v: Device.mode
  display:
    v: mode
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: 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).

source:
  v: http://hl7.org/fhir/StructureDefinition/Device
  l: Device
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.cycle
  l: extension-Device.cycle
target version:
  v: 0.1.0
element:
  code:
    v: Device.cycle
  display:
    v: cycle
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: 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).

source:
  v: http://hl7.org/fhir/StructureDefinition/Device
  l: Device
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.duration
  l: extension-Device.duration
target version:
  v: 0.1.0
element:
  code:
    v: Device.duration
  display:
    v: duration
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: 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).

source:
  v: http://hl7.org/fhir/StructureDefinition/Device
  l: Device
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.endpoint
  l: extension-Device.endpoint
target version:
  v: 0.1.0
element:
  code:
    v: Device.endpoint
  display:
    v: endpoint
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: 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).

source:
  v: http://hl7.org/fhir/StructureDefinition/Device
  l: Device
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.gateway
  l: extension-Device.gateway
target version:
  v: 0.1.0
element:
  code:
    v: Device.gateway
  display:
    v: gateway
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: 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.