Extensions for Using Data Elements from FHIR DSTU2 in FHIR R5
0.1.0 - STU International flag

Extensions for Using Data Elements from FHIR DSTU2 in FHIR R5 - Downloaded Version null See the Directory of published versions

: R2DeviceElementMapToR5 - JSON Representation

Page standards status: Trial-use Maturity Level: 0

Raw json | Download

{
  "resourceType" : "ConceptMap",
  "id" : "R2-Device-element-map-to-R5",
  "text" : {
    "status" : "generated",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p class=\"res-header-id\"><b>Generated Narrative: ConceptMap R2-Device-element-map-to-R5</b></p><a name=\"R2-Device-element-map-to-R5\"> </a><a name=\"hcR2-Device-element-map-to-R5\"> </a><p>Mapping from http://hl7.org/fhir/1.0 to http://hl7.org/fhir/5.0</p><br/><p><b>Group 1 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Device|1.0.2</code> to <a href=\"http://hl7.org/fhir/R5/device.html\">Deviceversion: 5.0.0)</a></p><table class=\"grid\"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Device.meta (meta)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#related-to\" title=\"related-to\">is related to</a></td><td>Device.meta</td><td>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.</td></tr><tr><td>Device.implicitRules (implicitRules)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Device.implicitRules</td><td>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 as much as possible.</td></tr><tr><td>Device.language (language)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Device.language</td><td>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).</td></tr><tr><td>Device.text (text)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#related-to\" title=\"related-to\">is related to</a></td><td>Device.text</td><td>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.</td></tr><tr><td>Device.contained (contained)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#related-to\" title=\"related-to\">is related to</a></td><td>Device.contained</td><td>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.</td></tr><tr><td>Device.identifier (identifier)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#related-to\" title=\"related-to\">is related to</a></td><td>Device.identifier</td><td>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.\nOften fixed to the device as a barcode and may include names given to the device in local usage.  Note that some of the barcodes affixed to the device identify its type, not its instance.  For the FDA mandated Unique Device Identifier (UDI) use  the Device.udi element.</td></tr><tr><td>Device.type (type)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Device.type</td><td>Element `Device.type` is mapped to FHIR R5 element `Device.type` as `SourceIsNarrowerThanTarget`.\nFor the FDA mandated Unique Device Identifier (UDI) use  the Device.udi element.</td></tr><tr><td>Device.note (note)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#related-to\" title=\"related-to\">is related to</a></td><td>Device.note</td><td>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.</td></tr><tr><td>Device.status (status)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#related-to\" title=\"related-to\">is related to</a></td><td>Device.status</td><td>Element `Device.status` is mapped to FHIR R5 element `Device.status` as `RelatedTo`.\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.</td></tr><tr><td>Device.manufacturer (manufacturer)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Device.manufacturer</td><td>Element `Device.manufacturer` is mapped to FHIR R5 element `Device.manufacturer` as `Equivalent`.</td></tr><tr><td>Device.model (model)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Device.modelNumber</td><td>Element `Device.model` is mapped to FHIR R5 element `Device.modelNumber` as `Equivalent`.</td></tr><tr><td>Device.version (version)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Device.version.value</td><td>Element `Device.version` is mapped to FHIR R5 element `Device.version.value` as `Equivalent`.</td></tr><tr><td>Device.manufactureDate (manufactureDate)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Device.manufactureDate</td><td>Element `Device.manufactureDate` is mapped to FHIR R5 element `Device.manufactureDate` as `Equivalent`.</td></tr><tr><td>Device.expiry (expiry)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Device.expirationDate</td><td>Element `Device.expiry` is mapped to FHIR R5 element `Device.expirationDate` as `Equivalent`.</td></tr><tr><td>Device.udi (udi)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Device.udiCarrier.deviceIdentifier</td><td>Element `Device.udi` is mapped to FHIR R5 element `Device.udiCarrier.deviceIdentifier` as `Equivalent`.\nThe unique identifier may identify an instance of a device uniquely, or it may only identify the type of the device. A portion of the UDI - the DI part - can be extracted from the UDI when required, and used to look up information about the device through the GUDID.</td></tr><tr><td>Device.lotNumber (lotNumber)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Device.lotNumber</td><td>Element `Device.lotNumber` is mapped to FHIR R5 element `Device.lotNumber` as `Equivalent`.\nAlphanumeric Maximum 20.</td></tr><tr><td>Device.owner (owner)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#related-to\" title=\"related-to\">is related to</a></td><td>Device.owner</td><td>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, reference.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `Device.owner` with unmapped reference targets: Organization.</td></tr><tr><td>Device.location (location)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#related-to\" title=\"related-to\">is related to</a></td><td>Device.location</td><td>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, reference.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `Device.location` with unmapped reference targets: Location.</td></tr><tr><td>Device.contact (contact)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#related-to\" title=\"related-to\">is related to</a></td><td>Device.contact</td><td>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.</td></tr><tr><td>Device.url (url)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Device.url</td><td>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 root URL from which a conformance statement may be retrieved.</td></tr></table><hr/><p><b>Group 2 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Device|1.0.2</code> to <a href=\"http://hl7.org/fhir/R5/deviceassociation.html\">DeviceAssociationversion: 5.0.0)</a></p><table class=\"grid\"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Device.meta (meta)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#related-to\" title=\"related-to\">is related to</a></td><td>DeviceAssociation.meta</td><td>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.</td></tr><tr><td>Device.implicitRules (implicitRules)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>DeviceAssociation.implicitRules</td><td>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 as much as possible.</td></tr><tr><td>Device.language (language)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>DeviceAssociation.language</td><td>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).</td></tr><tr><td>Device.text (text)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#related-to\" title=\"related-to\">is related to</a></td><td>DeviceAssociation.text</td><td>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.</td></tr><tr><td>Device.contained (contained)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#related-to\" title=\"related-to\">is related to</a></td><td>DeviceAssociation.contained</td><td>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.</td></tr><tr><td>Device.identifier (identifier)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#related-to\" title=\"related-to\">is related to</a></td><td>DeviceAssociation.identifier</td><td>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.\nOften fixed to the device as a barcode and may include names given to the device in local usage.  Note that some of the barcodes affixed to the device identify its type, not its instance.  For the FDA mandated Unique Device Identifier (UDI) use  the Device.udi element.</td></tr><tr><td>Device.status (status)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>DeviceAssociation.status</td><td>Element `Device.status` is mapped to FHIR R5 element `Device.status` as `RelatedTo`.\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.</td></tr><tr><td>Device.patient (patient)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#related-to\" title=\"related-to\">is related to</a></td><td>DeviceAssociation.subject</td><td>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, reference.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `Device.patient` with unmapped reference targets: Patient.</td></tr></table><hr/><p><b>Group 3 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Device|1.0.2</code> to <a href=\"StructureDefinition-ext-R2-Device.meta.html\">DSTU2: Metadata about the resource additional typesversion: 0.1.0)</a></p><table class=\"grid\"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Device.meta (meta)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#source-is-broader-than-target\" title=\"source-is-broader-than-target\">is broader than</a></td><td>Extension (DSTU2: Metadata about the resource additional types)</td><td>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.</td></tr></table><hr/><p><b>Group 4 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Device|1.0.2</code> to <a href=\"StructureDefinition-ext-R2-Device.text.html\">DSTU2: Text summary of the resource, for human interpretation additional typesversion: 0.1.0)</a></p><table class=\"grid\"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Device.text (text)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#source-is-broader-than-target\" title=\"source-is-broader-than-target\">is broader than</a></td><td>Extension (DSTU2: Text summary of the resource, for human interpretation additional types)</td><td>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.</td></tr></table><hr/><p><b>Group 5 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Device|1.0.2</code> to <a href=\"StructureDefinition-ext-R2-Device.identifier.html\">DSTU2: Instance id from manufacturer, owner, and others additional typesversion: 0.1.0)</a></p><table class=\"grid\"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Device.identifier (identifier)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#source-is-broader-than-target\" title=\"source-is-broader-than-target\">is broader than</a></td><td>Extension (DSTU2: Instance id from manufacturer, owner, and others additional types)</td><td>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.\nOften fixed to the device as a barcode and may include names given to the device in local usage.  Note that some of the barcodes affixed to the device identify its type, not its instance.  For the FDA mandated Unique Device Identifier (UDI) use  the Device.udi element.</td></tr></table><hr/><p><b>Group 6 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Device|1.0.2</code> to <a href=\"StructureDefinition-ext-R2-Device.note.html\">DSTU2: note additional typesversion: 0.1.0)</a></p><table class=\"grid\"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Device.note (note)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#source-is-broader-than-target\" title=\"source-is-broader-than-target\">is broader than</a></td><td>Extension (DSTU2: note additional types)</td><td>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.</td></tr></table><hr/><p><b>Group 7 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Device|1.0.2</code> to <a href=\"StructureDefinition-ext-R2-Device.contact.html\">DSTU2: contact additional typesversion: 0.1.0)</a></p><table class=\"grid\"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Device.contact (contact)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#source-is-broader-than-target\" title=\"source-is-broader-than-target\">is broader than</a></td><td>Extension (DSTU2: contact additional types)</td><td>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.</td></tr></table></div>"
  },
  "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-r2.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-r2.r5"
          }
        ]
      }
    }
  ],
  "url" : "http://hl7.org/fhir/uv/xver/ConceptMap/R2-Device-element-map-to-R5",
  "version" : "0.1.0",
  "name" : "R2DeviceElementMapToR5",
  "title" : "Cross-version mapping for FHIR DSTU2 Device to FHIR R5 Device",
  "status" : "active",
  "experimental" : false,
  "date" : "2026-03-17T16:05:26.469791-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 DSTU2 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/1.0",
  "targetScopeUri" : "http://hl7.org/fhir/5.0",
  "group" : [
    {
      "source" : "http://hl7.org/fhir/StructureDefinition/Device|1.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 as much as possible."
            }
          ]
        },
        {
          "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."
            }
          ]
        },
        {
          "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.\nOften fixed to the device as a barcode and may include names given to the device in local usage.  Note that some of the barcodes affixed to the device identify its type, not its instance.  For the FDA mandated Unique Device Identifier (UDI) use  the Device.udi element."
            }
          ]
        },
        {
          "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`.\nFor the FDA mandated Unique Device Identifier (UDI) use  the Device.udi element."
            }
          ]
        },
        {
          "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.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 `RelatedTo`.\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."
            }
          ]
        },
        {
          "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.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.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.expiry",
          "display" : "expiry",
          "target" : [
            {
              "code" : "Device.expirationDate",
              "display" : "Device.expirationDate",
              "relationship" : "equivalent",
              "comment" : "Element `Device.expiry` is mapped to FHIR R5 element `Device.expirationDate` as `Equivalent`."
            }
          ]
        },
        {
          "code" : "Device.udi",
          "display" : "udi",
          "target" : [
            {
              "code" : "Device.udiCarrier.deviceIdentifier",
              "display" : "Device.udiCarrier.deviceIdentifier",
              "relationship" : "equivalent",
              "comment" : "Element `Device.udi` is mapped to FHIR R5 element `Device.udiCarrier.deviceIdentifier` as `Equivalent`.\nThe unique identifier may identify an instance of a device uniquely, or it may only identify the type of the device. A portion of the UDI - the DI part - can be extracted from the UDI when required, and used to look up information about the device through the GUDID."
            }
          ]
        },
        {
          "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`.\nAlphanumeric Maximum 20."
            }
          ]
        },
        {
          "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, reference.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `Device.owner` with unmapped reference targets: Organization."
            }
          ]
        },
        {
          "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, reference.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `Device.location` with unmapped reference targets: Location."
            }
          ]
        },
        {
          "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.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 root URL from which a conformance statement may be retrieved."
            }
          ]
        }
      ]
    },
    {
      "source" : "http://hl7.org/fhir/StructureDefinition/Device|1.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 as much as possible."
            }
          ]
        },
        {
          "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."
            }
          ]
        },
        {
          "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.\nOften fixed to the device as a barcode and may include names given to the device in local usage.  Note that some of the barcodes affixed to the device identify its type, not its instance.  For the FDA mandated Unique Device Identifier (UDI) use  the Device.udi element."
            }
          ]
        },
        {
          "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 `RelatedTo`.\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."
            }
          ]
        },
        {
          "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, reference.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `Device.patient` with unmapped reference targets: Patient."
            }
          ]
        }
      ]
    },
    {
      "source" : "http://hl7.org/fhir/StructureDefinition/Device|1.0.2",
      "target" : "http://hl7.org/fhir/1.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|1.0.2",
      "target" : "http://hl7.org/fhir/1.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."
            }
          ]
        }
      ]
    },
    {
      "source" : "http://hl7.org/fhir/StructureDefinition/Device|1.0.2",
      "target" : "http://hl7.org/fhir/1.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.\nOften fixed to the device as a barcode and may include names given to the device in local usage.  Note that some of the barcodes affixed to the device identify its type, not its instance.  For the FDA mandated Unique Device Identifier (UDI) use  the Device.udi element."
            }
          ]
        }
      ]
    },
    {
      "source" : "http://hl7.org/fhir/StructureDefinition/Device|1.0.2",
      "target" : "http://hl7.org/fhir/1.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."
            }
          ]
        }
      ]
    },
    {
      "source" : "http://hl7.org/fhir/StructureDefinition/Device|1.0.2",
      "target" : "http://hl7.org/fhir/1.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."
            }
          ]
        }
      ]
    }
  ]
}