R5-Task-element-map-to-R4
type: ConceptMap
node role: treeRoot
id:
  v: R5-Task-element-map-to-R4
text:
  status:
    v: generated
  div:
    v: Generated Narrative: ConceptMap R5-Task-element-map-to-R4 Mapping from http://hl7.org/fhir/5.0 to http://hl7.org/fhir/4.0 Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/Task|5.0.0 to Taskversion: 4.0.1) Source Concept Details Relationship Target Concept Details Comment Codes from http://hl7.org/fhir/StructureDefinition/Task|5.0.0 Codes from Task Task.meta meta is equivalent to Task.meta Task.meta Element `Task.meta` is mapped to FHIR R4 element `Task.meta` as `Equivalent`. Task.implicitRules implicitRules is equivalent to Task.implicitRules Task.implicitRules Element `Task.implicitRules` is mapped to FHIR R4 element `Task.implicitRules` as `Equivalent`. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. 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 Task.language Element `Task.language` is mapped to FHIR R4 element `Task.language` as `Equivalent`. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for informa…
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-wg
    l: structuredefinition-wg
  value: Code
    v: fhir
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm
    l: structuredefinition-fmm
  value: Integer
    v: 0
    extension:
      url:
        v: http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom
        l: structuredefinition-conformance-derivedFrom
      value: Canonical
        v: http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4
        l: hl7.fhir.uv.xver-r5.r4
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status
    l: structuredefinition-standards-status
  value: Code
    v: trial-use
    extension:
      url:
        v: http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom
        l: structuredefinition-conformance-derivedFrom
      value: Canonical
        v: http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4
        l: hl7.fhir.uv.xver-r5.r4
url:
  v: http://hl7.org/fhir/uv/xver/ConceptMap/R5-Task-element-map-to-R4
  l: R5-Task-element-map-to-R4
version:
  v: 0.1.0
name:
  v: R5TaskElementMapToR4
title:
  v: Cross-version mapping for FHIR R5 Task to FHIR R4 Task
status:
  v: active
experimental:
  v: false
date:
  v: 2026-03-17T16:04:49.5597344-05:00
contact:
  name:
    v: FHIR Infrastructure
  telecom:
    system:
      v: url
    value:
      v: http://www.hl7.org/Special/committees/fiwg
description:
  v: This ConceptMap represents cross-version mappings for elements from a FHIR R5 Task to FHIR R4.
jurisdiction:
  coding:
    system:
      v: http://unstats.un.org/unsd/methods/m49/m49.htm
      l: m49.htm
    code:
      v: 001
    display:
      v: World
source: Canonical
  v: http://hl7.org/fhir/5.0
  l: http://hl7.org/fhir/5.0
target: Uri
  v: http://hl7.org/fhir/4.0
  l: http://hl7.org/fhir/4.0
group:
  source:
    v: http://hl7.org/fhir/StructureDefinition/Task
    l: Task
  source version:
    v: 5.0.0
  target:
    v: http://hl7.org/fhir/StructureDefinition/Task
    l: Task
  target version:
    v: 4.0.1
  element:
    code:
      v: Task.meta
    display:
      v: meta
    target:
      code:
        v: Task.meta
      display:
        v: Task.meta
      equivalence:
        v: equivalent
      comment:
        v: Element `Task.meta` is mapped to FHIR R4 element `Task.meta` as `Equivalent`.
  element:
    code:
      v: Task.implicitRules
    display:
      v: implicitRules
    target:
      code:
        v: Task.implicitRules
      display:
        v: Task.implicitRules
      equivalence:
        v: equivalent
      comment:
        v: Element `Task.implicitRules` is mapped to FHIR R4 element `Task.implicitRules` as `Equivalent`. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. 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.
  element:
    code:
      v: Task.language
    display:
      v: language
    target:
      code:
        v: Task.language
      display:
        v: Task.language
      equivalence:
        v: equivalent
      comment:
        v: Element `Task.language` is mapped to FHIR R4 element `Task.language` as `Equivalent`. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
  element:
    code:
      v: Task.text
    display:
      v: text
    target:
      code:
        v: Task.text
      display:
        v: Task.text
      equivalence:
        v: equivalent
      comment:
        v: Element `Task.text` is mapped to FHIR R4 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.
  element:
    code:
      v: Task.contained
    display:
      v: contained
    target:
      code:
        v: Task.contained
      display:
        v: Task.contained
      equivalence:
        v: equivalent
      comment:
        v: Element `Task.contained` is mapped to FHIR R4 element `Task.contained` as `Equivalent`. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.
  element:
    code:
      v: Task.identifier
    display:
      v: identifier
    target:
      code:
        v: Task.identifier
      display:
        v: Task.identifier
      equivalence:
        v: equivalent
      comment:
        v: Element `Task.identifier` is mapped to FHIR R4 element `Task.identifier` as `Equivalent`.
  element:
    code:
      v: Task.instantiatesCanonical
    display:
      v: instantiatesCanonical
    target:
      code:
        v: Task.instantiatesCanonical
      display:
        v: Task.instantiatesCanonical
      equivalence:
        v: equivalent
      comment:
        v: Element `Task.instantiatesCanonical` is mapped to FHIR R4 element `Task.instantiatesCanonical` as `Equivalent`.
  element:
    code:
      v: Task.instantiatesUri
    display:
      v: instantiatesUri
    target:
      code:
        v: Task.instantiatesUri
      display:
        v: Task.instantiatesUri
      equivalence:
        v: equivalent
      comment:
        v: Element `Task.instantiatesUri` is mapped to FHIR R4 element `Task.instantiatesUri` as `Equivalent`.

code:
  v: Task.basedOn
display:
  v: basedOn
target:
  code:
    v: Task.basedOn
  display:
    v: Task.basedOn
  equivalence:
    v: equivalent
  comment:
    v: Element `Task.basedOn` is mapped to FHIR R4 element `Task.basedOn` as `Equivalent`. 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).

code:
  v: Task.groupIdentifier
display:
  v: groupIdentifier
target:
  code:
    v: Task.groupIdentifier
  display:
    v: Task.groupIdentifier
  equivalence:
    v: equivalent
  comment:
    v: Element `Task.groupIdentifier` is mapped to FHIR R4 element `Task.groupIdentifier` as `Equivalent`.

code:
  v: Task.partOf
display:
  v: partOf
target:
  code:
    v: Task.partOf
  display:
    v: Task.partOf
  equivalence:
    v: equivalent
  comment:
    v: Element `Task.partOf` is mapped to FHIR R4 element `Task.partOf` as `Equivalent`. This should usually be 0..1.

code:
  v: Task.status
display:
  v: status
target:
  code:
    v: Task.status
  display:
    v: Task.status
  equivalence:
    v: equivalent
  comment:
    v: Element `Task.status` is mapped to FHIR R4 element `Task.status` as `Equivalent`.

code:
  v: Task.statusReason
display:
  v: statusReason
target:
  code:
    v: Task.statusReason
  display:
    v: Task.statusReason
  equivalence:
    v: wider
  comment:
    v: Element `Task.statusReason` is mapped to FHIR R4 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.

code:
  v: Task.businessStatus
display:
  v: businessStatus
target:
  code:
    v: Task.businessStatus
  display:
    v: Task.businessStatus
  equivalence:
    v: equivalent
  comment:
    v: Element `Task.businessStatus` is mapped to FHIR R4 element `Task.businessStatus` as `Equivalent`.

code:
  v: Task.intent
display:
  v: intent
target:
  code:
    v: Task.intent
  display:
    v: Task.intent
  equivalence:
    v: equivalent
  comment:
    v: Element `Task.intent` is mapped to FHIR R4 element `Task.intent` as `Equivalent`. This element is immutable. Proposed tasks, planned tasks, etc. must be distinct instances. In most cases, Tasks will have an intent of "order".

code:
  v: Task.priority
display:
  v: priority
target:
  code:
    v: Task.priority
  display:
    v: Task.priority
  equivalence:
    v: equivalent
  comment:
    v: Element `Task.priority` is mapped to FHIR R4 element `Task.priority` as `Equivalent`.

code:
  v: Task.code
display:
  v: code
target:
  code:
    v: Task.code
  display:
    v: Task.code
  equivalence:
    v: equivalent
  comment:
    v: Element `Task.code` is mapped to FHIR R4 element `Task.code` as `Equivalent`. The title (eg "My Tasks", "Outstanding Tasks for Patient X") should go into the code.

code:
  v: Task.description
display:
  v: description
target:
  code:
    v: Task.description
  display:
    v: Task.description
  equivalence:
    v: equivalent
  comment:
    v: Element `Task.description` is mapped to FHIR R4 element `Task.description` as `Equivalent`.

code:
  v: Task.focus
display:
  v: focus
target:
  code:
    v: Task.focus
  display:
    v: Task.focus
  equivalence:
    v: equivalent
  comment:
    v: Element `Task.focus` is mapped to FHIR R4 element `Task.focus` as `Equivalent`. If multiple resources need to be manipulated, use sub-tasks. (This ensures that status can be tracked independently for each referenced resource.).

code:
  v: Task.for
display:
  v: for
target:
  code:
    v: Task.for
  display:
    v: Task.for
  equivalence:
    v: equivalent
  comment:
    v: Element `Task.for` is mapped to FHIR R4 element `Task.for` as `Equivalent`.

code:
  v: Task.encounter
display:
  v: encounter
target:
  code:
    v: Task.encounter
  display:
    v: Task.encounter
  equivalence:
    v: equivalent
  comment:
    v: Element `Task.encounter` is mapped to FHIR R4 element `Task.encounter` as `Equivalent`.

code:
  v: Task.executionPeriod
display:
  v: executionPeriod
target:
  code:
    v: Task.executionPeriod
  display:
    v: Task.executionPeriod
  equivalence:
    v: equivalent
  comment:
    v: Element `Task.executionPeriod` is mapped to FHIR R4 element `Task.executionPeriod` as `Equivalent`.

code:
  v: Task.authoredOn
display:
  v: authoredOn
target:
  code:
    v: Task.authoredOn
  display:
    v: Task.authoredOn
  equivalence:
    v: equivalent
  comment:
    v: Element `Task.authoredOn` is mapped to FHIR R4 element `Task.authoredOn` as `Equivalent`.

code:
  v: Task.lastModified
display:
  v: lastModified
target:
  code:
    v: Task.lastModified
  display:
    v: Task.lastModified
  equivalence:
    v: equivalent
  comment:
    v: Element `Task.lastModified` is mapped to FHIR R4 element `Task.lastModified` as `Equivalent`.

code:
  v: Task.requester
display:
  v: requester
target:
  code:
    v: Task.requester
  display:
    v: Task.requester
  equivalence:
    v: equivalent
  comment:
    v: Element `Task.requester` is mapped to FHIR R4 element `Task.requester` as `Equivalent`.

code:
  v: Task.owner
display:
  v: owner
target:
  code:
    v: Task.owner
  display:
    v: Task.owner
  equivalence:
    v: equivalent
  comment:
    v: Element `Task.owner` is mapped to FHIR R4 element `Task.owner` as `Equivalent`. Tasks may be created with an owner not yet identified.

code:
  v: Task.location
display:
  v: location
target:
  code:
    v: Task.location
  display:
    v: Task.location
  equivalence:
    v: equivalent
  comment:
    v: Element `Task.location` is mapped to FHIR R4 element `Task.location` as `Equivalent`. 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.

code:
  v: Task.reason
display:
  v: reason
target:
  code:
    v: Task.reasonCode
  display:
    v: Task.reasonCode
  equivalence:
    v: relatedto
  comment:
    v: Element `Task.reason` is mapped to FHIR R4 element `Task.reasonCode` as `SourceIsBroaderThanTarget`. Element `Task.reason` is mapped to FHIR R4 element `Task.reasonReference` as `SourceIsBroaderThanTarget`. This will typically not be present for Tasks with a code of 'please fulfill' as, for those, the reason for action is conveyed on the Request pointed to by Task.focus. Some types of tasks will not need a 'reason'. E.g. a request to discharge a patient can be inferred to be 'because the patient is ready' and this would not need a reason to be stated on the Task.
target:
  code:
    v: Task.reasonReference
  display:
    v: Task.reasonReference
  equivalence:
    v: relatedto
  comment:
    v: Element `Task.reason` is mapped to FHIR R4 element `Task.reasonCode` as `SourceIsBroaderThanTarget`. Element `Task.reason` is mapped to FHIR R4 element `Task.reasonReference` as `SourceIsBroaderThanTarget`. 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.

code:
  v: Task.insurance
display:
  v: insurance
target:
  code:
    v: Task.insurance
  display:
    v: Task.insurance
  equivalence:
    v: equivalent
  comment:
    v: Element `Task.insurance` is mapped to FHIR R4 element `Task.insurance` as `Equivalent`.

code:
  v: Task.note
display:
  v: note
target:
  code:
    v: Task.note
  display:
    v: Task.note
  equivalence:
    v: equivalent
  comment:
    v: Element `Task.note` is mapped to FHIR R4 element `Task.note` as `Equivalent`.

code:
  v: Task.relevantHistory
display:
  v: relevantHistory
target:
  code:
    v: Task.relevantHistory
  display:
    v: Task.relevantHistory
  equivalence:
    v: equivalent
  comment:
    v: Element `Task.relevantHistory` is mapped to FHIR R4 element `Task.relevantHistory` as `Equivalent`. 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.

code:
  v: Task.restriction
display:
  v: restriction
target:
  code:
    v: Task.restriction
  display:
    v: Task.restriction
  equivalence:
    v: wider
  comment:
    v: Element `Task.restriction` is mapped to FHIR R4 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.

code:
  v: Task.restriction.repetitions
display:
  v: repetitions
target:
  code:
    v: Task.restriction.repetitions
  display:
    v: Task.restriction.repetitions
  equivalence:
    v: equivalent
  comment:
    v: Element `Task.restriction.repetitions` is mapped to FHIR R4 element `Task.restriction.repetitions` as `Equivalent`.

code:
  v: Task.restriction.period
display:
  v: period
target:
  code:
    v: Task.restriction.period
  display:
    v: Task.restriction.period
  equivalence:
    v: equivalent
  comment:
    v: Element `Task.restriction.period` is mapped to FHIR R4 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.

code:
  v: Task.restriction.recipient
display:
  v: recipient
target:
  code:
    v: Task.restriction.recipient
  display:
    v: Task.restriction.recipient
  equivalence:
    v: equivalent
  comment:
    v: Element `Task.restriction.recipient` is mapped to FHIR R4 element `Task.restriction.recipient` as `Equivalent`.

code:
  v: Task.input
display:
  v: input
target:
  code:
    v: Task.input
  display:
    v: Task.input
  equivalence:
    v: wider
  comment:
    v: Element `Task.input` is mapped to FHIR R4 element `Task.input` as `Equivalent`.

code:
  v: Task.input.type
display:
  v: type
target:
  code:
    v: Task.input.type
  display:
    v: Task.input.type
  equivalence:
    v: equivalent
  comment:
    v: Element `Task.input.type` is mapped to FHIR R4 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.

code:
  v: Task.input.value[x]
display:
  v: value[x]
target:
  code:
    v: Task.input.value[x]
  display:
    v: Task.input.value[x]
  equivalence:
    v: wider
  comment:
    v: Element `Task.input.value[x]` is mapped to FHIR R4 element `Task.input.value[x]` as `RelatedTo`. The mappings for `Task.input.value[x]` do not cover the following types: Availability, CodeableReference, ExtendedContactDetail, RatioRange. 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`.

code:
  v: Task.output
display:
  v: output
target:
  code:
    v: Task.output
  display:
    v: Task.output
  equivalence:
    v: wider
  comment:
    v: Element `Task.output` is mapped to FHIR R4 element `Task.output` as `Equivalent`.

code:
  v: Task.output.type
display:
  v: type
target:
  code:
    v: Task.output.type
  display:
    v: Task.output.type
  equivalence:
    v: equivalent
  comment:
    v: Element `Task.output.type` is mapped to FHIR R4 element `Task.output.type` as `Equivalent`.

code:
  v: Task.output.value[x]
display:
  v: value[x]
target:
  code:
    v: Task.output.value[x]
  display:
    v: Task.output.value[x]
  equivalence:
    v: wider
  comment:
    v: Element `Task.output.value[x]` is mapped to FHIR R4 element `Task.output.value[x]` as `RelatedTo`. The mappings for `Task.output.value[x]` do not cover the following types: Availability, CodeableReference, ExtendedContactDetail, RatioRange. 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`.

source:
  v: http://hl7.org/fhir/StructureDefinition/Task
  l: Task
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Task.statusReason
  l: extension-Task.statusReason
target version:
  v: 0.1.0
element:
  code:
    v: Task.statusReason
  display:
    v: statusReason
  target:
    code:
      v: Extension
    equivalence:
      v: equivalent
    comment:
      v: Element `Task.statusReason` is mapped to FHIR R4 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.

source:
  v: http://hl7.org/fhir/StructureDefinition/Task
  l: Task
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Task.requestedPeriod
  l: extension-Task.requestedPeriod
target version:
  v: 0.1.0
element:
  code:
    v: Task.requestedPeriod
  display:
    v: requestedPeriod
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: 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 R4. 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.

source:
  v: http://hl7.org/fhir/StructureDefinition/Task
  l: Task
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Task.requestedPerformer
  l: extension-Task.requestedPerformer
target version:
  v: 0.1.0
element:
  code:
    v: Task.requestedPerformer
  display:
    v: requestedPerformer
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: 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 R4. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/Task
  l: Task
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Task.performer
  l: extension-Task.performer
target version:
  v: 0.1.0
element:
  code:
    v: Task.performer
  display:
    v: performer
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: 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 R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: Task.performer.function
  display:
    v: function
  target:
    code:
      v: Extension.extension:function
    equivalence:
      v: wider
    comment:
      v: 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 Task based on following the parent source element upwards and mapping to `Task`. Element `Task.performer.function` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: Task.performer.actor
  display:
    v: actor
  target:
    code:
      v: Extension.extension:actor
    equivalence:
      v: wider
    comment:
      v: 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 Task based on following the parent source element upwards and mapping to `Task`. Element `Task.performer.actor` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/Task
  l: Task
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Task.input.value
  l: extension-Task.input.value
target version:
  v: 0.1.0
element:
  code:
    v: Task.input.value[x]
  display:
    v: value[x]
  target:
    code:
      v: Extension
    equivalence:
      v: equivalent
    comment:
      v: Element `Task.input.value[x]` is mapped to FHIR R4 element `Task.input.value[x]` as `RelatedTo`. The mappings for `Task.input.value[x]` do not cover the following types: Availability, CodeableReference, ExtendedContactDetail, RatioRange. 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`.

source:
  v: http://hl7.org/fhir/StructureDefinition/Task
  l: Task
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Task.output.value
  l: extension-Task.output.value
target version:
  v: 0.1.0
element:
  code:
    v: Task.output.value[x]
  display:
    v: value[x]
  target:
    code:
      v: Extension
    equivalence:
      v: equivalent
    comment:
      v: Element `Task.output.value[x]` is mapped to FHIR R4 element `Task.output.value[x]` as `RelatedTo`. The mappings for `Task.output.value[x]` do not cover the following types: Availability, CodeableReference, ExtendedContactDetail, RatioRange. 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`.