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

FHIR IG analytics

Packagehl7.fhir.uv.xver-r3.r4
Resource TypeConceptMap
IdConceptMap-R3-DeviceRequest-element-map-to-R4.json
FHIR VersionR4
Sourcehttp://hl7.org/fhir/uv/xver-r3.r4/0.1.0/ConceptMap-R3-DeviceRequest-element-map-to-R4.html
URLhttp://hl7.org/fhir/uv/xver/ConceptMap/R3-DeviceRequest-element-map-to-R4
Version0.1.0
Statusactive
Date2026-03-17T16:03:23.621339-05:00
NameR3DeviceRequestElementMapToR4
TitleCross-version mapping for FHIR STU3 DeviceRequest to FHIR R4 DeviceRequest
Realmuv
Authorityhl7
DescriptionThis ConceptMap represents cross-version mappings for elements from a FHIR STU3 DeviceRequest to FHIR R4.

Resources that use this resource

No resources found


Resources that this resource uses

StructureDefinition
hl7.fhir.uv.xver-r3.r4b.r4#0.0.1-snapshot-2extension-DeviceRequest.definitionCross-version Extension for R3.DeviceRequest.definition for use in FHIR R4B
hl7.fhir.uv.xver-r3.r4b#0.1.0extension-DeviceRequest.intentSTU3: proposal | plan | original-order | encoded | reflex-order additional types additional codes
hl7.fhir.uv.xver-r3.r4b#0.1.0extension-DeviceRequest.requester.onBehalfOfSTU3: Organization agent is acting for (new)

Narrative

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

Generated Narrative: ConceptMap R3-DeviceRequest-element-map-to-R4

Mapping from http://hl7.org/fhir/3.0 to http://hl7.org/fhir/4.0


Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceRequest|3.0.2 to DeviceRequestversion: 4.0.1)

Source CodeRelationshipTarget CodeComment
DeviceRequest.meta (meta)is equivalent toDeviceRequest.metaElement `DeviceRequest.meta` is mapped to FHIR R4 element `DeviceRequest.meta` as `Equivalent`.
DeviceRequest.implicitRules (implicitRules)is equivalent toDeviceRequest.implicitRulesElement `DeviceRequest.implicitRules` is mapped to FHIR R4 element `DeviceRequest.implicitRules` as `Equivalent`. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.
DeviceRequest.language (language)is equivalent toDeviceRequest.languageElement `DeviceRequest.language` is mapped to FHIR R4 element `DeviceRequest.language` as `Equivalent`. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
DeviceRequest.text (text)is equivalent toDeviceRequest.textElement `DeviceRequest.text` is mapped to FHIR R4 element `DeviceRequest.text` as `Equivalent`. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded in formation is added later.
DeviceRequest.contained (contained)is equivalent toDeviceRequest.containedElement `DeviceRequest.contained` is mapped to FHIR R4 element `DeviceRequest.contained` as `Equivalent`. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again.
DeviceRequest.identifier (identifier)is equivalent toDeviceRequest.identifierElement `DeviceRequest.identifier` is mapped to FHIR R4 element `DeviceRequest.identifier` as `Equivalent`.
DeviceRequest.basedOn (basedOn)is equivalent toDeviceRequest.basedOnElement `DeviceRequest.basedOn` is mapped to FHIR R4 element `DeviceRequest.basedOn` as `Equivalent`.
DeviceRequest.priorRequest (priorRequest)is equivalent toDeviceRequest.priorRequestElement `DeviceRequest.priorRequest` is mapped to FHIR R4 element `DeviceRequest.priorRequest` as `Equivalent`.
DeviceRequest.groupIdentifier (groupIdentifier)is equivalent toDeviceRequest.groupIdentifierElement `DeviceRequest.groupIdentifier` is mapped to FHIR R4 element `DeviceRequest.groupIdentifier` as `Equivalent`.
DeviceRequest.status (status)is equivalent toDeviceRequest.statusElement `DeviceRequest.status` is mapped to FHIR R4 element `DeviceRequest.status` as `Equivalent`. This element is labeled as a modifier because the status contains the codes cancelled and entered-in-error that mark the request as not currently valid.
DeviceRequest.intent (intent)maps to wider conceptDeviceRequest.intentElement `DeviceRequest.intent` is mapped to FHIR R4 element `DeviceRequest.intent` as `RelatedTo`. The mappings for `DeviceRequest.intent` do not cover the following types: CodeableConcept. The mappings for `DeviceRequest.intent` do not cover the following types based on type expansion: coding. The mappings for `DeviceRequest.intent` do not allow expression of the necessary codes, per the bindings on the source and target. The target context `DeviceRequest.intent` is a modifier element, so this extension does not need to be defined as a modifier.
DeviceRequest.priority (priority)is equivalent toDeviceRequest.priorityElement `DeviceRequest.priority` is mapped to FHIR R4 element `DeviceRequest.priority` as `Equivalent`.
DeviceRequest.code[x] (code[x])is equivalent toDeviceRequest.code[x]Element `DeviceRequest.code[x]` is mapped to FHIR R4 element `DeviceRequest.code[x]` as `Equivalent`. The target context `DeviceRequest.code[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `DeviceRequest`.
DeviceRequest.subject (subject)is equivalent toDeviceRequest.subjectElement `DeviceRequest.subject` is mapped to FHIR R4 element `DeviceRequest.subject` as `Equivalent`.
DeviceRequest.context (context)maps to wider conceptDeviceRequest.encounterElement `DeviceRequest.context` is mapped to FHIR R4 element `DeviceRequest.encounter` as `SourceIsBroaderThanTarget`. The mappings for `DeviceRequest.context` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `DeviceRequest.context` with unmapped reference targets: EpisodeOfCare.
DeviceRequest.occurrence[x] (occurrence[x])is equivalent toDeviceRequest.occurrence[x]Element `DeviceRequest.occurrence[x]` is mapped to FHIR R4 element `DeviceRequest.occurrence[x]` as `Equivalent`. The target context `DeviceRequest.occurrence[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `DeviceRequest`.
DeviceRequest.authoredOn (authoredOn)is equivalent toDeviceRequest.authoredOnElement `DeviceRequest.authoredOn` is mapped to FHIR R4 element `DeviceRequest.authoredOn` as `Equivalent`.
DeviceRequest.requester (requester)maps to wider conceptDeviceRequest.requesterElement `DeviceRequest.requester` is mapped to FHIR R4 element `DeviceRequest.requester` as `Equivalent`.
DeviceRequest.requester.agent (agent)is equivalent toDeviceRequest.requesterElement `DeviceRequest.requester.agent` is mapped to FHIR R4 element `DeviceRequest.requester` as `Equivalent`.
DeviceRequest.performerType (performerType)is equivalent toDeviceRequest.performerTypeElement `DeviceRequest.performerType` is mapped to FHIR R4 element `DeviceRequest.performerType` as `Equivalent`.
DeviceRequest.performer (performer)is equivalent toDeviceRequest.performerElement `DeviceRequest.performer` is mapped to FHIR R4 element `DeviceRequest.performer` as `Equivalent`.
DeviceRequest.reasonCode (reasonCode)is equivalent toDeviceRequest.reasonCodeElement `DeviceRequest.reasonCode` is mapped to FHIR R4 element `DeviceRequest.reasonCode` as `Equivalent`.
DeviceRequest.reasonReference (reasonReference)maps to wider conceptDeviceRequest.reasonReferenceElement `DeviceRequest.reasonReference` is mapped to FHIR R4 element `DeviceRequest.reasonReference` as `SourceIsBroaderThanTarget`. The mappings for `DeviceRequest.reasonReference` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `DeviceRequest.reasonReference` with unmapped reference targets: Resource.
DeviceRequest.supportingInfo (supportingInfo)is equivalent toDeviceRequest.supportingInfoElement `DeviceRequest.supportingInfo` is mapped to FHIR R4 element `DeviceRequest.supportingInfo` as `Equivalent`.
DeviceRequest.note (note)is equivalent toDeviceRequest.noteElement `DeviceRequest.note` is mapped to FHIR R4 element `DeviceRequest.note` as `Equivalent`.
DeviceRequest.relevantHistory (relevantHistory)is equivalent toDeviceRequest.relevantHistoryElement `DeviceRequest.relevantHistory` is mapped to FHIR R4 element `DeviceRequest.relevantHistory` as `Equivalent`. This may not include provenances for all versions of the request – only those deemed “relevant” or important. This SHALL NOT include the Provenance associated with this current version of the resource. (If that provenance is deemed to be a “relevant” change, it will need to be added as part of a later update. Until then, it can be queried directly as the Provenance that points to this version using _revinclude All Provenances should have some historical version of this Request as their subject.

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceRequest|3.0.2 to STU3: Protocol or definition (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceRequest.definition (definition)is equivalent toExtension (STU3: Protocol or definition (new))Element `DeviceRequest.definition` has a context of DeviceRequest based on following the parent source element upwards and mapping to `DeviceRequest`. Element `DeviceRequest.definition` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceRequest|3.0.2 to STU3: proposal | plan | original-order | encoded | reflex-order additional types additional codesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceRequest.intent (intent)is equivalent toExtension (STU3: proposal | plan | original-order | encoded | reflex-order additional types additional codes)Element `DeviceRequest.intent` is mapped to FHIR R4 element `DeviceRequest.intent` as `RelatedTo`. The mappings for `DeviceRequest.intent` do not cover the following types: CodeableConcept. The mappings for `DeviceRequest.intent` do not cover the following types based on type expansion: coding. The mappings for `DeviceRequest.intent` do not allow expression of the necessary codes, per the bindings on the source and target. The target context `DeviceRequest.intent` is a modifier element, so this extension does not need to be defined as a modifier.

Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceRequest|3.0.2 to STU3: Organization agent is acting for (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceRequest.requester.onBehalfOf (onBehalfOf)is equivalent toExtension (STU3: Organization agent is acting for (new))Element `DeviceRequest.requester.onBehalfOf` has a context of DeviceRequest.requester based on following the parent source element upwards and mapping to `DeviceRequest`. Element `DeviceRequest.requester.onBehalfOf` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Source1

{
  "resourceType": "ConceptMap",
  "id": "R3-DeviceRequest-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-r3.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-r3.r4"
          }
        ]
      }
    }
  ],
  "url": "http://hl7.org/fhir/uv/xver/ConceptMap/R3-DeviceRequest-element-map-to-R4",
  "version": "0.1.0",
  "name": "R3DeviceRequestElementMapToR4",
  "title": "Cross-version mapping for FHIR STU3 DeviceRequest to FHIR R4 DeviceRequest",
  "status": "active",
  "experimental": false,
  "date": "2026-03-17T16:03:23.621339-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 DeviceRequest to FHIR R4.",
  "jurisdiction": [
    {
      "coding": [
        {
          "system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code": "001",
          "display": "World"
        }
      ]
    }
  ],
  "sourceCanonical": "http://hl7.org/fhir/3.0",
  "targetUri": "http://hl7.org/fhir/4.0",
  "group": [
    {
      "source": "http://hl7.org/fhir/StructureDefinition/DeviceRequest",
      "sourceVersion": "3.0.2",
      "target": "http://hl7.org/fhir/StructureDefinition/DeviceRequest",
      "targetVersion": "4.0.1",
      "element": [
        {
          "code": "DeviceRequest.meta",
          "display": "meta",
          "target": [
            {
              "code": "DeviceRequest.meta",
              "display": "DeviceRequest.meta",
              "equivalence": "equivalent",
              "comment": "Element `DeviceRequest.meta` is mapped to FHIR R4 element `DeviceRequest.meta` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceRequest.implicitRules",
          "display": "implicitRules",
          "target": [
            {
              "code": "DeviceRequest.implicitRules",
              "display": "DeviceRequest.implicitRules",
              "equivalence": "equivalent",
              "comment": "Element `DeviceRequest.implicitRules` is mapped to FHIR R4 element `DeviceRequest.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": "DeviceRequest.language",
          "display": "language",
          "target": [
            {
              "code": "DeviceRequest.language",
              "display": "DeviceRequest.language",
              "equivalence": "equivalent",
              "comment": "Element `DeviceRequest.language` is mapped to FHIR R4 element `DeviceRequest.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": "DeviceRequest.text",
          "display": "text",
          "target": [
            {
              "code": "DeviceRequest.text",
              "display": "DeviceRequest.text",
              "equivalence": "equivalent",
              "comment": "Element `DeviceRequest.text` is mapped to FHIR R4 element `DeviceRequest.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 in formation is added later."
            }
          ]
        },
        {
          "code": "DeviceRequest.contained",
          "display": "contained",
          "target": [
            {
              "code": "DeviceRequest.contained",
              "display": "DeviceRequest.contained",
              "equivalence": "equivalent",
              "comment": "Element `DeviceRequest.contained` is mapped to FHIR R4 element `DeviceRequest.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."
            }
          ]
        },
        {
          "code": "DeviceRequest.identifier",
          "display": "identifier",
          "target": [
            {
              "code": "DeviceRequest.identifier",
              "display": "DeviceRequest.identifier",
              "equivalence": "equivalent",
              "comment": "Element `DeviceRequest.identifier` is mapped to FHIR R4 element `DeviceRequest.identifier` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceRequest.basedOn",
          "display": "basedOn",
          "target": [
            {
              "code": "DeviceRequest.basedOn",
              "display": "DeviceRequest.basedOn",
              "equivalence": "equivalent",
              "comment": "Element `DeviceRequest.basedOn` is mapped to FHIR R4 element `DeviceRequest.basedOn` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceRequest.priorRequest",
          "display": "priorRequest",
          "target": [
            {
              "code": "DeviceRequest.priorRequest",
              "display": "DeviceRequest.priorRequest",
              "equivalence": "equivalent",
              "comment": "Element `DeviceRequest.priorRequest` is mapped to FHIR R4 element `DeviceRequest.priorRequest` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceRequest.groupIdentifier",
          "display": "groupIdentifier",
          "target": [
            {
              "code": "DeviceRequest.groupIdentifier",
              "display": "DeviceRequest.groupIdentifier",
              "equivalence": "equivalent",
              "comment": "Element `DeviceRequest.groupIdentifier` is mapped to FHIR R4 element `DeviceRequest.groupIdentifier` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceRequest.status",
          "display": "status",
          "target": [
            {
              "code": "DeviceRequest.status",
              "display": "DeviceRequest.status",
              "equivalence": "equivalent",
              "comment": "Element `DeviceRequest.status` is mapped to FHIR R4 element `DeviceRequest.status` as `Equivalent`.\nThis element is labeled as a modifier because the status contains the codes cancelled and entered-in-error that mark the request as not currently valid."
            }
          ]
        },
        {
          "code": "DeviceRequest.intent",
          "display": "intent",
          "target": [
            {
              "code": "DeviceRequest.intent",
              "display": "DeviceRequest.intent",
              "equivalence": "wider",
              "comment": "Element `DeviceRequest.intent` is mapped to FHIR R4 element `DeviceRequest.intent` as `RelatedTo`.\nThe mappings for `DeviceRequest.intent` do not cover the following types: CodeableConcept.\nThe mappings for `DeviceRequest.intent` do not cover the following types based on type expansion: coding.\nThe mappings for `DeviceRequest.intent` do not allow expression of the necessary codes, per the bindings on the source and target.\nThe target context `DeviceRequest.intent` is a modifier element, so this extension does not need to be defined as a modifier."
            }
          ]
        },
        {
          "code": "DeviceRequest.priority",
          "display": "priority",
          "target": [
            {
              "code": "DeviceRequest.priority",
              "display": "DeviceRequest.priority",
              "equivalence": "equivalent",
              "comment": "Element `DeviceRequest.priority` is mapped to FHIR R4 element `DeviceRequest.priority` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceRequest.code[x]",
          "display": "code[x]",
          "target": [
            {
              "code": "DeviceRequest.code[x]",
              "display": "DeviceRequest.code[x]",
              "equivalence": "equivalent",
              "comment": "Element `DeviceRequest.code[x]` is mapped to FHIR R4 element `DeviceRequest.code[x]` as `Equivalent`.\nThe target context `DeviceRequest.code[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `DeviceRequest`."
            }
          ]
        },
        {
          "code": "DeviceRequest.subject",
          "display": "subject",
          "target": [
            {
              "code": "DeviceRequest.subject",
              "display": "DeviceRequest.subject",
              "equivalence": "equivalent",
              "comment": "Element `DeviceRequest.subject` is mapped to FHIR R4 element `DeviceRequest.subject` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceRequest.context",
          "display": "context",
          "target": [
            {
              "code": "DeviceRequest.encounter",
              "display": "DeviceRequest.encounter",
              "equivalence": "wider",
              "comment": "Element `DeviceRequest.context` is mapped to FHIR R4 element `DeviceRequest.encounter` as `SourceIsBroaderThanTarget`.\nThe mappings for `DeviceRequest.context` 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 `DeviceRequest.context` with unmapped reference targets: EpisodeOfCare."
            }
          ]
        },
        {
          "code": "DeviceRequest.occurrence[x]",
          "display": "occurrence[x]",
          "target": [
            {
              "code": "DeviceRequest.occurrence[x]",
              "display": "DeviceRequest.occurrence[x]",
              "equivalence": "equivalent",
              "comment": "Element `DeviceRequest.occurrence[x]` is mapped to FHIR R4 element `DeviceRequest.occurrence[x]` as `Equivalent`.\nThe target context `DeviceRequest.occurrence[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `DeviceRequest`."
            }
          ]
        },
        {
          "code": "DeviceRequest.authoredOn",
          "display": "authoredOn",
          "target": [
            {
              "code": "DeviceRequest.authoredOn",
              "display": "DeviceRequest.authoredOn",
              "equivalence": "equivalent",
              "comment": "Element `DeviceRequest.authoredOn` is mapped to FHIR R4 element `DeviceRequest.authoredOn` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceRequest.requester",
          "display": "requester",
          "target": [
            {
              "code": "DeviceRequest.requester",
              "display": "DeviceRequest.requester",
              "equivalence": "wider",
              "comment": "Element `DeviceRequest.requester` is mapped to FHIR R4 element `DeviceRequest.requester` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceRequest.requester.agent",
          "display": "agent",
          "target": [
            {
              "code": "DeviceRequest.requester",
              "display": "DeviceRequest.requester",
              "equivalence": "equivalent",
              "comment": "Element `DeviceRequest.requester.agent` is mapped to FHIR R4 element `DeviceRequest.requester` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceRequest.performerType",
          "display": "performerType",
          "target": [
            {
              "code": "DeviceRequest.performerType",
              "display": "DeviceRequest.performerType",
              "equivalence": "equivalent",
              "comment": "Element `DeviceRequest.performerType` is mapped to FHIR R4 element `DeviceRequest.performerType` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceRequest.performer",
          "display": "performer",
          "target": [
            {
              "code": "DeviceRequest.performer",
              "display": "DeviceRequest.performer",
              "equivalence": "equivalent",
              "comment": "Element `DeviceRequest.performer` is mapped to FHIR R4 element `DeviceRequest.performer` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceRequest.reasonCode",
          "display": "reasonCode",
          "target": [
            {
              "code": "DeviceRequest.reasonCode",
              "display": "DeviceRequest.reasonCode",
              "equivalence": "equivalent",
              "comment": "Element `DeviceRequest.reasonCode` is mapped to FHIR R4 element `DeviceRequest.reasonCode` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceRequest.reasonReference",
          "display": "reasonReference",
          "target": [
            {
              "code": "DeviceRequest.reasonReference",
              "display": "DeviceRequest.reasonReference",
              "equivalence": "wider",
              "comment": "Element `DeviceRequest.reasonReference` is mapped to FHIR R4 element `DeviceRequest.reasonReference` as `SourceIsBroaderThanTarget`.\nThe mappings for `DeviceRequest.reasonReference` 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 `DeviceRequest.reasonReference` with unmapped reference targets: Resource."
            }
          ]
        },
        {
          "code": "DeviceRequest.supportingInfo",
          "display": "supportingInfo",
          "target": [
            {
              "code": "DeviceRequest.supportingInfo",
              "display": "DeviceRequest.supportingInfo",
              "equivalence": "equivalent",
              "comment": "Element `DeviceRequest.supportingInfo` is mapped to FHIR R4 element `DeviceRequest.supportingInfo` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceRequest.note",
          "display": "note",
          "target": [
            {
              "code": "DeviceRequest.note",
              "display": "DeviceRequest.note",
              "equivalence": "equivalent",
              "comment": "Element `DeviceRequest.note` is mapped to FHIR R4 element `DeviceRequest.note` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceRequest.relevantHistory",
          "display": "relevantHistory",
          "target": [
            {
              "code": "DeviceRequest.relevantHistory",
              "display": "DeviceRequest.relevantHistory",
              "equivalence": "equivalent",
              "comment": "Element `DeviceRequest.relevantHistory` is mapped to FHIR R4 element `DeviceRequest.relevantHistory` as `Equivalent`.\nThis may not include provenances for all versions of the request – only those deemed “relevant” or important.\rThis SHALL NOT include the Provenance associated with this current version of the resource.  (If that provenance is deemed to be a “relevant” change, it will need to be added as part of a later update.  Until then, it can be queried directly as the Provenance that points to this version using _revinclude\rAll Provenances should have some historical version of this Request as their subject."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/DeviceRequest",
      "sourceVersion": "3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-DeviceRequest.definition",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "DeviceRequest.definition",
          "display": "definition",
          "target": [
            {
              "code": "Extension",
              "equivalence": "equivalent",
              "comment": "Element `DeviceRequest.definition` has a context of DeviceRequest based on following the parent source element upwards and mapping to `DeviceRequest`.\nElement `DeviceRequest.definition` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/DeviceRequest",
      "sourceVersion": "3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-DeviceRequest.intent",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "DeviceRequest.intent",
          "display": "intent",
          "target": [
            {
              "code": "Extension",
              "equivalence": "equivalent",
              "comment": "Element `DeviceRequest.intent` is mapped to FHIR R4 element `DeviceRequest.intent` as `RelatedTo`.\nThe mappings for `DeviceRequest.intent` do not cover the following types: CodeableConcept.\nThe mappings for `DeviceRequest.intent` do not cover the following types based on type expansion: coding.\nThe mappings for `DeviceRequest.intent` do not allow expression of the necessary codes, per the bindings on the source and target.\nThe target context `DeviceRequest.intent` is a modifier element, so this extension does not need to be defined as a modifier."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/DeviceRequest",
      "sourceVersion": "3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-DeviceRequest.requester.onBehalfOf",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "DeviceRequest.requester.onBehalfOf",
          "display": "onBehalfOf",
          "target": [
            {
              "code": "Extension",
              "equivalence": "equivalent",
              "comment": "Element `DeviceRequest.requester.onBehalfOf` has a context of DeviceRequest.requester based on following the parent source element upwards and mapping to `DeviceRequest`.\nElement `DeviceRequest.requester.onBehalfOf` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    }
  ]
}