Stream: workflow
Topic: Claiming a request, to work on it
Josh Mandel (Jun 16 2021 at 21:18):
For "filler" systems that look for active requests ("in force and ready to be acted upon"), how to do they indicate that they have "claimed" a request? I would have expected a status in http://build.fhir.org/valueset-request-status.html like in-progress to indicate work in progress. This would allow queries to atomically update a Request, (e.g., guarded by an If-Match ETag), to be sure only one filler can grab a given request from the queue.
Josh Mandel (Jun 16 2021 at 21:18):
Am I misunderstanding something about how the model is intended to work?
Josh Mandel (Jun 16 2021 at 21:22):
See discussion at #implementers > SMS and Twilio for a use case here.
Vassil Peytchev (Jun 16 2021 at 23:18):
You assign yourself self as the Task owner.
Vassil Peytchev (Jun 17 2021 at 00:32):
That would mean using Task instead of CommunicationRequest (in the SMS thread)
Josh Mandel (Jun 17 2021 at 00:42):
(see discussion on this Task point in the other channel.)
Lloyd McKenzie (Jun 24 2021 at 01:51):
A Request, by itself, is not directly actionable. Someone needs to ask for it to be fulfilled. This can be done by setting a Tag on the request (if the specific filler is explicitly identified). If the filler is not identified, the only way it can be claimed is with Task. Fillers generally can't modify Request resources at all (unless their modifying their 'filler-order' copy of the original 'placer-order').
Last updated: Apr 12 2022 at 19:14 UTC
