FHIR IG analytics| Package | hl7.fhir.uv.xver-r5.r3 |
| Resource Type | ConceptMap |
| Id | ConceptMap-R5-Task-element-map-to-R3.json |
| FHIR Version | R3 |
| Source | http://hl7.org/fhir/uv/xver-r5.r3/0.1.0/ConceptMap-R5-Task-element-map-to-R3.html |
| URL | http://hl7.org/fhir/uv/xver/ConceptMap/R5-Task-element-map-to-R3 |
| Version | 0.1.0 |
| Status | active |
| Date | 2026-03-17T16:05:22.4222058-05:00 |
| Name | R5TaskElementMapToR3 |
| Title | Cross-version mapping for FHIR R5 Task to FHIR STU3 ProcessRequest |
| Realm | uv |
| Authority | hl7 |
| Description | This ConceptMap represents cross-version mappings for elements from a FHIR R5 Task to FHIR STU3. |
No resources found
| StructureDefinition | ||
| hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2 | extension-Task.input.value | Cross-version Extension for R5.Task.input.value[x] for use in FHIR R4 |
| hl7.fhir.uv.xver-r5.r3#0.1.0 | extension-Task.insurance | R5: Associated insurance coverage (new) |
| hl7.fhir.uv.xver-r5.r3#0.1.0 | extension-Task.intent | R5: unknown | proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option |
| hl7.fhir.uv.xver-r5.r3#0.1.0 | extension-Task.location | R5: Where task occurs (new) |
| hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2 | extension-Task.output.value | Cross-version Extension for R5.Task.output.value[x] for use in FHIR R4 |
| hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2 | extension-Task.performer | Cross-version Extension for R5.Task.performer for use in FHIR R4 |
| hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2 | extension-Task.reason | Cross-version Extension for R5.Task.reason for use in FHIR R4 |
| de.gematik.dipag#1.0.4 | extension-Task.requestedPerformer | Digitale Patientenrechnung Task RequestedPerformer |
| hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2 | extension-Task.requestedPeriod | Cross-version Extension for R5.Task.requestedPeriod for use in FHIR R4 |
| hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2 | extension-Task.statusReason | Cross-version Extension for R5.Task.statusReason for use in FHIR R4 |
Note: links and images are rebased to the (stated) source
Generated Narrative: ConceptMap R5-Task-element-map-to-R3
Mapping from http://hl7.org/fhir/5.0 to http://hl7.org/fhir/3.0
Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/Task|5.0.0 to http://hl7.org/fhir/StructureDefinition/ProcessRequest|3.0.2
| Source Code | Relationship | Target Code | Comment |
| Task.meta (meta) | is equivalent to | ProcessRequest.meta | 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`. |
| Task.implicitRules (implicitRules) | is equivalent to | ProcessRequest.implicitRules | 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. |
| Task.language (language) | is equivalent to | ProcessRequest.language | 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). |
| Task.text (text) | is equivalent to | ProcessRequest.text | 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. |
| Task.contained (contained) | is related to | ProcessRequest.contained | 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. |
| Task.identifier (identifier) | is equivalent to | ProcessRequest.identifier | 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`. |
| Task.status (status) | is related to | ProcessRequest.status | 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`. |
Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/Task|5.0.0 to http://hl7.org/fhir/StructureDefinition/ProcessResponse|3.0.2
| Source Code | Relationship | Target Code | Comment |
| Task.meta (meta) | is equivalent to | ProcessResponse.meta | 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`. |
| Task.implicitRules (implicitRules) | is equivalent to | ProcessResponse.implicitRules | 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. |
| Task.language (language) | is equivalent to | ProcessResponse.language | 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). |
| Task.text (text) | is equivalent to | ProcessResponse.text | 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. |
| Task.contained (contained) | is related to | ProcessResponse.contained | 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. |
| Task.identifier (identifier) | is equivalent to | ProcessResponse.identifier | 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`. |
| Task.status (status) | is related to | ProcessResponse.status | 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`. |
Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/Task|5.0.0 to http://hl7.org/fhir/StructureDefinition/Task|3.0.2
| Source Code | Relationship | Target Code | Comment |
| Task.meta (meta) | is equivalent to | Task.meta | 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`. |
| Task.implicitRules (implicitRules) | is equivalent to | Task.implicitRules | 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. |
| Task.language (language) | is equivalent to | Task.language | 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). |
| Task.text (text) | is equivalent to | Task.text | 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. |
| Task.contained (contained) | is related to | Task.contained | 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. |
| Task.identifier (identifier) | is equivalent to | Task.identifier | 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`. |
| Task.instantiatesCanonical (instantiatesCanonical) | is equivalent to | Task.definition[x] | 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`. |
| Task.instantiatesUri (instantiatesUri) | is equivalent to | Task.definition[x] | 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`. |
| Task.basedOn (basedOn) | is related to | Task.basedOn | 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). |
| Task.groupIdentifier (groupIdentifier) | is equivalent to | Task.groupIdentifier | Element `Task.groupIdentifier` is mapped to FHIR STU3 element `Task.groupIdentifier` as `Equivalent`. |
| Task.partOf (partOf) | is related to | Task.partOf | 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. |
| Task.status (status) | is equivalent to | Task.status | 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`. |
| Task.statusReason (statusReason) | is related to | Task.statusReason | 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. |
| Task.businessStatus (businessStatus) | is equivalent to | Task.businessStatus | Element `Task.businessStatus` is mapped to FHIR STU3 element `Task.businessStatus` as `Equivalent`. |
| Task.intent (intent) | is related to | Task.intent | 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". |
| Task.priority (priority) | is equivalent to | Task.priority | Element `Task.priority` is mapped to FHIR STU3 element `Task.priority` as `Equivalent`. |
| Task.code (code) | is equivalent to | Task.code | 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. |
| Task.description (description) | is equivalent to | Task.description | Element `Task.description` is mapped to FHIR STU3 element `Task.description` as `Equivalent`. |
| Task.focus (focus) | is related to | Task.focus | 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.). |
| Task.for (for) | is related to | Task.for | 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. |
| Task.encounter (encounter) | is related to | Task.context | 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. |
| Task.executionPeriod (executionPeriod) | is equivalent to | Task.executionPeriod | Element `Task.executionPeriod` is mapped to FHIR STU3 element `Task.executionPeriod` as `Equivalent`. |
| Task.authoredOn (authoredOn) | is equivalent to | Task.authoredOn | Element `Task.authoredOn` is mapped to FHIR STU3 element `Task.authoredOn` as `Equivalent`. |
| Task.lastModified (lastModified) | is equivalent to | Task.lastModified | Element `Task.lastModified` is mapped to FHIR STU3 element `Task.lastModified` as `Equivalent`. |
| Task.requester (requester) | is related to | Task.requester.agent | 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. |
| Task.owner (owner) | is related to | Task.owner | 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. |
| Task.reason (reason) | is related to | Task.reason | 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. |
| Task.note (note) | is equivalent to | Task.note | Element `Task.note` is mapped to FHIR STU3 element `Task.note` as `Equivalent`. |
| Task.relevantHistory (relevantHistory) | is related to | Task.relevantHistory | 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. |
| Task.restriction (restriction) | is related to | Task.restriction | 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. |
| Task.restriction.repetitions (repetitions) | is equivalent to | Task.restriction.repetitions | Element `Task.restriction.repetitions` is mapped to FHIR STU3 element `Task.restriction.repetitions` as `Equivalent`. |
| Task.restriction.period (period) | is equivalent to | Task.restriction.period | 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. |
| Task.restriction.recipient (recipient) | is related to | Task.restriction.recipient | 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. |
| Task.input (input) | is related to | Task.input | Element `Task.input` is mapped to FHIR STU3 element `Task.input` as `Equivalent`. |
| Task.input.type (type) | is equivalent to | Task.input.type | 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. |
| Task.input.value[x] (value[x]) | is related to | Task.input.value[x] | 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`. |
| Task.output (output) | is related to | Task.output | Element `Task.output` is mapped to FHIR STU3 element `Task.output` as `Equivalent`. |
| Task.output.type (type) | is equivalent to | Task.output.type | Element `Task.output.type` is mapped to FHIR STU3 element `Task.output.type` as `Equivalent`. |
| Task.output.value[x] (value[x]) | is related to | Task.output.value[x] | 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`. |
Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/Task|5.0.0 to R5: statusReason additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| Task.statusReason (statusReason) | maps to wider concept | Extension (R5: statusReason additional types) | 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. |
Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/Task|5.0.0 to R5: unknown | proposal | plan | order | original-order | reflex-order | filler-order | instance-order | optionversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| Task.intent (intent) | maps to wider concept | Extension (R5: unknown | proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option) | 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". |
Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/Task|5.0.0 to R5: When the task should be performed (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| Task.requestedPeriod (requestedPeriod) | maps to wider concept | Extension (R5: When the task should be performed (new)) | 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. |
Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/Task|5.0.0 to R5: Who should perform Task (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| Task.requestedPerformer (requestedPerformer) | maps to wider concept | Extension (R5: Who should perform Task (new)) | 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). |
Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/Task|5.0.0 to R5: Who or what performed the task (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| Task.performer (performer) | maps to wider concept | Extension (R5: Who or what performed the task (new)) | 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). |
| Task.performer.function (function) | maps to wider concept | Extension.extension:function (R5: Type of performance (new)) | 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). |
| Task.performer.actor (actor) | maps to wider concept | Extension.extension:actor (R5: Who performed the task (new)) | 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). |
Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/Task|5.0.0 to R5: Where task occurs (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| Task.location (location) | maps to wider concept | Extension (R5: Where task occurs (new)) | 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. |
Group 10 Mapping from http://hl7.org/fhir/StructureDefinition/Task|5.0.0 to R5: reason additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| Task.reason (reason) | maps to wider concept | Extension (R5: reason additional types) | 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. |
Group 11 Mapping from http://hl7.org/fhir/StructureDefinition/Task|5.0.0 to R5: Associated insurance coverage (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| Task.insurance (insurance) | maps to wider concept | Extension (R5: Associated insurance coverage (new)) | 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). |
Group 12 Mapping from http://hl7.org/fhir/StructureDefinition/Task|5.0.0 to R5: value additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| Task.input.value[x] (value[x]) | maps to wider concept | Extension (R5: value additional types) | 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`. |
Group 13 Mapping from http://hl7.org/fhir/StructureDefinition/Task|5.0.0 to R5: value additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| Task.output.value[x] (value[x]) | maps to wider concept | Extension (R5: value additional types) | 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`. |
{
"resourceType": "ConceptMap",
"id": "R5-Task-element-map-to-R3",
"text": {
"status": "generated",
"div": "<!-- snip (see above) -->"
},
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
"valueCode": "fhir"
},
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
"valueInteger": 0,
"_valueInteger": {
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
"valueUri": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r3"
}
]
}
},
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
"valueCode": "trial-use",
"_valueCode": {
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
"valueUri": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r3"
}
]
}
}
],
"url": "http://hl7.org/fhir/uv/xver/ConceptMap/R5-Task-element-map-to-R3",
"version": "0.1.0",
"name": "R5TaskElementMapToR3",
"title": "Cross-version mapping for FHIR R5 Task to FHIR STU3 ProcessRequest",
"status": "active",
"experimental": false,
"date": "2026-03-17T16:05:22.4222058-05:00",
"contact": [
{
"name": "FHIR Infrastructure",
"telecom": [
{
"system": "url",
"value": "http://www.hl7.org/Special/committees/fiwg"
}
]
}
],
"description": "This ConceptMap represents cross-version mappings for elements from a FHIR R5 Task to FHIR STU3.",
"jurisdiction": [
{
"coding": [
{
"system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code": "001",
"display": "World"
}
]
}
],
"sourceUri": "http://hl7.org/fhir/5.0",
"targetUri": "http://hl7.org/fhir/3.0",
"group": [
{
"source": "http://hl7.org/fhir/StructureDefinition/Task",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/StructureDefinition/ProcessRequest",
"targetVersion": "3.0.2",
"element": [
{
"code": "Task.meta",
"display": "meta",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "ProcessRequest.meta",
"display": "ProcessRequest.meta",
"equivalence": "equivalent",
"comment": "Element `Task.meta` is mapped to FHIR STU3 element `ProcessRequest.meta` as `Equivalent`.\nElement `Task.meta` is mapped to FHIR STU3 element `ProcessResponse.meta` as `Equivalent`.\nElement `Task.meta` is mapped to FHIR STU3 element `Task.meta` as `Equivalent`."
}
]
},
{
"code": "Task.implicitRules",
"display": "implicitRules",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "ProcessRequest.implicitRules",
"display": "ProcessRequest.implicitRules",
"equivalence": "equivalent",
"comment": "Element `Task.implicitRules` is mapped to FHIR STU3 element `ProcessRequest.implicitRules` as `Equivalent`.\nElement `Task.implicitRules` is mapped to FHIR STU3 element `ProcessResponse.implicitRules` as `Equivalent`.\nElement `Task.implicitRules` is mapped to FHIR STU3 element `Task.implicitRules` as `Equivalent`.\nAsserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. 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."
}
]
},
{
"code": "Task.language",
"display": "language",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "ProcessRequest.language",
"display": "ProcessRequest.language",
"equivalence": "equivalent",
"comment": "Element `Task.language` is mapped to FHIR STU3 element `ProcessRequest.language` as `Equivalent`.\nElement `Task.language` is mapped to FHIR STU3 element `ProcessResponse.language` as `Equivalent`.\nElement `Task.language` is mapped to FHIR STU3 element `Task.language` as `Equivalent`.\nLanguage is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute)."
}
]
},
{
"code": "Task.text",
"display": "text",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "ProcessRequest.text",
"display": "ProcessRequest.text",
"equivalence": "equivalent",
"comment": "Element `Task.text` is mapped to FHIR STU3 element `ProcessRequest.text` as `Equivalent`.\nElement `Task.text` is mapped to FHIR STU3 element `ProcessResponse.text` as `Equivalent`.\nElement `Task.text` is mapped to FHIR STU3 element `Task.text` as `Equivalent`.\nContained 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."
}
]
},
{
"code": "Task.contained",
"display": "contained",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "relatedto"
}
],
"code": "ProcessRequest.contained",
"display": "ProcessRequest.contained",
"equivalence": "relatedto",
"comment": "Element `Task.contained` is mapped to FHIR STU3 element `ProcessRequest.contained` as `SourceIsBroaderThanTarget`.\nElement `Task.contained` is mapped to FHIR STU3 element `ProcessResponse.contained` as `SourceIsBroaderThanTarget`.\nElement `Task.contained` is mapped to FHIR STU3 element `Task.contained` as `SourceIsBroaderThanTarget`.\nThis should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels."
}
]
},
{
"code": "Task.identifier",
"display": "identifier",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "ProcessRequest.identifier",
"display": "ProcessRequest.identifier",
"equivalence": "equivalent",
"comment": "Element `Task.identifier` is mapped to FHIR STU3 element `ProcessRequest.identifier` as `Equivalent`.\nElement `Task.identifier` is mapped to FHIR STU3 element `ProcessResponse.identifier` as `Equivalent`.\nElement `Task.identifier` is mapped to FHIR STU3 element `Task.identifier` as `Equivalent`."
}
]
},
{
"code": "Task.status",
"display": "status",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "relatedto"
}
],
"code": "ProcessRequest.status",
"display": "ProcessRequest.status",
"equivalence": "relatedto",
"comment": "Element `Task.status` is mapped to FHIR STU3 element `ProcessRequest.status` as `RelatedTo`.\nElement `Task.status` is mapped to FHIR STU3 element `ProcessResponse.status` as `RelatedTo`.\nElement `Task.status` is mapped to FHIR STU3 element `Task.status` as `Equivalent`."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/Task",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/StructureDefinition/ProcessResponse",
"targetVersion": "3.0.2",
"element": [
{
"code": "Task.meta",
"display": "meta",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "ProcessResponse.meta",
"display": "ProcessResponse.meta",
"equivalence": "equivalent",
"comment": "Element `Task.meta` is mapped to FHIR STU3 element `ProcessRequest.meta` as `Equivalent`.\nElement `Task.meta` is mapped to FHIR STU3 element `ProcessResponse.meta` as `Equivalent`.\nElement `Task.meta` is mapped to FHIR STU3 element `Task.meta` as `Equivalent`."
}
]
},
{
"code": "Task.implicitRules",
"display": "implicitRules",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "ProcessResponse.implicitRules",
"display": "ProcessResponse.implicitRules",
"equivalence": "equivalent",
"comment": "Element `Task.implicitRules` is mapped to FHIR STU3 element `ProcessRequest.implicitRules` as `Equivalent`.\nElement `Task.implicitRules` is mapped to FHIR STU3 element `ProcessResponse.implicitRules` as `Equivalent`.\nElement `Task.implicitRules` is mapped to FHIR STU3 element `Task.implicitRules` as `Equivalent`.\nAsserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. 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."
}
]
},
{
"code": "Task.language",
"display": "language",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "ProcessResponse.language",
"display": "ProcessResponse.language",
"equivalence": "equivalent",
"comment": "Element `Task.language` is mapped to FHIR STU3 element `ProcessRequest.language` as `Equivalent`.\nElement `Task.language` is mapped to FHIR STU3 element `ProcessResponse.language` as `Equivalent`.\nElement `Task.language` is mapped to FHIR STU3 element `Task.language` as `Equivalent`.\nLanguage is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute)."
}
]
},
{
"code": "Task.text",
"display": "text",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "ProcessResponse.text",
"display": "ProcessResponse.text",
"equivalence": "equivalent",
"comment": "Element `Task.text` is mapped to FHIR STU3 element `ProcessRequest.text` as `Equivalent`.\nElement `Task.text` is mapped to FHIR STU3 element `ProcessResponse.text` as `Equivalent`.\nElement `Task.text` is mapped to FHIR STU3 element `Task.text` as `Equivalent`.\nContained 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."
}
]
},
{
"code": "Task.contained",
"display": "contained",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "relatedto"
}
],
"code": "ProcessResponse.contained",
"display": "ProcessResponse.contained",
"equivalence": "relatedto",
"comment": "Element `Task.contained` is mapped to FHIR STU3 element `ProcessRequest.contained` as `SourceIsBroaderThanTarget`.\nElement `Task.contained` is mapped to FHIR STU3 element `ProcessResponse.contained` as `SourceIsBroaderThanTarget`.\nElement `Task.contained` is mapped to FHIR STU3 element `Task.contained` as `SourceIsBroaderThanTarget`.\nThis should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels."
}
]
},
{
"code": "Task.identifier",
"display": "identifier",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "ProcessResponse.identifier",
"display": "ProcessResponse.identifier",
"equivalence": "equivalent",
"comment": "Element `Task.identifier` is mapped to FHIR STU3 element `ProcessRequest.identifier` as `Equivalent`.\nElement `Task.identifier` is mapped to FHIR STU3 element `ProcessResponse.identifier` as `Equivalent`.\nElement `Task.identifier` is mapped to FHIR STU3 element `Task.identifier` as `Equivalent`."
}
]
},
{
"code": "Task.status",
"display": "status",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "relatedto"
}
],
"code": "ProcessResponse.status",
"display": "ProcessResponse.status",
"equivalence": "relatedto",
"comment": "Element `Task.status` is mapped to FHIR STU3 element `ProcessRequest.status` as `RelatedTo`.\nElement `Task.status` is mapped to FHIR STU3 element `ProcessResponse.status` as `RelatedTo`.\nElement `Task.status` is mapped to FHIR STU3 element `Task.status` as `Equivalent`."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/Task",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/StructureDefinition/Task",
"targetVersion": "3.0.2",
"element": [
{
"code": "Task.meta",
"display": "meta",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Task.meta",
"display": "Task.meta",
"equivalence": "equivalent",
"comment": "Element `Task.meta` is mapped to FHIR STU3 element `ProcessRequest.meta` as `Equivalent`.\nElement `Task.meta` is mapped to FHIR STU3 element `ProcessResponse.meta` as `Equivalent`.\nElement `Task.meta` is mapped to FHIR STU3 element `Task.meta` as `Equivalent`."
}
]
},
{
"code": "Task.implicitRules",
"display": "implicitRules",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Task.implicitRules",
"display": "Task.implicitRules",
"equivalence": "equivalent",
"comment": "Element `Task.implicitRules` is mapped to FHIR STU3 element `ProcessRequest.implicitRules` as `Equivalent`.\nElement `Task.implicitRules` is mapped to FHIR STU3 element `ProcessResponse.implicitRules` as `Equivalent`.\nElement `Task.implicitRules` is mapped to FHIR STU3 element `Task.implicitRules` as `Equivalent`.\nAsserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. 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."
}
]
},
{
"code": "Task.language",
"display": "language",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Task.language",
"display": "Task.language",
"equivalence": "equivalent",
"comment": "Element `Task.language` is mapped to FHIR STU3 element `ProcessRequest.language` as `Equivalent`.\nElement `Task.language` is mapped to FHIR STU3 element `ProcessResponse.language` as `Equivalent`.\nElement `Task.language` is mapped to FHIR STU3 element `Task.language` as `Equivalent`.\nLanguage is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute)."
}
]
},
{
"code": "Task.text",
"display": "text",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Task.text",
"display": "Task.text",
"equivalence": "equivalent",
"comment": "Element `Task.text` is mapped to FHIR STU3 element `ProcessRequest.text` as `Equivalent`.\nElement `Task.text` is mapped to FHIR STU3 element `ProcessResponse.text` as `Equivalent`.\nElement `Task.text` is mapped to FHIR STU3 element `Task.text` as `Equivalent`.\nContained 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."
}
]
},
{
"code": "Task.contained",
"display": "contained",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "relatedto"
}
],
"code": "Task.contained",
"display": "Task.contained",
"equivalence": "relatedto",
"comment": "Element `Task.contained` is mapped to FHIR STU3 element `ProcessRequest.contained` as `SourceIsBroaderThanTarget`.\nElement `Task.contained` is mapped to FHIR STU3 element `ProcessResponse.contained` as `SourceIsBroaderThanTarget`.\nElement `Task.contained` is mapped to FHIR STU3 element `Task.contained` as `SourceIsBroaderThanTarget`.\nThis should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels."
}
]
},
{
"code": "Task.identifier",
"display": "identifier",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Task.identifier",
"display": "Task.identifier",
"equivalence": "equivalent",
"comment": "Element `Task.identifier` is mapped to FHIR STU3 element `ProcessRequest.identifier` as `Equivalent`.\nElement `Task.identifier` is mapped to FHIR STU3 element `ProcessResponse.identifier` as `Equivalent`.\nElement `Task.identifier` is mapped to FHIR STU3 element `Task.identifier` as `Equivalent`."
}
]
},
{
"code": "Task.instantiatesCanonical",
"display": "instantiatesCanonical",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Task.definition[x]",
"display": "Task.definition[x]",
"equivalence": "equivalent",
"comment": "Element `Task.instantiatesCanonical` is mapped to FHIR STU3 element `Task.definition[x]` as `Equivalent`.\nThe target context `Task.definition[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Task`."
}
]
},
{
"code": "Task.instantiatesUri",
"display": "instantiatesUri",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Task.definition[x]",
"display": "Task.definition[x]",
"equivalence": "equivalent",
"comment": "Element `Task.instantiatesUri` is mapped to FHIR STU3 element `Task.definition[x]` as `Equivalent`.\nThe target context `Task.definition[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Task`."
}
]
},
{
"code": "Task.basedOn",
"display": "basedOn",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "relatedto"
}
],
"code": "Task.basedOn",
"display": "Task.basedOn",
"equivalence": "relatedto",
"comment": "Element `Task.basedOn` is mapped to FHIR STU3 element `Task.basedOn` as `SourceIsBroaderThanTarget`.\nThe mappings for `Task.basedOn` do not cover the following types based on type expansion: display, identifier, reference, type.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Task.basedOn` with unmapped reference targets: Resource.\nTask.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)."
}
]
},
{
"code": "Task.groupIdentifier",
"display": "groupIdentifier",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Task.groupIdentifier",
"display": "Task.groupIdentifier",
"equivalence": "equivalent",
"comment": "Element `Task.groupIdentifier` is mapped to FHIR STU3 element `Task.groupIdentifier` as `Equivalent`."
}
]
},
{
"code": "Task.partOf",
"display": "partOf",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "relatedto"
}
],
"code": "Task.partOf",
"display": "Task.partOf",
"equivalence": "relatedto",
"comment": "Element `Task.partOf` is mapped to FHIR STU3 element `Task.partOf` as `SourceIsBroaderThanTarget`.\nThe mappings for `Task.partOf` do not cover the following types based on type expansion: display, identifier, reference, type.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Task.partOf` with unmapped reference targets: Task.\nThis should usually be 0..1."
}
]
},
{
"code": "Task.status",
"display": "status",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Task.status",
"display": "Task.status",
"equivalence": "equivalent",
"comment": "Element `Task.status` is mapped to FHIR STU3 element `ProcessRequest.status` as `RelatedTo`.\nElement `Task.status` is mapped to FHIR STU3 element `ProcessResponse.status` as `RelatedTo`.\nElement `Task.status` is mapped to FHIR STU3 element `Task.status` as `Equivalent`."
}
]
},
{
"code": "Task.statusReason",
"display": "statusReason",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "relatedto"
}
],
"code": "Task.statusReason",
"display": "Task.statusReason",
"equivalence": "relatedto",
"comment": "Element `Task.statusReason` is mapped to FHIR STU3 element `Task.statusReason` as `SourceIsBroaderThanTarget`.\nThe mappings for `Task.statusReason` do not cover the following types: CodeableReference.\nThe mappings for `Task.statusReason` do not cover the following types based on type expansion: reference.\nThis applies to the current status. Look at the history of the task to see reasons for past statuses."
}
]
},
{
"code": "Task.businessStatus",
"display": "businessStatus",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Task.businessStatus",
"display": "Task.businessStatus",
"equivalence": "equivalent",
"comment": "Element `Task.businessStatus` is mapped to FHIR STU3 element `Task.businessStatus` as `Equivalent`."
}
]
},
{
"code": "Task.intent",
"display": "intent",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "relatedto"
}
],
"code": "Task.intent",
"display": "Task.intent",
"equivalence": "relatedto",
"comment": "Element `Task.intent` is mapped to FHIR STU3 element `Task.intent` as `SourceIsBroaderThanTarget`.\nThis element is immutable. Proposed tasks, planned tasks, etc. must be distinct instances.\n\nIn most cases, Tasks will have an intent of \"order\"."
}
]
},
{
"code": "Task.priority",
"display": "priority",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Task.priority",
"display": "Task.priority",
"equivalence": "equivalent",
"comment": "Element `Task.priority` is mapped to FHIR STU3 element `Task.priority` as `Equivalent`."
}
]
},
{
"code": "Task.code",
"display": "code",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Task.code",
"display": "Task.code",
"equivalence": "equivalent",
"comment": "Element `Task.code` is mapped to FHIR STU3 element `Task.code` as `Equivalent`.\nThe title (eg \"My Tasks\", \"Outstanding Tasks for Patient X\") should go into the code."
}
]
},
{
"code": "Task.description",
"display": "description",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Task.description",
"display": "Task.description",
"equivalence": "equivalent",
"comment": "Element `Task.description` is mapped to FHIR STU3 element `Task.description` as `Equivalent`."
}
]
},
{
"code": "Task.focus",
"display": "focus",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "relatedto"
}
],
"code": "Task.focus",
"display": "Task.focus",
"equivalence": "relatedto",
"comment": "Element `Task.focus` is mapped to FHIR STU3 element `Task.focus` as `SourceIsBroaderThanTarget`.\nThe mappings for `Task.focus` do not cover the following types based on type expansion: display, identifier, reference, type.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Task.focus` with unmapped reference targets: Resource.\nIf multiple resources need to be manipulated, use sub-tasks. (This ensures that status can be tracked independently for each referenced resource.)."
}
]
},
{
"code": "Task.for",
"display": "for",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "relatedto"
}
],
"code": "Task.for",
"display": "Task.for",
"equivalence": "relatedto",
"comment": "Element `Task.for` is mapped to FHIR STU3 element `Task.for` as `SourceIsBroaderThanTarget`.\nThe mappings for `Task.for` do not cover the following types based on type expansion: display, identifier, reference, type.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Task.for` with unmapped reference targets: Resource."
}
]
},
{
"code": "Task.encounter",
"display": "encounter",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "relatedto"
}
],
"code": "Task.context",
"display": "Task.context",
"equivalence": "relatedto",
"comment": "Element `Task.encounter` is mapped to FHIR STU3 element `Task.context` as `SourceIsBroaderThanTarget`.\nThe mappings for `Task.encounter` do not cover the following types based on type expansion: display, identifier, reference, type.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Task.encounter` with unmapped reference targets: Encounter."
}
]
},
{
"code": "Task.executionPeriod",
"display": "executionPeriod",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Task.executionPeriod",
"display": "Task.executionPeriod",
"equivalence": "equivalent",
"comment": "Element `Task.executionPeriod` is mapped to FHIR STU3 element `Task.executionPeriod` as `Equivalent`."
}
]
},
{
"code": "Task.authoredOn",
"display": "authoredOn",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Task.authoredOn",
"display": "Task.authoredOn",
"equivalence": "equivalent",
"comment": "Element `Task.authoredOn` is mapped to FHIR STU3 element `Task.authoredOn` as `Equivalent`."
}
]
},
{
"code": "Task.lastModified",
"display": "lastModified",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Task.lastModified",
"display": "Task.lastModified",
"equivalence": "equivalent",
"comment": "Element `Task.lastModified` is mapped to FHIR STU3 element `Task.lastModified` as `Equivalent`."
}
]
},
{
"code": "Task.requester",
"display": "requester",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "relatedto"
}
],
"code": "Task.requester.agent",
"display": "Task.requester.agent",
"equivalence": "relatedto",
"comment": "Element `Task.requester` is mapped to FHIR STU3 element `Task.requester.agent` as `SourceIsBroaderThanTarget`.\nThe 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."
}
]
},
{
"code": "Task.owner",
"display": "owner",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "relatedto"
}
],
"code": "Task.owner",
"display": "Task.owner",
"equivalence": "relatedto",
"comment": "Element `Task.owner` is mapped to FHIR STU3 element `Task.owner` as `SourceIsBroaderThanTarget`.\nThe 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.\nTasks may be created with an owner not yet identified."
}
]
},
{
"code": "Task.reason",
"display": "reason",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "relatedto"
}
],
"code": "Task.reason",
"display": "Task.reason",
"equivalence": "relatedto",
"comment": "Element `Task.reason` is mapped to FHIR STU3 element `Task.reason` as `SourceIsBroaderThanTarget`.\nThe mappings for `Task.reason` do not cover the following types: CodeableReference.\nThe mappings for `Task.reason` do not cover the following types based on type expansion: reference.\nThis 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."
}
]
},
{
"code": "Task.note",
"display": "note",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Task.note",
"display": "Task.note",
"equivalence": "equivalent",
"comment": "Element `Task.note` is mapped to FHIR STU3 element `Task.note` as `Equivalent`."
}
]
},
{
"code": "Task.relevantHistory",
"display": "relevantHistory",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "relatedto"
}
],
"code": "Task.relevantHistory",
"display": "Task.relevantHistory",
"equivalence": "relatedto",
"comment": "Element `Task.relevantHistory` is mapped to FHIR STU3 element `Task.relevantHistory` as `SourceIsBroaderThanTarget`.\nThe mappings for `Task.relevantHistory` do not cover the following types based on type expansion: display, identifier, reference, type.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Task.relevantHistory` with unmapped reference targets: Provenance.\nThis 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."
}
]
},
{
"code": "Task.restriction",
"display": "restriction",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "relatedto"
}
],
"code": "Task.restriction",
"display": "Task.restriction",
"equivalence": "relatedto",
"comment": "Element `Task.restriction` is mapped to FHIR STU3 element `Task.restriction` as `Equivalent`.\nTask.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."
}
]
},
{
"code": "Task.restriction.repetitions",
"display": "repetitions",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Task.restriction.repetitions",
"display": "Task.restriction.repetitions",
"equivalence": "equivalent",
"comment": "Element `Task.restriction.repetitions` is mapped to FHIR STU3 element `Task.restriction.repetitions` as `Equivalent`."
}
]
},
{
"code": "Task.restriction.period",
"display": "period",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Task.restriction.period",
"display": "Task.restriction.period",
"equivalence": "equivalent",
"comment": "Element `Task.restriction.period` is mapped to FHIR STU3 element `Task.restriction.period` as `Equivalent`.\nThis 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.\n\nNote that period.high is the due date representing the time by which the task should be completed."
}
]
},
{
"code": "Task.restriction.recipient",
"display": "recipient",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "relatedto"
}
],
"code": "Task.restriction.recipient",
"display": "Task.restriction.recipient",
"equivalence": "relatedto",
"comment": "Element `Task.restriction.recipient` is mapped to FHIR STU3 element `Task.restriction.recipient` as `SourceIsBroaderThanTarget`.\nThe 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."
}
]
},
{
"code": "Task.input",
"display": "input",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "relatedto"
}
],
"code": "Task.input",
"display": "Task.input",
"equivalence": "relatedto",
"comment": "Element `Task.input` is mapped to FHIR STU3 element `Task.input` as `Equivalent`."
}
]
},
{
"code": "Task.input.type",
"display": "type",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Task.input.type",
"display": "Task.input.type",
"equivalence": "equivalent",
"comment": "Element `Task.input.type` is mapped to FHIR STU3 element `Task.input.type` as `Equivalent`.\nIf 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."
}
]
},
{
"code": "Task.input.value[x]",
"display": "value[x]",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "relatedto"
}
],
"code": "Task.input.value[x]",
"display": "Task.input.value[x]",
"equivalence": "relatedto",
"comment": "Element `Task.input.value[x]` is mapped to FHIR STU3 element `Task.input.value[x]` as `RelatedTo`.\nThe 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.\nThe 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`."
}
]
},
{
"code": "Task.output",
"display": "output",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "relatedto"
}
],
"code": "Task.output",
"display": "Task.output",
"equivalence": "relatedto",
"comment": "Element `Task.output` is mapped to FHIR STU3 element `Task.output` as `Equivalent`."
}
]
},
{
"code": "Task.output.type",
"display": "type",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Task.output.type",
"display": "Task.output.type",
"equivalence": "equivalent",
"comment": "Element `Task.output.type` is mapped to FHIR STU3 element `Task.output.type` as `Equivalent`."
}
]
},
{
"code": "Task.output.value[x]",
"display": "value[x]",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "relatedto"
}
],
"code": "Task.output.value[x]",
"display": "Task.output.value[x]",
"equivalence": "relatedto",
"comment": "Element `Task.output.value[x]` is mapped to FHIR STU3 element `Task.output.value[x]` as `RelatedTo`.\nThe 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.\nThe 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`."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/Task",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Task.statusReason",
"targetVersion": "0.1.0",
"element": [
{
"code": "Task.statusReason",
"display": "statusReason",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension",
"equivalence": "wider",
"comment": "Element `Task.statusReason` is mapped to FHIR STU3 element `Task.statusReason` as `SourceIsBroaderThanTarget`.\nThe mappings for `Task.statusReason` do not cover the following types: CodeableReference.\nThe mappings for `Task.statusReason` do not cover the following types based on type expansion: reference.\nThis applies to the current status. Look at the history of the task to see reasons for past statuses."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/Task",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Task.intent",
"targetVersion": "0.1.0",
"element": [
{
"code": "Task.intent",
"display": "intent",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension",
"equivalence": "wider",
"comment": "Element `Task.intent` is mapped to FHIR STU3 element `Task.intent` as `SourceIsBroaderThanTarget`.\nThis element is immutable. Proposed tasks, planned tasks, etc. must be distinct instances.\n\nIn most cases, Tasks will have an intent of \"order\"."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/Task",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Task.requestedPeriod",
"targetVersion": "0.1.0",
"element": [
{
"code": "Task.requestedPeriod",
"display": "requestedPeriod",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension",
"equivalence": "wider",
"comment": "Element `Task.requestedPeriod` has a context of ProcessRequest based on following the parent source element upwards and mapping to `ProcessRequest`.\nElement `Task.requestedPeriod` has a context of ProcessResponse based on following the parent source element upwards and mapping to `ProcessResponse`.\nElement `Task.requestedPeriod` has a context of Task based on following the parent source element upwards and mapping to `Task`.\nElement `Task.requestedPeriod` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nThis 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."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/Task",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Task.requestedPerformer",
"targetVersion": "0.1.0",
"element": [
{
"code": "Task.requestedPerformer",
"display": "requestedPerformer",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension",
"equivalence": "wider",
"comment": "Element `Task.requestedPerformer` has a context of ProcessRequest based on following the parent source element upwards and mapping to `ProcessRequest`.\nElement `Task.requestedPerformer` has a context of ProcessResponse based on following the parent source element upwards and mapping to `ProcessResponse`.\nElement `Task.requestedPerformer` has a context of Task based on following the parent source element upwards and mapping to `Task`.\nElement `Task.requestedPerformer` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/Task",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Task.performer",
"targetVersion": "0.1.0",
"element": [
{
"code": "Task.performer",
"display": "performer",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension",
"equivalence": "wider",
"comment": "Element `Task.performer` has a context of ProcessRequest based on following the parent source element upwards and mapping to `ProcessRequest`.\nElement `Task.performer` has a context of ProcessResponse based on following the parent source element upwards and mapping to `ProcessResponse`.\nElement `Task.performer` has a context of Task based on following the parent source element upwards and mapping to `Task`.\nElement `Task.performer` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
}
]
},
{
"code": "Task.performer.function",
"display": "function",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension.extension:function",
"equivalence": "wider",
"comment": "Element `Task.performer.function` is part of an existing definition because parent element `Task.performer` requires a cross-version extension.\nElement `Task.performer.function` has a context of ProcessRequest based on following the parent source element upwards and mapping to `ProcessRequest`.\nElement `Task.performer.function` has a context of ProcessResponse based on following the parent source element upwards and mapping to `ProcessResponse`.\nElement `Task.performer.function` has a context of Task based on following the parent source element upwards and mapping to `Task`.\nElement `Task.performer.function` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
}
]
},
{
"code": "Task.performer.actor",
"display": "actor",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension.extension:actor",
"equivalence": "wider",
"comment": "Element `Task.performer.actor` is part of an existing definition because parent element `Task.performer` requires a cross-version extension.\nElement `Task.performer.actor` has a context of ProcessRequest based on following the parent source element upwards and mapping to `ProcessRequest`.\nElement `Task.performer.actor` has a context of ProcessResponse based on following the parent source element upwards and mapping to `ProcessResponse`.\nElement `Task.performer.actor` has a context of Task based on following the parent source element upwards and mapping to `Task`.\nElement `Task.performer.actor` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/Task",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Task.location",
"targetVersion": "0.1.0",
"element": [
{
"code": "Task.location",
"display": "location",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension",
"equivalence": "wider",
"comment": "Element `Task.location` has a context of ProcessRequest based on following the parent source element upwards and mapping to `ProcessRequest`.\nElement `Task.location` has a context of ProcessResponse based on following the parent source element upwards and mapping to `ProcessResponse`.\nElement `Task.location` has a context of Task based on following the parent source element upwards and mapping to `Task`.\nElement `Task.location` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nThis 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."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/Task",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Task.reason",
"targetVersion": "0.1.0",
"element": [
{
"code": "Task.reason",
"display": "reason",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension",
"equivalence": "wider",
"comment": "Element `Task.reason` is mapped to FHIR STU3 element `Task.reason` as `SourceIsBroaderThanTarget`.\nThe mappings for `Task.reason` do not cover the following types: CodeableReference.\nThe mappings for `Task.reason` do not cover the following types based on type expansion: reference.\nThis 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."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/Task",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Task.insurance",
"targetVersion": "0.1.0",
"element": [
{
"code": "Task.insurance",
"display": "insurance",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension",
"equivalence": "wider",
"comment": "Element `Task.insurance` has a context of ProcessRequest based on following the parent source element upwards and mapping to `ProcessRequest`.\nElement `Task.insurance` has a context of ProcessResponse based on following the parent source element upwards and mapping to `ProcessResponse`.\nElement `Task.insurance` has a context of Task based on following the parent source element upwards and mapping to `Task`.\nElement `Task.insurance` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/Task",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Task.input.value",
"targetVersion": "0.1.0",
"element": [
{
"code": "Task.input.value[x]",
"display": "value[x]",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension",
"equivalence": "wider",
"comment": "Element `Task.input.value[x]` is mapped to FHIR STU3 element `Task.input.value[x]` as `RelatedTo`.\nThe 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.\nThe 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`."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/Task",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Task.output.value",
"targetVersion": "0.1.0",
"element": [
{
"code": "Task.output.value[x]",
"display": "value[x]",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension",
"equivalence": "wider",
"comment": "Element `Task.output.value[x]` is mapped to FHIR STU3 element `Task.output.value[x]` as `RelatedTo`.\nThe 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.\nThe 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`."
}
]
}
]
}
]
}