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": "R3-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-r3.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-r3.r5"
          }
        ]
      }
    }
  ],
  "url": "http://hl7.org/fhir/uv/xver/ConceptMap/R3-Device-element-map-to-R5",
  "version": "0.1.0",
  "name": "R3DeviceElementMapToR5",
  "title": "Cross-version mapping for FHIR STU3 Device to FHIR R5 Device",
  "status": "active",
  "experimental": false,
  "date": "2026-03-17T16:04:59.4788914-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 STU3 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/3.0",
  "targetScopeUri": "http://hl7.org/fhir/5.0",
  "group": [
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device|3.0.2",
      "target": "http://hl7.org/fhir/StructureDefinition/Device|5.0.0",
      "element": [
        {
          "code": "Device.meta",
          "display": "meta",
          "target": [
            {
              "code": "Device.meta",
              "display": "Device.meta",
              "relationship": "related-to",
              "comment": "Element `Device.meta` is mapped to FHIR R5 element `Device.meta` as `SourceIsBroaderThanTarget`.\nElement `Device.meta` is mapped to FHIR R5 element `DeviceAssociation.meta` as `SourceIsBroaderThanTarget`.\nThe mappings for `Device.meta` do not cover the following types: Meta.\nThe mappings for `Device.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId."
            }
          ]
        },
        {
          "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. \n\nThis element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."
            }
          ]
        },
        {
          "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": "related-to",
              "comment": "Element `Device.text` is mapped to FHIR R5 element `Device.text` as `SourceIsBroaderThanTarget`.\nElement `Device.text` is mapped to FHIR R5 element `DeviceAssociation.text` as `SourceIsBroaderThanTarget`.\nThe mappings for `Device.text` do not cover the following types: Narrative.\nThe mappings for `Device.text` do not cover the following types based on type expansion: div, status.\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 in formation is added later."
            }
          ]
        },
        {
          "code": "Device.contained",
          "display": "contained",
          "target": [
            {
              "code": "Device.contained",
              "display": "Device.contained",
              "relationship": "related-to",
              "comment": "Element `Device.contained` is mapped to FHIR R5 element `Device.contained` as `SourceIsBroaderThanTarget`.\nElement `Device.contained` is mapped to FHIR R5 element `DeviceAssociation.contained` as `SourceIsBroaderThanTarget`.\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."
            }
          ]
        },
        {
          "code": "Device.identifier",
          "display": "identifier",
          "target": [
            {
              "code": "Device.identifier",
              "display": "Device.identifier",
              "relationship": "related-to",
              "comment": "Element `Device.identifier` is mapped to FHIR R5 element `Device.identifier` as `SourceIsBroaderThanTarget`.\nElement `Device.identifier` is mapped to FHIR R5 element `DeviceAssociation.identifier` as `SourceIsBroaderThanTarget`.\nThe mappings for `Device.identifier` do not cover the following types: Identifier.\nThe mappings for `Device.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value.\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.  For [UDI](https://hl7.org/fhir/device.html#5.11.3.2.2),  this element corresponds to the variable portion of the UDI that identifies the serial number of a specific device. See [UDI mappings](https://hl7.org/fhir/devi.html#udi) for a complete mapping of UDI parts to Device."
            }
          ]
        },
        {
          "code": "Device.udi",
          "display": "udi",
          "target": [
            {
              "code": "Device.udiCarrier",
              "display": "Device.udiCarrier",
              "relationship": "related-to",
              "comment": "Element `Device.udi` is mapped to FHIR R5 element `Device.udiCarrier` as `SourceIsNarrowerThanTarget`.\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.udi.deviceIdentifier",
          "display": "deviceIdentifier",
          "target": [
            {
              "code": "Device.udiCarrier.deviceIdentifier",
              "display": "Device.udiCarrier.deviceIdentifier",
              "relationship": "equivalent",
              "comment": "Element `Device.udi.deviceIdentifier` is mapped to FHIR R5 element `Device.udiCarrier.deviceIdentifier` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.udi.jurisdiction",
          "display": "jurisdiction",
          "target": [
            {
              "code": "Device.udiCarrier.jurisdiction",
              "display": "Device.udiCarrier.jurisdiction",
              "relationship": "equivalent",
              "comment": "Element `Device.udi.jurisdiction` is mapped to FHIR R5 element `Device.udiCarrier.jurisdiction` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.udi.carrierHRF",
          "display": "carrierHRF",
          "target": [
            {
              "code": "Device.udiCarrier.carrierHRF",
              "display": "Device.udiCarrier.carrierHRF",
              "relationship": "equivalent",
              "comment": "Element `Device.udi.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.udi.carrierAIDC",
          "display": "carrierAIDC",
          "target": [
            {
              "code": "Device.udiCarrier.carrierAIDC",
              "display": "Device.udiCarrier.carrierAIDC",
              "relationship": "equivalent",
              "comment": "Element `Device.udi.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.udi.issuer",
          "display": "issuer",
          "target": [
            {
              "code": "Device.udiCarrier.issuer",
              "display": "Device.udiCarrier.issuer",
              "relationship": "equivalent",
              "comment": "Element `Device.udi.issuer` is mapped to FHIR R5 element `Device.udiCarrier.issuer` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.udi.entryType",
          "display": "entryType",
          "target": [
            {
              "code": "Device.udiCarrier.entryType",
              "display": "Device.udiCarrier.entryType",
              "relationship": "related-to",
              "comment": "Element `Device.udi.entryType` is mapped to FHIR R5 element `Device.udiCarrier.entryType` as `RelatedTo`.\nThe mappings for `Device.udi.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.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.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.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.model",
          "display": "model",
          "target": [
            {
              "code": "Device.modelNumber",
              "display": "Device.modelNumber",
              "relationship": "equivalent",
              "comment": "Element `Device.model` is mapped to FHIR R5 element `Device.modelNumber` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.version",
          "display": "version",
          "target": [
            {
              "code": "Device.version.value",
              "display": "Device.version.value",
              "relationship": "equivalent",
              "comment": "Element `Device.version` is mapped to FHIR R5 element `Device.version.value` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.owner",
          "display": "owner",
          "target": [
            {
              "code": "Device.owner",
              "display": "Device.owner",
              "relationship": "related-to",
              "comment": "Element `Device.owner` is mapped to FHIR R5 element `Device.owner` as `SourceIsBroaderThanTarget`.\nThe mappings for `Device.owner` do not cover the following types based on type expansion: display, identifier, reference.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `Device.owner` with unmapped reference targets: Organization."
            }
          ]
        },
        {
          "code": "Device.contact",
          "display": "contact",
          "target": [
            {
              "code": "Device.contact",
              "display": "Device.contact",
              "relationship": "related-to",
              "comment": "Element `Device.contact` is mapped to FHIR R5 element `Device.contact` as `SourceIsBroaderThanTarget`.\nThe mappings for `Device.contact` do not cover the following types: ContactPoint.\nThe mappings for `Device.contact` do not cover the following types based on type expansion: period, rank, system, use, value.\nused for troubleshooting etc."
            }
          ]
        },
        {
          "code": "Device.location",
          "display": "location",
          "target": [
            {
              "code": "Device.location",
              "display": "Device.location",
              "relationship": "related-to",
              "comment": "Element `Device.location` is mapped to FHIR R5 element `Device.location` as `SourceIsBroaderThanTarget`.\nThe mappings for `Device.location` do not cover the following types based on type expansion: display, identifier, reference.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `Device.location` with unmapped reference targets: Location."
            }
          ]
        },
        {
          "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": "related-to",
              "comment": "Element `Device.note` is mapped to FHIR R5 element `Device.note` as `SourceIsBroaderThanTarget`.\nThe mappings for `Device.note` do not cover the following types: Annotation.\nThe mappings for `Device.note` do not cover the following types based on type expansion: author[x], text, time."
            }
          ]
        },
        {
          "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`."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device|3.0.2",
      "target": "http://hl7.org/fhir/StructureDefinition/DeviceAssociation|5.0.0",
      "element": [
        {
          "code": "Device.meta",
          "display": "meta",
          "target": [
            {
              "code": "DeviceAssociation.meta",
              "display": "DeviceAssociation.meta",
              "relationship": "related-to",
              "comment": "Element `Device.meta` is mapped to FHIR R5 element `Device.meta` as `SourceIsBroaderThanTarget`.\nElement `Device.meta` is mapped to FHIR R5 element `DeviceAssociation.meta` as `SourceIsBroaderThanTarget`.\nThe mappings for `Device.meta` do not cover the following types: Meta.\nThe mappings for `Device.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId."
            }
          ]
        },
        {
          "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. \n\nThis element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."
            }
          ]
        },
        {
          "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": "related-to",
              "comment": "Element `Device.text` is mapped to FHIR R5 element `Device.text` as `SourceIsBroaderThanTarget`.\nElement `Device.text` is mapped to FHIR R5 element `DeviceAssociation.text` as `SourceIsBroaderThanTarget`.\nThe mappings for `Device.text` do not cover the following types: Narrative.\nThe mappings for `Device.text` do not cover the following types based on type expansion: div, status.\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 in formation is added later."
            }
          ]
        },
        {
          "code": "Device.contained",
          "display": "contained",
          "target": [
            {
              "code": "DeviceAssociation.contained",
              "display": "DeviceAssociation.contained",
              "relationship": "related-to",
              "comment": "Element `Device.contained` is mapped to FHIR R5 element `Device.contained` as `SourceIsBroaderThanTarget`.\nElement `Device.contained` is mapped to FHIR R5 element `DeviceAssociation.contained` as `SourceIsBroaderThanTarget`.\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."
            }
          ]
        },
        {
          "code": "Device.identifier",
          "display": "identifier",
          "target": [
            {
              "code": "DeviceAssociation.identifier",
              "display": "DeviceAssociation.identifier",
              "relationship": "related-to",
              "comment": "Element `Device.identifier` is mapped to FHIR R5 element `Device.identifier` as `SourceIsBroaderThanTarget`.\nElement `Device.identifier` is mapped to FHIR R5 element `DeviceAssociation.identifier` as `SourceIsBroaderThanTarget`.\nThe mappings for `Device.identifier` do not cover the following types: Identifier.\nThe mappings for `Device.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value.\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.  For [UDI](https://hl7.org/fhir/device.html#5.11.3.2.2),  this element corresponds to the variable portion of the UDI that identifies the serial number of a specific device. See [UDI mappings](https://hl7.org/fhir/devi.html#udi) for a complete mapping of UDI parts to Device."
            }
          ]
        },
        {
          "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.patient",
          "display": "patient",
          "target": [
            {
              "code": "DeviceAssociation.subject",
              "display": "DeviceAssociation.subject",
              "relationship": "related-to",
              "comment": "Element `Device.patient` is mapped to FHIR R5 element `DeviceAssociation.subject` as `RelatedTo`.\nThe mappings for `Device.patient` do not cover the following types based on type expansion: display, identifier, reference.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `Device.patient` with unmapped reference targets: Patient."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device|3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-Device.meta|0.1.0",
      "element": [
        {
          "code": "Device.meta",
          "display": "meta",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Device.meta` is mapped to FHIR R5 element `Device.meta` as `SourceIsBroaderThanTarget`.\nElement `Device.meta` is mapped to FHIR R5 element `DeviceAssociation.meta` as `SourceIsBroaderThanTarget`.\nThe mappings for `Device.meta` do not cover the following types: Meta.\nThe mappings for `Device.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device|3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-Device.text|0.1.0",
      "element": [
        {
          "code": "Device.text",
          "display": "text",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Device.text` is mapped to FHIR R5 element `Device.text` as `SourceIsBroaderThanTarget`.\nElement `Device.text` is mapped to FHIR R5 element `DeviceAssociation.text` as `SourceIsBroaderThanTarget`.\nThe mappings for `Device.text` do not cover the following types: Narrative.\nThe mappings for `Device.text` do not cover the following types based on type expansion: div, status.\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 in formation is added later."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device|3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-Device.identifier|0.1.0",
      "element": [
        {
          "code": "Device.identifier",
          "display": "identifier",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Device.identifier` is mapped to FHIR R5 element `Device.identifier` as `SourceIsBroaderThanTarget`.\nElement `Device.identifier` is mapped to FHIR R5 element `DeviceAssociation.identifier` as `SourceIsBroaderThanTarget`.\nThe mappings for `Device.identifier` do not cover the following types: Identifier.\nThe mappings for `Device.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value.\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.  For [UDI](https://hl7.org/fhir/device.html#5.11.3.2.2),  this element corresponds to the variable portion of the UDI that identifies the serial number of a specific device. See [UDI mappings](https://hl7.org/fhir/devi.html#udi) for a complete mapping of UDI parts to Device."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device|3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-Device.udi.name|0.1.0",
      "element": [
        {
          "code": "Device.udi.name",
          "display": "name",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Device.udi.name` has a context of Device.udiCarrier based on following the parent source element upwards and mapping to `Device`.\nElement `Device.udi.name` has a context of DeviceAssociation based on following the parent source element upwards and mapping to `DeviceAssociation`.\nElement `Device.udi.name` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).\nUse the `Device.type`  for a generic type or kind of device name.  Note the [GUDID](http://www.fda.gov/medicaldevices/deviceregulationandguidance/uniquedeviceidentification/globaludidatabasegudid/default.htm) lists the name as the 'Brand Name'."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device|3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-Device.udi.entryType|0.1.0",
      "element": [
        {
          "code": "Device.udi.entryType",
          "display": "entryType",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Device.udi.entryType` is mapped to FHIR R5 element `Device.udiCarrier.entryType` as `RelatedTo`.\nThe mappings for `Device.udi.entryType` do not allow expression of the necessary codes, per the bindings on the source and target."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device|3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-Device.contact|0.1.0",
      "element": [
        {
          "code": "Device.contact",
          "display": "contact",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Device.contact` is mapped to FHIR R5 element `Device.contact` as `SourceIsBroaderThanTarget`.\nThe mappings for `Device.contact` do not cover the following types: ContactPoint.\nThe mappings for `Device.contact` do not cover the following types based on type expansion: period, rank, system, use, value.\nused for troubleshooting etc."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device|3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-Device.note|0.1.0",
      "element": [
        {
          "code": "Device.note",
          "display": "note",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Device.note` is mapped to FHIR R5 element `Device.note` as `SourceIsBroaderThanTarget`.\nThe mappings for `Device.note` do not cover the following types: Annotation.\nThe mappings for `Device.note` do not cover the following types based on type expansion: author[x], text, time."
            }
          ]
        }
      ]
    }
  ]
}