Stream: implementers
Topic: Service Request status vs Service status
Bart Decuypere (Feb 15 2022 at 12:59):
ServiceRequest.status is indicating the status of the service request, not the status of the action/service being requested. Nevertheless, we also need to indicate the status of the action/service being requested. This is in fact the thing my business is interested in. How can we model the status of the action/service being requested together with the ServiceRequest, without making things overly complex. Do you have any suggestions @Jose Costa Teixeira , @Lloyd McKenzie
René Spronk (Feb 15 2022 at 13:12):
That's the status on the Task resource, and the status on the FHIR Resource that records the event of 'doing the thing that is requested'. The latter status going to 'completed' is the best source of truth, the status of the Task is derived from that, and in turn the Task status impacts the status of the request.
Lloyd McKenzie (Feb 15 2022 at 15:27):
You'd have a Task that says "please fulfill" and its status would (ideally) progress from Requested->Accepted->In-progress->Completed. When all relevant tasks were completed and the requester was satisfied, the ServiceRequest itself would transition from 'active' to 'complete'.
Jose Costa Teixeira (Feb 15 2022 at 16:14):
I think we should have some guidance on how to "add" a task without forcing a complex workflow management infrastructure
Jose Costa Teixeira (Feb 15 2022 at 16:15):
Is there such a thing?
Last updated: Apr 12 2022 at 19:14 UTC
