FHIR Chat · serviceRequest · workflow

Stream: workflow

Topic: serviceRequest


view this post on Zulip Tejay Cardon (Dec 02 2020 at 21:20):

Hello. I'm looking for a little advice. The ServiceRequest documentation specifically mentions using service request for a "pharmacist medication review". We're looking to build an API that allows a client to request a medication review. this would trigger our pharmacists to review the patient medication profile and make recommended adjustments. We believe the end result should be represented as a pharmacist eCarePlan (adheres to the careplan fhir shape).

However, we're running to a couple of areas of uncertainty, and I'm hoping we can get some advice. If we're totally off base, let me know.

  1. would the initial request endpoint just be a post to /serviceRequest? Or would a custom endpoint make more sense?
  2. given the response is a carePlan, how does the client know when the result is ready, or where to find it? I can't find any field on serviceRequest that references the response to the request.

Best we have come up with so far is a post to /serviceRequest, followed by subscribing to changes in the service request. When the request is "completed" the client would then make a request to /carePlan with a filter for "basedOn" with the initial service request. Only, it looks like basedOn for carePlan requires another carePlan...

Any ideas? Thank you!!

view this post on Zulip Vassil Peytchev (Dec 02 2020 at 21:43):

ServiceRequest in general is for recording the authorization for an action. Your use case may benefit from using Task instead, where the CarePlan will become the output of the Task. The general workflow, as described, seems to be fine.

view this post on Zulip Tejay Cardon (Dec 03 2020 at 17:26):

Thank you Vassil. In our case we may be billing for the service too, so sounds like the authorization aspect of the servicerequest might make it a stronger fit.

view this post on Zulip Vassil Peytchev (Dec 03 2020 at 19:09):

In that case you could consider both ServiceRequest and Task, where Task.basedOn will reference the ServiceRequest, and Task.output will reference the CarePlan. An important consideration would be where the ServiceRequest is instantiated, as usually the authorizing entity needs to be the owner of the ServiceRequest.

view this post on Zulip Tejay Cardon (Dec 04 2020 at 22:31):

Ah, that makes much more sense. Thank you.


Last updated: Apr 12 2022 at 19:14 UTC