Extensions for Using Data Elements from FHIR STU3 in FHIR R4
0.1.0 - STU
Extensions for Using Data Elements from FHIR STU3 in FHIR R4
0.1.0 - STU
Extensions for Using Data Elements from FHIR STU3 in FHIR R4 - Downloaded Version null See the Directory of published versions
| Official URL: http://hl7.org/fhir/uv/xver/ConceptMap/R3-ProcessRequest-element-map-to-R4 | Version: 0.1.0 | |||
| Standards status: Trial-use | Maturity Level: 0 | Computable Name: R3ProcessRequestElementMapToR4 | ||
This ConceptMap represents cross-version mappings for elements from a FHIR STU3 ProcessRequest to FHIR 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/ProcessRequest|3.0.2 to Taskversion: 4.0.1)
| Source Code | Relationship | Target Code | Comment |
| ProcessRequest.meta (meta) | is equivalent to | Task.meta | Element `ProcessRequest.meta` is mapped to FHIR R4 element `Task.meta` as `Equivalent`. |
| ProcessRequest.implicitRules (implicitRules) | is equivalent to | Task.implicitRules | Element `ProcessRequest.implicitRules` is mapped to FHIR R4 element `Task.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. |
| ProcessRequest.language (language) | is equivalent to | Task.language | Element `ProcessRequest.language` is mapped to FHIR R4 element `Task.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). |
| ProcessRequest.text (text) | is equivalent to | Task.text | Element `ProcessRequest.text` is mapped to FHIR R4 element `Task.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. |
| ProcessRequest.contained (contained) | is equivalent to | Task.contained | Element `ProcessRequest.contained` is mapped to FHIR R4 element `Task.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. |
| ProcessRequest.identifier (identifier) | is equivalent to | Task.identifier | Element `ProcessRequest.identifier` is mapped to FHIR R4 element `Task.identifier` as `Equivalent`. |
| ProcessRequest.status (status) | is related to | Task.status | Element `ProcessRequest.status` is mapped to FHIR R4 element `Task.status` as `RelatedTo`. The mappings for `ProcessRequest.status` do not allow expression of the necessary codes, per the bindings on the source and target. The target context `Task.status` is a modifier element, so this extension does not need to be defined as a modifier. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid. |
Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/ProcessRequest|3.0.2 to STU3: active | cancelled | draft | entered-in-error additional codesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ProcessRequest.status (status) | maps to wider concept | Extension (STU3: active | cancelled | draft | entered-in-error additional codes) | Element `ProcessRequest.status` is mapped to FHIR R4 element `Task.status` as `RelatedTo`. The mappings for `ProcessRequest.status` do not allow expression of the necessary codes, per the bindings on the source and target. The target context `Task.status` is a modifier element, so this extension does not need to be defined as a modifier. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid. |
Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/ProcessRequest|3.0.2 to STU3: cancel | poll | reprocess | status (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ProcessRequest.action (action) | is equivalent to | Extension (STU3: cancel | poll | reprocess | status (new)) | Element `ProcessRequest.action` has a context of Task based on following the parent source element upwards and mapping to `Task`. Element `ProcessRequest.action` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/ProcessRequest|3.0.2 to STU3: Party which is the target of the request (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ProcessRequest.target (target) | is equivalent to | Extension (STU3: Party which is the target of the request (new)) | Element `ProcessRequest.target` has a context of Task based on following the parent source element upwards and mapping to `Task`. Element `ProcessRequest.target` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/ProcessRequest|3.0.2 to STU3: Creation date (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ProcessRequest.created (created) | is equivalent to | Extension (STU3: Creation date (new)) | Element `ProcessRequest.created` has a context of Task based on following the parent source element upwards and mapping to `Task`. Element `ProcessRequest.created` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/ProcessRequest|3.0.2 to STU3: Responsible practitioner (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ProcessRequest.provider (provider) | is equivalent to | Extension (STU3: Responsible practitioner (new)) | Element `ProcessRequest.provider` has a context of Task based on following the parent source element upwards and mapping to `Task`. Element `ProcessRequest.provider` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/ProcessRequest|3.0.2 to STU3: Responsible organization (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ProcessRequest.organization (organization) | is equivalent to | Extension (STU3: Responsible organization (new)) | Element `ProcessRequest.organization` has a context of Task based on following the parent source element upwards and mapping to `Task`. Element `ProcessRequest.organization` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/ProcessRequest|3.0.2 to STU3: Reference to the Request resource (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ProcessRequest.request (request) | is equivalent to | Extension (STU3: Reference to the Request resource (new)) | Element `ProcessRequest.request` has a context of Task based on following the parent source element upwards and mapping to `Task`. Element `ProcessRequest.request` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/ProcessRequest|3.0.2 to STU3: Reference to the Response resource (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ProcessRequest.response (response) | is equivalent to | Extension (STU3: Reference to the Response resource (new)) | Element `ProcessRequest.response` has a context of Task based on following the parent source element upwards and mapping to `Task`. Element `ProcessRequest.response` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
Group 10 Mapping from http://hl7.org/fhir/StructureDefinition/ProcessRequest|3.0.2 to STU3: Remove history (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ProcessRequest.nullify (nullify) | is equivalent to | Extension (STU3: Remove history (new)) | Element `ProcessRequest.nullify` has a context of Task based on following the parent source element upwards and mapping to `Task`. Element `ProcessRequest.nullify` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
Group 11 Mapping from http://hl7.org/fhir/StructureDefinition/ProcessRequest|3.0.2 to STU3: Reference number/string (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ProcessRequest.reference (reference) | is equivalent to | Extension (STU3: Reference number/string (new)) | Element `ProcessRequest.reference` has a context of Task based on following the parent source element upwards and mapping to `Task`. Element `ProcessRequest.reference` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
Group 12 Mapping from http://hl7.org/fhir/StructureDefinition/ProcessRequest|3.0.2 to STU3: Items to re-adjudicate (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ProcessRequest.item (item) | maps to wider concept | Extension (STU3: Items to re-adjudicate (new)) | Element `ProcessRequest.item` has a context of Task based on following the parent source element upwards and mapping to `Task`. Element `ProcessRequest.item` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
| ProcessRequest.item.sequenceLinkId (sequenceLinkId) | is equivalent to | Extension.extension:sequenceLinkId (STU3: Service instance (new)) | Element `ProcessRequest.item.sequenceLinkId` is part of an existing definition because parent element `ProcessRequest.item` requires a cross-version extension. Element `ProcessRequest.item.sequenceLinkId` has a context of Task based on following the parent source element upwards and mapping to `Task`. Element `ProcessRequest.item.sequenceLinkId` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
Group 13 Mapping from http://hl7.org/fhir/StructureDefinition/ProcessRequest|3.0.2 to STU3: Resource type(s) to include (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ProcessRequest.include (include) | is equivalent to | Extension (STU3: Resource type(s) to include (new)) | Element `ProcessRequest.include` has a context of Task based on following the parent source element upwards and mapping to `Task`. Element `ProcessRequest.include` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
Group 14 Mapping from http://hl7.org/fhir/StructureDefinition/ProcessRequest|3.0.2 to STU3: Resource type(s) to exclude (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ProcessRequest.exclude (exclude) | is equivalent to | Extension (STU3: Resource type(s) to exclude (new)) | Element `ProcessRequest.exclude` has a context of Task based on following the parent source element upwards and mapping to `Task`. Element `ProcessRequest.exclude` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
Group 15 Mapping from http://hl7.org/fhir/StructureDefinition/ProcessRequest|3.0.2 to STU3: Selection period (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| ProcessRequest.period (period) | is equivalent to | Extension (STU3: Selection period (new)) | Element `ProcessRequest.period` has a context of Task based on following the parent source element upwards and mapping to `Task`. Element `ProcessRequest.period` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
IG © 2025+ FHIR Infrastructure. Package hl7.fhir.uv.xver-r3.r4#0.1.0 based on FHIR 4.0.1. Generated 2026-03-20
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change