Stream: implementers
Topic: Communication (with documents)
Ramandeep Dhanoa (Nov 25 2019 at 21:41):
Hi @Lloyd McKenzie , we need inputs/suggestion on how/which resources we could use for our following workflow:
1. GP creates the referral and referral order is created (Health Information exchange (HIE) generates referralOrderID and send order to all identified recipients..)
2. Recipients accept/reject it, HIE updates order accordingly (use referralOrderID from Step 1)
3. Specialist schedules patient for consultation, originating referral order is updated with appointment information and new information (use referralOrderID from Step 1)
4. Specialist completes the consultation and produces consult report (closure of originating referral order workflow) (use referralOrderID from Step 1)
I want to map this workflow to FHIR which is basically communication (like email) along with exchange of documents (consult report). Also, we are looking for delivery notifications/acknowledgments as well (CommunicationRequest?).
Vassil Peytchev (Nov 25 2019 at 21:50):
You can look at the Workflow area. You are looking at ServiceRequest and most likely Task.
http://build.fhir.org/workflow.html
Lloyd McKenzie (Nov 26 2019 at 08:05):
The general approach in FHIR is that the 'order' is not updated by the system filling the order - because the filling system generally doesn't have authorization to change the order and also because there may be multiple filling systems involved - either in parallel or over time. Instead, the ServiceRequest defines what's "authorized" for the referral. It may be directed or not. A Task is then created seeking fulfillment. The Task might be directed or not. Systems can then "claim" the Task and choose to accept it or reject it. If rejected, a new Task can be created seeking fulfillment from other systems. Once accepted, the Task gets updated with intermediary and eventually final results. The workflow section Vassil pointed to talks about the different means of systems interacting in terms of finding out what has changed depending on what system it's stored on.
Ramandeep Dhanoa (Nov 26 2019 at 16:30):
Thanks @Vassil Peytchev and @Lloyd McKenzie
Last updated: Apr 12 2022 at 19:14 UTC
