Extensions for Using Data Elements from FHIR STU3 in FHIR R4B
0.1.0 - STU
Extensions for Using Data Elements from FHIR STU3 in FHIR R4B
0.1.0 - STU
Extensions for Using Data Elements from FHIR STU3 in FHIR R4B - Downloaded Version null See the Directory of published versions
| Official URL: http://hl7.org/fhir/uv/xver/ConceptMap/R3-ProcedureRequest-element-map-to-R4B | Version: 0.1.0 | |||
| Standards status: Trial-use | Maturity Level: 0 | Computable Name: R3ProcedureRequestElementMapToR4B | ||
This ConceptMap represents cross-version mappings for elements from a FHIR STU3 ProcedureRequest to FHIR R4B.
Mapping from http://hl7.org/fhir/3.0 to http://hl7.org/fhir/4.3
Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/ProcedureRequest|3.0.2 to ServiceRequestversion: 4.3.0)
| Source Code | Relationship | Target Code | Comment |
| ProcedureRequest.meta (meta) | maps to wider concept | ServiceRequest.meta | Element `ProcedureRequest.meta` is mapped to FHIR R4B element `ServiceRequest.meta` as `SourceIsBroaderThanTarget`. The mappings for `ProcedureRequest.meta` do not cover the following types: Meta. The mappings for `ProcedureRequest.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId. |
| ProcedureRequest.implicitRules (implicitRules) | is equivalent to | ServiceRequest.implicitRules | Element `ProcedureRequest.implicitRules` is mapped to FHIR R4B element `ServiceRequest.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. |
| ProcedureRequest.language (language) | is equivalent to | ServiceRequest.language | Element `ProcedureRequest.language` is mapped to FHIR R4B element `ServiceRequest.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). |
| ProcedureRequest.text (text) | maps to wider concept | ServiceRequest.text | Element `ProcedureRequest.text` is mapped to FHIR R4B element `ServiceRequest.text` as `SourceIsBroaderThanTarget`. The mappings for `ProcedureRequest.text` do not cover the following types: Narrative. The mappings for `ProcedureRequest.text` do not cover the following types based on type expansion: div, status. 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. |
| ProcedureRequest.contained (contained) | is equivalent to | ServiceRequest.contained | Element `ProcedureRequest.contained` is mapped to FHIR R4B element `ServiceRequest.contained` as `SourceIsBroaderThanTarget`. 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. |
| ProcedureRequest.identifier (identifier) | maps to wider concept | ServiceRequest.identifier | Element `ProcedureRequest.identifier` is mapped to FHIR R4B element `ServiceRequest.identifier` as `SourceIsBroaderThanTarget`. The mappings for `ProcedureRequest.identifier` do not cover the following types: Identifier. The mappings for `ProcedureRequest.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value. The 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. |
| ProcedureRequest.basedOn (basedOn) | maps to wider concept | ServiceRequest.basedOn | Element `ProcedureRequest.basedOn` is mapped to FHIR R4B element `ServiceRequest.basedOn` as `SourceIsBroaderThanTarget`. The mappings for `ProcedureRequest.basedOn` 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 `ProcedureRequest.basedOn` with unmapped reference targets: Resource. |
| ProcedureRequest.replaces (replaces) | maps to wider concept | ServiceRequest.replaces | Element `ProcedureRequest.replaces` is mapped to FHIR R4B element `ServiceRequest.replaces` as `SourceIsBroaderThanTarget`. The mappings for `ProcedureRequest.replaces` 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 `ProcedureRequest.replaces` with unmapped reference targets: Resource. |
| ProcedureRequest.requisition (requisition) | maps to wider concept | ServiceRequest.requisition | Element `ProcedureRequest.requisition` is mapped to FHIR R4B element `ServiceRequest.requisition` as `SourceIsBroaderThanTarget`. The mappings for `ProcedureRequest.requisition` do not cover the following types: Identifier. The mappings for `ProcedureRequest.requisition` do not cover the following types based on type expansion: assigner, period, system, type, use, value. Requests 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. |
| ProcedureRequest.status (status) | is equivalent to | ServiceRequest.status | Element `ProcedureRequest.status` is mapped to FHIR R4B element `ServiceRequest.status` as `Equivalent`. The 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. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid. |
| ProcedureRequest.intent (intent) | narrower | ServiceRequest.intent | Element `ProcedureRequest.intent` is mapped to FHIR R4B element `ServiceRequest.intent` as `SourceIsNarrowerThanTarget`. The mappings for `ProcedureRequest.intent` do not allow expression of the necessary codes, per the bindings on the source and target. This element is labeled as a modifier because the intent alters when and how the resource is actually applicable. |
| ProcedureRequest.priority (priority) | is equivalent to | ServiceRequest.priority | Element `ProcedureRequest.priority` is mapped to FHIR R4B element `ServiceRequest.priority` as `Equivalent`. |
| ProcedureRequest.doNotPerform (doNotPerform) | is equivalent to | ServiceRequest.doNotPerform | Element `ProcedureRequest.doNotPerform` is mapped to FHIR R4B element `ServiceRequest.doNotPerform` as `Equivalent`. This 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. |
| ProcedureRequest.category (category) | is equivalent to | ServiceRequest.category | Element `ProcedureRequest.category` is mapped to FHIR R4B element `ServiceRequest.category` as `Equivalent`. There 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. |
| ProcedureRequest.code (code) | is equivalent to | ServiceRequest.code | Element `ProcedureRequest.code` is mapped to FHIR R4B element `ServiceRequest.code` as `Equivalent`. Many 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. |
| ProcedureRequest.subject (subject) | maps to wider concept | ServiceRequest.subject | Element `ProcedureRequest.subject` is mapped to FHIR R4B element `ServiceRequest.subject` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `ProcedureRequest.subject` with unmapped reference targets: Device, Group, Location, Patient. |
| ProcedureRequest.context (context) | maps to wider concept | ServiceRequest.encounter | Element `ProcedureRequest.context` is mapped to FHIR R4B element `ServiceRequest.encounter` as `SourceIsBroaderThanTarget`. The mappings for `ProcedureRequest.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 `ProcedureRequest.context` with unmapped reference targets: Encounter, EpisodeOfCare. |
| ProcedureRequest.occurrence[x] (occurrence[x]) | maps to wider concept | ServiceRequest.occurrence[x] | Element `ProcedureRequest.occurrence[x]` is mapped to FHIR R4B element `ServiceRequest.occurrence[x]` as `SourceIsBroaderThanTarget`. The mappings for `ProcedureRequest.occurrence[x]` do not cover the following types: Period, Timing. The target context `ServiceRequest.occurrence[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `ServiceRequest`. |
| ProcedureRequest.asNeeded[x] (asNeeded[x]) | is equivalent to | ServiceRequest.asNeeded[x] | Element `ProcedureRequest.asNeeded[x]` is mapped to FHIR R4B element `ServiceRequest.asNeeded[x]` as `Equivalent`. The target context `ServiceRequest.asNeeded[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `ServiceRequest`. |
| ProcedureRequest.authoredOn (authoredOn) | is equivalent to | ServiceRequest.authoredOn | Element `ProcedureRequest.authoredOn` is mapped to FHIR R4B element `ServiceRequest.authoredOn` as `Equivalent`. |
| ProcedureRequest.requester (requester) | maps to wider concept | ServiceRequest.requester | Element `ProcedureRequest.requester` is mapped to FHIR R4B element `ServiceRequest.requester` as `Equivalent`. This not the dispatcher, but rather who is the authorizer. |
| ProcedureRequest.requester.agent (agent) | maps to wider concept | ServiceRequest.requester | Element `ProcedureRequest.requester.agent` is mapped to FHIR R4B element `ServiceRequest.requester` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `ProcedureRequest.requester.agent` with unmapped reference targets: Device, Organization, Practitioner. |
| ProcedureRequest.performerType (performerType) | is equivalent to | ServiceRequest.performerType | Element `ProcedureRequest.performerType` is mapped to FHIR R4B element `ServiceRequest.performerType` as `Equivalent`. this 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”. |
| ProcedureRequest.performer (performer) | is related to | ServiceRequest.performer | Element `ProcedureRequest.performer` is mapped to FHIR R4B element `ServiceRequest.performer` as `RelatedTo`. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `ProcedureRequest.performer` with unmapped reference targets: Device, HealthcareService, Organization, Patient, Practitioner, RelatedPerson. If needed, use an [extension](https://hl7.org/fhir/extensibility.html) for listing alternative performers and/or roles and/or preference. |
| ProcedureRequest.reasonCode (reasonCode) | is equivalent to | ServiceRequest.reasonCode | Element `ProcedureRequest.reasonCode` is mapped to FHIR R4B element `ServiceRequest.reasonCode` as `Equivalent`. This 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). |
| ProcedureRequest.reasonReference (reasonReference) | maps to wider concept | ServiceRequest.reasonReference | Element `ProcedureRequest.reasonReference` is mapped to FHIR R4B element `ServiceRequest.reasonReference` as `SourceIsBroaderThanTarget`. The mappings for `ProcedureRequest.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 `ProcedureRequest.reasonReference` with unmapped reference targets: Condition, Observation. This 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). |
| ProcedureRequest.supportingInfo (supportingInfo) | maps to wider concept | ServiceRequest.supportingInfo | Element `ProcedureRequest.supportingInfo` is mapped to FHIR R4B element `ServiceRequest.supportingInfo` as `SourceIsBroaderThanTarget`. The mappings for `ProcedureRequest.supportingInfo` 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 `ProcedureRequest.supportingInfo` with unmapped reference targets: Resource. |
| ProcedureRequest.specimen (specimen) | maps to wider concept | ServiceRequest.specimen | Element `ProcedureRequest.specimen` is mapped to FHIR R4B element `ServiceRequest.specimen` as `SourceIsBroaderThanTarget`. The mappings for `ProcedureRequest.specimen` 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 `ProcedureRequest.specimen` with unmapped reference targets: Specimen. Many 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. |
| ProcedureRequest.bodySite (bodySite) | is equivalent to | ServiceRequest.bodySite | Element `ProcedureRequest.bodySite` is mapped to FHIR R4B element `ServiceRequest.bodySite` as `Equivalent`. Only 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). |
| ProcedureRequest.note (note) | maps to wider concept | ServiceRequest.note | Element `ProcedureRequest.note` is mapped to FHIR R4B element `ServiceRequest.note` as `SourceIsBroaderThanTarget`. The mappings for `ProcedureRequest.note` do not cover the following types: Annotation. The mappings for `ProcedureRequest.note` do not cover the following types based on type expansion: author[x], text, time. |
| ProcedureRequest.relevantHistory (relevantHistory) | maps to wider concept | ServiceRequest.relevantHistory | Element `ProcedureRequest.relevantHistory` is mapped to FHIR R4B element `ServiceRequest.relevantHistory` as `SourceIsBroaderThanTarget`. The mappings for `ProcedureRequest.relevantHistory` 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 `ProcedureRequest.relevantHistory` with unmapped reference targets: Provenance. 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/ProcedureRequest|3.0.2 to STU3: meta additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ProcedureRequest.meta (meta) | maps to wider concept | Extension (STU3: meta additional types) | Element `ProcedureRequest.meta` is mapped to FHIR R4B element `ServiceRequest.meta` as `SourceIsBroaderThanTarget`. The mappings for `ProcedureRequest.meta` do not cover the following types: Meta. The mappings for `ProcedureRequest.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId. |
Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/ProcedureRequest|3.0.2 to STU3: text additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ProcedureRequest.text (text) | maps to wider concept | Extension (STU3: text additional types) | Element `ProcedureRequest.text` is mapped to FHIR R4B element `ServiceRequest.text` as `SourceIsBroaderThanTarget`. The mappings for `ProcedureRequest.text` do not cover the following types: Narrative. The mappings for `ProcedureRequest.text` do not cover the following types based on type expansion: div, status. 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. |
Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/ProcedureRequest|3.0.2 to STU3: identifier additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ProcedureRequest.identifier (identifier) | maps to wider concept | Extension (STU3: identifier additional types) | Element `ProcedureRequest.identifier` is mapped to FHIR R4B element `ServiceRequest.identifier` as `SourceIsBroaderThanTarget`. The mappings for `ProcedureRequest.identifier` do not cover the following types: Identifier. The mappings for `ProcedureRequest.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value. The 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. |
Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/ProcedureRequest|3.0.2 to STU3: Protocol or definition (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ProcedureRequest.definition (definition) | is equivalent to | Extension (STU3: Protocol or definition (new)) | Element `ProcedureRequest.definition` has a context of ServiceRequest based on following the parent source element upwards and mapping to `ServiceRequest`. Element `ProcedureRequest.definition` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). |
Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/ProcedureRequest|3.0.2 to STU3: requisition additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ProcedureRequest.requisition (requisition) | maps to wider concept | Extension (STU3: requisition additional types) | Element `ProcedureRequest.requisition` is mapped to FHIR R4B element `ServiceRequest.requisition` as `SourceIsBroaderThanTarget`. The mappings for `ProcedureRequest.requisition` do not cover the following types: Identifier. The mappings for `ProcedureRequest.requisition` do not cover the following types based on type expansion: assigner, period, system, type, use, value. Requests 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. |
Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/ProcedureRequest|3.0.2 to STU3: When procedure should occur additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ProcedureRequest.occurrence[x] (occurrence[x]) | maps to wider concept | Extension (STU3: When procedure should occur additional types) | Element `ProcedureRequest.occurrence[x]` is mapped to FHIR R4B element `ServiceRequest.occurrence[x]` as `SourceIsBroaderThanTarget`. The mappings for `ProcedureRequest.occurrence[x]` do not cover the following types: Period, Timing. The target context `ServiceRequest.occurrence[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `ServiceRequest`. |
Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/ProcedureRequest|3.0.2 to STU3: Organization agent is acting for (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ProcedureRequest.requester.onBehalfOf (onBehalfOf) | is equivalent to | Extension (STU3: Organization agent is acting for (new)) | Element `ProcedureRequest.requester.onBehalfOf` has a context of ServiceRequest.requester based on following the parent source element upwards and mapping to `ServiceRequest`. Element `ProcedureRequest.requester.onBehalfOf` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). |
Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/ProcedureRequest|3.0.2 to STU3: note additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ProcedureRequest.note (note) | maps to wider concept | Extension (STU3: note additional types) | Element `ProcedureRequest.note` is mapped to FHIR R4B element `ServiceRequest.note` as `SourceIsBroaderThanTarget`. The mappings for `ProcedureRequest.note` do not cover the following types: Annotation. The mappings for `ProcedureRequest.note` do not cover the following types based on type expansion: author[x], text, time. |
IG © 2025+ FHIR Infrastructure. Package hl7.fhir.uv.xver-r3.r4b#0.1.0 based on FHIR 4.3.0. Generated 2026-03-20
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change