FHIR © HL7.org  |  FHIRsmith 4.0.1  |  Server Home  |  XIG Home  |  XIG Stats  | 

FHIR IG analytics

Packagehl7.fhir.uv.xver-r4b.r5
Resource TypeConceptMap
IdConceptMap-R4B-Device-element-map-to-R5.json
FHIR VersionR5
Sourcehttp://hl7.org/fhir/uv/xver-r4b.r5/0.1.0/ConceptMap-R4B-Device-element-map-to-R5.html
URLhttp://hl7.org/fhir/uv/xver/ConceptMap/R4B-Device-element-map-to-R5
Version0.1.0
Statusactive
Date2026-03-17T16:03:51.3076028-05:00
NameR4BDeviceElementMapToR5
TitleCross-version mapping for FHIR R4B Device to FHIR R5 Device
Realmuv
Authorityhl7
DescriptionThis ConceptMap represents cross-version mappings for elements from a FHIR R4B Device to FHIR R5.

Resources that use this resource

No resources found


Resources that this resource uses

StructureDefinition
hl7.fhir.uv.xver-r4b.r5#0.1.0extension-Device.deviceName.typeR4B: udi-label-name | user-friendly-name | patient-reported-name | manufacturer-name | model-name | other
hl7.fhir.uv.xver-r4b.r5#0.1.0extension-Device.distinctIdentifierR4B: The distinct identification string (new)
hl7.fhir.uv.xver-r4b.r5#0.1.0extension-Device.property.valueCodeR4B: Property value as a code, e.g., NTP4 (synced to NTP) (new)
hl7.fhir.uv.xver-r4b.r5#0.1.0extension-Device.property.valueQuantityR4B: Property value as a quantity (new)
hl7.fhir.uv.xver-r4b.r5#0.1.0extension-Device.specialization.systemTypeR4B: The standard that is used to operate and communicate (new)
hl7.fhir.uv.xver-r4b.r5#0.1.0extension-Device.specialization.versionR4B: The version of the standard that is used to operate and communicate (new)
hl7.fhir.uv.xver-r4b.r5#0.1.0extension-Device.udiCarrier.entryTypeR4B: barcode | rfid | manual + additional codes

Narrative

Note: links and images are rebased to the (stated) source

Generated Narrative: ConceptMap R4B-Device-element-map-to-R5

Mapping from http://hl7.org/fhir/4.3 to http://hl7.org/fhir/5.0


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

Source Concept DetailsRelationshipTarget Concept DetailsComment
Codes from http://hl7.org/fhir/StructureDefinition/Device|4.3.0Codes from Device
Device.metametais equivalent toDevice.metaDevice.metaElement `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.implicitRulesimplicitRulesis equivalent toDevice.implicitRulesDevice.implicitRulesElement `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.languagelanguageis equivalent toDevice.languageDevice.languageElement `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.texttextis equivalent toDevice.textDevice.textElement `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.containedcontainedis equivalent toDevice.containedDevice.containedElement `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.identifieridentifieris equivalent toDevice.identifierDevice.identifierElement `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.definitiondefinitionis equivalent toDevice.definitionDevice.definitionElement `Device.definition` is mapped to FHIR R5 element `Device.definition` as `SourceIsNarrowerThanTarget`.
Device.udiCarrierudiCarrieris related toDevice.udiCarrierDevice.udiCarrierElement `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.deviceIdentifierdeviceIdentifieris equivalent toDevice.udiCarrier.deviceIdentifierDevice.udiCarrier.deviceIdentifierElement `Device.udiCarrier.deviceIdentifier` is mapped to FHIR R5 element `Device.udiCarrier.deviceIdentifier` as `Equivalent`.
Device.udiCarrier.issuerissueris equivalent toDevice.udiCarrier.issuerDevice.udiCarrier.issuerElement `Device.udiCarrier.issuer` is mapped to FHIR R5 element `Device.udiCarrier.issuer` as `Equivalent`.
Device.udiCarrier.jurisdictionjurisdictionis equivalent toDevice.udiCarrier.jurisdictionDevice.udiCarrier.jurisdictionElement `Device.udiCarrier.jurisdiction` is mapped to FHIR R5 element `Device.udiCarrier.jurisdiction` as `Equivalent`.
Device.udiCarrier.carrierAIDCcarrierAIDCis equivalent toDevice.udiCarrier.carrierAIDCDevice.udiCarrier.carrierAIDCElement `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.carrierHRFcarrierHRFis equivalent toDevice.udiCarrier.carrierHRFDevice.udiCarrier.carrierHRFElement `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.entryTypeentryTypeis related toDevice.udiCarrier.entryTypeDevice.udiCarrier.entryTypeElement `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.statusstatusis related toDevice.statusDevice.statusElement `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.manufacturermanufactureris equivalent toDevice.manufacturerDevice.manufacturerElement `Device.manufacturer` is mapped to FHIR R5 element `Device.manufacturer` as `Equivalent`.
Device.manufactureDatemanufactureDateis equivalent toDevice.manufactureDateDevice.manufactureDateElement `Device.manufactureDate` is mapped to FHIR R5 element `Device.manufactureDate` as `Equivalent`.
Device.expirationDateexpirationDateis equivalent toDevice.expirationDateDevice.expirationDateElement `Device.expirationDate` is mapped to FHIR R5 element `Device.expirationDate` as `Equivalent`.
Device.lotNumberlotNumberis equivalent toDevice.lotNumberDevice.lotNumberElement `Device.lotNumber` is mapped to FHIR R5 element `Device.lotNumber` as `Equivalent`.
Device.serialNumberserialNumberis equivalent toDevice.serialNumberDevice.serialNumberElement `Device.serialNumber` is mapped to FHIR R5 element `Device.serialNumber` as `Equivalent`. Alphanumeric Maximum 20.
Device.deviceNamedeviceNameis related toDevice.displayNameDevice.displayNameElement `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`.
is related toDevice.nameDevice.nameElement `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.namenameis equivalent toDevice.name.valueDevice.name.valueElement `Device.deviceName.name` is mapped to FHIR R5 element `Device.name.value` as `Equivalent`.
Device.deviceName.typetypeis related toDevice.name.typeDevice.name.typeElement `Device.deviceName.type` is mapped to FHIR R5 element `Device.name.type` as `SourceIsBroaderThanTarget`.
Device.modelNumbermodelNumberis equivalent toDevice.modelNumberDevice.modelNumberElement `Device.modelNumber` is mapped to FHIR R5 element `Device.modelNumber` as `Equivalent`.
Device.partNumberpartNumberis equivalent toDevice.partNumberDevice.partNumberElement `Device.partNumber` is mapped to FHIR R5 element `Device.partNumber` as `Equivalent`. Alphanumeric Maximum 20.
Device.typetypeis equivalent toDevice.typeDevice.typeElement `Device.type` is mapped to FHIR R5 element `Device.type` as `SourceIsNarrowerThanTarget`.
Device.specializationspecializationis related toDevice.conformsToDevice.conformsToElement `Device.specialization` is mapped to FHIR R5 element `Device.conformsTo` as `Equivalent`.
Device.versionversionis related toDevice.versionDevice.versionElement `Device.version` is mapped to FHIR R5 element `Device.version` as `Equivalent`.
Device.version.typetypeis equivalent toDevice.version.typeDevice.version.typeElement `Device.version.type` is mapped to FHIR R5 element `Device.version.type` as `Equivalent`.
Device.version.componentcomponentis equivalent toDevice.version.componentDevice.version.componentElement `Device.version.component` is mapped to FHIR R5 element `Device.version.component` as `Equivalent`.
Device.version.valuevalueis equivalent toDevice.version.valueDevice.version.valueElement `Device.version.value` is mapped to FHIR R5 element `Device.version.value` as `Equivalent`.
Device.propertypropertyis related toDevice.propertyDevice.propertyElement `Device.property` is mapped to FHIR R5 element `Device.property` as `Equivalent`.
Device.property.typetypeis equivalent toDevice.property.typeDevice.property.typeElement `Device.property.type` is mapped to FHIR R5 element `Device.property.type` as `Equivalent`.
Device.ownerowneris equivalent toDevice.ownerDevice.ownerElement `Device.owner` is mapped to FHIR R5 element `Device.owner` as `Equivalent`.
Device.contactcontactis equivalent toDevice.contactDevice.contactElement `Device.contact` is mapped to FHIR R5 element `Device.contact` as `Equivalent`. used for troubleshooting etc.
Device.locationlocationis equivalent toDevice.locationDevice.locationElement `Device.location` is mapped to FHIR R5 element `Device.location` as `Equivalent`.
Device.urlurlis equivalent toDevice.urlDevice.urlElement `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.notenoteis equivalent toDevice.noteDevice.noteElement `Device.note` is mapped to FHIR R5 element `Device.note` as `Equivalent`.
Device.safetysafetyis equivalent toDevice.safetyDevice.safetyElement `Device.safety` is mapped to FHIR R5 element `Device.safety` as `Equivalent`.
Device.parentparentis equivalent toDevice.parentDevice.parentElement `Device.parent` is mapped to FHIR R5 element `Device.parent` as `Equivalent`.

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

Source CodeRelationshipTarget CodeComment
Device.meta (meta)is equivalent toDeviceAssociation.metaElement `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)is equivalent toDeviceAssociation.implicitRulesElement `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)is equivalent toDeviceAssociation.languageElement `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)is equivalent toDeviceAssociation.textElement `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)is equivalent toDeviceAssociation.containedElement `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)is equivalent toDeviceAssociation.identifierElement `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)is equivalent toDeviceAssociation.statusElement `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)is equivalent toDeviceAssociation.statusReasonElement `Device.statusReason` is mapped to FHIR R5 element `DeviceAssociation.statusReason` as `Equivalent`.
Device.patient (patient)is equivalent toDeviceAssociation.subjectElement `Device.patient` is mapped to FHIR R5 element `DeviceAssociation.subject` as `SourceIsNarrowerThanTarget`.

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

Source CodeRelationshipTarget CodeComment
Device.udiCarrier.entryType (entryType)is broader thanExtension (R4B: 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.3.0 to R4B: The distinct identification string (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Device.distinctIdentifier (distinctIdentifier)is broader thanExtension (R4B: 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)*.

Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/Device|4.3.0 to R4B: udi-label-name | user-friendly-name | patient-reported-name | manufacturer-name | model-name | otherversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
Device.deviceName.type (type)is broader thanExtension (R4B: udi-label-name | user-friendly-name | patient-reported-name | manufacturer-name | model-name | other)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.3.0 to R4B: The standard that is used to operate and communicate (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Device.specialization.systemType (systemType)is broader thanExtension (R4B: 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.3.0 to R4B: The version of the standard that is used to operate and communicate (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Device.specialization.version (version)is broader thanExtension (R4B: 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.3.0 to R4B: Property value as a quantity (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Device.property.valueQuantity (valueQuantity)is broader thanExtension (R4B: 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.3.0 to R4B: Property value as a code, e.g., NTP4 (synced to NTP) (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Device.property.valueCode (valueCode)is broader thanExtension (R4B: Property value as a code, e.g., NTP4 (synced to NTP) (new))Element `Device.property.valueCode` has a context of Device.property based on following the parent source element upwards and mapping to `Device`. Element `Device.property.valueCode` has a context of DeviceAssociation based on following the parent source element upwards and mapping to `DeviceAssociation`. Element `Device.property.valueCode` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

Source1

{
  "resourceType": "ConceptMap",
  "id": "R4B-Device-element-map-to-R5",
  "text": {
    "status": "generated",
    "div": "<!-- snip (see above) -->"
  },
  "extension": [
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
      "valueCode": "fhir"
    },
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
      "valueInteger": 0,
      "_valueInteger": {
        "extension": [
          {
            "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
            "valueCanonical": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4b.r5"
          }
        ]
      }
    },
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
      "valueCode": "trial-use",
      "_valueCode": {
        "extension": [
          {
            "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
            "valueCanonical": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4b.r5"
          }
        ]
      }
    }
  ],
  "url": "http://hl7.org/fhir/uv/xver/ConceptMap/R4B-Device-element-map-to-R5",
  "version": "0.1.0",
  "name": "R4BDeviceElementMapToR5",
  "title": "Cross-version mapping for FHIR R4B Device to FHIR R5 Device",
  "status": "active",
  "experimental": false,
  "date": "2026-03-17T16:03:51.3076028-05:00",
  "contact": [
    {
      "name": "FHIR Infrastructure",
      "telecom": [
        {
          "system": "url",
          "value": "http://www.hl7.org/Special/committees/fiwg"
        }
      ]
    }
  ],
  "description": "This ConceptMap represents cross-version mappings for elements from a FHIR R4B Device to FHIR R5.",
  "jurisdiction": [
    {
      "coding": [
        {
          "system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code": "001",
          "display": "World"
        }
      ]
    }
  ],
  "sourceScopeCanonical": "http://hl7.org/fhir/4.3",
  "targetScopeUri": "http://hl7.org/fhir/5.0",
  "group": [
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device|4.3.0",
      "target": "http://hl7.org/fhir/StructureDefinition/Device|5.0.0",
      "element": [
        {
          "code": "Device.meta",
          "display": "meta",
          "target": [
            {
              "code": "Device.meta",
              "display": "Device.meta",
              "relationship": "equivalent",
              "comment": "Element `Device.meta` is mapped to FHIR R5 element `Device.meta` as `Equivalent`.\nElement `Device.meta` is mapped to FHIR R5 element `DeviceAssociation.meta` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.implicitRules",
          "display": "implicitRules",
          "target": [
            {
              "code": "Device.implicitRules",
              "display": "Device.implicitRules",
              "relationship": "equivalent",
              "comment": "Element `Device.implicitRules` is mapped to FHIR R5 element `Device.implicitRules` as `Equivalent`.\nElement `Device.implicitRules` is mapped to FHIR R5 element `DeviceAssociation.implicitRules` as `Equivalent`.\nAsserting 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."
            }
          ]
        },
        {
          "code": "Device.language",
          "display": "language",
          "target": [
            {
              "code": "Device.language",
              "display": "Device.language",
              "relationship": "equivalent",
              "comment": "Element `Device.language` is mapped to FHIR R5 element `Device.language` as `Equivalent`.\nElement `Device.language` is mapped to FHIR R5 element `DeviceAssociation.language` as `Equivalent`.\nLanguage 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)."
            }
          ]
        },
        {
          "code": "Device.text",
          "display": "text",
          "target": [
            {
              "code": "Device.text",
              "display": "Device.text",
              "relationship": "equivalent",
              "comment": "Element `Device.text` is mapped to FHIR R5 element `Device.text` as `Equivalent`.\nElement `Device.text` is mapped to FHIR R5 element `DeviceAssociation.text` as `Equivalent`.\nContained 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."
            }
          ]
        },
        {
          "code": "Device.contained",
          "display": "contained",
          "target": [
            {
              "code": "Device.contained",
              "display": "Device.contained",
              "relationship": "equivalent",
              "comment": "Element `Device.contained` is mapped to FHIR R5 element `Device.contained` as `Equivalent`.\nElement `Device.contained` is mapped to FHIR R5 element `DeviceAssociation.contained` as `Equivalent`.\nThis 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."
            }
          ]
        },
        {
          "code": "Device.identifier",
          "display": "identifier",
          "target": [
            {
              "code": "Device.identifier",
              "display": "Device.identifier",
              "relationship": "equivalent",
              "comment": "Element `Device.identifier` is mapped to FHIR R5 element `Device.identifier` as `Equivalent`.\nElement `Device.identifier` is mapped to FHIR R5 element `DeviceAssociation.identifier` as `Equivalent`.\nThe 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."
            }
          ]
        },
        {
          "code": "Device.definition",
          "display": "definition",
          "target": [
            {
              "code": "Device.definition",
              "display": "Device.definition",
              "relationship": "equivalent",
              "comment": "Element `Device.definition` is mapped to FHIR R5 element `Device.definition` as `SourceIsNarrowerThanTarget`."
            }
          ]
        },
        {
          "code": "Device.udiCarrier",
          "display": "udiCarrier",
          "target": [
            {
              "code": "Device.udiCarrier",
              "display": "Device.udiCarrier",
              "relationship": "related-to",
              "comment": "Element `Device.udiCarrier` is mapped to FHIR R5 element `Device.udiCarrier` as `Equivalent`.\nUDI 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": "Device.udiCarrier.deviceIdentifier",
          "display": "deviceIdentifier",
          "target": [
            {
              "code": "Device.udiCarrier.deviceIdentifier",
              "display": "Device.udiCarrier.deviceIdentifier",
              "relationship": "equivalent",
              "comment": "Element `Device.udiCarrier.deviceIdentifier` is mapped to FHIR R5 element `Device.udiCarrier.deviceIdentifier` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.udiCarrier.issuer",
          "display": "issuer",
          "target": [
            {
              "code": "Device.udiCarrier.issuer",
              "display": "Device.udiCarrier.issuer",
              "relationship": "equivalent",
              "comment": "Element `Device.udiCarrier.issuer` is mapped to FHIR R5 element `Device.udiCarrier.issuer` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.udiCarrier.jurisdiction",
          "display": "jurisdiction",
          "target": [
            {
              "code": "Device.udiCarrier.jurisdiction",
              "display": "Device.udiCarrier.jurisdiction",
              "relationship": "equivalent",
              "comment": "Element `Device.udiCarrier.jurisdiction` is mapped to FHIR R5 element `Device.udiCarrier.jurisdiction` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.udiCarrier.carrierAIDC",
          "display": "carrierAIDC",
          "target": [
            {
              "code": "Device.udiCarrier.carrierAIDC",
              "display": "Device.udiCarrier.carrierAIDC",
              "relationship": "equivalent",
              "comment": "Element `Device.udiCarrier.carrierAIDC` is mapped to FHIR R5 element `Device.udiCarrier.carrierAIDC` as `Equivalent`.\nThe 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": "Device.udiCarrier.carrierHRF",
          "display": "carrierHRF",
          "target": [
            {
              "code": "Device.udiCarrier.carrierHRF",
              "display": "Device.udiCarrier.carrierHRF",
              "relationship": "equivalent",
              "comment": "Element `Device.udiCarrier.carrierHRF` is mapped to FHIR R5 element `Device.udiCarrier.carrierHRF` as `Equivalent`.\nIf separate barcodes for DI and PI are present, concatenate the string with DI first and in order of human readable expression on label."
            }
          ]
        },
        {
          "code": "Device.udiCarrier.entryType",
          "display": "entryType",
          "target": [
            {
              "code": "Device.udiCarrier.entryType",
              "display": "Device.udiCarrier.entryType",
              "relationship": "related-to",
              "comment": "Element `Device.udiCarrier.entryType` is mapped to FHIR R5 element `Device.udiCarrier.entryType` as `RelatedTo`.\nThe mappings for `Device.udiCarrier.entryType` do not allow expression of the necessary codes, per the bindings on the source and target."
            }
          ]
        },
        {
          "code": "Device.status",
          "display": "status",
          "target": [
            {
              "code": "Device.status",
              "display": "Device.status",
              "relationship": "related-to",
              "comment": "Element `Device.status` is mapped to FHIR R5 element `Device.status` as `SourceIsBroaderThanTarget`.\nElement `Device.status` is mapped to FHIR R5 element `DeviceAssociation.status` as `SourceIsNarrowerThanTarget`.\nThe mappings for `Device.status` do not allow expression of the necessary codes, per the bindings on the source and target.\nThis 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."
            }
          ]
        },
        {
          "code": "Device.manufacturer",
          "display": "manufacturer",
          "target": [
            {
              "code": "Device.manufacturer",
              "display": "Device.manufacturer",
              "relationship": "equivalent",
              "comment": "Element `Device.manufacturer` is mapped to FHIR R5 element `Device.manufacturer` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.manufactureDate",
          "display": "manufactureDate",
          "target": [
            {
              "code": "Device.manufactureDate",
              "display": "Device.manufactureDate",
              "relationship": "equivalent",
              "comment": "Element `Device.manufactureDate` is mapped to FHIR R5 element `Device.manufactureDate` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.expirationDate",
          "display": "expirationDate",
          "target": [
            {
              "code": "Device.expirationDate",
              "display": "Device.expirationDate",
              "relationship": "equivalent",
              "comment": "Element `Device.expirationDate` is mapped to FHIR R5 element `Device.expirationDate` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.lotNumber",
          "display": "lotNumber",
          "target": [
            {
              "code": "Device.lotNumber",
              "display": "Device.lotNumber",
              "relationship": "equivalent",
              "comment": "Element `Device.lotNumber` is mapped to FHIR R5 element `Device.lotNumber` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.serialNumber",
          "display": "serialNumber",
          "target": [
            {
              "code": "Device.serialNumber",
              "display": "Device.serialNumber",
              "relationship": "equivalent",
              "comment": "Element `Device.serialNumber` is mapped to FHIR R5 element `Device.serialNumber` as `Equivalent`.\nAlphanumeric Maximum 20."
            }
          ]
        },
        {
          "code": "Device.deviceName",
          "display": "deviceName",
          "target": [
            {
              "code": "Device.displayName",
              "display": "Device.displayName",
              "relationship": "related-to",
              "comment": "Element `Device.deviceName` is mapped to FHIR R5 element `Device.displayName` as `RelatedTo`.\nElement `Device.deviceName` is mapped to FHIR R5 element `Device.name` as `Equivalent`."
            },
            {
              "code": "Device.name",
              "display": "Device.name",
              "relationship": "related-to",
              "comment": "Element `Device.deviceName` is mapped to FHIR R5 element `Device.displayName` as `RelatedTo`.\nElement `Device.deviceName` is mapped to FHIR R5 element `Device.name` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.deviceName.name",
          "display": "name",
          "target": [
            {
              "code": "Device.name.value",
              "display": "Device.name.value",
              "relationship": "equivalent",
              "comment": "Element `Device.deviceName.name` is mapped to FHIR R5 element `Device.name.value` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.deviceName.type",
          "display": "type",
          "target": [
            {
              "code": "Device.name.type",
              "display": "Device.name.type",
              "relationship": "related-to",
              "comment": "Element `Device.deviceName.type` is mapped to FHIR R5 element `Device.name.type` as `SourceIsBroaderThanTarget`."
            }
          ]
        },
        {
          "code": "Device.modelNumber",
          "display": "modelNumber",
          "target": [
            {
              "code": "Device.modelNumber",
              "display": "Device.modelNumber",
              "relationship": "equivalent",
              "comment": "Element `Device.modelNumber` is mapped to FHIR R5 element `Device.modelNumber` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.partNumber",
          "display": "partNumber",
          "target": [
            {
              "code": "Device.partNumber",
              "display": "Device.partNumber",
              "relationship": "equivalent",
              "comment": "Element `Device.partNumber` is mapped to FHIR R5 element `Device.partNumber` as `Equivalent`.\nAlphanumeric Maximum 20."
            }
          ]
        },
        {
          "code": "Device.type",
          "display": "type",
          "target": [
            {
              "code": "Device.type",
              "display": "Device.type",
              "relationship": "equivalent",
              "comment": "Element `Device.type` is mapped to FHIR R5 element `Device.type` as `SourceIsNarrowerThanTarget`."
            }
          ]
        },
        {
          "code": "Device.specialization",
          "display": "specialization",
          "target": [
            {
              "code": "Device.conformsTo",
              "display": "Device.conformsTo",
              "relationship": "related-to",
              "comment": "Element `Device.specialization` is mapped to FHIR R5 element `Device.conformsTo` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.version",
          "display": "version",
          "target": [
            {
              "code": "Device.version",
              "display": "Device.version",
              "relationship": "related-to",
              "comment": "Element `Device.version` is mapped to FHIR R5 element `Device.version` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.version.type",
          "display": "type",
          "target": [
            {
              "code": "Device.version.type",
              "display": "Device.version.type",
              "relationship": "equivalent",
              "comment": "Element `Device.version.type` is mapped to FHIR R5 element `Device.version.type` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.version.component",
          "display": "component",
          "target": [
            {
              "code": "Device.version.component",
              "display": "Device.version.component",
              "relationship": "equivalent",
              "comment": "Element `Device.version.component` is mapped to FHIR R5 element `Device.version.component` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.version.value",
          "display": "value",
          "target": [
            {
              "code": "Device.version.value",
              "display": "Device.version.value",
              "relationship": "equivalent",
              "comment": "Element `Device.version.value` is mapped to FHIR R5 element `Device.version.value` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.property",
          "display": "property",
          "target": [
            {
              "code": "Device.property",
              "display": "Device.property",
              "relationship": "related-to",
              "comment": "Element `Device.property` is mapped to FHIR R5 element `Device.property` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.property.type",
          "display": "type",
          "target": [
            {
              "code": "Device.property.type",
              "display": "Device.property.type",
              "relationship": "equivalent",
              "comment": "Element `Device.property.type` is mapped to FHIR R5 element `Device.property.type` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.owner",
          "display": "owner",
          "target": [
            {
              "code": "Device.owner",
              "display": "Device.owner",
              "relationship": "equivalent",
              "comment": "Element `Device.owner` is mapped to FHIR R5 element `Device.owner` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.contact",
          "display": "contact",
          "target": [
            {
              "code": "Device.contact",
              "display": "Device.contact",
              "relationship": "equivalent",
              "comment": "Element `Device.contact` is mapped to FHIR R5 element `Device.contact` as `Equivalent`.\nused for troubleshooting etc."
            }
          ]
        },
        {
          "code": "Device.location",
          "display": "location",
          "target": [
            {
              "code": "Device.location",
              "display": "Device.location",
              "relationship": "equivalent",
              "comment": "Element `Device.location` is mapped to FHIR R5 element `Device.location` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.url",
          "display": "url",
          "target": [
            {
              "code": "Device.url",
              "display": "Device.url",
              "relationship": "equivalent",
              "comment": "Element `Device.url` is mapped to FHIR R5 element `Device.url` as `Equivalent`.\nIf the device is running a FHIR server, the network address should  be the Base URL from which a conformance statement may be retrieved."
            }
          ]
        },
        {
          "code": "Device.note",
          "display": "note",
          "target": [
            {
              "code": "Device.note",
              "display": "Device.note",
              "relationship": "equivalent",
              "comment": "Element `Device.note` is mapped to FHIR R5 element `Device.note` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.safety",
          "display": "safety",
          "target": [
            {
              "code": "Device.safety",
              "display": "Device.safety",
              "relationship": "equivalent",
              "comment": "Element `Device.safety` is mapped to FHIR R5 element `Device.safety` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.parent",
          "display": "parent",
          "target": [
            {
              "code": "Device.parent",
              "display": "Device.parent",
              "relationship": "equivalent",
              "comment": "Element `Device.parent` is mapped to FHIR R5 element `Device.parent` as `Equivalent`."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device|4.3.0",
      "target": "http://hl7.org/fhir/StructureDefinition/DeviceAssociation|5.0.0",
      "element": [
        {
          "code": "Device.meta",
          "display": "meta",
          "target": [
            {
              "code": "DeviceAssociation.meta",
              "display": "DeviceAssociation.meta",
              "relationship": "equivalent",
              "comment": "Element `Device.meta` is mapped to FHIR R5 element `Device.meta` as `Equivalent`.\nElement `Device.meta` is mapped to FHIR R5 element `DeviceAssociation.meta` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.implicitRules",
          "display": "implicitRules",
          "target": [
            {
              "code": "DeviceAssociation.implicitRules",
              "display": "DeviceAssociation.implicitRules",
              "relationship": "equivalent",
              "comment": "Element `Device.implicitRules` is mapped to FHIR R5 element `Device.implicitRules` as `Equivalent`.\nElement `Device.implicitRules` is mapped to FHIR R5 element `DeviceAssociation.implicitRules` as `Equivalent`.\nAsserting 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."
            }
          ]
        },
        {
          "code": "Device.language",
          "display": "language",
          "target": [
            {
              "code": "DeviceAssociation.language",
              "display": "DeviceAssociation.language",
              "relationship": "equivalent",
              "comment": "Element `Device.language` is mapped to FHIR R5 element `Device.language` as `Equivalent`.\nElement `Device.language` is mapped to FHIR R5 element `DeviceAssociation.language` as `Equivalent`.\nLanguage 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)."
            }
          ]
        },
        {
          "code": "Device.text",
          "display": "text",
          "target": [
            {
              "code": "DeviceAssociation.text",
              "display": "DeviceAssociation.text",
              "relationship": "equivalent",
              "comment": "Element `Device.text` is mapped to FHIR R5 element `Device.text` as `Equivalent`.\nElement `Device.text` is mapped to FHIR R5 element `DeviceAssociation.text` as `Equivalent`.\nContained 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."
            }
          ]
        },
        {
          "code": "Device.contained",
          "display": "contained",
          "target": [
            {
              "code": "DeviceAssociation.contained",
              "display": "DeviceAssociation.contained",
              "relationship": "equivalent",
              "comment": "Element `Device.contained` is mapped to FHIR R5 element `Device.contained` as `Equivalent`.\nElement `Device.contained` is mapped to FHIR R5 element `DeviceAssociation.contained` as `Equivalent`.\nThis 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."
            }
          ]
        },
        {
          "code": "Device.identifier",
          "display": "identifier",
          "target": [
            {
              "code": "DeviceAssociation.identifier",
              "display": "DeviceAssociation.identifier",
              "relationship": "equivalent",
              "comment": "Element `Device.identifier` is mapped to FHIR R5 element `Device.identifier` as `Equivalent`.\nElement `Device.identifier` is mapped to FHIR R5 element `DeviceAssociation.identifier` as `Equivalent`.\nThe 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."
            }
          ]
        },
        {
          "code": "Device.status",
          "display": "status",
          "target": [
            {
              "code": "DeviceAssociation.status",
              "display": "DeviceAssociation.status",
              "relationship": "equivalent",
              "comment": "Element `Device.status` is mapped to FHIR R5 element `Device.status` as `SourceIsBroaderThanTarget`.\nElement `Device.status` is mapped to FHIR R5 element `DeviceAssociation.status` as `SourceIsNarrowerThanTarget`.\nThe mappings for `Device.status` do not allow expression of the necessary codes, per the bindings on the source and target.\nThis 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."
            }
          ]
        },
        {
          "code": "Device.statusReason",
          "display": "statusReason",
          "target": [
            {
              "code": "DeviceAssociation.statusReason",
              "display": "DeviceAssociation.statusReason",
              "relationship": "equivalent",
              "comment": "Element `Device.statusReason` is mapped to FHIR R5 element `DeviceAssociation.statusReason` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.patient",
          "display": "patient",
          "target": [
            {
              "code": "DeviceAssociation.subject",
              "display": "DeviceAssociation.subject",
              "relationship": "equivalent",
              "comment": "Element `Device.patient` is mapped to FHIR R5 element `DeviceAssociation.subject` as `SourceIsNarrowerThanTarget`."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device|4.3.0",
      "target": "http://hl7.org/fhir/4.3/StructureDefinition/extension-Device.udiCarrier.entryType|0.1.0",
      "element": [
        {
          "code": "Device.udiCarrier.entryType",
          "display": "entryType",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Device.udiCarrier.entryType` is mapped to FHIR R5 element `Device.udiCarrier.entryType` as `RelatedTo`.\nThe mappings for `Device.udiCarrier.entryType` do not allow expression of the necessary codes, per the bindings on the source and target."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device|4.3.0",
      "target": "http://hl7.org/fhir/4.3/StructureDefinition/extension-Device.distinctIdentifier|0.1.0",
      "element": [
        {
          "code": "Device.distinctIdentifier",
          "display": "distinctIdentifier",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Device.distinctIdentifier` has a context of Device based on following the parent source element upwards and mapping to `Device`.\nElement `Device.distinctIdentifier` has a context of DeviceAssociation based on following the parent source element upwards and mapping to `DeviceAssociation`.\nElement `Device.distinctIdentifier` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).\nFor example, this applies to devices in the United States regulated under *Code of Federal Regulation 21CFR§1271.290(c)*."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device|4.3.0",
      "target": "http://hl7.org/fhir/4.3/StructureDefinition/extension-Device.deviceName.type|0.1.0",
      "element": [
        {
          "code": "Device.deviceName.type",
          "display": "type",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Device.deviceName.type` is mapped to FHIR R5 element `Device.name.type` as `SourceIsBroaderThanTarget`."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device|4.3.0",
      "target": "http://hl7.org/fhir/4.3/StructureDefinition/extension-Device.specialization.systemType|0.1.0",
      "element": [
        {
          "code": "Device.specialization.systemType",
          "display": "systemType",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Device.specialization.systemType` has a context of Device.conformsTo based on following the parent source element upwards and mapping to `Device`.\nElement `Device.specialization.systemType` has a context of DeviceAssociation based on following the parent source element upwards and mapping to `DeviceAssociation`.\nElement `Device.specialization.systemType` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device|4.3.0",
      "target": "http://hl7.org/fhir/4.3/StructureDefinition/extension-Device.specialization.version|0.1.0",
      "element": [
        {
          "code": "Device.specialization.version",
          "display": "version",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Device.specialization.version` has a context of Device.conformsTo based on following the parent source element upwards and mapping to `Device`.\nElement `Device.specialization.version` has a context of DeviceAssociation based on following the parent source element upwards and mapping to `DeviceAssociation`.\nElement `Device.specialization.version` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device|4.3.0",
      "target": "http://hl7.org/fhir/4.3/StructureDefinition/extension-Device.property.valueQuantity|0.1.0",
      "element": [
        {
          "code": "Device.property.valueQuantity",
          "display": "valueQuantity",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Device.property.valueQuantity` has a context of Device.property based on following the parent source element upwards and mapping to `Device`.\nElement `Device.property.valueQuantity` has a context of DeviceAssociation based on following the parent source element upwards and mapping to `DeviceAssociation`.\nElement `Device.property.valueQuantity` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device|4.3.0",
      "target": "http://hl7.org/fhir/4.3/StructureDefinition/extension-Device.property.valueCode|0.1.0",
      "element": [
        {
          "code": "Device.property.valueCode",
          "display": "valueCode",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Device.property.valueCode` has a context of Device.property based on following the parent source element upwards and mapping to `Device`.\nElement `Device.property.valueCode` has a context of DeviceAssociation based on following the parent source element upwards and mapping to `DeviceAssociation`.\nElement `Device.property.valueCode` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    }
  ]
}