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
| Page standards status: Trial-use | Maturity Level: 0 |
<ConceptMap xmlns="http://hl7.org/fhir">
<id value="R3-ProcessRequest-element-map-to-R4"/>
<text>
<status value="generated"/>
<div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: ConceptMap R3-ProcessRequest-element-map-to-R4</b></p><a name="R3-ProcessRequest-element-map-to-R4"> </a><a name="hcR3-ProcessRequest-element-map-to-R4"> </a><p>Mapping from http://hl7.org/fhir/3.0 to http://hl7.org/fhir/4.0</p><br/><p><b>Group 1 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ProcessRequest|3.0.2</code> to <a href="http://hl7.org/fhir/R4/task.html">Taskversion: 4.0.1)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>ProcessRequest.meta (meta)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Task.meta</td><td>Element `ProcessRequest.meta` is mapped to FHIR R4 element `Task.meta` as `Equivalent`.</td></tr><tr><td>ProcessRequest.implicitRules (implicitRules)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Task.implicitRules</td><td>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.</td></tr><tr><td>ProcessRequest.language (language)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Task.language</td><td>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).</td></tr><tr><td>ProcessRequest.text (text)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Task.text</td><td>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.</td></tr><tr><td>ProcessRequest.contained (contained)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Task.contained</td><td>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.</td></tr><tr><td>ProcessRequest.identifier (identifier)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Task.identifier</td><td>Element `ProcessRequest.identifier` is mapped to FHIR R4 element `Task.identifier` as `Equivalent`.</td></tr><tr><td>ProcessRequest.status (status)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td>Task.status</td><td>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.</td></tr></table><hr/><p><b>Group 2 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ProcessRequest|3.0.2</code> to <a href="StructureDefinition-ext-R3-ProcessRequest.status.html">STU3: active | cancelled | draft | entered-in-error additional codesversion: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>ProcessRequest.status (status)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (STU3: active | cancelled | draft | entered-in-error additional codes)</td><td>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.</td></tr></table><hr/><p><b>Group 3 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ProcessRequest|3.0.2</code> to <a href="StructureDefinition-ext-R3-ProcessRequest.action.html">STU3: cancel | poll | reprocess | status (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>ProcessRequest.action (action)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (STU3: cancel | poll | reprocess | status (new))</td><td>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).</td></tr></table><hr/><p><b>Group 4 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ProcessRequest|3.0.2</code> to <a href="StructureDefinition-ext-R3-ProcessRequest.target.html">STU3: Party which is the target of the request (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>ProcessRequest.target (target)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (STU3: Party which is the target of the request (new))</td><td>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).</td></tr></table><hr/><p><b>Group 5 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ProcessRequest|3.0.2</code> to <a href="StructureDefinition-ext-R3-ProcessRequest.created.html">STU3: Creation date (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>ProcessRequest.created (created)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (STU3: Creation date (new))</td><td>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).</td></tr></table><hr/><p><b>Group 6 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ProcessRequest|3.0.2</code> to <a href="StructureDefinition-ext-R3-ProcessRequest.provider.html">STU3: Responsible practitioner (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>ProcessRequest.provider (provider)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (STU3: Responsible practitioner (new))</td><td>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).</td></tr></table><hr/><p><b>Group 7 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ProcessRequest|3.0.2</code> to <a href="StructureDefinition-ext-R3-ProcessRequest.organization.html">STU3: Responsible organization (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>ProcessRequest.organization (organization)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (STU3: Responsible organization (new))</td><td>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).</td></tr></table><hr/><p><b>Group 8 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ProcessRequest|3.0.2</code> to <a href="StructureDefinition-ext-R3-ProcessRequest.request.html">STU3: Reference to the Request resource (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>ProcessRequest.request (request)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (STU3: Reference to the Request resource (new))</td><td>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).</td></tr></table><hr/><p><b>Group 9 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ProcessRequest|3.0.2</code> to <a href="StructureDefinition-ext-R3-ProcessRequest.response.html">STU3: Reference to the Response resource (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>ProcessRequest.response (response)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (STU3: Reference to the Response resource (new))</td><td>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).</td></tr></table><hr/><p><b>Group 10 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ProcessRequest|3.0.2</code> to <a href="StructureDefinition-ext-R3-ProcessRequest.nullify.html">STU3: Remove history (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>ProcessRequest.nullify (nullify)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (STU3: Remove history (new))</td><td>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).</td></tr></table><hr/><p><b>Group 11 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ProcessRequest|3.0.2</code> to <a href="StructureDefinition-ext-R3-ProcessRequest.reference.html">STU3: Reference number/string (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>ProcessRequest.reference (reference)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (STU3: Reference number/string (new))</td><td>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).</td></tr></table><hr/><p><b>Group 12 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ProcessRequest|3.0.2</code> to <a href="StructureDefinition-ext-R3-ProcessRequest.item.html">STU3: Items to re-adjudicate (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>ProcessRequest.item (item)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (STU3: Items to re-adjudicate (new))</td><td>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).</td></tr><tr><td>ProcessRequest.item.sequenceLinkId (sequenceLinkId)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension.extension:sequenceLinkId (STU3: Service instance (new))</td><td>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).</td></tr></table><hr/><p><b>Group 13 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ProcessRequest|3.0.2</code> to <a href="StructureDefinition-ext-R3-ProcessRequest.include.html">STU3: Resource type(s) to include (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>ProcessRequest.include (include)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (STU3: Resource type(s) to include (new))</td><td>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).</td></tr></table><hr/><p><b>Group 14 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ProcessRequest|3.0.2</code> to <a href="StructureDefinition-ext-R3-ProcessRequest.exclude.html">STU3: Resource type(s) to exclude (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>ProcessRequest.exclude (exclude)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (STU3: Resource type(s) to exclude (new))</td><td>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).</td></tr></table><hr/><p><b>Group 15 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ProcessRequest|3.0.2</code> to <a href="StructureDefinition-ext-R3-ProcessRequest.period.html">STU3: Selection period (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>ProcessRequest.period (period)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (STU3: Selection period (new))</td><td>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).</td></tr></table></div>
</text>
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
<valueCode value="fhir"/>
</extension>
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
<valueInteger value="0">
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom">
<valueCanonical
value="http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r3.r4"/>
</extension>
</valueInteger>
</extension>
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
<valueCode value="trial-use">
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom">
<valueCanonical
value="http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r3.r4"/>
</extension>
</valueCode>
</extension>
<url
value="http://hl7.org/fhir/uv/xver/ConceptMap/R3-ProcessRequest-element-map-to-R4"/>
<version value="0.1.0"/>
<name value="R3ProcessRequestElementMapToR4"/>
<title
value="Cross-version mapping for FHIR STU3 ProcessRequest to FHIR R4 Task"/>
<status value="active"/>
<experimental value="false"/>
<date value="2026-03-17T16:03:24.1186925-05:00"/>
<contact>
<name value="FHIR Infrastructure"/>
<telecom>
<system value="url"/>
<value value="http://www.hl7.org/Special/committees/fiwg"/>
</telecom>
</contact>
<description
value="This ConceptMap represents cross-version mappings for elements from a FHIR STU3 ProcessRequest to FHIR R4."/>
<jurisdiction>
<coding>
<system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
<code value="001"/>
<display value="World"/>
</coding>
</jurisdiction>
<sourceCanonical value="http://hl7.org/fhir/3.0"/>
<targetUri value="http://hl7.org/fhir/4.0"/>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/ProcessRequest"/>
<sourceVersion value="3.0.2"/>
<target value="http://hl7.org/fhir/StructureDefinition/Task"/>
<targetVersion value="4.0.1"/>
<element>
<code value="ProcessRequest.meta"/>
<display value="meta"/>
<target>
<code value="Task.meta"/>
<display value="Task.meta"/>
<equivalence value="equivalent"/>
<comment
value="Element `ProcessRequest.meta` is mapped to FHIR R4 element `Task.meta` as `Equivalent`."/>
</target>
</element>
<element>
<code value="ProcessRequest.implicitRules"/>
<display value="implicitRules"/>
<target>
<code value="Task.implicitRules"/>
<display value="Task.implicitRules"/>
<equivalence value="equivalent"/>
<comment
value="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."/>
</target>
</element>
<element>
<code value="ProcessRequest.language"/>
<display value="language"/>
<target>
<code value="Task.language"/>
<display value="Task.language"/>
<equivalence value="equivalent"/>
<comment
value="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)."/>
</target>
</element>
<element>
<code value="ProcessRequest.text"/>
<display value="text"/>
<target>
<code value="Task.text"/>
<display value="Task.text"/>
<equivalence value="equivalent"/>
<comment
value="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."/>
</target>
</element>
<element>
<code value="ProcessRequest.contained"/>
<display value="contained"/>
<target>
<code value="Task.contained"/>
<display value="Task.contained"/>
<equivalence value="equivalent"/>
<comment
value="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."/>
</target>
</element>
<element>
<code value="ProcessRequest.identifier"/>
<display value="identifier"/>
<target>
<code value="Task.identifier"/>
<display value="Task.identifier"/>
<equivalence value="equivalent"/>
<comment
value="Element `ProcessRequest.identifier` is mapped to FHIR R4 element `Task.identifier` as `Equivalent`."/>
</target>
</element>
<element>
<code value="ProcessRequest.status"/>
<display value="status"/>
<target>
<code value="Task.status"/>
<display value="Task.status"/>
<equivalence value="relatedto"/>
<comment
value="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."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/ProcessRequest"/>
<sourceVersion value="3.0.2"/>
<target
value="http://hl7.org/fhir/3.0/StructureDefinition/extension-ProcessRequest.status"/>
<targetVersion value="0.1.0"/>
<element>
<code value="ProcessRequest.status"/>
<display value="status"/>
<target>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="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."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/ProcessRequest"/>
<sourceVersion value="3.0.2"/>
<target
value="http://hl7.org/fhir/3.0/StructureDefinition/extension-ProcessRequest.action"/>
<targetVersion value="0.1.0"/>
<element>
<code value="ProcessRequest.action"/>
<display value="action"/>
<target>
<code value="Extension"/>
<equivalence value="equivalent"/>
<comment
value="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)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/ProcessRequest"/>
<sourceVersion value="3.0.2"/>
<target
value="http://hl7.org/fhir/3.0/StructureDefinition/extension-ProcessRequest.target"/>
<targetVersion value="0.1.0"/>
<element>
<code value="ProcessRequest.target"/>
<display value="target"/>
<target>
<code value="Extension"/>
<equivalence value="equivalent"/>
<comment
value="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)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/ProcessRequest"/>
<sourceVersion value="3.0.2"/>
<target
value="http://hl7.org/fhir/3.0/StructureDefinition/extension-ProcessRequest.created"/>
<targetVersion value="0.1.0"/>
<element>
<code value="ProcessRequest.created"/>
<display value="created"/>
<target>
<code value="Extension"/>
<equivalence value="equivalent"/>
<comment
value="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)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/ProcessRequest"/>
<sourceVersion value="3.0.2"/>
<target
value="http://hl7.org/fhir/3.0/StructureDefinition/extension-ProcessRequest.provider"/>
<targetVersion value="0.1.0"/>
<element>
<code value="ProcessRequest.provider"/>
<display value="provider"/>
<target>
<code value="Extension"/>
<equivalence value="equivalent"/>
<comment
value="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)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/ProcessRequest"/>
<sourceVersion value="3.0.2"/>
<target
value="http://hl7.org/fhir/3.0/StructureDefinition/extension-ProcessRequest.organization"/>
<targetVersion value="0.1.0"/>
<element>
<code value="ProcessRequest.organization"/>
<display value="organization"/>
<target>
<code value="Extension"/>
<equivalence value="equivalent"/>
<comment
value="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)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/ProcessRequest"/>
<sourceVersion value="3.0.2"/>
<target
value="http://hl7.org/fhir/3.0/StructureDefinition/extension-ProcessRequest.request"/>
<targetVersion value="0.1.0"/>
<element>
<code value="ProcessRequest.request"/>
<display value="request"/>
<target>
<code value="Extension"/>
<equivalence value="equivalent"/>
<comment
value="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)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/ProcessRequest"/>
<sourceVersion value="3.0.2"/>
<target
value="http://hl7.org/fhir/3.0/StructureDefinition/extension-ProcessRequest.response"/>
<targetVersion value="0.1.0"/>
<element>
<code value="ProcessRequest.response"/>
<display value="response"/>
<target>
<code value="Extension"/>
<equivalence value="equivalent"/>
<comment
value="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)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/ProcessRequest"/>
<sourceVersion value="3.0.2"/>
<target
value="http://hl7.org/fhir/3.0/StructureDefinition/extension-ProcessRequest.nullify"/>
<targetVersion value="0.1.0"/>
<element>
<code value="ProcessRequest.nullify"/>
<display value="nullify"/>
<target>
<code value="Extension"/>
<equivalence value="equivalent"/>
<comment
value="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)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/ProcessRequest"/>
<sourceVersion value="3.0.2"/>
<target
value="http://hl7.org/fhir/3.0/StructureDefinition/extension-ProcessRequest.reference"/>
<targetVersion value="0.1.0"/>
<element>
<code value="ProcessRequest.reference"/>
<display value="reference"/>
<target>
<code value="Extension"/>
<equivalence value="equivalent"/>
<comment
value="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)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/ProcessRequest"/>
<sourceVersion value="3.0.2"/>
<target
value="http://hl7.org/fhir/3.0/StructureDefinition/extension-ProcessRequest.item"/>
<targetVersion value="0.1.0"/>
<element>
<code value="ProcessRequest.item"/>
<display value="item"/>
<target>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="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)."/>
</target>
</element>
<element>
<code value="ProcessRequest.item.sequenceLinkId"/>
<display value="sequenceLinkId"/>
<target>
<code value="Extension.extension:sequenceLinkId"/>
<equivalence value="equivalent"/>
<comment
value="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)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/ProcessRequest"/>
<sourceVersion value="3.0.2"/>
<target
value="http://hl7.org/fhir/3.0/StructureDefinition/extension-ProcessRequest.include"/>
<targetVersion value="0.1.0"/>
<element>
<code value="ProcessRequest.include"/>
<display value="include"/>
<target>
<code value="Extension"/>
<equivalence value="equivalent"/>
<comment
value="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)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/ProcessRequest"/>
<sourceVersion value="3.0.2"/>
<target
value="http://hl7.org/fhir/3.0/StructureDefinition/extension-ProcessRequest.exclude"/>
<targetVersion value="0.1.0"/>
<element>
<code value="ProcessRequest.exclude"/>
<display value="exclude"/>
<target>
<code value="Extension"/>
<equivalence value="equivalent"/>
<comment
value="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)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/ProcessRequest"/>
<sourceVersion value="3.0.2"/>
<target
value="http://hl7.org/fhir/3.0/StructureDefinition/extension-ProcessRequest.period"/>
<targetVersion value="0.1.0"/>
<element>
<code value="ProcessRequest.period"/>
<display value="period"/>
<target>
<code value="Extension"/>
<equivalence value="equivalent"/>
<comment
value="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)."/>
</target>
</element>
</group>
</ConceptMap>
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