A task to be performed.

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.

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.

This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.

An Extension

R5: Task.requestedPeriod (new:Period)

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.

R5: Task.requestedPerformer (new:CodeableReference(Practitioner,PractitionerRole,Organization,CareTeam,HealthcareService,Patient,Device,RelatedPerson))

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).

R5: Task.performer (new:BackboneElement)

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).

R5: Task.location (new:Reference(Location))

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.

R5: Task.insurance (new:Reference(Coverage,ClaimResponse))

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).

An Extension

R5: Task.doNotPerform (new:boolean)

Element Task.doNotPerform has a context of ProcessRequest based on following the parent source element upwards and mapping to ProcessRequest. Element Task.doNotPerform has a context of ProcessResponse based on following the parent source element upwards and mapping to ProcessResponse. Element Task.doNotPerform has a context of Task based on following the parent source element upwards and mapping to Task. Element Task.doNotPerform has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). An externally-defined extension that has been mapped as the representation of FHIR R5 element Task.doNotPerform: http://hl7.org/fhir/StructureDefinition/request-doNotPerform. The attributes provided with the Task qualify what is not to be done. For example, if a requestedPeriod is provided, the 'do not' request only applies within the specified time. If a requestedPerformer is specified then the 'do not' request only applies to performers of that type. Qualifiers include: code, subject, occurrence, requestedPerformer and performer.

In some cases, the Request.code may pre-coordinate prohibition into the requested action. E.g. 'NPO' (nothing by mouth), 'DNR' (do not recussitate). If this happens, doNotPerform SHALL NOT be set to true. I.e. The resource shall not have double negation. (E.g. 'Do not DNR').

doNotPerform should ONLY be used with Tasks that are tightly bounded in time or process phase. E.g. 'Do not fulfill the midnight dose of medication X tonight due to the early morning scheduled procedure, where the nurse could reasonably check off 'Med X not given at midnight as instructed'. Similarly, a decision support proposal that a patient should not be given a standard intake questionnaire (because the patient is cognitively impaired) would be marked as 'complete' or 'rejected' when the clinician preps the CarePlan or order set after reviewing the decision support results. If there is a need to create a standing order to not do something that can't be satisfied by a single 'non-action', but rather an ongoing refusal to perform the function, MedicationRequest, ServiceRequest or some other form of authorization should be used.

The current status of the task.

The current status of the task.

These states enable coordination of task status with off-the-shelf workflow solutions that support automation of tasks.

Indicates the "level" of actionability associated with the Task. I.e. Is this a proposed task, a planned task, an actionable task, etc.

This element is immutable. Proposed tasks, planned tasks, etc. must be distinct instances.

In most cases, Tasks will have an intent of "order".

Distinguishes whether the task is a proposal, plan or full order

An Extension

R5: 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".

R5: Task.requestedPeriod (new:Period)

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.

R5: Task.requestedPerformer (new:CodeableReference(Practitioner,PractitionerRole,Organization,CareTeam,HealthcareService,Patient,Device,RelatedPerson))

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).

R5: Task.performer (new:BackboneElement)

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).

R5: Task.location (new:Reference(Location))

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.

R5: Task.insurance (new:Reference(Coverage,ClaimResponse))

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).

R5: Task.doNotPerform (new:boolean)

Element Task.doNotPerform has a context of ProcessRequest based on following the parent source element upwards and mapping to ProcessRequest. Element Task.doNotPerform has a context of ProcessResponse based on following the parent source element upwards and mapping to ProcessResponse. Element Task.doNotPerform has a context of Task based on following the parent source element upwards and mapping to Task. Element Task.doNotPerform has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). An externally-defined extension that has been mapped as the representation of FHIR R5 element Task.doNotPerform: http://hl7.org/fhir/StructureDefinition/request-doNotPerform. The attributes provided with the Task qualify what is not to be done. For example, if a requestedPeriod is provided, the 'do not' request only applies within the specified time. If a requestedPerformer is specified then the 'do not' request only applies to performers of that type. Qualifiers include: code, subject, occurrence, requestedPerformer and performer.

In some cases, the Request.code may pre-coordinate prohibition into the requested action. E.g. 'NPO' (nothing by mouth), 'DNR' (do not recussitate). If this happens, doNotPerform SHALL NOT be set to true. I.e. The resource shall not have double negation. (E.g. 'Do not DNR').

doNotPerform should ONLY be used with Tasks that are tightly bounded in time or process phase. E.g. 'Do not fulfill the midnight dose of medication X tonight due to the early morning scheduled procedure, where the nurse could reasonably check off 'Med X not given at midnight as instructed'. Similarly, a decision support proposal that a patient should not be given a standard intake questionnaire (because the patient is cognitively impaired) would be marked as 'complete' or 'rejected' when the clinician preps the CarePlan or order set after reviewing the decision support results. If there is a need to create a standing order to not do something that can't be satisfied by a single 'non-action', but rather an ongoing refusal to perform the function, MedicationRequest, ServiceRequest or some other form of authorization should be used.

R5: Task.basedOn additional types from child elements (display, identifier, reference, type)

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).

R5: Task.partOf additional types from child elements (display, identifier, reference, type)

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.

R5: Task.statusReason additional types (CodeableReference) additional types from child elements (reference)

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.

R5: 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".

R5: Task.focus additional types from child elements (display, identifier, reference, type)

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.).

R5: Task.for additional types from child elements (display, identifier, reference, type)

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.

R5: Task.encounter additional types from child elements (display, identifier, reference, type)

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.

R5: Task.requester

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.

R5: 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.

R5: Task.reason additional types (CodeableReference) additional types from child elements (reference)

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.

R5: Task.relevantHistory additional types from child elements (display, identifier, reference, type)

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.

R5: 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.

R5: Task.input.value[x] additional types (uuid, CodeableReference, RatioRange, ContactDetail, DataRequirement, Expression, ParameterDefinition, RelatedArtifact, TriggerDefinition, UsageContext, Availability, ExtendedContactDetail, Dosage)

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.

R5: Task.output.value[x] additional types (uuid, CodeableReference, RatioRange, ContactDetail, DataRequirement, Expression, ParameterDefinition, RelatedArtifact, TriggerDefinition, UsageContext, Availability, ExtendedContactDetail, Dosage)

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.

A task to be performed.

The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

The only time that a resource does not have an id is when it is being submitted to the server using a create operation.

The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource.

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.

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.

This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.

The base language in which the resource is written.

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).

Unless not suitable, these codes SHALL be taken from Common Languages
(extensible to http://hl7.org/fhir/ValueSet/languages|3.0.2)

A human language.

A human-readable narrative that contains a summary of the resource, and may be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.

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 in formation is added later.

These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.

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.

An Extension

R5: Task.requestedPeriod (new:Period)

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.

R5: Task.requestedPerformer (new:CodeableReference(Practitioner,PractitionerRole,Organization,CareTeam,HealthcareService,Patient,Device,RelatedPerson))

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).

R5: Task.performer (new:BackboneElement)

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).

R5: Task.location (new:Reference(Location))

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.

R5: Task.insurance (new:Reference(Coverage,ClaimResponse))

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).

An Extension

R5: Task.doNotPerform (new:boolean)

Element Task.doNotPerform has a context of ProcessRequest based on following the parent source element upwards and mapping to ProcessRequest. Element Task.doNotPerform has a context of ProcessResponse based on following the parent source element upwards and mapping to ProcessResponse. Element Task.doNotPerform has a context of Task based on following the parent source element upwards and mapping to Task. Element Task.doNotPerform has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). An externally-defined extension that has been mapped as the representation of FHIR R5 element Task.doNotPerform: http://hl7.org/fhir/StructureDefinition/request-doNotPerform. The attributes provided with the Task qualify what is not to be done. For example, if a requestedPeriod is provided, the 'do not' request only applies within the specified time. If a requestedPerformer is specified then the 'do not' request only applies to performers of that type. Qualifiers include: code, subject, occurrence, requestedPerformer and performer.

In some cases, the Request.code may pre-coordinate prohibition into the requested action. E.g. 'NPO' (nothing by mouth), 'DNR' (do not recussitate). If this happens, doNotPerform SHALL NOT be set to true. I.e. The resource shall not have double negation. (E.g. 'Do not DNR').

doNotPerform should ONLY be used with Tasks that are tightly bounded in time or process phase. E.g. 'Do not fulfill the midnight dose of medication X tonight due to the early morning scheduled procedure, where the nurse could reasonably check off 'Med X not given at midnight as instructed'. Similarly, a decision support proposal that a patient should not be given a standard intake questionnaire (because the patient is cognitively impaired) would be marked as 'complete' or 'rejected' when the clinician preps the CarePlan or order set after reviewing the decision support results. If there is a need to create a standing order to not do something that can't be satisfied by a single 'non-action', but rather an ongoing refusal to perform the function, MedicationRequest, ServiceRequest or some other form of authorization should be used.

The business identifier for this task.

A reference to a formal or informal definition of the task. For example, a protocol, a step within a defined workflow definition, etc.

Enables a formal definition of how he task is to be performed (e.g. using BPMN, BPEL, XPDL or other formal notation) to be associated with a task, enabling automation.

BasedOn refers to a higher-level authorization that triggered the creation of the task. It references a "request" resource such as a ProcedureRequest, MedicationRequest, ProcedureRequest, CarePlan, etc. which is distinct from the "request" resource the task is seeking to fulfil. This latter resource is referenced by FocusOn. For example, based on a ProcedureRequest (= BasedOn), a task is created to fulfil a procedureRequest ( = FocusOn ) to collect a specimen from a patient.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R5: Task.basedOn additional types from child elements (display, identifier, reference, type)

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).

A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Plain text narrative that identifies the resource in addition to the resource reference.

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

An identifier that links together multiple tasks and other requests that were created in the same context.

Billing and/or reporting can be linked to whether multiple requests were created as a single unit.

Task that this particular task is part of.

This should usually be 0..1.

Allows tasks to be broken down into sub-steps (and this division can occur independent of the original task).

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R5: Task.partOf additional types from child elements (display, identifier, reference, type)

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.

A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Plain text narrative that identifies the resource in addition to the resource reference.

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

The current status of the task.

The current status of the task.

These states enable coordination of task status with off-the-shelf workflow solutions that support automation of tasks.

An explanation as to why this task is held, failed, was refused, etc.

This applies to the current status. Look at the history of the task to see reasons for past statuses.

Codes to identify the reason for current status. These will typically be specific to a particular workflow.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R5: Task.statusReason additional types (CodeableReference) additional types from child elements (reference)

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.

A reference to a code defined by a terminology system.

Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.

Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings.

A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.

Very often the text is the same as a displayName of one of the codings.

The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.

Contains business-specific nuances of the business state.

The domain-specific business-contextual sub-state of the task. For example: "Blood drawn", "IV inserted", "Awaiting physician signature", etc.

There's often a need to track substates of a task - this is often variable by specific workflow implementation.

Indicates the "level" of actionability associated with the Task. I.e. Is this a proposed task, a planned task, an actionable task, etc.

This element is immutable. Proposed tasks, planned tasks, etc. must be distinct instances.

In most cases, Tasks will have an intent of "order".

Distinguishes whether the task is a proposal, plan or full order

unique id for the element within a resource (for internal references)

An Extension

R5: 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".

Primitive value for code

Indicates how quickly the Task should be addressed with respect to other requests.

The task's priority

Used to identify the service level expected while performing a task.

A name or code (or both) briefly describing what the task involves.

The title (eg "My Tasks", "Outstanding Tasks for Patient X") should go into the code.

Codes to identify what the task involves. These will typically be specific to a particular workflow.

A free-text description of what is to be performed.

The request being actioned or the resource being manipulated by this task.

If multiple resources need to be manipulated, use sub-tasks. (This ensures that status can be tracked independently for each referenced resource.).

Used to identify the thing to be done.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R5: Task.focus additional types from child elements (display, identifier, reference, type)

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.).

A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Plain text narrative that identifies the resource in addition to the resource reference.

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

The entity who benefits from the performance of the service specified in the task (e.g., the patient).

Used to track tasks outstanding for a beneficiary. Do not use to track the task owner or creator (see owner and creator respectively). This can also affect access control.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R5: Task.for additional types from child elements (display, identifier, reference, type)

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.

A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Plain text narrative that identifies the resource in addition to the resource reference.

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

The healthcare event (e.g. a patient and healthcare provider interaction) during which this task was created.

For some tasks it may be important to know the link between the task or episode of care the task originated within.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R5: Task.encounter additional types from child elements (display, identifier, reference, type)

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.

A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Plain text narrative that identifies the resource in addition to the resource reference.

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

Identifies the time action was first taken against the task (start) and/or the time final action was taken against the task prior to marking it as completed (end).

The date and time this task was created.

Most often used along with lastUpdated to track duration of task to supporting monitoring and management.

The date and time of last modification to this task.

Used along with history to track task activity and time in a particular task state. This enables monitoring and management.

The creator of the task.

Identifies who created this task. May be used by access control mechanisms (e.g., to ensure that only the creator can cancel a task).

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

The device, practitioner, etc. who initiated the task.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R5: Task.requester

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.

A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Plain text narrative that identifies the resource in addition to the resource reference.

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

The organization the device or practitioner was acting on behalf of when they initiated the task.

Practitioners and Devices can be associated with multiple organizations. This element indicates which organization they were acting on behalf of when authoring the request.

The type of participant that can execute the task.

The type(s) of task performers allowed

Use to distinguish tasks on different activity queues.

Individual organization or Device currently responsible for task execution.

Tasks may be created with an owner not yet identified.

Identifies who is expected to perform this task.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R5: 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.

A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Plain text narrative that identifies the resource in addition to the resource reference.

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

A description or code indicating why this task needs to be performed.

This should only be included if there is no focus or if it differs from the reason indicated on the focus.

Indicates why the task is needed. E.g. Suspended because patient admitted to hospital.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R5: Task.reason additional types (CodeableReference) additional types from child elements (reference)

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.

A reference to a code defined by a terminology system.

Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.

Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings.

A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.

Very often the text is the same as a displayName of one of the codings.

The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.

Free-text information captured about the task as it progresses.

Links to Provenance records for past versions of this Task that identify key state transitions or updates that are likely to be relevant to a user looking at the current version of the task.

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.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R5: Task.relevantHistory additional types from child elements (display, identifier, reference, type)

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.

A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Plain text narrative that identifies the resource in addition to the resource reference.

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

If the Task.focus is a request resource and the task is seeking fulfillment (i.e is asking for the request to be actioned), this element identifies any limitations on what parts of the referenced request should be actioned.

Sometimes when fulfillment is sought, you don't want full fulfillment.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Indicates the number of times the requested action should occur.

E.g. order that requests monthly lab tests, fulfillment is sought for 1.

Over what time-period is fulfillment sought.

Note that period.high is the due date representing the time by which the task should be completed.

E.g. order that authorizes 1 year's services. Fulfillment is sought for next 3 months.

For requests that are targeted to more than on potential recipient/target, for whom is fulfillment sought?

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R5: 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.

A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Plain text narrative that identifies the resource in addition to the resource reference.

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

Additional information that may be needed in the execution of the task.

Resources and data used to perform the task. This data is used in the business logic of task execution, and is stored separately because it varies between workflows.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R5: Task.input.value[x] additional types (uuid, CodeableReference, RatioRange, ContactDetail, DataRequirement, Expression, ParameterDefinition, RelatedArtifact, TriggerDefinition, UsageContext, Availability, ExtendedContactDetail, Dosage)

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.

May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

A code or description indicating how the input is intended to be used as part of the task execution.

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.

Codes to identify types of input parameters. These will typically be specific to a particular workflow. E.g. "Comparison source", "Applicable consent", "Concommitent Medications", etc.

Inputs are named to enable task automation to bind data and pass it from one task to the next.

The value of the input parameter as a basic type.

Outputs produced by the Task.

Resources and data produced during the execution the task. This data is generated by the business logic of task execution, and is stored separately because it varies between workflows.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R5: Task.output.value[x] additional types (uuid, CodeableReference, RatioRange, ContactDetail, DataRequirement, Expression, ParameterDefinition, RelatedArtifact, TriggerDefinition, UsageContext, Availability, ExtendedContactDetail, Dosage)

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.

May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

The name of the Output parameter.

Codes to identify types of input parameters. These will typically be specific to a particular workflow. E.g. "Identified issues", "Preliminary results", "Filler order", "Final results", etc.

Outputs are named to enable task automation to bind data and pass it from one task to the next.

The value of the Output parameter as a basic type.

Task outputs can take any form.