FHIR IG analytics

Resources that use this resource

No resources found

Resources that this resource uses

No resources found

Narrative

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

Source1

{
  "resourceType": "ConceptMap",
  "id": "R4B-DeviceUseStatement-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-r4b.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-r4b.r4"
          }
        ]
      }
    }
  ],
  "url": "http://hl7.org/fhir/uv/xver/ConceptMap/R4B-DeviceUseStatement-element-map-to-R4",
  "version": "0.1.0",
  "name": "R4BDeviceUseStatementElementMapToR4",
  "title": "Cross-version mapping for FHIR R4B DeviceUseStatement to FHIR R4 DeviceUseStatement",
  "status": "active",
  "experimental": false,
  "date": "2026-03-17T16:03:45.9195402-05:00",
  "contact": [
    {
      "name": "FHIR Infrastructure",
      "telecom": [
        {
          "system": "url",
          "value": "http://www.hl7.org/Special/committees/fiwg"
        }
      ]
    }
  ],
  "description": "This ConceptMap represents cross-version mappings for elements from a FHIR R4B DeviceUseStatement to FHIR R4.",
  "jurisdiction": [
    {
      "coding": [
        {
          "system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code": "001",
          "display": "World"
        }
      ]
    }
  ],
  "sourceCanonical": "http://hl7.org/fhir/4.3",
  "targetUri": "http://hl7.org/fhir/4.0",
  "group": [
    {
      "source": "http://hl7.org/fhir/StructureDefinition/DeviceUseStatement",
      "sourceVersion": "4.3.0",
      "target": "http://hl7.org/fhir/StructureDefinition/DeviceUseStatement",
      "targetVersion": "4.0.1",
      "element": [
        {
          "code": "DeviceUseStatement.meta",
          "display": "meta",
          "target": [
            {
              "code": "DeviceUseStatement.meta",
              "display": "DeviceUseStatement.meta",
              "equivalence": "equivalent",
              "comment": "Element `DeviceUseStatement.meta` is mapped to FHIR R4 element `DeviceUseStatement.meta` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceUseStatement.implicitRules",
          "display": "implicitRules",
          "target": [
            {
              "code": "DeviceUseStatement.implicitRules",
              "display": "DeviceUseStatement.implicitRules",
              "equivalence": "equivalent",
              "comment": "Element `DeviceUseStatement.implicitRules` is mapped to FHIR R4 element `DeviceUseStatement.implicitRules` as `Equivalent`.\nAsserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc."
            }
          ]
        },
        {
          "code": "DeviceUseStatement.language",
          "display": "language",
          "target": [
            {
              "code": "DeviceUseStatement.language",
              "display": "DeviceUseStatement.language",
              "equivalence": "equivalent",
              "comment": "Element `DeviceUseStatement.language` is mapped to FHIR R4 element `DeviceUseStatement.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": "DeviceUseStatement.text",
          "display": "text",
          "target": [
            {
              "code": "DeviceUseStatement.text",
              "display": "DeviceUseStatement.text",
              "equivalence": "equivalent",
              "comment": "Element `DeviceUseStatement.text` is mapped to FHIR R4 element `DeviceUseStatement.text` as `Equivalent`.\nContained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied).  This may be necessary for data from legacy systems where information is captured as a \"text blob\" or where text is additionally entered raw or narrated and encoded information is added later."
            }
          ]
        },
        {
          "code": "DeviceUseStatement.contained",
          "display": "contained",
          "target": [
            {
              "code": "DeviceUseStatement.contained",
              "display": "DeviceUseStatement.contained",
              "equivalence": "equivalent",
              "comment": "Element `DeviceUseStatement.contained` is mapped to FHIR R4 element `DeviceUseStatement.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": "DeviceUseStatement.identifier",
          "display": "identifier",
          "target": [
            {
              "code": "DeviceUseStatement.identifier",
              "display": "DeviceUseStatement.identifier",
              "equivalence": "equivalent",
              "comment": "Element `DeviceUseStatement.identifier` is mapped to FHIR R4 element `DeviceUseStatement.identifier` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceUseStatement.basedOn",
          "display": "basedOn",
          "target": [
            {
              "code": "DeviceUseStatement.basedOn",
              "display": "DeviceUseStatement.basedOn",
              "equivalence": "equivalent",
              "comment": "Element `DeviceUseStatement.basedOn` is mapped to FHIR R4 element `DeviceUseStatement.basedOn` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceUseStatement.status",
          "display": "status",
          "target": [
            {
              "code": "DeviceUseStatement.status",
              "display": "DeviceUseStatement.status",
              "equivalence": "equivalent",
              "comment": "Element `DeviceUseStatement.status` is mapped to FHIR R4 element `DeviceUseStatement.status` as `Equivalent`.\nDeviceUseStatment is a statement at a point in time.  The status is only representative at the point when it was asserted.  The value set for contains codes that assert the status of the use  by the patient (for example, stopped or on hold) as well as codes that assert the status of the resource itself (for example, entered in error).\r\rThis element is labeled as a modifier because the status contains the codes that mark the statement as not currently valid."
            }
          ]
        },
        {
          "code": "DeviceUseStatement.subject",
          "display": "subject",
          "target": [
            {
              "code": "DeviceUseStatement.subject",
              "display": "DeviceUseStatement.subject",
              "equivalence": "equivalent",
              "comment": "Element `DeviceUseStatement.subject` is mapped to FHIR R4 element `DeviceUseStatement.subject` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceUseStatement.derivedFrom",
          "display": "derivedFrom",
          "target": [
            {
              "code": "DeviceUseStatement.derivedFrom",
              "display": "DeviceUseStatement.derivedFrom",
              "equivalence": "equivalent",
              "comment": "Element `DeviceUseStatement.derivedFrom` is mapped to FHIR R4 element `DeviceUseStatement.derivedFrom` as `Equivalent`.\nThe most common use cases for deriving a DeviceUseStatement comes from creating it from a request or from an observation or a claim. it should be noted that the amount of information that is available varies from the type resource that you derive the DeviceUseStatement from."
            }
          ]
        },
        {
          "code": "DeviceUseStatement.timing[x]",
          "display": "timing[x]",
          "target": [
            {
              "code": "DeviceUseStatement.timing[x]",
              "display": "DeviceUseStatement.timing[x]",
              "equivalence": "equivalent",
              "comment": "Element `DeviceUseStatement.timing[x]` is mapped to FHIR R4 element `DeviceUseStatement.timing[x]` as `Equivalent`.\nThe target context `DeviceUseStatement.timing[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `DeviceUseStatement`."
            }
          ]
        },
        {
          "code": "DeviceUseStatement.recordedOn",
          "display": "recordedOn",
          "target": [
            {
              "code": "DeviceUseStatement.recordedOn",
              "display": "DeviceUseStatement.recordedOn",
              "equivalence": "equivalent",
              "comment": "Element `DeviceUseStatement.recordedOn` is mapped to FHIR R4 element `DeviceUseStatement.recordedOn` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceUseStatement.source",
          "display": "source",
          "target": [
            {
              "code": "DeviceUseStatement.source",
              "display": "DeviceUseStatement.source",
              "equivalence": "equivalent",
              "comment": "Element `DeviceUseStatement.source` is mapped to FHIR R4 element `DeviceUseStatement.source` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceUseStatement.device",
          "display": "device",
          "target": [
            {
              "code": "DeviceUseStatement.device",
              "display": "DeviceUseStatement.device",
              "equivalence": "equivalent",
              "comment": "Element `DeviceUseStatement.device` is mapped to FHIR R4 element `DeviceUseStatement.device` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceUseStatement.reasonCode",
          "display": "reasonCode",
          "target": [
            {
              "code": "DeviceUseStatement.reasonCode",
              "display": "DeviceUseStatement.reasonCode",
              "equivalence": "equivalent",
              "comment": "Element `DeviceUseStatement.reasonCode` is mapped to FHIR R4 element `DeviceUseStatement.reasonCode` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceUseStatement.reasonReference",
          "display": "reasonReference",
          "target": [
            {
              "code": "DeviceUseStatement.reasonReference",
              "display": "DeviceUseStatement.reasonReference",
              "equivalence": "equivalent",
              "comment": "Element `DeviceUseStatement.reasonReference` is mapped to FHIR R4 element `DeviceUseStatement.reasonReference` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceUseStatement.bodySite",
          "display": "bodySite",
          "target": [
            {
              "code": "DeviceUseStatement.bodySite",
              "display": "DeviceUseStatement.bodySite",
              "equivalence": "equivalent",
              "comment": "Element `DeviceUseStatement.bodySite` is mapped to FHIR R4 element `DeviceUseStatement.bodySite` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceUseStatement.note",
          "display": "note",
          "target": [
            {
              "code": "DeviceUseStatement.note",
              "display": "DeviceUseStatement.note",
              "equivalence": "equivalent",
              "comment": "Element `DeviceUseStatement.note` is mapped to FHIR R4 element `DeviceUseStatement.note` as `Equivalent`."
            }
          ]
        }
      ]
    }
  ]
}