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 information about the relationship between xml:lang and the html lang attribute). Task.text text is equivalent to Task.text Task.text 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. Task.contained contained is equivalent to Task.contained Task.contained 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. Task.identifier identifier is equivalent to Task.identifier Task.identifier Element `Task.identifier` is mapped to FHIR R4 element `Task.identifier` as `Equivalent`. Task.instantiatesCanonical instantiatesCanonical is equivalent to Task.instantiatesCanonical Task.instantiatesCanonical Element `Task.instantiatesCanonical` is mapped to FHIR R4 element `Task.instantiatesCanonical` as `Equivalent`. Task.instantiatesUri instantiatesUri is equivalent to Task.instantiatesUri Task.instantiatesUri Element `Task.instantiatesUri` is mapped to FHIR R4 element `Task.instantiatesUri` as `Equivalent`. Task.basedOn basedOn is equivalent to Task.basedOn Task.basedOn 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). Task.groupIdentifier groupIdentifier is equivalent to Task.groupIdentifier Task.groupIdentifier Element `Task.groupIdentifier` is mapped to FHIR R4 element `Task.groupIdentifier` as `Equivalent`. Task.partOf partOf is equivalent to Task.partOf Task.partOf Element `Task.partOf` is mapped to FHIR R4 element `Task.partOf` as `Equivalent`. This should usually be 0..1. Task.status status is equivalent to Task.status Task.status Element `Task.status` is mapped to FHIR R4 element `Task.status` as `Equivalent`. Task.statusReason statusReason maps to wider concept Task.statusReason Task.statusReason 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. Task.businessStatus businessStatus is equivalent to Task.businessStatus Task.businessStatus Element `Task.businessStatus` is mapped to FHIR R4 element `Task.businessStatus` as `Equivalent`. Task.intent intent is equivalent to Task.intent Task.intent 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". Task.priority priority is equivalent to Task.priority Task.priority Element `Task.priority` is mapped to FHIR R4 element `Task.priority` as `Equivalent`. Task.code code is equivalent to Task.code Task.code 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. Task.description description is equivalent to Task.description Task.description Element `Task.description` is mapped to FHIR R4 element `Task.description` as `Equivalent`. Task.focus focus is equivalent to Task.focus Task.focus 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.). Task.for for is equivalent to Task.for Task.for Element `Task.for` is mapped to FHIR R4 element `Task.for` as `Equivalent`. Task.encounter encounter is equivalent to Task.encounter Task.encounter Element `Task.encounter` is mapped to FHIR R4 element `Task.encounter` as `Equivalent`. Task.executionPeriod executionPeriod is equivalent to Task.executionPeriod Task.executionPeriod Element `Task.executionPeriod` is mapped to FHIR R4 element `Task.executionPeriod` as `Equivalent`. Task.authoredOn authoredOn is equivalent to Task.authoredOn Task.authoredOn Element `Task.authoredOn` is mapped to FHIR R4 element `Task.authoredOn` as `Equivalent`. Task.lastModified lastModified is equivalent to Task.lastModified Task.lastModified Element `Task.lastModified` is mapped to FHIR R4 element `Task.lastModified` as `Equivalent`. Task.requester requester is equivalent to Task.requester Task.requester Element `Task.requester` is mapped to FHIR R4 element `Task.requester` as `Equivalent`. Task.owner owner is equivalent to Task.owner Task.owner Element `Task.owner` is mapped to FHIR R4 element `Task.owner` as `Equivalent`. Tasks may be created with an owner not yet identified. Task.location location is equivalent to Task.location Task.location 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. Task.reason reason is related to Task.reasonCode Task.reasonCode 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. is related to Task.reasonReference Task.reasonReference 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. Task.insurance insurance is equivalent to Task.insurance Task.insurance Element `Task.insurance` is mapped to FHIR R4 element `Task.insurance` as `Equivalent`. Task.note note is equivalent to Task.note Task.note Element `Task.note` is mapped to FHIR R4 element `Task.note` as `Equivalent`. Task.relevantHistory relevantHistory is equivalent to Task.relevantHistory Task.relevantHistory 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. Task.restriction restriction maps to wider concept Task.restriction Task.restriction 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. Task.restriction.repetitions repetitions is equivalent to Task.restriction.repetitions Task.restriction.repetitions Element `Task.restriction.repetitions` is mapped to FHIR R4 element `Task.restriction.repetitions` as `Equivalent`. Task.restriction.period period is equivalent to Task.restriction.period Task.restriction.period 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. Task.restriction.recipient recipient is equivalent to Task.restriction.recipient Task.restriction.recipient Element `Task.restriction.recipient` is mapped to FHIR R4 element `Task.restriction.recipient` as `Equivalent`. Task.input input maps to wider concept Task.input Task.input Element `Task.input` is mapped to FHIR R4 element `Task.input` as `Equivalent`. Task.input.type type is equivalent to Task.input.type Task.input.type 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. Task.input.value[x] value[x] maps to wider concept Task.input.value[x] Task.input.value[x] 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`. Task.output output maps to wider concept Task.output Task.output Element `Task.output` is mapped to FHIR R4 element `Task.output` as `Equivalent`. Task.output.type type is equivalent to Task.output.type Task.output.type Element `Task.output.type` is mapped to FHIR R4 element `Task.output.type` as `Equivalent`. Task.output.value[x] value[x] maps to wider concept Task.output.value[x] Task.output.value[x] 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`. Group 2 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) is equivalent to Extension (R5: statusReason additional types) 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. Group 3 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 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. Group 4 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 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). Group 5 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 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). 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 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). 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 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). Group 6 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]) is equivalent to Extension (R5: value additional types) 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`. Group 7 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]) is equivalent to Extension (R5: value additional types) 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`.
Cross-version mapping for FHIR R5 Task to FHIR R4 Task
This ConceptMap represents cross-version mappings for elements from a FHIR R5 Task to FHIR R4.
Element `Task.meta` is mapped to FHIR R4 element `Task.meta` as `Equivalent`.
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 `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 `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 `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 `Task.identifier` is mapped to FHIR R4 element `Task.identifier` as `Equivalent`.
Element `Task.instantiatesCanonical` is mapped to FHIR R4 element `Task.instantiatesCanonical` as `Equivalent`.
Element `Task.instantiatesUri` is mapped to FHIR R4 element `Task.instantiatesUri` as `Equivalent`.
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).
Element `Task.groupIdentifier` is mapped to FHIR R4 element `Task.groupIdentifier` as `Equivalent`.
Element `Task.partOf` is mapped to FHIR R4 element `Task.partOf` as `Equivalent`. This should usually be 0..1.
Element `Task.status` is mapped to FHIR R4 element `Task.status` as `Equivalent`.
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.
Element `Task.businessStatus` is mapped to FHIR R4 element `Task.businessStatus` as `Equivalent`.
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".
Element `Task.priority` is mapped to FHIR R4 element `Task.priority` as `Equivalent`.
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.
Element `Task.description` is mapped to FHIR R4 element `Task.description` as `Equivalent`.
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.).
Element `Task.for` is mapped to FHIR R4 element `Task.for` as `Equivalent`.
Element `Task.encounter` is mapped to FHIR R4 element `Task.encounter` as `Equivalent`.
Element `Task.executionPeriod` is mapped to FHIR R4 element `Task.executionPeriod` as `Equivalent`.
Element `Task.authoredOn` is mapped to FHIR R4 element `Task.authoredOn` as `Equivalent`.
Element `Task.lastModified` is mapped to FHIR R4 element `Task.lastModified` as `Equivalent`.
Element `Task.requester` is mapped to FHIR R4 element `Task.requester` as `Equivalent`.
Element `Task.owner` is mapped to FHIR R4 element `Task.owner` as `Equivalent`. Tasks may be created with an owner not yet identified.
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.
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.
Element `Task.insurance` is mapped to FHIR R4 element `Task.insurance` as `Equivalent`.
Element `Task.note` is mapped to FHIR R4 element `Task.note` as `Equivalent`.
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.
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.
Element `Task.restriction.repetitions` is mapped to FHIR R4 element `Task.restriction.repetitions` as `Equivalent`.
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.
Element `Task.restriction.recipient` is mapped to FHIR R4 element `Task.restriction.recipient` as `Equivalent`.
Element `Task.input` is mapped to FHIR R4 element `Task.input` as `Equivalent`.
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.
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`.
Element `Task.output` is mapped to FHIR R4 element `Task.output` as `Equivalent`.
Element `Task.output.type` is mapped to FHIR R4 element `Task.output.type` as `Equivalent`.
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`.
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.
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).
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 `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 `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).