• Content
• Detailed Descriptions
• Examples
• Example operations
• XML
• JSON

StructureDefinition: ehealth-task

Introduction

A task resource describes an activity that can be performed and tracks the state of completion of that activity. It is a representation that an activity should be or has been initiated, and eventually, represents the successful or unsuccessful completion of that activity.

Scope and Usage

In scope of the eHealth Infrastructure, the Task resource is used for:

• tracking an activity to be performed by a Practitioner, CareTeam or Organization. The entity responsible for performing the Task is identified through the extension ehealth-task-responsible.
• coordinating which Practitioner has assigned or been assigned a Task. This is identified through owner.

Task resources are produced by the eHealth Infrastructure as reaction to measurements being submitted, measurements being submitted at odd timing or expected measurements not being submitted. Measurements in the form of Observation, QuestionnaireResponse or other resources are expected to be submitted by a Patient according to a measurement regime specified in a CarePlan and referenced CarePlan/ProcedureRequest.

The context in which the Task is created is identified through context. In the eHealth Infrastructure, this is currently a reference to an EpisodeOfCare, but in future use, it could be a reference to an Encounter. The focus element describes what resource the Task responsible should be acting on and can reference any resource.

Use of Task for coordinating assessment of submitted measurement

The eHealth Infrastructure supports that automated processing rules can be defined, attached to plans (through the complex of PlanDefinition/ActivityDefinition/Library and CarePlan/ProcedureRequest) and applied to submitted measurements. This includes automated processing rules performing triaging based on comparison of submitted measurements against reference ranges specified in CarePlan/ProcedureRequest. The definition of each automated processing rule controls whether to create the following as a result of the applying the rule:

• zero, one or more Communication resources of profile ehealth-message
• zero, one or more Task resources of profile ehealth-task
• zero, one or more ClinicalImpression resources of profile ehealth-clinicalimpression

A typical result of triaging, for instance, is expected to be:

• A Communication referring to a Task
• A Task referring to a ClinicalImpression
• A ClinicalImpression referring to one or more measurements (Observation, QuestionnaireResponse or Media)

In case no automated processing rule has been attached to the plan, the current fallback automated processing rule creates a Task that referes to a single measurement. This, however, could change.

A typical Task created by triaging has (is expected to have):

• Task category is a coding that states need to assess a triaging result
• Task ehealth-task-responsible that references the one or more CareTeam attached to the CarePlan
• Task ehealth-restriction-category is a coding that can be used to restrict access to the task, for instance restricting a task so only CareTeam members involved in monitoring measurements can access it
• Task priority reflecting the urgency set by the triaging rule
• Task focus references the ClinicalImpression

Use of Task for resolving missing measurement

In case the eHealth Infrastructure detects that a measurement submission is missing, it creates a Communication for the CareTeam(s) attached to the CarePlan stating that the Patient should be reminded to follow the measurement regime. It also creates a Task where:

• Task category is a coding that states need to resolve why measurement submission is missing
• Task ehealth-task-responsible references the one or more CareTeam attached to the CarePlan
• Task ehealth-restriction-category is a coding that can be used to restrict access to the task, for instance restricting a task so only CareTeam members involved in monitoring measurements can access it
• Task priority set to routine
• Task focus references the ProcedureRequest for the missing measurement

Use of Task for unexpected measurement

In case the eHealth Infrastructure detects a measurement submission at unexpected or odd time compared to the measurement regime, it creates a Task where:

• Task category is a coding that states need to resolve unexpected measurement submission* Task ehealth-task-responsible references the one or more CareTeam attached to the CarePlan
• Task ehealth-restriction-category is a coding that can be used to restrict access to the task, for instance restricting a task so only CareTeam members involved in monitoring measurements can access it
• Task priority set to routine
• Task focus references Observation, QuestionnaireResponse or Media (the measurement)

No use of Task for coordinating measuring to be performed by Patient

No Task resources are created to assist in adhering to a measurement regime.

Use of Task in coordinating activities across multiple patients

The Task extension ehealth-task-responsible enables that multiple entities (CareTeam, Practitioner, Patient, RelatedPerson) can be responsible for the Task. It is expected, for instance, that each CareTeam will provide support/monitoring of multiple patients. The Task resources for which a CareTeam is responsible can form a list sorted by priority to support triaging.

When a Task has been assigned to a particular individual (through Task owner) it is possible for the Task responsible(s) to reassign the Task. This way, CareTeam members can coordinate Task assignments (by adding Practitioner as Task owner and setting Task status) while preserving the CareTeam as fallback in case the Practitioner is unable to process the Task, for instance due to absence.

Formal Views of Profile Content

The official URL for this profile is:

http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-task

This profile builds on Task.

This profile was published on Tue Feb 04 09:11:17 UTC 2020 as a draft by ehealth.sundhed.dk.

Description of Profiles, Differentials, Snapshots, and how the XML and JSON presentations work.

 

Terminology Bindings

Path	Conformance	ValueSet
Task.language	extensible	Common Languages Max Binding: All Languages
Task.groupIdentifier.use	required	IdentifierUse
Task.groupIdentifier.type	extensible	Identifier Type Codes
Task.status	required	TaskStatus
Task.statusReason	example
Task.businessStatus	example
Task.intent	required	RequestIntent
Task.priority	required	RequestPriority
Task.code	example
Task.performerType	preferred	TaskPerformerType
Task.reason	example
Task.input.type	example
Task.output.type	example

Constraints

Id	Path	Details	Requirements
dom-2	Task	If the resource is contained in another resource, it SHALL NOT contain nested Resources : contained.contained.empty()
dom-1	Task	If the resource is contained in another resource, it SHALL NOT contain any narrative : contained.text.empty()
dom-4	Task	If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated : contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-3	Task	If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource : contained.where(('#'+id in %resource.descendants().reference).not()).empty()
inv-1	Task	Last modified date must be greater than or equal to authored-on date. : lastModified.exists().not() or authoredOn.exists().not() or lastModified >= authoredOn
ele-1	Task.extension:category	All FHIR elements must have a @value or children : hasValue() | (children().count() > id.count())
ext-1	Task.extension:category	Must have either extensions or value[x], not both : extension.exists() != value.exists()
ele-1	Task.extension:responsible	All FHIR elements must have a @value or children : hasValue() | (children().count() > id.count())
ext-1	Task.extension:responsible	Must have either extensions or value[x], not both : extension.exists() != value.exists()
ele-1	Task.extension:restrictionCategory	All FHIR elements must have a @value or children : hasValue() | (children().count() > id.count())
ext-1	Task.extension:restrictionCategory	Must have either extensions or value[x], not both : extension.exists() != value.exists()
ele-1	Task.requester	All FHIR elements must have a @value or children : hasValue() | (children().count() > id.count())
ele-1	Task.restriction	All FHIR elements must have a @value or children : hasValue() | (children().count() > id.count())
ele-1	Task.input	All FHIR elements must have a @value or children : hasValue() | (children().count() > id.count())
ele-1	Task.output	All FHIR elements must have a @value or children : hasValue() | (children().count() > id.count())

.