FHIR IG analytics

Resources that use this resource

No resources found

Resources that this resource uses

Narrative

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

Source1

{
  "resourceType": "ConceptMap",
  "id": "R5-Device-element-map-to-R4",
  "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-r5.r4"
          }
        ]
      }
    },
    {
      "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-r5.r4"
          }
        ]
      }
    }
  ],
  "url": "http://hl7.org/fhir/uv/xver/ConceptMap/R5-Device-element-map-to-R4",
  "version": "0.1.0",
  "name": "R5DeviceElementMapToR4",
  "title": "Cross-version mapping for FHIR R5 Device to FHIR R4 Device",
  "status": "active",
  "experimental": false,
  "date": "2026-03-17T16:04:44.9538459-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 R5 Device to FHIR R4.",
  "jurisdiction": [
    {
      "coding": [
        {
          "system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code": "001",
          "display": "World"
        }
      ]
    }
  ],
  "sourceCanonical": "http://hl7.org/fhir/5.0",
  "targetUri": "http://hl7.org/fhir/4.0",
  "group": [
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/StructureDefinition/Device",
      "targetVersion": "4.0.1",
      "element": [
        {
          "code": "Device.meta",
          "display": "meta",
          "target": [
            {
              "code": "Device.meta",
              "display": "Device.meta",
              "equivalence": "equivalent",
              "comment": "Element `Device.meta` is mapped to FHIR R4 element `Device.meta` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.implicitRules",
          "display": "implicitRules",
          "target": [
            {
              "code": "Device.implicitRules",
              "display": "Device.implicitRules",
              "equivalence": "equivalent",
              "comment": "Element `Device.implicitRules` is mapped to FHIR R4 element `Device.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 its narrative along with other profiles, value sets, etc."
            }
          ]
        },
        {
          "code": "Device.language",
          "display": "language",
          "target": [
            {
              "code": "Device.language",
              "display": "Device.language",
              "equivalence": "equivalent",
              "comment": "Element `Device.language` is mapped to FHIR R4 element `Device.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",
              "equivalence": "equivalent",
              "comment": "Element `Device.text` is mapped to FHIR R4 element `Device.text` as `Equivalent`.\nContained 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."
            }
          ]
        },
        {
          "code": "Device.contained",
          "display": "contained",
          "target": [
            {
              "code": "Device.contained",
              "display": "Device.contained",
              "equivalence": "equivalent",
              "comment": "Element `Device.contained` is mapped to FHIR R4 element `Device.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",
              "equivalence": "equivalent",
              "comment": "Element `Device.identifier` is mapped to FHIR R4 element `Device.identifier` as `Equivalent`.\nCertain 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."
            }
          ]
        },
        {
          "code": "Device.displayName",
          "display": "displayName",
          "target": [
            {
              "code": "Device.deviceName",
              "display": "Device.deviceName",
              "equivalence": "relatedto",
              "comment": "Element `Device.displayName` is mapped to FHIR R4 element `Device.deviceName` as `RelatedTo`.\nThe mappings for `Device.displayName` do not cover the following types: string.\nThe mappings for `Device.displayName` do not cover the following types based on type expansion: value."
            }
          ]
        },
        {
          "code": "Device.definition",
          "display": "definition",
          "target": [
            {
              "code": "Device.definition",
              "display": "Device.definition",
              "equivalence": "wider",
              "comment": "Element `Device.definition` is mapped to FHIR R4 element `Device.definition` as `SourceIsBroaderThanTarget`.\nThe mappings for `Device.definition` do not cover the following types: CodeableReference.\nThe mappings for `Device.definition` do not cover the following types based on type expansion: concept."
            }
          ]
        },
        {
          "code": "Device.udiCarrier",
          "display": "udiCarrier",
          "target": [
            {
              "code": "Device.udiCarrier",
              "display": "Device.udiCarrier",
              "equivalence": "wider",
              "comment": "Element `Device.udiCarrier` is mapped to FHIR R4 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",
              "equivalence": "equivalent",
              "comment": "Element `Device.udiCarrier.deviceIdentifier` is mapped to FHIR R4 element `Device.udiCarrier.deviceIdentifier` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.udiCarrier.issuer",
          "display": "issuer",
          "target": [
            {
              "code": "Device.udiCarrier.issuer",
              "display": "Device.udiCarrier.issuer",
              "equivalence": "equivalent",
              "comment": "Element `Device.udiCarrier.issuer` is mapped to FHIR R4 element `Device.udiCarrier.issuer` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.udiCarrier.jurisdiction",
          "display": "jurisdiction",
          "target": [
            {
              "code": "Device.udiCarrier.jurisdiction",
              "display": "Device.udiCarrier.jurisdiction",
              "equivalence": "equivalent",
              "comment": "Element `Device.udiCarrier.jurisdiction` is mapped to FHIR R4 element `Device.udiCarrier.jurisdiction` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.udiCarrier.carrierAIDC",
          "display": "carrierAIDC",
          "target": [
            {
              "code": "Device.udiCarrier.carrierAIDC",
              "display": "Device.udiCarrier.carrierAIDC",
              "equivalence": "equivalent",
              "comment": "Element `Device.udiCarrier.carrierAIDC` is mapped to FHIR R4 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",
              "equivalence": "equivalent",
              "comment": "Element `Device.udiCarrier.carrierHRF` is mapped to FHIR R4 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",
              "equivalence": "wider",
              "comment": "Element `Device.udiCarrier.entryType` is mapped to FHIR R4 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",
              "equivalence": "equivalent",
              "comment": "Element `Device.status` is mapped to FHIR R4 element `Device.status` as `SourceIsNarrowerThanTarget`.\nThe mappings for `Device.status` do not allow expression of the necessary codes, per the bindings on the source and target."
            }
          ]
        },
        {
          "code": "Device.manufacturer",
          "display": "manufacturer",
          "target": [
            {
              "code": "Device.manufacturer",
              "display": "Device.manufacturer",
              "equivalence": "equivalent",
              "comment": "Element `Device.manufacturer` is mapped to FHIR R4 element `Device.manufacturer` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.manufactureDate",
          "display": "manufactureDate",
          "target": [
            {
              "code": "Device.manufactureDate",
              "display": "Device.manufactureDate",
              "equivalence": "equivalent",
              "comment": "Element `Device.manufactureDate` is mapped to FHIR R4 element `Device.manufactureDate` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.expirationDate",
          "display": "expirationDate",
          "target": [
            {
              "code": "Device.expirationDate",
              "display": "Device.expirationDate",
              "equivalence": "equivalent",
              "comment": "Element `Device.expirationDate` is mapped to FHIR R4 element `Device.expirationDate` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.lotNumber",
          "display": "lotNumber",
          "target": [
            {
              "code": "Device.lotNumber",
              "display": "Device.lotNumber",
              "equivalence": "equivalent",
              "comment": "Element `Device.lotNumber` is mapped to FHIR R4 element `Device.lotNumber` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.serialNumber",
          "display": "serialNumber",
          "target": [
            {
              "code": "Device.serialNumber",
              "display": "Device.serialNumber",
              "equivalence": "equivalent",
              "comment": "Element `Device.serialNumber` is mapped to FHIR R4 element `Device.serialNumber` as `Equivalent`.\nAlphanumeric 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": "Device.name",
          "display": "name",
          "target": [
            {
              "code": "Device.deviceName",
              "display": "Device.deviceName",
              "equivalence": "wider",
              "comment": "Element `Device.name` is mapped to FHIR R4 element `Device.deviceName` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.name.value",
          "display": "value",
          "target": [
            {
              "code": "Device.deviceName",
              "display": "Device.deviceName",
              "equivalence": "equivalent",
              "comment": "Element `Device.name.value` is mapped to FHIR R4 element `Device.deviceName.name` as `Equivalent`.\nElement `Device.name.value` is mapped to FHIR R4 element `Device.deviceName` as `SourceIsNarrowerThanTarget`."
            },
            {
              "code": "Device.deviceName.name",
              "display": "Device.deviceName.name",
              "equivalence": "equivalent",
              "comment": "Element `Device.name.value` is mapped to FHIR R4 element `Device.deviceName.name` as `Equivalent`.\nElement `Device.name.value` is mapped to FHIR R4 element `Device.deviceName` as `SourceIsNarrowerThanTarget`."
            }
          ]
        },
        {
          "code": "Device.name.type",
          "display": "type",
          "target": [
            {
              "code": "Device.deviceName.type",
              "display": "Device.deviceName.type",
              "equivalence": "narrower",
              "comment": "Element `Device.name.type` is mapped to FHIR R4 element `Device.deviceName.type` as `SourceIsNarrowerThanTarget`.\nThe mappings for `Device.name.type` do not allow expression of the necessary codes, per the bindings on the source and target."
            }
          ]
        },
        {
          "code": "Device.name.display",
          "display": "display",
          "target": [
            {
              "code": "Device.deviceName",
              "display": "Device.deviceName",
              "equivalence": "narrower",
              "comment": "Element `Device.name.display` is mapped to FHIR R4 element `Device.deviceName` as `SourceIsNarrowerThanTarget`."
            }
          ]
        },
        {
          "code": "Device.modelNumber",
          "display": "modelNumber",
          "target": [
            {
              "code": "Device.modelNumber",
              "display": "Device.modelNumber",
              "equivalence": "equivalent",
              "comment": "Element `Device.modelNumber` is mapped to FHIR R4 element `Device.modelNumber` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.partNumber",
          "display": "partNumber",
          "target": [
            {
              "code": "Device.partNumber",
              "display": "Device.partNumber",
              "equivalence": "equivalent",
              "comment": "Element `Device.partNumber` is mapped to FHIR R4 element `Device.partNumber` as `Equivalent`.\nAlphanumeric Maximum 20."
            }
          ]
        },
        {
          "code": "Device.type",
          "display": "type",
          "target": [
            {
              "code": "Device.type",
              "display": "Device.type",
              "equivalence": "equivalent",
              "comment": "Element `Device.type` is mapped to FHIR R4 element `Device.type` as `SourceIsBroaderThanTarget`.\nMultiple 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": "Device.version",
          "display": "version",
          "target": [
            {
              "code": "Device.version",
              "display": "Device.version",
              "equivalence": "wider",
              "comment": "Element `Device.version` is mapped to FHIR R4 element `Device.version` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.version.type",
          "display": "type",
          "target": [
            {
              "code": "Device.version.type",
              "display": "Device.version.type",
              "equivalence": "equivalent",
              "comment": "Element `Device.version.type` is mapped to FHIR R4 element `Device.version.type` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.version.component",
          "display": "component",
          "target": [
            {
              "code": "Device.version.component",
              "display": "Device.version.component",
              "equivalence": "equivalent",
              "comment": "Element `Device.version.component` is mapped to FHIR R4 element `Device.version.component` as `Equivalent`.\nNote 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": "Device.version.value",
          "display": "value",
          "target": [
            {
              "code": "Device.version.value",
              "display": "Device.version.value",
              "equivalence": "equivalent",
              "comment": "Element `Device.version.value` is mapped to FHIR R4 element `Device.version.value` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.conformsTo",
          "display": "conformsTo",
          "target": [
            {
              "code": "Device.specialization",
              "display": "Device.specialization",
              "equivalence": "wider",
              "comment": "Element `Device.conformsTo` is mapped to FHIR R4 element `Device.specialization` as `Equivalent`.\nAn externally-defined extension that has been mapped as the representation of FHIR R5 element `Device.conformsTo`: `http://hl7.org/fhir/StructureDefinition/device-conformsTo`."
            }
          ]
        },
        {
          "code": "Device.conformsTo.category",
          "display": "category",
          "target": [
            {
              "code": "Device.specialization",
              "display": "Device.specialization",
              "equivalence": "narrower",
              "comment": "Element `Device.conformsTo.category` is mapped to FHIR R4 element `Device.specialization` as `SourceIsNarrowerThanTarget`."
            }
          ]
        },
        {
          "code": "Device.conformsTo.specification",
          "display": "specification",
          "target": [
            {
              "code": "Device.specialization",
              "display": "Device.specialization",
              "equivalence": "narrower",
              "comment": "Element `Device.conformsTo.specification` is mapped to FHIR R4 element `Device.specialization` as `SourceIsNarrowerThanTarget`."
            }
          ]
        },
        {
          "code": "Device.property",
          "display": "property",
          "target": [
            {
              "code": "Device.property",
              "display": "Device.property",
              "equivalence": "wider",
              "comment": "Element `Device.property` is mapped to FHIR R4 element `Device.property` as `Equivalent`.\nDynamic 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": "Device.property.type",
          "display": "type",
          "target": [
            {
              "code": "Device.property.type",
              "display": "Device.property.type",
              "equivalence": "equivalent",
              "comment": "Element `Device.property.type` is mapped to FHIR R4 element `Device.property.type` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.property.value[x]",
          "display": "value[x]",
          "target": [
            {
              "code": "Device.property.valueCode",
              "display": "Device.property.valueCode",
              "equivalence": "relatedto",
              "comment": "Element `Device.property.value[x]` is mapped to FHIR R4 element `Device.property.valueQuantity` as `RelatedTo`.\nElement `Device.property.value[x]` is mapped to FHIR R4 element `Device.property.valueCode` as `RelatedTo`.\nThe mappings for `Device.property.value[x]` do not cover the following types: Attachment, boolean, integer, Range, string.\nThe 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": "Device.property.valueQuantity",
              "display": "Device.property.valueQuantity",
              "equivalence": "relatedto",
              "comment": "Element `Device.property.value[x]` is mapped to FHIR R4 element `Device.property.valueQuantity` as `RelatedTo`.\nElement `Device.property.value[x]` is mapped to FHIR R4 element `Device.property.valueCode` as `RelatedTo`.\nThe mappings for `Device.property.value[x]` do not cover the following types: Attachment, boolean, integer, Range, string.\nThe 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": "Device.owner",
          "display": "owner",
          "target": [
            {
              "code": "Device.owner",
              "display": "Device.owner",
              "equivalence": "equivalent",
              "comment": "Element `Device.owner` is mapped to FHIR R4 element `Device.owner` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.contact",
          "display": "contact",
          "target": [
            {
              "code": "Device.contact",
              "display": "Device.contact",
              "equivalence": "equivalent",
              "comment": "Element `Device.contact` is mapped to FHIR R4 element `Device.contact` as `Equivalent`.\nused for troubleshooting etc."
            }
          ]
        },
        {
          "code": "Device.location",
          "display": "location",
          "target": [
            {
              "code": "Device.location",
              "display": "Device.location",
              "equivalence": "equivalent",
              "comment": "Element `Device.location` is mapped to FHIR R4 element `Device.location` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.url",
          "display": "url",
          "target": [
            {
              "code": "Device.url",
              "display": "Device.url",
              "equivalence": "equivalent",
              "comment": "Element `Device.url` is mapped to FHIR R4 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",
              "equivalence": "equivalent",
              "comment": "Element `Device.note` is mapped to FHIR R4 element `Device.note` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.safety",
          "display": "safety",
          "target": [
            {
              "code": "Device.safety",
              "display": "Device.safety",
              "equivalence": "equivalent",
              "comment": "Element `Device.safety` is mapped to FHIR R4 element `Device.safety` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.parent",
          "display": "parent",
          "target": [
            {
              "code": "Device.parent",
              "display": "Device.parent",
              "equivalence": "equivalent",
              "comment": "Element `Device.parent` is mapped to FHIR R4 element `Device.parent` as `Equivalent`.\nFor 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": "http://hl7.org/fhir/StructureDefinition/Device",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.displayName",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Device.displayName",
          "display": "displayName",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `Device.displayName` is mapped to FHIR R4 element `Device.deviceName` as `RelatedTo`.\nThe mappings for `Device.displayName` do not cover the following types: string.\nThe mappings for `Device.displayName` do not cover the following types based on type expansion: value."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.definition",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Device.definition",
          "display": "definition",
          "target": [
            {
              "code": "Extension",
              "equivalence": "equivalent",
              "comment": "Element `Device.definition` is mapped to FHIR R4 element `Device.definition` as `SourceIsBroaderThanTarget`.\nThe mappings for `Device.definition` do not cover the following types: CodeableReference.\nThe mappings for `Device.definition` do not cover the following types based on type expansion: concept."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.udiCarrier.entryType",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Device.udiCarrier.entryType",
          "display": "entryType",
          "target": [
            {
              "code": "Extension",
              "equivalence": "equivalent",
              "comment": "Element `Device.udiCarrier.entryType` is mapped to FHIR R4 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",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.availabilityStatus",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Device.availabilityStatus",
          "display": "availabilityStatus",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `Device.availabilityStatus` has a context of Device based on following the parent source element upwards and mapping to `Device`.\nElement `Device.availabilityStatus` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.biologicalSourceEvent",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Device.biologicalSourceEvent",
          "display": "biologicalSourceEvent",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `Device.biologicalSourceEvent` has a context of Device based on following the parent source element upwards and mapping to `Device`.\nElement `Device.biologicalSourceEvent` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nNecessary 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": "http://hl7.org/fhir/StructureDefinition/Device",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.category",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Device.category",
          "display": "category",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `Device.category` has a context of Device based on following the parent source element upwards and mapping to `Device`.\nElement `Device.category` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.version.installDate",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Device.version.installDate",
          "display": "installDate",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `Device.version.installDate` has a context of Device.version based on following the parent source element upwards and mapping to `Device`.\nElement `Device.version.installDate` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.conformsTo.version",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Device.conformsTo.version",
          "display": "version",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `Device.conformsTo.version` has a context of Device.specialization based on following the parent source element upwards and mapping to `Device`.\nElement `Device.conformsTo.version` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.property.value",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Device.property.value[x]",
          "display": "value[x]",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `Device.property.value[x]` is mapped to FHIR R4 element `Device.property.valueQuantity` as `RelatedTo`.\nElement `Device.property.value[x]` is mapped to FHIR R4 element `Device.property.valueCode` as `RelatedTo`.\nThe mappings for `Device.property.value[x]` do not cover the following types: Attachment, boolean, integer, Range, string.\nThe 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": "http://hl7.org/fhir/StructureDefinition/Device",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.mode",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Device.mode",
          "display": "mode",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `Device.mode` has a context of Device based on following the parent source element upwards and mapping to `Device`.\nElement `Device.mode` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.cycle",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Device.cycle",
          "display": "cycle",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `Device.cycle` has a context of Device based on following the parent source element upwards and mapping to `Device`.\nElement `Device.cycle` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.duration",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Device.duration",
          "display": "duration",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `Device.duration` has a context of Device based on following the parent source element upwards and mapping to `Device`.\nElement `Device.duration` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.endpoint",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Device.endpoint",
          "display": "endpoint",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `Device.endpoint` has a context of Device based on following the parent source element upwards and mapping to `Device`.\nElement `Device.endpoint` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.gateway",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Device.gateway",
          "display": "gateway",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `Device.gateway` has a context of Device based on following the parent source element upwards and mapping to `Device`.\nElement `Device.gateway` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nThe 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."
            }
          ]
        }
      ]
    }
  ]
}