Extensions for Using Data Elements from FHIR R5 in FHIR STU3
0.1.0 - STU
Extensions for Using Data Elements from FHIR R5 in FHIR STU3
0.1.0 - STU
Extensions for Using Data Elements from FHIR R5 in FHIR STU3 - 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="R5-Task-element-map-to-R3"/>
<text>
<status value="generated"/>
<div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: ConceptMap R5-Task-element-map-to-R3</b></p><a name="R5-Task-element-map-to-R3"> </a><a name="hcR5-Task-element-map-to-R3"> </a><p>Mapping from http://hl7.org/fhir/5.0 to http://hl7.org/fhir/3.0</p><br/><p><b>Group 1 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Task|5.0.0</code> to <code>http://hl7.org/fhir/StructureDefinition/ProcessRequest|3.0.2</code></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>Task.meta (meta)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>ProcessRequest.meta</td><td>Element `Task.meta` is mapped to FHIR STU3 element `ProcessRequest.meta` as `Equivalent`.
Element `Task.meta` is mapped to FHIR STU3 element `ProcessResponse.meta` as `Equivalent`.
Element `Task.meta` is mapped to FHIR STU3 element `Task.meta` as `Equivalent`.</td></tr><tr><td>Task.implicitRules (implicitRules)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>ProcessRequest.implicitRules</td><td>Element `Task.implicitRules` is mapped to FHIR STU3 element `ProcessRequest.implicitRules` as `Equivalent`.
Element `Task.implicitRules` is mapped to FHIR STU3 element `ProcessResponse.implicitRules` as `Equivalent`.
Element `Task.implicitRules` is mapped to FHIR STU3 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.</td></tr><tr><td>Task.language (language)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>ProcessRequest.language</td><td>Element `Task.language` is mapped to FHIR STU3 element `ProcessRequest.language` as `Equivalent`.
Element `Task.language` is mapped to FHIR STU3 element `ProcessResponse.language` as `Equivalent`.
Element `Task.language` is mapped to FHIR STU3 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>Task.text (text)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>ProcessRequest.text</td><td>Element `Task.text` is mapped to FHIR STU3 element `ProcessRequest.text` as `Equivalent`.
Element `Task.text` is mapped to FHIR STU3 element `ProcessResponse.text` as `Equivalent`.
Element `Task.text` is mapped to FHIR STU3 element `Task.text` as `Equivalent`.
Contained resources do not have a 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 information is added later.</td></tr><tr><td>Task.contained (contained)</td><td><a href="CodeSystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td>ProcessRequest.contained</td><td>Element `Task.contained` is mapped to FHIR STU3 element `ProcessRequest.contained` as `SourceIsBroaderThanTarget`.
Element `Task.contained` is mapped to FHIR STU3 element `ProcessResponse.contained` as `SourceIsBroaderThanTarget`.
Element `Task.contained` is mapped to FHIR STU3 element `Task.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. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.</td></tr><tr><td>Task.identifier (identifier)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>ProcessRequest.identifier</td><td>Element `Task.identifier` is mapped to FHIR STU3 element `ProcessRequest.identifier` as `Equivalent`.
Element `Task.identifier` is mapped to FHIR STU3 element `ProcessResponse.identifier` as `Equivalent`.
Element `Task.identifier` is mapped to FHIR STU3 element `Task.identifier` as `Equivalent`.</td></tr><tr><td>Task.status (status)</td><td><a href="CodeSystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td>ProcessRequest.status</td><td>Element `Task.status` is mapped to FHIR STU3 element `ProcessRequest.status` as `RelatedTo`.
Element `Task.status` is mapped to FHIR STU3 element `ProcessResponse.status` as `RelatedTo`.
Element `Task.status` is mapped to FHIR STU3 element `Task.status` as `Equivalent`.</td></tr></table><hr/><p><b>Group 2 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Task|5.0.0</code> to <code>http://hl7.org/fhir/StructureDefinition/ProcessResponse|3.0.2</code></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>Task.meta (meta)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>ProcessResponse.meta</td><td>Element `Task.meta` is mapped to FHIR STU3 element `ProcessRequest.meta` as `Equivalent`.
Element `Task.meta` is mapped to FHIR STU3 element `ProcessResponse.meta` as `Equivalent`.
Element `Task.meta` is mapped to FHIR STU3 element `Task.meta` as `Equivalent`.</td></tr><tr><td>Task.implicitRules (implicitRules)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>ProcessResponse.implicitRules</td><td>Element `Task.implicitRules` is mapped to FHIR STU3 element `ProcessRequest.implicitRules` as `Equivalent`.
Element `Task.implicitRules` is mapped to FHIR STU3 element `ProcessResponse.implicitRules` as `Equivalent`.
Element `Task.implicitRules` is mapped to FHIR STU3 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.</td></tr><tr><td>Task.language (language)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>ProcessResponse.language</td><td>Element `Task.language` is mapped to FHIR STU3 element `ProcessRequest.language` as `Equivalent`.
Element `Task.language` is mapped to FHIR STU3 element `ProcessResponse.language` as `Equivalent`.
Element `Task.language` is mapped to FHIR STU3 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>Task.text (text)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>ProcessResponse.text</td><td>Element `Task.text` is mapped to FHIR STU3 element `ProcessRequest.text` as `Equivalent`.
Element `Task.text` is mapped to FHIR STU3 element `ProcessResponse.text` as `Equivalent`.
Element `Task.text` is mapped to FHIR STU3 element `Task.text` as `Equivalent`.
Contained resources do not have a 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 information is added later.</td></tr><tr><td>Task.contained (contained)</td><td><a href="CodeSystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td>ProcessResponse.contained</td><td>Element `Task.contained` is mapped to FHIR STU3 element `ProcessRequest.contained` as `SourceIsBroaderThanTarget`.
Element `Task.contained` is mapped to FHIR STU3 element `ProcessResponse.contained` as `SourceIsBroaderThanTarget`.
Element `Task.contained` is mapped to FHIR STU3 element `Task.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. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.</td></tr><tr><td>Task.identifier (identifier)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>ProcessResponse.identifier</td><td>Element `Task.identifier` is mapped to FHIR STU3 element `ProcessRequest.identifier` as `Equivalent`.
Element `Task.identifier` is mapped to FHIR STU3 element `ProcessResponse.identifier` as `Equivalent`.
Element `Task.identifier` is mapped to FHIR STU3 element `Task.identifier` as `Equivalent`.</td></tr><tr><td>Task.status (status)</td><td><a href="CodeSystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td>ProcessResponse.status</td><td>Element `Task.status` is mapped to FHIR STU3 element `ProcessRequest.status` as `RelatedTo`.
Element `Task.status` is mapped to FHIR STU3 element `ProcessResponse.status` as `RelatedTo`.
Element `Task.status` is mapped to FHIR STU3 element `Task.status` as `Equivalent`.</td></tr></table><hr/><p><b>Group 3 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Task|5.0.0</code> to <code>http://hl7.org/fhir/StructureDefinition/Task|3.0.2</code></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>Task.meta (meta)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Task.meta</td><td>Element `Task.meta` is mapped to FHIR STU3 element `ProcessRequest.meta` as `Equivalent`.
Element `Task.meta` is mapped to FHIR STU3 element `ProcessResponse.meta` as `Equivalent`.
Element `Task.meta` is mapped to FHIR STU3 element `Task.meta` as `Equivalent`.</td></tr><tr><td>Task.implicitRules (implicitRules)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Task.implicitRules</td><td>Element `Task.implicitRules` is mapped to FHIR STU3 element `ProcessRequest.implicitRules` as `Equivalent`.
Element `Task.implicitRules` is mapped to FHIR STU3 element `ProcessResponse.implicitRules` as `Equivalent`.
Element `Task.implicitRules` is mapped to FHIR STU3 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.</td></tr><tr><td>Task.language (language)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Task.language</td><td>Element `Task.language` is mapped to FHIR STU3 element `ProcessRequest.language` as `Equivalent`.
Element `Task.language` is mapped to FHIR STU3 element `ProcessResponse.language` as `Equivalent`.
Element `Task.language` is mapped to FHIR STU3 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>Task.text (text)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Task.text</td><td>Element `Task.text` is mapped to FHIR STU3 element `ProcessRequest.text` as `Equivalent`.
Element `Task.text` is mapped to FHIR STU3 element `ProcessResponse.text` as `Equivalent`.
Element `Task.text` is mapped to FHIR STU3 element `Task.text` as `Equivalent`.
Contained resources do not have a 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 information is added later.</td></tr><tr><td>Task.contained (contained)</td><td><a href="CodeSystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td>Task.contained</td><td>Element `Task.contained` is mapped to FHIR STU3 element `ProcessRequest.contained` as `SourceIsBroaderThanTarget`.
Element `Task.contained` is mapped to FHIR STU3 element `ProcessResponse.contained` as `SourceIsBroaderThanTarget`.
Element `Task.contained` is mapped to FHIR STU3 element `Task.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. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.</td></tr><tr><td>Task.identifier (identifier)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Task.identifier</td><td>Element `Task.identifier` is mapped to FHIR STU3 element `ProcessRequest.identifier` as `Equivalent`.
Element `Task.identifier` is mapped to FHIR STU3 element `ProcessResponse.identifier` as `Equivalent`.
Element `Task.identifier` is mapped to FHIR STU3 element `Task.identifier` as `Equivalent`.</td></tr><tr><td>Task.instantiatesCanonical (instantiatesCanonical)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Task.definition[x]</td><td>Element `Task.instantiatesCanonical` is mapped to FHIR STU3 element `Task.definition[x]` as `Equivalent`.
The target context `Task.definition[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Task`.</td></tr><tr><td>Task.instantiatesUri (instantiatesUri)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Task.definition[x]</td><td>Element `Task.instantiatesUri` is mapped to FHIR STU3 element `Task.definition[x]` as `Equivalent`.
The target context `Task.definition[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Task`.</td></tr><tr><td>Task.basedOn (basedOn)</td><td><a href="CodeSystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td>Task.basedOn</td><td>Element `Task.basedOn` is mapped to FHIR STU3 element `Task.basedOn` as `SourceIsBroaderThanTarget`.
The mappings for `Task.basedOn` do not cover the following types based on type expansion: display, identifier, reference, type.
The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Task.basedOn` with unmapped reference targets: Resource.
Task.basedOn is never the same as Task.focus. Task.basedOn will typically not be present for 'please fulfill' Tasks as a distinct authorization is rarely needed to request fulfillment. If the Task is seeking fulfillment of an order, the order to be fulfilled is always communicated using `focus`, never basedOn. However, authorization may be needed to perform other types of Task actions. As an example of when both would be present, a Task seeking suspension of a prescription might have a Task.basedOn pointing to the ServiceRequest ordering surgery (which is the driver for suspending the MedicationRequest - which would be the Task.focus).</td></tr><tr><td>Task.groupIdentifier (groupIdentifier)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Task.groupIdentifier</td><td>Element `Task.groupIdentifier` is mapped to FHIR STU3 element `Task.groupIdentifier` as `Equivalent`.</td></tr><tr><td>Task.partOf (partOf)</td><td><a href="CodeSystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td>Task.partOf</td><td>Element `Task.partOf` is mapped to FHIR STU3 element `Task.partOf` as `SourceIsBroaderThanTarget`.
The mappings for `Task.partOf` do not cover the following types based on type expansion: display, identifier, reference, type.
The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Task.partOf` with unmapped reference targets: Task.
This should usually be 0..1.</td></tr><tr><td>Task.status (status)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Task.status</td><td>Element `Task.status` is mapped to FHIR STU3 element `ProcessRequest.status` as `RelatedTo`.
Element `Task.status` is mapped to FHIR STU3 element `ProcessResponse.status` as `RelatedTo`.
Element `Task.status` is mapped to FHIR STU3 element `Task.status` as `Equivalent`.</td></tr><tr><td>Task.statusReason (statusReason)</td><td><a href="CodeSystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td>Task.statusReason</td><td>Element `Task.statusReason` is mapped to FHIR STU3 element `Task.statusReason` as `SourceIsBroaderThanTarget`.
The mappings for `Task.statusReason` do not cover the following types: CodeableReference.
The mappings for `Task.statusReason` do not cover the following types based on type expansion: reference.
This applies to the current status. Look at the history of the task to see reasons for past statuses.</td></tr><tr><td>Task.businessStatus (businessStatus)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Task.businessStatus</td><td>Element `Task.businessStatus` is mapped to FHIR STU3 element `Task.businessStatus` as `Equivalent`.</td></tr><tr><td>Task.intent (intent)</td><td><a href="CodeSystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td>Task.intent</td><td>Element `Task.intent` is mapped to FHIR STU3 element `Task.intent` as `SourceIsBroaderThanTarget`.
This element is immutable. Proposed tasks, planned tasks, etc. must be distinct instances.
In most cases, Tasks will have an intent of "order".</td></tr><tr><td>Task.priority (priority)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Task.priority</td><td>Element `Task.priority` is mapped to FHIR STU3 element `Task.priority` as `Equivalent`.</td></tr><tr><td>Task.code (code)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Task.code</td><td>Element `Task.code` is mapped to FHIR STU3 element `Task.code` as `Equivalent`.
The title (eg "My Tasks", "Outstanding Tasks for Patient X") should go into the code.</td></tr><tr><td>Task.description (description)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Task.description</td><td>Element `Task.description` is mapped to FHIR STU3 element `Task.description` as `Equivalent`.</td></tr><tr><td>Task.focus (focus)</td><td><a href="CodeSystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td>Task.focus</td><td>Element `Task.focus` is mapped to FHIR STU3 element `Task.focus` as `SourceIsBroaderThanTarget`.
The mappings for `Task.focus` do not cover the following types based on type expansion: display, identifier, reference, type.
The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Task.focus` with unmapped reference targets: Resource.
If multiple resources need to be manipulated, use sub-tasks. (This ensures that status can be tracked independently for each referenced resource.).</td></tr><tr><td>Task.for (for)</td><td><a href="CodeSystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td>Task.for</td><td>Element `Task.for` is mapped to FHIR STU3 element `Task.for` as `SourceIsBroaderThanTarget`.
The mappings for `Task.for` do not cover the following types based on type expansion: display, identifier, reference, type.
The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Task.for` with unmapped reference targets: Resource.</td></tr><tr><td>Task.encounter (encounter)</td><td><a href="CodeSystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td>Task.context</td><td>Element `Task.encounter` is mapped to FHIR STU3 element `Task.context` as `SourceIsBroaderThanTarget`.
The mappings for `Task.encounter` do not cover the following types based on type expansion: display, identifier, reference, type.
The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Task.encounter` with unmapped reference targets: Encounter.</td></tr><tr><td>Task.executionPeriod (executionPeriod)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Task.executionPeriod</td><td>Element `Task.executionPeriod` is mapped to FHIR STU3 element `Task.executionPeriod` as `Equivalent`.</td></tr><tr><td>Task.authoredOn (authoredOn)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Task.authoredOn</td><td>Element `Task.authoredOn` is mapped to FHIR STU3 element `Task.authoredOn` as `Equivalent`.</td></tr><tr><td>Task.lastModified (lastModified)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Task.lastModified</td><td>Element `Task.lastModified` is mapped to FHIR STU3 element `Task.lastModified` as `Equivalent`.</td></tr><tr><td>Task.requester (requester)</td><td><a href="CodeSystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td>Task.requester.agent</td><td>Element `Task.requester` is mapped to FHIR STU3 element `Task.requester.agent` as `SourceIsBroaderThanTarget`.
The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Task.requester` with unmapped reference targets: Device, Organization, Patient, Practitioner, PractitionerRole, RelatedPerson.</td></tr><tr><td>Task.owner (owner)</td><td><a href="CodeSystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td>Task.owner</td><td>Element `Task.owner` is mapped to FHIR STU3 element `Task.owner` as `SourceIsBroaderThanTarget`.
The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Task.owner` with unmapped reference targets: CareTeam, Organization, Patient, Practitioner, PractitionerRole, RelatedPerson.
Tasks may be created with an owner not yet identified.</td></tr><tr><td>Task.reason (reason)</td><td><a href="CodeSystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td>Task.reason</td><td>Element `Task.reason` is mapped to FHIR STU3 element `Task.reason` as `SourceIsBroaderThanTarget`.
The mappings for `Task.reason` do not cover the following types: CodeableReference.
The mappings for `Task.reason` do not cover the following types based on type expansion: reference.
This will typically not be present for Tasks with a code of 'please fulfill' as, for those, the reason for action is conveyed on the Request pointed to by Task.focus. Some types of tasks will not need a 'reason'. E.g. a request to discharge a patient can be inferred to be 'because the patient is ready' and this would not need a reason to be stated on the Task.</td></tr><tr><td>Task.note (note)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Task.note</td><td>Element `Task.note` is mapped to FHIR STU3 element `Task.note` as `Equivalent`.</td></tr><tr><td>Task.relevantHistory (relevantHistory)</td><td><a href="CodeSystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td>Task.relevantHistory</td><td>Element `Task.relevantHistory` is mapped to FHIR STU3 element `Task.relevantHistory` as `SourceIsBroaderThanTarget`.
The mappings for `Task.relevantHistory` do not cover the following types based on type expansion: display, identifier, reference, type.
The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Task.relevantHistory` with unmapped reference targets: Provenance.
This element does not point to the Provenance associated with the *current* version of the resource - as it would be created after this version existed. The Provenance for the current version can be retrieved with a _revinclude.</td></tr><tr><td>Task.restriction (restriction)</td><td><a href="CodeSystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td>Task.restriction</td><td>Element `Task.restriction` is mapped to FHIR STU3 element `Task.restriction` as `Equivalent`.
Task.restriction can only be present if the Task is seeking fulfillment of another Request resource, and the restriction identifies what subset of the authorization conveyed by the request is supposed to be fulfilled by this Task. A possible example could be a standing order (the request) covering a significant time period and/or individuals, while the Task seeks fulfillment for only a subset of that time-period and a single individual.</td></tr><tr><td>Task.restriction.repetitions (repetitions)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Task.restriction.repetitions</td><td>Element `Task.restriction.repetitions` is mapped to FHIR STU3 element `Task.restriction.repetitions` as `Equivalent`.</td></tr><tr><td>Task.restriction.period (period)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Task.restriction.period</td><td>Element `Task.restriction.period` is mapped to FHIR STU3 element `Task.restriction.period` as `Equivalent`.
This is distinct from Task.executionPeriod. ExecutionPeriod indicates when the task needs to be initiated, while Task.restriction.period specifies the subset of the overall authorization that this period covers. For example, a MedicationRequest with an overall effective period of 1 year might have a Task whose restriction.period is 2 months (i.e. satisfy 2 months of medication therapy), while the execution period might be 'between now and 5 days from now' - i.e. If you say yes to this, then you're agreeing to supply medication for that 2 month period within the next 5 days.
Note that period.high is the due date representing the time by which the task should be completed.</td></tr><tr><td>Task.restriction.recipient (recipient)</td><td><a href="CodeSystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td>Task.restriction.recipient</td><td>Element `Task.restriction.recipient` is mapped to FHIR STU3 element `Task.restriction.recipient` as `SourceIsBroaderThanTarget`.
The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Task.restriction.recipient` with unmapped reference targets: Group, Organization, Patient, Practitioner, PractitionerRole, RelatedPerson.</td></tr><tr><td>Task.input (input)</td><td><a href="CodeSystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td>Task.input</td><td>Element `Task.input` is mapped to FHIR STU3 element `Task.input` as `Equivalent`.</td></tr><tr><td>Task.input.type (type)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Task.input.type</td><td>Element `Task.input.type` is mapped to FHIR STU3 element `Task.input.type` as `Equivalent`.
If referencing a BPMN workflow or Protocol, the "system" is the URL for the workflow definition and the code is the "name" of the required input.</td></tr><tr><td>Task.input.value[x] (value[x])</td><td><a href="CodeSystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td>Task.input.value[x]</td><td>Element `Task.input.value[x]` is mapped to FHIR STU3 element `Task.input.value[x]` as `RelatedTo`.
The mappings for `Task.input.value[x]` do not cover the following types: Availability, CodeableReference, ContactDetail, DataRequirement, Dosage, Expression, ExtendedContactDetail, ParameterDefinition, RatioRange, RelatedArtifact, TriggerDefinition, UsageContext, uuid.
The target context `Task.input.value[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Task.input`.</td></tr><tr><td>Task.output (output)</td><td><a href="CodeSystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td>Task.output</td><td>Element `Task.output` is mapped to FHIR STU3 element `Task.output` as `Equivalent`.</td></tr><tr><td>Task.output.type (type)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Task.output.type</td><td>Element `Task.output.type` is mapped to FHIR STU3 element `Task.output.type` as `Equivalent`.</td></tr><tr><td>Task.output.value[x] (value[x])</td><td><a href="CodeSystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td>Task.output.value[x]</td><td>Element `Task.output.value[x]` is mapped to FHIR STU3 element `Task.output.value[x]` as `RelatedTo`.
The mappings for `Task.output.value[x]` do not cover the following types: Availability, CodeableReference, ContactDetail, DataRequirement, Dosage, Expression, ExtendedContactDetail, ParameterDefinition, RatioRange, RelatedArtifact, TriggerDefinition, UsageContext, uuid.
The target context `Task.output.value[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Task.output`.</td></tr></table><hr/><p><b>Group 4 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Task|5.0.0</code> to <a href="StructureDefinition-ext-R5-Task.statusReason.html">R5: statusReason additional typesversion: 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>Task.statusReason (statusReason)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: statusReason additional types)</td><td>Element `Task.statusReason` is mapped to FHIR STU3 element `Task.statusReason` as `SourceIsBroaderThanTarget`.
The mappings for `Task.statusReason` do not cover the following types: CodeableReference.
The mappings for `Task.statusReason` do not cover the following types based on type expansion: reference.
This applies to the current status. Look at the history of the task to see reasons for past statuses.</td></tr></table><hr/><p><b>Group 5 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Task|5.0.0</code> to <a href="StructureDefinition-ext-R5-Task.intent.html">R5: unknown | proposal | plan | order | original-order | reflex-order | filler-order | instance-order | optionversion: 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>Task.intent (intent)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: unknown | proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option)</td><td>Element `Task.intent` is mapped to FHIR STU3 element `Task.intent` as `SourceIsBroaderThanTarget`.
This element is immutable. Proposed tasks, planned tasks, etc. must be distinct instances.
In most cases, Tasks will have an intent of "order".</td></tr></table><hr/><p><b>Group 6 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Task|5.0.0</code> to <a href="StructureDefinition-ext-R5-Task.requestedPeriod.html">R5: When the task should be performed (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>Task.requestedPeriod (requestedPeriod)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: When the task should be performed (new))</td><td>Element `Task.requestedPeriod` has a context of ProcessRequest based on following the parent source element upwards and mapping to `ProcessRequest`.
Element `Task.requestedPeriod` has a context of ProcessResponse based on following the parent source element upwards and mapping to `ProcessResponse`.
Element `Task.requestedPeriod` has a context of Task based on following the parent source element upwards and mapping to `Task`.
Element `Task.requestedPeriod` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
This is typically used when the Task is *not* seeking fulfillment of a focus Request, as in that case the period would be specified on the Request and/or in the Task.restriction.period. Instead, it is used for stand-alone tasks.</td></tr></table><hr/><p><b>Group 7 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Task|5.0.0</code> to <a href="StructureDefinition-ext-R5-Task.requestedPerformer.html">R5: Who should perform Task (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>Task.requestedPerformer (requestedPerformer)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: Who should perform Task (new))</td><td>Element `Task.requestedPerformer` has a context of ProcessRequest based on following the parent source element upwards and mapping to `ProcessRequest`.
Element `Task.requestedPerformer` has a context of ProcessResponse based on following the parent source element upwards and mapping to `ProcessResponse`.
Element `Task.requestedPerformer` has a context of Task based on following the parent source element upwards and mapping to `Task`.
Element `Task.requestedPerformer` has no mapping targets in FHIR STU3. 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/Task|5.0.0</code> to <a href="StructureDefinition-ext-R5-Task.performer.html">R5: Who or what performed the task (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>Task.performer (performer)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: Who or what performed the task (new))</td><td>Element `Task.performer` has a context of ProcessRequest based on following the parent source element upwards and mapping to `ProcessRequest`.
Element `Task.performer` has a context of ProcessResponse based on following the parent source element upwards and mapping to `ProcessResponse`.
Element `Task.performer` has a context of Task based on following the parent source element upwards and mapping to `Task`.
Element `Task.performer` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>Task.performer.function (function)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:function (R5: Type of performance (new))</td><td>Element `Task.performer.function` is part of an existing definition because parent element `Task.performer` requires a cross-version extension.
Element `Task.performer.function` has a context of ProcessRequest based on following the parent source element upwards and mapping to `ProcessRequest`.
Element `Task.performer.function` has a context of ProcessResponse based on following the parent source element upwards and mapping to `ProcessResponse`.
Element `Task.performer.function` has a context of Task based on following the parent source element upwards and mapping to `Task`.
Element `Task.performer.function` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>Task.performer.actor (actor)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:actor (R5: Who performed the task (new))</td><td>Element `Task.performer.actor` is part of an existing definition because parent element `Task.performer` requires a cross-version extension.
Element `Task.performer.actor` has a context of ProcessRequest based on following the parent source element upwards and mapping to `ProcessRequest`.
Element `Task.performer.actor` has a context of ProcessResponse based on following the parent source element upwards and mapping to `ProcessResponse`.
Element `Task.performer.actor` has a context of Task based on following the parent source element upwards and mapping to `Task`.
Element `Task.performer.actor` has no mapping targets in FHIR STU3. 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/Task|5.0.0</code> to <a href="StructureDefinition-ext-R5-Task.location.html">R5: Where task occurs (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>Task.location (location)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: Where task occurs (new))</td><td>Element `Task.location` has a context of ProcessRequest based on following the parent source element upwards and mapping to `ProcessRequest`.
Element `Task.location` has a context of ProcessResponse based on following the parent source element upwards and mapping to `ProcessResponse`.
Element `Task.location` has a context of Task based on following the parent source element upwards and mapping to `Task`.
Element `Task.location` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
This should only be specified when the Task to be/being performed happens or is expected to happen primarily within the bounds of a single Location. Other locations (e.g. source, destination, etc.) would either be reflected on the 'basedOn' Request or be conveyed as distinct Task.input values.</td></tr></table><hr/><p><b>Group 10 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Task|5.0.0</code> to <a href="StructureDefinition-ext-R5-Task.reason.html">R5: reason additional typesversion: 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>Task.reason (reason)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: reason additional types)</td><td>Element `Task.reason` is mapped to FHIR STU3 element `Task.reason` as `SourceIsBroaderThanTarget`.
The mappings for `Task.reason` do not cover the following types: CodeableReference.
The mappings for `Task.reason` do not cover the following types based on type expansion: reference.
This will typically not be present for Tasks with a code of 'please fulfill' as, for those, the reason for action is conveyed on the Request pointed to by Task.focus. Some types of tasks will not need a 'reason'. E.g. a request to discharge a patient can be inferred to be 'because the patient is ready' and this would not need a reason to be stated on the Task.</td></tr></table><hr/><p><b>Group 11 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Task|5.0.0</code> to <a href="StructureDefinition-ext-R5-Task.insurance.html">R5: Associated insurance coverage (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>Task.insurance (insurance)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: Associated insurance coverage (new))</td><td>Element `Task.insurance` has a context of ProcessRequest based on following the parent source element upwards and mapping to `ProcessRequest`.
Element `Task.insurance` has a context of ProcessResponse based on following the parent source element upwards and mapping to `ProcessResponse`.
Element `Task.insurance` has a context of Task based on following the parent source element upwards and mapping to `Task`.
Element `Task.insurance` has no mapping targets in FHIR STU3. 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/Task|5.0.0</code> to <a href="StructureDefinition-ext-R5-Task.inp.value.html">R5: value additional typesversion: 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>Task.input.value[x] (value[x])</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: value additional types)</td><td>Element `Task.input.value[x]` is mapped to FHIR STU3 element `Task.input.value[x]` as `RelatedTo`.
The mappings for `Task.input.value[x]` do not cover the following types: Availability, CodeableReference, ContactDetail, DataRequirement, Dosage, Expression, ExtendedContactDetail, ParameterDefinition, RatioRange, RelatedArtifact, TriggerDefinition, UsageContext, uuid.
The target context `Task.input.value[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Task.input`.</td></tr></table><hr/><p><b>Group 13 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Task|5.0.0</code> to <a href="StructureDefinition-ext-R5-Task.out.value.html">R5: value additional typesversion: 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>Task.output.value[x] (value[x])</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: value additional types)</td><td>Element `Task.output.value[x]` is mapped to FHIR STU3 element `Task.output.value[x]` as `RelatedTo`.
The mappings for `Task.output.value[x]` do not cover the following types: Availability, CodeableReference, ContactDetail, DataRequirement, Dosage, Expression, ExtendedContactDetail, ParameterDefinition, RatioRange, RelatedArtifact, TriggerDefinition, UsageContext, uuid.
The target context `Task.output.value[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Task.output`.</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">
<valueUri
value="http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r3"/>
</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">
<valueUri
value="http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r3"/>
</extension>
</valueCode>
</extension>
<url
value="http://hl7.org/fhir/uv/xver/ConceptMap/R5-Task-element-map-to-R3"/>
<version value="0.1.0"/>
<name value="R5TaskElementMapToR3"/>
<title
value="Cross-version mapping for FHIR R5 Task to FHIR STU3 ProcessRequest"/>
<status value="active"/>
<experimental value="false"/>
<date value="2026-03-17T16:05:22.4222058-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 R5 Task to FHIR STU3."/>
<jurisdiction>
<coding>
<system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
<code value="001"/>
<display value="World"/>
</coding>
</jurisdiction>
<sourceUri value="http://hl7.org/fhir/5.0"/>
<targetUri value="http://hl7.org/fhir/3.0"/>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Task"/>
<sourceVersion value="5.0.0"/>
<target value="http://hl7.org/fhir/StructureDefinition/ProcessRequest"/>
<targetVersion value="3.0.2"/>
<element>
<code value="Task.meta"/>
<display value="meta"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="ProcessRequest.meta"/>
<display value="ProcessRequest.meta"/>
<equivalence value="equivalent"/>
<comment
value="Element `Task.meta` is mapped to FHIR STU3 element `ProcessRequest.meta` as `Equivalent`.
Element `Task.meta` is mapped to FHIR STU3 element `ProcessResponse.meta` as `Equivalent`.
Element `Task.meta` is mapped to FHIR STU3 element `Task.meta` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Task.implicitRules"/>
<display value="implicitRules"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="ProcessRequest.implicitRules"/>
<display value="ProcessRequest.implicitRules"/>
<equivalence value="equivalent"/>
<comment
value="Element `Task.implicitRules` is mapped to FHIR STU3 element `ProcessRequest.implicitRules` as `Equivalent`.
Element `Task.implicitRules` is mapped to FHIR STU3 element `ProcessResponse.implicitRules` as `Equivalent`.
Element `Task.implicitRules` is mapped to FHIR STU3 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc."/>
</target>
</element>
<element>
<code value="Task.language"/>
<display value="language"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="ProcessRequest.language"/>
<display value="ProcessRequest.language"/>
<equivalence value="equivalent"/>
<comment
value="Element `Task.language` is mapped to FHIR STU3 element `ProcessRequest.language` as `Equivalent`.
Element `Task.language` is mapped to FHIR STU3 element `ProcessResponse.language` as `Equivalent`.
Element `Task.language` is mapped to FHIR STU3 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="Task.text"/>
<display value="text"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="ProcessRequest.text"/>
<display value="ProcessRequest.text"/>
<equivalence value="equivalent"/>
<comment
value="Element `Task.text` is mapped to FHIR STU3 element `ProcessRequest.text` as `Equivalent`.
Element `Task.text` is mapped to FHIR STU3 element `ProcessResponse.text` as `Equivalent`.
Element `Task.text` is mapped to FHIR STU3 element `Task.text` as `Equivalent`.
Contained resources do not have a 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 information is added later."/>
</target>
</element>
<element>
<code value="Task.contained"/>
<display value="contained"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="relatedto"/>
</modifierExtension>
<code value="ProcessRequest.contained"/>
<display value="ProcessRequest.contained"/>
<equivalence value="relatedto"/>
<comment
value="Element `Task.contained` is mapped to FHIR STU3 element `ProcessRequest.contained` as `SourceIsBroaderThanTarget`.
Element `Task.contained` is mapped to FHIR STU3 element `ProcessResponse.contained` as `SourceIsBroaderThanTarget`.
Element `Task.contained` is mapped to FHIR STU3 element `Task.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. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels."/>
</target>
</element>
<element>
<code value="Task.identifier"/>
<display value="identifier"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="ProcessRequest.identifier"/>
<display value="ProcessRequest.identifier"/>
<equivalence value="equivalent"/>
<comment
value="Element `Task.identifier` is mapped to FHIR STU3 element `ProcessRequest.identifier` as `Equivalent`.
Element `Task.identifier` is mapped to FHIR STU3 element `ProcessResponse.identifier` as `Equivalent`.
Element `Task.identifier` is mapped to FHIR STU3 element `Task.identifier` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Task.status"/>
<display value="status"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="relatedto"/>
</modifierExtension>
<code value="ProcessRequest.status"/>
<display value="ProcessRequest.status"/>
<equivalence value="relatedto"/>
<comment
value="Element `Task.status` is mapped to FHIR STU3 element `ProcessRequest.status` as `RelatedTo`.
Element `Task.status` is mapped to FHIR STU3 element `ProcessResponse.status` as `RelatedTo`.
Element `Task.status` is mapped to FHIR STU3 element `Task.status` as `Equivalent`."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Task"/>
<sourceVersion value="5.0.0"/>
<target value="http://hl7.org/fhir/StructureDefinition/ProcessResponse"/>
<targetVersion value="3.0.2"/>
<element>
<code value="Task.meta"/>
<display value="meta"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="ProcessResponse.meta"/>
<display value="ProcessResponse.meta"/>
<equivalence value="equivalent"/>
<comment
value="Element `Task.meta` is mapped to FHIR STU3 element `ProcessRequest.meta` as `Equivalent`.
Element `Task.meta` is mapped to FHIR STU3 element `ProcessResponse.meta` as `Equivalent`.
Element `Task.meta` is mapped to FHIR STU3 element `Task.meta` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Task.implicitRules"/>
<display value="implicitRules"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="ProcessResponse.implicitRules"/>
<display value="ProcessResponse.implicitRules"/>
<equivalence value="equivalent"/>
<comment
value="Element `Task.implicitRules` is mapped to FHIR STU3 element `ProcessRequest.implicitRules` as `Equivalent`.
Element `Task.implicitRules` is mapped to FHIR STU3 element `ProcessResponse.implicitRules` as `Equivalent`.
Element `Task.implicitRules` is mapped to FHIR STU3 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc."/>
</target>
</element>
<element>
<code value="Task.language"/>
<display value="language"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="ProcessResponse.language"/>
<display value="ProcessResponse.language"/>
<equivalence value="equivalent"/>
<comment
value="Element `Task.language` is mapped to FHIR STU3 element `ProcessRequest.language` as `Equivalent`.
Element `Task.language` is mapped to FHIR STU3 element `ProcessResponse.language` as `Equivalent`.
Element `Task.language` is mapped to FHIR STU3 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="Task.text"/>
<display value="text"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="ProcessResponse.text"/>
<display value="ProcessResponse.text"/>
<equivalence value="equivalent"/>
<comment
value="Element `Task.text` is mapped to FHIR STU3 element `ProcessRequest.text` as `Equivalent`.
Element `Task.text` is mapped to FHIR STU3 element `ProcessResponse.text` as `Equivalent`.
Element `Task.text` is mapped to FHIR STU3 element `Task.text` as `Equivalent`.
Contained resources do not have a 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 information is added later."/>
</target>
</element>
<element>
<code value="Task.contained"/>
<display value="contained"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="relatedto"/>
</modifierExtension>
<code value="ProcessResponse.contained"/>
<display value="ProcessResponse.contained"/>
<equivalence value="relatedto"/>
<comment
value="Element `Task.contained` is mapped to FHIR STU3 element `ProcessRequest.contained` as `SourceIsBroaderThanTarget`.
Element `Task.contained` is mapped to FHIR STU3 element `ProcessResponse.contained` as `SourceIsBroaderThanTarget`.
Element `Task.contained` is mapped to FHIR STU3 element `Task.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. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels."/>
</target>
</element>
<element>
<code value="Task.identifier"/>
<display value="identifier"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="ProcessResponse.identifier"/>
<display value="ProcessResponse.identifier"/>
<equivalence value="equivalent"/>
<comment
value="Element `Task.identifier` is mapped to FHIR STU3 element `ProcessRequest.identifier` as `Equivalent`.
Element `Task.identifier` is mapped to FHIR STU3 element `ProcessResponse.identifier` as `Equivalent`.
Element `Task.identifier` is mapped to FHIR STU3 element `Task.identifier` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Task.status"/>
<display value="status"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="relatedto"/>
</modifierExtension>
<code value="ProcessResponse.status"/>
<display value="ProcessResponse.status"/>
<equivalence value="relatedto"/>
<comment
value="Element `Task.status` is mapped to FHIR STU3 element `ProcessRequest.status` as `RelatedTo`.
Element `Task.status` is mapped to FHIR STU3 element `ProcessResponse.status` as `RelatedTo`.
Element `Task.status` is mapped to FHIR STU3 element `Task.status` as `Equivalent`."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Task"/>
<sourceVersion value="5.0.0"/>
<target value="http://hl7.org/fhir/StructureDefinition/Task"/>
<targetVersion value="3.0.2"/>
<element>
<code value="Task.meta"/>
<display value="meta"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Task.meta"/>
<display value="Task.meta"/>
<equivalence value="equivalent"/>
<comment
value="Element `Task.meta` is mapped to FHIR STU3 element `ProcessRequest.meta` as `Equivalent`.
Element `Task.meta` is mapped to FHIR STU3 element `ProcessResponse.meta` as `Equivalent`.
Element `Task.meta` is mapped to FHIR STU3 element `Task.meta` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Task.implicitRules"/>
<display value="implicitRules"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Task.implicitRules"/>
<display value="Task.implicitRules"/>
<equivalence value="equivalent"/>
<comment
value="Element `Task.implicitRules` is mapped to FHIR STU3 element `ProcessRequest.implicitRules` as `Equivalent`.
Element `Task.implicitRules` is mapped to FHIR STU3 element `ProcessResponse.implicitRules` as `Equivalent`.
Element `Task.implicitRules` is mapped to FHIR STU3 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc."/>
</target>
</element>
<element>
<code value="Task.language"/>
<display value="language"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Task.language"/>
<display value="Task.language"/>
<equivalence value="equivalent"/>
<comment
value="Element `Task.language` is mapped to FHIR STU3 element `ProcessRequest.language` as `Equivalent`.
Element `Task.language` is mapped to FHIR STU3 element `ProcessResponse.language` as `Equivalent`.
Element `Task.language` is mapped to FHIR STU3 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="Task.text"/>
<display value="text"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Task.text"/>
<display value="Task.text"/>
<equivalence value="equivalent"/>
<comment
value="Element `Task.text` is mapped to FHIR STU3 element `ProcessRequest.text` as `Equivalent`.
Element `Task.text` is mapped to FHIR STU3 element `ProcessResponse.text` as `Equivalent`.
Element `Task.text` is mapped to FHIR STU3 element `Task.text` as `Equivalent`.
Contained resources do not have a 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 information is added later."/>
</target>
</element>
<element>
<code value="Task.contained"/>
<display value="contained"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="relatedto"/>
</modifierExtension>
<code value="Task.contained"/>
<display value="Task.contained"/>
<equivalence value="relatedto"/>
<comment
value="Element `Task.contained` is mapped to FHIR STU3 element `ProcessRequest.contained` as `SourceIsBroaderThanTarget`.
Element `Task.contained` is mapped to FHIR STU3 element `ProcessResponse.contained` as `SourceIsBroaderThanTarget`.
Element `Task.contained` is mapped to FHIR STU3 element `Task.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. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels."/>
</target>
</element>
<element>
<code value="Task.identifier"/>
<display value="identifier"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Task.identifier"/>
<display value="Task.identifier"/>
<equivalence value="equivalent"/>
<comment
value="Element `Task.identifier` is mapped to FHIR STU3 element `ProcessRequest.identifier` as `Equivalent`.
Element `Task.identifier` is mapped to FHIR STU3 element `ProcessResponse.identifier` as `Equivalent`.
Element `Task.identifier` is mapped to FHIR STU3 element `Task.identifier` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Task.instantiatesCanonical"/>
<display value="instantiatesCanonical"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Task.definition[x]"/>
<display value="Task.definition[x]"/>
<equivalence value="equivalent"/>
<comment
value="Element `Task.instantiatesCanonical` is mapped to FHIR STU3 element `Task.definition[x]` as `Equivalent`.
The target context `Task.definition[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Task`."/>
</target>
</element>
<element>
<code value="Task.instantiatesUri"/>
<display value="instantiatesUri"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Task.definition[x]"/>
<display value="Task.definition[x]"/>
<equivalence value="equivalent"/>
<comment
value="Element `Task.instantiatesUri` is mapped to FHIR STU3 element `Task.definition[x]` as `Equivalent`.
The target context `Task.definition[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Task`."/>
</target>
</element>
<element>
<code value="Task.basedOn"/>
<display value="basedOn"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="relatedto"/>
</modifierExtension>
<code value="Task.basedOn"/>
<display value="Task.basedOn"/>
<equivalence value="relatedto"/>
<comment
value="Element `Task.basedOn` is mapped to FHIR STU3 element `Task.basedOn` as `SourceIsBroaderThanTarget`.
The mappings for `Task.basedOn` do not cover the following types based on type expansion: display, identifier, reference, type.
The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Task.basedOn` with unmapped reference targets: Resource.
Task.basedOn is never the same as Task.focus. Task.basedOn will typically not be present for 'please fulfill' Tasks as a distinct authorization is rarely needed to request fulfillment. If the Task is seeking fulfillment of an order, the order to be fulfilled is always communicated using `focus`, never basedOn. However, authorization may be needed to perform other types of Task actions. As an example of when both would be present, a Task seeking suspension of a prescription might have a Task.basedOn pointing to the ServiceRequest ordering surgery (which is the driver for suspending the MedicationRequest - which would be the Task.focus)."/>
</target>
</element>
<element>
<code value="Task.groupIdentifier"/>
<display value="groupIdentifier"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Task.groupIdentifier"/>
<display value="Task.groupIdentifier"/>
<equivalence value="equivalent"/>
<comment
value="Element `Task.groupIdentifier` is mapped to FHIR STU3 element `Task.groupIdentifier` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Task.partOf"/>
<display value="partOf"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="relatedto"/>
</modifierExtension>
<code value="Task.partOf"/>
<display value="Task.partOf"/>
<equivalence value="relatedto"/>
<comment
value="Element `Task.partOf` is mapped to FHIR STU3 element `Task.partOf` as `SourceIsBroaderThanTarget`.
The mappings for `Task.partOf` do not cover the following types based on type expansion: display, identifier, reference, type.
The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Task.partOf` with unmapped reference targets: Task.
This should usually be 0..1."/>
</target>
</element>
<element>
<code value="Task.status"/>
<display value="status"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Task.status"/>
<display value="Task.status"/>
<equivalence value="equivalent"/>
<comment
value="Element `Task.status` is mapped to FHIR STU3 element `ProcessRequest.status` as `RelatedTo`.
Element `Task.status` is mapped to FHIR STU3 element `ProcessResponse.status` as `RelatedTo`.
Element `Task.status` is mapped to FHIR STU3 element `Task.status` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Task.statusReason"/>
<display value="statusReason"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="relatedto"/>
</modifierExtension>
<code value="Task.statusReason"/>
<display value="Task.statusReason"/>
<equivalence value="relatedto"/>
<comment
value="Element `Task.statusReason` is mapped to FHIR STU3 element `Task.statusReason` as `SourceIsBroaderThanTarget`.
The mappings for `Task.statusReason` do not cover the following types: CodeableReference.
The mappings for `Task.statusReason` do not cover the following types based on type expansion: reference.
This applies to the current status. Look at the history of the task to see reasons for past statuses."/>
</target>
</element>
<element>
<code value="Task.businessStatus"/>
<display value="businessStatus"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Task.businessStatus"/>
<display value="Task.businessStatus"/>
<equivalence value="equivalent"/>
<comment
value="Element `Task.businessStatus` is mapped to FHIR STU3 element `Task.businessStatus` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Task.intent"/>
<display value="intent"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="relatedto"/>
</modifierExtension>
<code value="Task.intent"/>
<display value="Task.intent"/>
<equivalence value="relatedto"/>
<comment
value="Element `Task.intent` is mapped to FHIR STU3 element `Task.intent` as `SourceIsBroaderThanTarget`.
This element is immutable. Proposed tasks, planned tasks, etc. must be distinct instances.
In most cases, Tasks will have an intent of "order"."/>
</target>
</element>
<element>
<code value="Task.priority"/>
<display value="priority"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Task.priority"/>
<display value="Task.priority"/>
<equivalence value="equivalent"/>
<comment
value="Element `Task.priority` is mapped to FHIR STU3 element `Task.priority` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Task.code"/>
<display value="code"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Task.code"/>
<display value="Task.code"/>
<equivalence value="equivalent"/>
<comment
value="Element `Task.code` is mapped to FHIR STU3 element `Task.code` as `Equivalent`.
The title (eg "My Tasks", "Outstanding Tasks for Patient X") should go into the code."/>
</target>
</element>
<element>
<code value="Task.description"/>
<display value="description"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Task.description"/>
<display value="Task.description"/>
<equivalence value="equivalent"/>
<comment
value="Element `Task.description` is mapped to FHIR STU3 element `Task.description` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Task.focus"/>
<display value="focus"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="relatedto"/>
</modifierExtension>
<code value="Task.focus"/>
<display value="Task.focus"/>
<equivalence value="relatedto"/>
<comment
value="Element `Task.focus` is mapped to FHIR STU3 element `Task.focus` as `SourceIsBroaderThanTarget`.
The mappings for `Task.focus` do not cover the following types based on type expansion: display, identifier, reference, type.
The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Task.focus` with unmapped reference targets: Resource.
If multiple resources need to be manipulated, use sub-tasks. (This ensures that status can be tracked independently for each referenced resource.)."/>
</target>
</element>
<element>
<code value="Task.for"/>
<display value="for"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="relatedto"/>
</modifierExtension>
<code value="Task.for"/>
<display value="Task.for"/>
<equivalence value="relatedto"/>
<comment
value="Element `Task.for` is mapped to FHIR STU3 element `Task.for` as `SourceIsBroaderThanTarget`.
The mappings for `Task.for` do not cover the following types based on type expansion: display, identifier, reference, type.
The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Task.for` with unmapped reference targets: Resource."/>
</target>
</element>
<element>
<code value="Task.encounter"/>
<display value="encounter"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="relatedto"/>
</modifierExtension>
<code value="Task.context"/>
<display value="Task.context"/>
<equivalence value="relatedto"/>
<comment
value="Element `Task.encounter` is mapped to FHIR STU3 element `Task.context` as `SourceIsBroaderThanTarget`.
The mappings for `Task.encounter` do not cover the following types based on type expansion: display, identifier, reference, type.
The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Task.encounter` with unmapped reference targets: Encounter."/>
</target>
</element>
<element>
<code value="Task.executionPeriod"/>
<display value="executionPeriod"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Task.executionPeriod"/>
<display value="Task.executionPeriod"/>
<equivalence value="equivalent"/>
<comment
value="Element `Task.executionPeriod` is mapped to FHIR STU3 element `Task.executionPeriod` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Task.authoredOn"/>
<display value="authoredOn"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Task.authoredOn"/>
<display value="Task.authoredOn"/>
<equivalence value="equivalent"/>
<comment
value="Element `Task.authoredOn` is mapped to FHIR STU3 element `Task.authoredOn` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Task.lastModified"/>
<display value="lastModified"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Task.lastModified"/>
<display value="Task.lastModified"/>
<equivalence value="equivalent"/>
<comment
value="Element `Task.lastModified` is mapped to FHIR STU3 element `Task.lastModified` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Task.requester"/>
<display value="requester"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="relatedto"/>
</modifierExtension>
<code value="Task.requester.agent"/>
<display value="Task.requester.agent"/>
<equivalence value="relatedto"/>
<comment
value="Element `Task.requester` is mapped to FHIR STU3 element `Task.requester.agent` as `SourceIsBroaderThanTarget`.
The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Task.requester` with unmapped reference targets: Device, Organization, Patient, Practitioner, PractitionerRole, RelatedPerson."/>
</target>
</element>
<element>
<code value="Task.owner"/>
<display value="owner"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="relatedto"/>
</modifierExtension>
<code value="Task.owner"/>
<display value="Task.owner"/>
<equivalence value="relatedto"/>
<comment
value="Element `Task.owner` is mapped to FHIR STU3 element `Task.owner` as `SourceIsBroaderThanTarget`.
The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Task.owner` with unmapped reference targets: CareTeam, Organization, Patient, Practitioner, PractitionerRole, RelatedPerson.
Tasks may be created with an owner not yet identified."/>
</target>
</element>
<element>
<code value="Task.reason"/>
<display value="reason"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="relatedto"/>
</modifierExtension>
<code value="Task.reason"/>
<display value="Task.reason"/>
<equivalence value="relatedto"/>
<comment
value="Element `Task.reason` is mapped to FHIR STU3 element `Task.reason` as `SourceIsBroaderThanTarget`.
The mappings for `Task.reason` do not cover the following types: CodeableReference.
The mappings for `Task.reason` do not cover the following types based on type expansion: reference.
This will typically not be present for Tasks with a code of 'please fulfill' as, for those, the reason for action is conveyed on the Request pointed to by Task.focus. Some types of tasks will not need a 'reason'. E.g. a request to discharge a patient can be inferred to be 'because the patient is ready' and this would not need a reason to be stated on the Task."/>
</target>
</element>
<element>
<code value="Task.note"/>
<display value="note"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Task.note"/>
<display value="Task.note"/>
<equivalence value="equivalent"/>
<comment
value="Element `Task.note` is mapped to FHIR STU3 element `Task.note` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Task.relevantHistory"/>
<display value="relevantHistory"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="relatedto"/>
</modifierExtension>
<code value="Task.relevantHistory"/>
<display value="Task.relevantHistory"/>
<equivalence value="relatedto"/>
<comment
value="Element `Task.relevantHistory` is mapped to FHIR STU3 element `Task.relevantHistory` as `SourceIsBroaderThanTarget`.
The mappings for `Task.relevantHistory` do not cover the following types based on type expansion: display, identifier, reference, type.
The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Task.relevantHistory` with unmapped reference targets: Provenance.
This element does not point to the Provenance associated with the *current* version of the resource - as it would be created after this version existed. The Provenance for the current version can be retrieved with a _revinclude."/>
</target>
</element>
<element>
<code value="Task.restriction"/>
<display value="restriction"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="relatedto"/>
</modifierExtension>
<code value="Task.restriction"/>
<display value="Task.restriction"/>
<equivalence value="relatedto"/>
<comment
value="Element `Task.restriction` is mapped to FHIR STU3 element `Task.restriction` as `Equivalent`.
Task.restriction can only be present if the Task is seeking fulfillment of another Request resource, and the restriction identifies what subset of the authorization conveyed by the request is supposed to be fulfilled by this Task. A possible example could be a standing order (the request) covering a significant time period and/or individuals, while the Task seeks fulfillment for only a subset of that time-period and a single individual."/>
</target>
</element>
<element>
<code value="Task.restriction.repetitions"/>
<display value="repetitions"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Task.restriction.repetitions"/>
<display value="Task.restriction.repetitions"/>
<equivalence value="equivalent"/>
<comment
value="Element `Task.restriction.repetitions` is mapped to FHIR STU3 element `Task.restriction.repetitions` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Task.restriction.period"/>
<display value="period"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Task.restriction.period"/>
<display value="Task.restriction.period"/>
<equivalence value="equivalent"/>
<comment
value="Element `Task.restriction.period` is mapped to FHIR STU3 element `Task.restriction.period` as `Equivalent`.
This is distinct from Task.executionPeriod. ExecutionPeriod indicates when the task needs to be initiated, while Task.restriction.period specifies the subset of the overall authorization that this period covers. For example, a MedicationRequest with an overall effective period of 1 year might have a Task whose restriction.period is 2 months (i.e. satisfy 2 months of medication therapy), while the execution period might be 'between now and 5 days from now' - i.e. If you say yes to this, then you're agreeing to supply medication for that 2 month period within the next 5 days.
Note that period.high is the due date representing the time by which the task should be completed."/>
</target>
</element>
<element>
<code value="Task.restriction.recipient"/>
<display value="recipient"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="relatedto"/>
</modifierExtension>
<code value="Task.restriction.recipient"/>
<display value="Task.restriction.recipient"/>
<equivalence value="relatedto"/>
<comment
value="Element `Task.restriction.recipient` is mapped to FHIR STU3 element `Task.restriction.recipient` as `SourceIsBroaderThanTarget`.
The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Task.restriction.recipient` with unmapped reference targets: Group, Organization, Patient, Practitioner, PractitionerRole, RelatedPerson."/>
</target>
</element>
<element>
<code value="Task.input"/>
<display value="input"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="relatedto"/>
</modifierExtension>
<code value="Task.input"/>
<display value="Task.input"/>
<equivalence value="relatedto"/>
<comment
value="Element `Task.input` is mapped to FHIR STU3 element `Task.input` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Task.input.type"/>
<display value="type"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Task.input.type"/>
<display value="Task.input.type"/>
<equivalence value="equivalent"/>
<comment
value="Element `Task.input.type` is mapped to FHIR STU3 element `Task.input.type` as `Equivalent`.
If referencing a BPMN workflow or Protocol, the "system" is the URL for the workflow definition and the code is the "name" of the required input."/>
</target>
</element>
<element>
<code value="Task.input.value[x]"/>
<display value="value[x]"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="relatedto"/>
</modifierExtension>
<code value="Task.input.value[x]"/>
<display value="Task.input.value[x]"/>
<equivalence value="relatedto"/>
<comment
value="Element `Task.input.value[x]` is mapped to FHIR STU3 element `Task.input.value[x]` as `RelatedTo`.
The mappings for `Task.input.value[x]` do not cover the following types: Availability, CodeableReference, ContactDetail, DataRequirement, Dosage, Expression, ExtendedContactDetail, ParameterDefinition, RatioRange, RelatedArtifact, TriggerDefinition, UsageContext, uuid.
The target context `Task.input.value[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Task.input`."/>
</target>
</element>
<element>
<code value="Task.output"/>
<display value="output"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="relatedto"/>
</modifierExtension>
<code value="Task.output"/>
<display value="Task.output"/>
<equivalence value="relatedto"/>
<comment
value="Element `Task.output` is mapped to FHIR STU3 element `Task.output` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Task.output.type"/>
<display value="type"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Task.output.type"/>
<display value="Task.output.type"/>
<equivalence value="equivalent"/>
<comment
value="Element `Task.output.type` is mapped to FHIR STU3 element `Task.output.type` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Task.output.value[x]"/>
<display value="value[x]"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="relatedto"/>
</modifierExtension>
<code value="Task.output.value[x]"/>
<display value="Task.output.value[x]"/>
<equivalence value="relatedto"/>
<comment
value="Element `Task.output.value[x]` is mapped to FHIR STU3 element `Task.output.value[x]` as `RelatedTo`.
The mappings for `Task.output.value[x]` do not cover the following types: Availability, CodeableReference, ContactDetail, DataRequirement, Dosage, Expression, ExtendedContactDetail, ParameterDefinition, RatioRange, RelatedArtifact, TriggerDefinition, UsageContext, uuid.
The target context `Task.output.value[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Task.output`."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Task"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Task.statusReason"/>
<targetVersion value="0.1.0"/>
<element>
<code value="Task.statusReason"/>
<display value="statusReason"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `Task.statusReason` is mapped to FHIR STU3 element `Task.statusReason` as `SourceIsBroaderThanTarget`.
The mappings for `Task.statusReason` do not cover the following types: CodeableReference.
The mappings for `Task.statusReason` do not cover the following types based on type expansion: reference.
This applies to the current status. Look at the history of the task to see reasons for past statuses."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Task"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Task.intent"/>
<targetVersion value="0.1.0"/>
<element>
<code value="Task.intent"/>
<display value="intent"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `Task.intent` is mapped to FHIR STU3 element `Task.intent` as `SourceIsBroaderThanTarget`.
This element is immutable. Proposed tasks, planned tasks, etc. must be distinct instances.
In most cases, Tasks will have an intent of "order"."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Task"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Task.requestedPeriod"/>
<targetVersion value="0.1.0"/>
<element>
<code value="Task.requestedPeriod"/>
<display value="requestedPeriod"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `Task.requestedPeriod` has a context of ProcessRequest based on following the parent source element upwards and mapping to `ProcessRequest`.
Element `Task.requestedPeriod` has a context of ProcessResponse based on following the parent source element upwards and mapping to `ProcessResponse`.
Element `Task.requestedPeriod` has a context of Task based on following the parent source element upwards and mapping to `Task`.
Element `Task.requestedPeriod` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
This is typically used when the Task is *not* seeking fulfillment of a focus Request, as in that case the period would be specified on the Request and/or in the Task.restriction.period. Instead, it is used for stand-alone tasks."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Task"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Task.requestedPerformer"/>
<targetVersion value="0.1.0"/>
<element>
<code value="Task.requestedPerformer"/>
<display value="requestedPerformer"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `Task.requestedPerformer` has a context of ProcessRequest based on following the parent source element upwards and mapping to `ProcessRequest`.
Element `Task.requestedPerformer` has a context of ProcessResponse based on following the parent source element upwards and mapping to `ProcessResponse`.
Element `Task.requestedPerformer` has a context of Task based on following the parent source element upwards and mapping to `Task`.
Element `Task.requestedPerformer` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Task"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Task.performer"/>
<targetVersion value="0.1.0"/>
<element>
<code value="Task.performer"/>
<display value="performer"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `Task.performer` has a context of ProcessRequest based on following the parent source element upwards and mapping to `ProcessRequest`.
Element `Task.performer` has a context of ProcessResponse based on following the parent source element upwards and mapping to `ProcessResponse`.
Element `Task.performer` has a context of Task based on following the parent source element upwards and mapping to `Task`.
Element `Task.performer` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="Task.performer.function"/>
<display value="function"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension.extension:function"/>
<equivalence value="wider"/>
<comment
value="Element `Task.performer.function` is part of an existing definition because parent element `Task.performer` requires a cross-version extension.
Element `Task.performer.function` has a context of ProcessRequest based on following the parent source element upwards and mapping to `ProcessRequest`.
Element `Task.performer.function` has a context of ProcessResponse based on following the parent source element upwards and mapping to `ProcessResponse`.
Element `Task.performer.function` has a context of Task based on following the parent source element upwards and mapping to `Task`.
Element `Task.performer.function` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="Task.performer.actor"/>
<display value="actor"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension.extension:actor"/>
<equivalence value="wider"/>
<comment
value="Element `Task.performer.actor` is part of an existing definition because parent element `Task.performer` requires a cross-version extension.
Element `Task.performer.actor` has a context of ProcessRequest based on following the parent source element upwards and mapping to `ProcessRequest`.
Element `Task.performer.actor` has a context of ProcessResponse based on following the parent source element upwards and mapping to `ProcessResponse`.
Element `Task.performer.actor` has a context of Task based on following the parent source element upwards and mapping to `Task`.
Element `Task.performer.actor` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Task"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Task.location"/>
<targetVersion value="0.1.0"/>
<element>
<code value="Task.location"/>
<display value="location"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `Task.location` has a context of ProcessRequest based on following the parent source element upwards and mapping to `ProcessRequest`.
Element `Task.location` has a context of ProcessResponse based on following the parent source element upwards and mapping to `ProcessResponse`.
Element `Task.location` has a context of Task based on following the parent source element upwards and mapping to `Task`.
Element `Task.location` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
This should only be specified when the Task to be/being performed happens or is expected to happen primarily within the bounds of a single Location. Other locations (e.g. source, destination, etc.) would either be reflected on the 'basedOn' Request or be conveyed as distinct Task.input values."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Task"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Task.reason"/>
<targetVersion value="0.1.0"/>
<element>
<code value="Task.reason"/>
<display value="reason"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `Task.reason` is mapped to FHIR STU3 element `Task.reason` as `SourceIsBroaderThanTarget`.
The mappings for `Task.reason` do not cover the following types: CodeableReference.
The mappings for `Task.reason` do not cover the following types based on type expansion: reference.
This will typically not be present for Tasks with a code of 'please fulfill' as, for those, the reason for action is conveyed on the Request pointed to by Task.focus. Some types of tasks will not need a 'reason'. E.g. a request to discharge a patient can be inferred to be 'because the patient is ready' and this would not need a reason to be stated on the Task."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Task"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Task.insurance"/>
<targetVersion value="0.1.0"/>
<element>
<code value="Task.insurance"/>
<display value="insurance"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `Task.insurance` has a context of ProcessRequest based on following the parent source element upwards and mapping to `ProcessRequest`.
Element `Task.insurance` has a context of ProcessResponse based on following the parent source element upwards and mapping to `ProcessResponse`.
Element `Task.insurance` has a context of Task based on following the parent source element upwards and mapping to `Task`.
Element `Task.insurance` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Task"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Task.input.value"/>
<targetVersion value="0.1.0"/>
<element>
<code value="Task.input.value[x]"/>
<display value="value[x]"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `Task.input.value[x]` is mapped to FHIR STU3 element `Task.input.value[x]` as `RelatedTo`.
The mappings for `Task.input.value[x]` do not cover the following types: Availability, CodeableReference, ContactDetail, DataRequirement, Dosage, Expression, ExtendedContactDetail, ParameterDefinition, RatioRange, RelatedArtifact, TriggerDefinition, UsageContext, uuid.
The target context `Task.input.value[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Task.input`."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Task"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Task.output.value"/>
<targetVersion value="0.1.0"/>
<element>
<code value="Task.output.value[x]"/>
<display value="value[x]"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `Task.output.value[x]` is mapped to FHIR STU3 element `Task.output.value[x]` as `RelatedTo`.
The mappings for `Task.output.value[x]` do not cover the following types: Availability, CodeableReference, ContactDetail, DataRequirement, Dosage, Expression, ExtendedContactDetail, ParameterDefinition, RatioRange, RelatedArtifact, TriggerDefinition, UsageContext, uuid.
The target context `Task.output.value[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Task.output`."/>
</target>
</element>
</group>
</ConceptMap>
IG © 2025+ FHIR Infrastructure. Package hl7.fhir.uv.xver-r5.r3#0.1.0 based on FHIR 3.0.2. Generated 2026-03-20
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change