Extensions for Using Data Elements from FHIR R4 in FHIR STU3
0.1.0 - STU International flag

Extensions for Using Data Elements from FHIR R4 in FHIR STU3 - Downloaded Version null See the Directory of published versions

ConceptMap: R4TaskElementMapToR3

Official URL: http://hl7.org/fhir/uv/xver/ConceptMap/R4-Task-element-map-to-R3 Version: 0.1.0
Standards status: Trial-use Maturity Level: 0 Computable Name: R4TaskElementMapToR3

This ConceptMap represents cross-version mappings for elements from a FHIR R4 Task to FHIR STU3.

Mapping from http://hl7.org/fhir/4.0 to http://hl7.org/fhir/3.0


Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/Task|4.0.1 to http://hl7.org/fhir/StructureDefinition/ProcessRequest|3.0.2

Source CodeRelationshipTarget CodeComment
Task.meta (meta)is equivalent toProcessRequest.metaElement `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 toProcessRequest.implicitRulesElement `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 it's narrative along with other profiles, value sets, etc.
Task.language (language)is equivalent toProcessRequest.languageElement `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 toProcessRequest.textElement `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 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 equivalent toProcessRequest.containedElement `Task.contained` is mapped to FHIR STU3 element `ProcessRequest.contained` as `Equivalent`. Element `Task.contained` is mapped to FHIR STU3 element `ProcessResponse.contained` as `Equivalent`. Element `Task.contained` is mapped to FHIR STU3 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.
Task.identifier (identifier)is equivalent toProcessRequest.identifierElement `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 toProcessRequest.statusElement `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|4.0.1 to http://hl7.org/fhir/StructureDefinition/ProcessResponse|3.0.2

Source CodeRelationshipTarget CodeComment
Task.meta (meta)is equivalent toProcessResponse.metaElement `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 toProcessResponse.implicitRulesElement `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 it's narrative along with other profiles, value sets, etc.
Task.language (language)is equivalent toProcessResponse.languageElement `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 toProcessResponse.textElement `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 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 equivalent toProcessResponse.containedElement `Task.contained` is mapped to FHIR STU3 element `ProcessRequest.contained` as `Equivalent`. Element `Task.contained` is mapped to FHIR STU3 element `ProcessResponse.contained` as `Equivalent`. Element `Task.contained` is mapped to FHIR STU3 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.
Task.identifier (identifier)is equivalent toProcessResponse.identifierElement `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 toProcessResponse.statusElement `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|4.0.1 to http://hl7.org/fhir/StructureDefinition/Task|3.0.2

Source CodeRelationshipTarget CodeComment
Task.meta (meta)is equivalent toTask.metaElement `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 toTask.implicitRulesElement `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 it's narrative along with other profiles, value sets, etc.
Task.language (language)is equivalent toTask.languageElement `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 toTask.textElement `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 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 equivalent toTask.containedElement `Task.contained` is mapped to FHIR STU3 element `ProcessRequest.contained` as `Equivalent`. Element `Task.contained` is mapped to FHIR STU3 element `ProcessResponse.contained` as `Equivalent`. Element `Task.contained` is mapped to FHIR STU3 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.
Task.identifier (identifier)is equivalent toTask.identifierElement `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 toTask.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 toTask.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 equivalent toTask.basedOnElement `Task.basedOn` is mapped to FHIR STU3 element `Task.basedOn` as `Equivalent`.
Task.groupIdentifier (groupIdentifier)is equivalent toTask.groupIdentifierElement `Task.groupIdentifier` is mapped to FHIR STU3 element `Task.groupIdentifier` as `Equivalent`.
Task.partOf (partOf)is equivalent toTask.partOfElement `Task.partOf` is mapped to FHIR STU3 element `Task.partOf` as `Equivalent`. This should usually be 0..1.
Task.status (status)is equivalent toTask.statusElement `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 equivalent toTask.statusReasonElement `Task.statusReason` is mapped to FHIR STU3 element `Task.statusReason` as `Equivalent`. This applies to the current status. Look at the history of the task to see reasons for past statuses.
Task.businessStatus (businessStatus)is equivalent toTask.businessStatusElement `Task.businessStatus` is mapped to FHIR STU3 element `Task.businessStatus` as `Equivalent`.
Task.intent (intent)is related toTask.intentElement `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 toTask.priorityElement `Task.priority` is mapped to FHIR STU3 element `Task.priority` as `Equivalent`.
Task.code (code)is equivalent toTask.codeElement `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 toTask.descriptionElement `Task.description` is mapped to FHIR STU3 element `Task.description` as `Equivalent`.
Task.focus (focus)is equivalent toTask.focusElement `Task.focus` is mapped to FHIR STU3 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.).
Task.for (for)is equivalent toTask.forElement `Task.for` is mapped to FHIR STU3 element `Task.for` as `Equivalent`.
Task.encounter (encounter)is equivalent toTask.contextElement `Task.encounter` is mapped to FHIR STU3 element `Task.context` as `Equivalent`.
Task.executionPeriod (executionPeriod)is equivalent toTask.executionPeriodElement `Task.executionPeriod` is mapped to FHIR STU3 element `Task.executionPeriod` as `Equivalent`.
Task.authoredOn (authoredOn)is equivalent toTask.authoredOnElement `Task.authoredOn` is mapped to FHIR STU3 element `Task.authoredOn` as `Equivalent`.
Task.lastModified (lastModified)is equivalent toTask.lastModifiedElement `Task.lastModified` is mapped to FHIR STU3 element `Task.lastModified` as `Equivalent`.
Task.requester (requester)is related toTask.requester.agentElement `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 R4 element `Task.requester` with unmapped reference targets: PractitionerRole.
Task.performerType (performerType)is equivalent toTask.performerTypeElement `Task.performerType` is mapped to FHIR STU3 element `Task.performerType` as `Equivalent`.
Task.owner (owner)is related toTask.ownerElement `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 R4 element `Task.owner` with unmapped reference targets: CareTeam, HealthcareService, PractitionerRole. Tasks may be created with an owner not yet identified.
Task.reasonCode (reasonCode)is equivalent toTask.reasonElement `Task.reasonCode` is mapped to FHIR STU3 element `Task.reason` as `Equivalent`. This should only be included if there is no focus or if it differs from the reason indicated on the focus.
Task.note (note)is equivalent toTask.noteElement `Task.note` is mapped to FHIR STU3 element `Task.note` as `Equivalent`.
Task.relevantHistory (relevantHistory)is equivalent toTask.relevantHistoryElement `Task.relevantHistory` is mapped to FHIR STU3 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.
Task.restriction (restriction)is related toTask.restrictionElement `Task.restriction` is mapped to FHIR STU3 element `Task.restriction` as `Equivalent`.
Task.restriction.repetitions (repetitions)is equivalent toTask.restriction.repetitionsElement `Task.restriction.repetitions` is mapped to FHIR STU3 element `Task.restriction.repetitions` as `Equivalent`.
Task.restriction.period (period)is equivalent toTask.restriction.periodElement `Task.restriction.period` is mapped to FHIR STU3 element `Task.restriction.period` as `Equivalent`. Note that period.high is the due date representing the time by which the task should be completed.
Task.restriction.recipient (recipient)is related toTask.restriction.recipientElement `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 R4 element `Task.restriction.recipient` with unmapped reference targets: PractitionerRole.
Task.input (input)is related toTask.inputElement `Task.input` is mapped to FHIR STU3 element `Task.input` as `Equivalent`.
Task.input.type (type)is equivalent toTask.input.typeElement `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 toTask.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: ContactDetail, Contributor, DataRequirement, Dosage, Expression, ParameterDefinition, 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 toTask.outputElement `Task.output` is mapped to FHIR STU3 element `Task.output` as `Equivalent`.
Task.output.type (type)is equivalent toTask.output.typeElement `Task.output.type` is mapped to FHIR STU3 element `Task.output.type` as `Equivalent`.
Task.output.value[x] (value[x])is related toTask.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: ContactDetail, Contributor, DataRequirement, Dosage, Expression, ParameterDefinition, 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|4.0.1 to R4: unknown | proposal | plan | order | original-order | reflex-order | filler-order | instance-order | optionversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
Task.intent (intent)maps to wider conceptExtension (R4: 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 5 Mapping from http://hl7.org/fhir/StructureDefinition/Task|4.0.1 to R4: Where task occurs (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Task.location (location)maps to wider conceptExtension (R4: 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).

Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/Task|4.0.1 to R4: Why task is needed (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Task.reasonReference (reasonReference)maps to wider conceptExtension (R4: Why task is needed (new))Element `Task.reasonReference` has a context of ProcessRequest based on following the parent source element upwards and mapping to `ProcessRequest`. Element `Task.reasonReference` has a context of ProcessResponse based on following the parent source element upwards and mapping to `ProcessResponse`. Element `Task.reasonReference` has a context of Task based on following the parent source element upwards and mapping to `Task`. Element `Task.reasonReference` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Tasks might be justified based on an Observation, a Condition, a past or planned procedure, etc. This should only be included if there is no focus or if it differs from the reason indicated on the focus. Use the CodeableConcept text element in `Task.reasonCode` if the data is free (uncoded) text.

Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/Task|4.0.1 to R4: Associated insurance coverage (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Task.insurance (insurance)maps to wider conceptExtension (R4: 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 8 Mapping from http://hl7.org/fhir/StructureDefinition/Task|4.0.1 to R4: value additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
Task.input.value[x] (value[x])maps to wider conceptExtension (R4: 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: ContactDetail, Contributor, DataRequirement, Dosage, Expression, ParameterDefinition, 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 9 Mapping from http://hl7.org/fhir/StructureDefinition/Task|4.0.1 to R4: value additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
Task.output.value[x] (value[x])maps to wider conceptExtension (R4: 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: ContactDetail, Contributor, DataRequirement, Dosage, Expression, ParameterDefinition, 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`.