FHIR IG analytics

Resources that use this resource

No resources found

Resources that this resource uses

Narrative

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

Source1

{
  "resourceType": "ConceptMap",
  "id": "R3-ProcedureRequest-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-ProcedureRequest-element-map-to-R4",
  "version": "0.1.0",
  "name": "R3ProcedureRequestElementMapToR4",
  "title": "Cross-version mapping for FHIR STU3 ProcedureRequest to FHIR R4 ServiceRequest",
  "status": "active",
  "experimental": false,
  "date": "2026-03-17T16:03:24.1149631-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 ProcedureRequest 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/ProcedureRequest",
      "sourceVersion": "3.0.2",
      "target": "http://hl7.org/fhir/StructureDefinition/ServiceRequest",
      "targetVersion": "4.0.1",
      "element": [
        {
          "code": "ProcedureRequest.meta",
          "display": "meta",
          "target": [
            {
              "code": "ServiceRequest.meta",
              "display": "ServiceRequest.meta",
              "equivalence": "equivalent",
              "comment": "Element `ProcedureRequest.meta` is mapped to FHIR R4 element `ServiceRequest.meta` as `Equivalent`."
            }
          ]
        },
        {
          "code": "ProcedureRequest.implicitRules",
          "display": "implicitRules",
          "target": [
            {
              "code": "ServiceRequest.implicitRules",
              "display": "ServiceRequest.implicitRules",
              "equivalence": "equivalent",
              "comment": "Element `ProcedureRequest.implicitRules` is mapped to FHIR R4 element `ServiceRequest.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": "ProcedureRequest.language",
          "display": "language",
          "target": [
            {
              "code": "ServiceRequest.language",
              "display": "ServiceRequest.language",
              "equivalence": "equivalent",
              "comment": "Element `ProcedureRequest.language` is mapped to FHIR R4 element `ServiceRequest.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": "ProcedureRequest.text",
          "display": "text",
          "target": [
            {
              "code": "ServiceRequest.text",
              "display": "ServiceRequest.text",
              "equivalence": "equivalent",
              "comment": "Element `ProcedureRequest.text` is mapped to FHIR R4 element `ServiceRequest.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": "ProcedureRequest.contained",
          "display": "contained",
          "target": [
            {
              "code": "ServiceRequest.contained",
              "display": "ServiceRequest.contained",
              "equivalence": "equivalent",
              "comment": "Element `ProcedureRequest.contained` is mapped to FHIR R4 element `ServiceRequest.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": "ProcedureRequest.identifier",
          "display": "identifier",
          "target": [
            {
              "code": "ServiceRequest.identifier",
              "display": "ServiceRequest.identifier",
              "equivalence": "equivalent",
              "comment": "Element `ProcedureRequest.identifier` is mapped to FHIR R4 element `ServiceRequest.identifier` as `Equivalent`.\nThe identifier.type element is used to distinguish between the identifiers assigned by the orderer (known as the 'Placer' in HL7 v2) and the producer of the observations in response to the order (known as the 'Filler' in HL7 v2).  For further discussion and examples see the resource notes section below."
            }
          ]
        },
        {
          "code": "ProcedureRequest.basedOn",
          "display": "basedOn",
          "target": [
            {
              "code": "ServiceRequest.basedOn",
              "display": "ServiceRequest.basedOn",
              "equivalence": "wider",
              "comment": "Element `ProcedureRequest.basedOn` is mapped to FHIR R4 element `ServiceRequest.basedOn` as `SourceIsBroaderThanTarget`.\nThe mappings for `ProcedureRequest.basedOn` 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 `ProcedureRequest.basedOn` with unmapped reference targets: Resource."
            }
          ]
        },
        {
          "code": "ProcedureRequest.replaces",
          "display": "replaces",
          "target": [
            {
              "code": "ServiceRequest.replaces",
              "display": "ServiceRequest.replaces",
              "equivalence": "wider",
              "comment": "Element `ProcedureRequest.replaces` is mapped to FHIR R4 element `ServiceRequest.replaces` as `SourceIsBroaderThanTarget`.\nThe mappings for `ProcedureRequest.replaces` 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 `ProcedureRequest.replaces` with unmapped reference targets: Resource."
            }
          ]
        },
        {
          "code": "ProcedureRequest.requisition",
          "display": "requisition",
          "target": [
            {
              "code": "ServiceRequest.requisition",
              "display": "ServiceRequest.requisition",
              "equivalence": "equivalent",
              "comment": "Element `ProcedureRequest.requisition` is mapped to FHIR R4 element `ServiceRequest.requisition` as `Equivalent`.\nRequests are linked either by a \"basedOn\" relationship (i.e. one request is fulfilling another) or by having a common requisition. Requests that are part of the same requisition are generally treated independently from the perspective of changing their state or maintaining them after initial creation."
            }
          ]
        },
        {
          "code": "ProcedureRequest.status",
          "display": "status",
          "target": [
            {
              "code": "ServiceRequest.status",
              "display": "ServiceRequest.status",
              "equivalence": "equivalent",
              "comment": "Element `ProcedureRequest.status` is mapped to FHIR R4 element `ServiceRequest.status` as `Equivalent`.\nThe status is generally fully in the control of the requester - they determine whether the order is draft or active and, after it has been activated, competed, cancelled or suspended. States relating to the activities of the performer are reflected on either the corresponding event (see [Event Pattern](https://hl7.org/fhir/event.html) for general discussion) or using the [Task](https://hl7.org/fhir/task.html) resource.\n\nThis element is labeled as a modifier because the status contains codes that mark the resource as not currently valid."
            }
          ]
        },
        {
          "code": "ProcedureRequest.intent",
          "display": "intent",
          "target": [
            {
              "code": "ServiceRequest.intent",
              "display": "ServiceRequest.intent",
              "equivalence": "narrower",
              "comment": "Element `ProcedureRequest.intent` is mapped to FHIR R4 element `ServiceRequest.intent` as `SourceIsNarrowerThanTarget`.\nThe mappings for `ProcedureRequest.intent` do not allow expression of the necessary codes, per the bindings on the source and target.\nThis element is labeled as a modifier because the intent alters when and how the resource is actually applicable."
            }
          ]
        },
        {
          "code": "ProcedureRequest.priority",
          "display": "priority",
          "target": [
            {
              "code": "ServiceRequest.priority",
              "display": "ServiceRequest.priority",
              "equivalence": "equivalent",
              "comment": "Element `ProcedureRequest.priority` is mapped to FHIR R4 element `ServiceRequest.priority` as `Equivalent`."
            }
          ]
        },
        {
          "code": "ProcedureRequest.doNotPerform",
          "display": "doNotPerform",
          "target": [
            {
              "code": "ServiceRequest.doNotPerform",
              "display": "ServiceRequest.doNotPerform",
              "equivalence": "equivalent",
              "comment": "Element `ProcedureRequest.doNotPerform` is mapped to FHIR R4 element `ServiceRequest.doNotPerform` as `Equivalent`.\nThis element is labeled as a [modifier](https://hl7.org/fhir/conformance-rule.html#isModifier.html) because it indicates that a procedure shouldn't happen, instead of a request for it to happen.  In general, only the code and timeframe will be present, though occasional additional qualifiers such as body site or even performer could be included to narrow the scope of the prohibition.  If the ProcedureRequest.code and ProcedureRequest.doNotPerform both contain negation, that will reinforce prohibition and should not have a double negative interpretation."
            }
          ]
        },
        {
          "code": "ProcedureRequest.category",
          "display": "category",
          "target": [
            {
              "code": "ServiceRequest.category",
              "display": "ServiceRequest.category",
              "equivalence": "equivalent",
              "comment": "Element `ProcedureRequest.category` is mapped to FHIR R4 element `ServiceRequest.category` as `Equivalent`.\nThere may be multiple axis of categorization depending on the context or use case for retrieving or displaying the resource.  The level of granularity is defined by the category concepts in the value set."
            }
          ]
        },
        {
          "code": "ProcedureRequest.code",
          "display": "code",
          "target": [
            {
              "code": "ServiceRequest.code",
              "display": "ServiceRequest.code",
              "equivalence": "equivalent",
              "comment": "Element `ProcedureRequest.code` is mapped to FHIR R4 element `ServiceRequest.code` as `Equivalent`.\nMany laboratory and radiology procedure codes embed the specimen/organ system in the test ordeer name, for example,  serum or serum/plasma glucose, or a chest xray. The specimen may not be recorded separately from the test code."
            }
          ]
        },
        {
          "code": "ProcedureRequest.subject",
          "display": "subject",
          "target": [
            {
              "code": "ServiceRequest.subject",
              "display": "ServiceRequest.subject",
              "equivalence": "equivalent",
              "comment": "Element `ProcedureRequest.subject` is mapped to FHIR R4 element `ServiceRequest.subject` as `Equivalent`."
            }
          ]
        },
        {
          "code": "ProcedureRequest.context",
          "display": "context",
          "target": [
            {
              "code": "ServiceRequest.encounter",
              "display": "ServiceRequest.encounter",
              "equivalence": "wider",
              "comment": "Element `ProcedureRequest.context` is mapped to FHIR R4 element `ServiceRequest.encounter` as `SourceIsBroaderThanTarget`.\nThe mappings for `ProcedureRequest.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 `ProcedureRequest.context` with unmapped reference targets: EpisodeOfCare."
            }
          ]
        },
        {
          "code": "ProcedureRequest.occurrence[x]",
          "display": "occurrence[x]",
          "target": [
            {
              "code": "ServiceRequest.occurrence[x]",
              "display": "ServiceRequest.occurrence[x]",
              "equivalence": "equivalent",
              "comment": "Element `ProcedureRequest.occurrence[x]` is mapped to FHIR R4 element `ServiceRequest.occurrence[x]` as `Equivalent`.\nThe target context `ServiceRequest.occurrence[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `ServiceRequest`."
            }
          ]
        },
        {
          "code": "ProcedureRequest.asNeeded[x]",
          "display": "asNeeded[x]",
          "target": [
            {
              "code": "ServiceRequest.asNeeded[x]",
              "display": "ServiceRequest.asNeeded[x]",
              "equivalence": "equivalent",
              "comment": "Element `ProcedureRequest.asNeeded[x]` is mapped to FHIR R4 element `ServiceRequest.asNeeded[x]` as `Equivalent`.\nThe target context `ServiceRequest.asNeeded[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `ServiceRequest`."
            }
          ]
        },
        {
          "code": "ProcedureRequest.authoredOn",
          "display": "authoredOn",
          "target": [
            {
              "code": "ServiceRequest.authoredOn",
              "display": "ServiceRequest.authoredOn",
              "equivalence": "equivalent",
              "comment": "Element `ProcedureRequest.authoredOn` is mapped to FHIR R4 element `ServiceRequest.authoredOn` as `Equivalent`."
            }
          ]
        },
        {
          "code": "ProcedureRequest.requester",
          "display": "requester",
          "target": [
            {
              "code": "ServiceRequest.requester",
              "display": "ServiceRequest.requester",
              "equivalence": "wider",
              "comment": "Element `ProcedureRequest.requester` is mapped to FHIR R4 element `ServiceRequest.requester` as `Equivalent`.\nThis not the dispatcher, but rather who is the authorizer."
            }
          ]
        },
        {
          "code": "ProcedureRequest.requester.agent",
          "display": "agent",
          "target": [
            {
              "code": "ServiceRequest.requester",
              "display": "ServiceRequest.requester",
              "equivalence": "equivalent",
              "comment": "Element `ProcedureRequest.requester.agent` is mapped to FHIR R4 element `ServiceRequest.requester` as `Equivalent`."
            }
          ]
        },
        {
          "code": "ProcedureRequest.performerType",
          "display": "performerType",
          "target": [
            {
              "code": "ServiceRequest.performerType",
              "display": "ServiceRequest.performerType",
              "equivalence": "equivalent",
              "comment": "Element `ProcedureRequest.performerType` is mapped to FHIR R4 element `ServiceRequest.performerType` as `Equivalent`.\nthis is a  role, not  a participation type.  I.e. does not describe the task, but describes the capacity.  For example, “compounding pharmacy” or “psychiatrist” or “internal referral”."
            }
          ]
        },
        {
          "code": "ProcedureRequest.performer",
          "display": "performer",
          "target": [
            {
              "code": "ServiceRequest.performer",
              "display": "ServiceRequest.performer",
              "equivalence": "narrower",
              "comment": "Element `ProcedureRequest.performer` is mapped to FHIR R4 element `ServiceRequest.performer` as `SourceIsNarrowerThanTarget`.\nIf needed, use an [extension](https://hl7.org/fhir/extensibility.html) for listing alternative performers and/or roles and/or preference."
            }
          ]
        },
        {
          "code": "ProcedureRequest.reasonCode",
          "display": "reasonCode",
          "target": [
            {
              "code": "ServiceRequest.reasonCode",
              "display": "ServiceRequest.reasonCode",
              "equivalence": "equivalent",
              "comment": "Element `ProcedureRequest.reasonCode` is mapped to FHIR R4 element `ServiceRequest.reasonCode` as `Equivalent`.\nThis may be used to decide how the diagnostic investigation will be performed, or even if it will be performed at all.   Use CodeableConcept text element if the data is free (uncoded) text as shown in the [CT Scan example](https://hl7.org/fhir/procedurerequest-example-di.html)."
            }
          ]
        },
        {
          "code": "ProcedureRequest.reasonReference",
          "display": "reasonReference",
          "target": [
            {
              "code": "ServiceRequest.reasonReference",
              "display": "ServiceRequest.reasonReference",
              "equivalence": "equivalent",
              "comment": "Element `ProcedureRequest.reasonReference` is mapped to FHIR R4 element `ServiceRequest.reasonReference` as `Equivalent`.\nThis may be used to decide how the diagnostic investigation will be performed, or even if it will be performed at all.   Use CodeableConcept text element if the data is free (uncoded) text as shown in the [CT Scan example](https://hl7.org/fhir/procedurerequest-example-di.html)."
            }
          ]
        },
        {
          "code": "ProcedureRequest.supportingInfo",
          "display": "supportingInfo",
          "target": [
            {
              "code": "ServiceRequest.supportingInfo",
              "display": "ServiceRequest.supportingInfo",
              "equivalence": "equivalent",
              "comment": "Element `ProcedureRequest.supportingInfo` is mapped to FHIR R4 element `ServiceRequest.supportingInfo` as `Equivalent`."
            }
          ]
        },
        {
          "code": "ProcedureRequest.specimen",
          "display": "specimen",
          "target": [
            {
              "code": "ServiceRequest.specimen",
              "display": "ServiceRequest.specimen",
              "equivalence": "equivalent",
              "comment": "Element `ProcedureRequest.specimen` is mapped to FHIR R4 element `ServiceRequest.specimen` as `Equivalent`.\nMany diagnostic procedures need a specimen, but the request itself is not actually about the specimen. This element is for when the diagnostic is requested on already existing specimens and the request points to the specimen it applies to.    Conversely, If the request is entered first with an unknown specimen, The [Specimen](https://hl7.org/fhir/specimen.html) resource references to the ProcedureRequest."
            }
          ]
        },
        {
          "code": "ProcedureRequest.bodySite",
          "display": "bodySite",
          "target": [
            {
              "code": "ServiceRequest.bodySite",
              "display": "ServiceRequest.bodySite",
              "equivalence": "equivalent",
              "comment": "Element `ProcedureRequest.bodySite` is mapped to FHIR R4 element `ServiceRequest.bodySite` as `Equivalent`.\nOnly used if not implicit in the code found in ProcedureRequest.type.  If the use case requires BodySite to be handled as a separate resource instead of an inline coded element (e.g. to identify and track separately)  then use the standard extension [procedurerequest-targetBodySite](https://hl7.org/fhir/extension-procedurerequest-targetbodysite.html)."
            }
          ]
        },
        {
          "code": "ProcedureRequest.note",
          "display": "note",
          "target": [
            {
              "code": "ServiceRequest.note",
              "display": "ServiceRequest.note",
              "equivalence": "equivalent",
              "comment": "Element `ProcedureRequest.note` is mapped to FHIR R4 element `ServiceRequest.note` as `Equivalent`."
            }
          ]
        },
        {
          "code": "ProcedureRequest.relevantHistory",
          "display": "relevantHistory",
          "target": [
            {
              "code": "ServiceRequest.relevantHistory",
              "display": "ServiceRequest.relevantHistory",
              "equivalence": "equivalent",
              "comment": "Element `ProcedureRequest.relevantHistory` is mapped to FHIR R4 element `ServiceRequest.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/ProcedureRequest",
      "sourceVersion": "3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-ProcedureRequest.definition",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "ProcedureRequest.definition",
          "display": "definition",
          "target": [
            {
              "code": "Extension",
              "equivalence": "equivalent",
              "comment": "Element `ProcedureRequest.definition` has a context of ServiceRequest based on following the parent source element upwards and mapping to `ServiceRequest`.\nElement `ProcedureRequest.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/ProcedureRequest",
      "sourceVersion": "3.0.2",
      "target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-ProcedureRequest.requester.onBehalfOf",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "ProcedureRequest.requester.onBehalfOf",
          "display": "onBehalfOf",
          "target": [
            {
              "code": "Extension",
              "equivalence": "equivalent",
              "comment": "Element `ProcedureRequest.requester.onBehalfOf` has a context of ServiceRequest.requester based on following the parent source element upwards and mapping to `ServiceRequest`.\nElement `ProcedureRequest.requester.onBehalfOf` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    }
  ]
}