eHealth Infrastructure - Local Development build (v2.10.0). See the Directory of published versions
Official URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-task | Version: 2.10.0 | |||
Active as of 2023-10-24 | Computable Name: ehealth-task |
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.
In scope of the eHealth Infrastructure, the Task resource is used for:
ehealth-task-responsible
.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/ServiceRequest.
The context in which the Task is created is identified through episodeOfCare
. The focus
element describes what resource the Task responsible should be acting on and can reference any resource. The for
element can contain a reference to a Patient and shall be specified if the Task pertains to a Patient as subject. In case episodeOfCare
references an EpisodeOfCare, it is enforced that for
references the same Patient as is referenced in the EpisodeOfCare.”
The eHealth Infrastructure supports that automated processing rules can be defined as Library resources, attached to plans (through the complex of PlanDefinition/ActivityDefinition/Library and CarePlan/ServiceRequest) and applied to submitted measurements. This includes automated processing rules performing triaging based on comparison of submitted measurements against reference ranges specified in CarePlan/ServiceRequest.
The definition of each automated processing rule controls whether to create the following as a result of the applying the rule:
ehealth-message
ehealth-task
ehealth-clinicalimpression
A typical result of triaging, for instance, is expected to be:
In case no automated processing rule has been attached to the plan, the current fallback automated processing rule creates a Task that refers to a single measurement. This, however, could change.
A typical Task created by triaging is expected to have:
category
is a coding that states need to assess a triaging resultehealth-task-responsible
that references the one or more CareTeam attached to the CarePlanehealth-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 itpriority
reflecting the urgency set by the triaging rulefocus
referencing the ClinicalImpression that was also created during triaging. Focus can be overridden by the automated processing rule to reference something different than the ClinicalImpression.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:
category
is a coding that states need to resolve why measurement submission is missingehealth-task-responsible
references the one or more CareTeam attached to the CarePlanehealth-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 itpriority
set to routine
focus
references the ServiceRequest for the missing measurementIn case the eHealth Infrastructure detects a measurement submission at unexpected or odd time compared to the measurement regime, it creates a Task where:
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 CarePlanehealth-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 itpriority
set to routine
focus
references Observation, QuestionnaireResponse or Media (the measurement)No Task resources are created to assist in adhering to a measurement regime.
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.
Usage:
Description of Profiles, Differentials, Snapshots and how the different presentations work.
Other representations of profile: CSV, Excel, Schematron