If you’re not using the Task resource you’re probably missing out on FHIR workflows.
FHIR is more than just interconnected resources. It also defines workflows that help articulate and manage activities across systems and processes.
The Task resource is an integral part of many of these workflows. Here are examples of Tasks that might be created and tracked as part of an Encounter, ServiceRequest or CarePlan:
- cancelling an order
- fulfilling an order
- sending a report to a GP
- merging a set of records
- admitting a patient
Are you having difficulty managing how data is updated across various FHIR resources?
Are you considering creating custom statuses or extensions to manage progress and state?
If you are, you might be trying to invent something that already exists. You should look more closely at workflows and the Task resource.
FHIR’s workflow module documents the coordination of various activities:
- How events can be triggered
- The sequence of connected activities
- How statuses should be kept and verified.
Start here: http://hl7.org/fhir/R4/workflow-module.html
Followed by the workflow overview: http://hl7.org/fhir/R4/workflow.html
And workflow communication patterns: http://hl7.org/fhir/R4/workflow-communications.html
Then take a close look at the Task resource type itself: http://hl7.org/fhir/R4/task.html
This is a heavy and complicated topic — not for the faint hearted and not for beginners.
But if you’re working on a large FHIR project and you’re not using the Task resource, chances are your data model is missing some key components.
---