I’ve said it before. Now I’m saying it again.
FHIR’s Task resource is the most unappreciated resource type in FHIR and one of the most useful.
If you’re not using it, your app or solution is more complicated than it needs to be.
Guaranteed.
What’s so special about it?
The Task resource type enables seamless workflows in FHIR.
It makes it possible for multiple applications to work together, each one pulling Tasks from the same FHIR server, one after the other.
Application A performs one task => then application B performs its Task => then C, and so on down the chain.
Couple this with FHIR Subscriptions that notify listening apps when a new Task is waiting for them to action and you have a complete FHIR workflow management system.
Out of the box and with little effort.
One of the first questions I ask technical architects when I look at a new FHIR project is “Are you using Task resources?”
If the answer is no, I roll up my sleeves because I know we’ll all have a lot of work to do.
The Task resource type: https://hl7.org/fhir/R4/task.html
---