Stream: implementers
Topic: RequestGroup.action.condition, 'action not available here'
Travis Stenerson (Nov 01 2017 at 20:46):
We have a use case that we would appreciate guidance on and RequestGroup.action.condition seems the most appropriate.
As a CDS service, we return a set of requests resources contained in a RequestGroup. Consumer organizations have the option to exclude certain procedures or regimens that may not be available at their facility. The source material defining these recommendations requires that we present the recommendation as a whole. We want to indicate that this procedure is excluded or not available at their facility and thus can not be selected as an order. The CDS response should show the recommendation, but flag it as unavailable. This condition field seems like a good option here, though any suggestion would be appreciated.
Is there guidance on how this could be accomplished in FHIR?
Thanks
Lloyd McKenzie (Nov 01 2017 at 21:24):
@Bryn Rhodes ?
Bryn Rhodes (Nov 09 2017 at 19:46):
When you are preparing the RequestGroup to be sent back, that's when you know whether the action is applicable based on the location of the requester, right? So are you saying you would just set the condition expression to false? I think that would work, but it would assume that the consuming system understood a request group with enough fidelity to depict that false as "Show this, but gray it out". That seems like a lot of assumptions to put around the meaning of the condition.
Bryn Rhodes (Nov 09 2017 at 19:49):
And I assume the response is coming back through CDS Hooks?
Travis Stenerson (Nov 09 2017 at 23:18):
Yes, that's exactly correct. It's likely that we will profile request group and extend or slice that condition field to make this clear in the data as well as explain it in the IG. And yes, somewhat through CDS-Hooks. Though we are working closely with the consuming system so the security protocol is going to differ slightly. The payload will look similar, but we needed to communicate selection behavior outside of whats possible in suggestion cards, so we're using a RequestGroup in a GuidanceResponse. As well, this GR will serve as a record of the decision support interaction.
Thanks Bryn.
Bryn Rhodes (Nov 10 2017 at 03:09):
So, one issue here is that the GuidanceResponse resource has been voted to be deprecated, though we haven't yet applied the change because tracking the lifecycle of a decision support response keeps coming up as a use case. Can I ask you to submit a tracker item that details how you are using GuidanceResponse? I'm also very interested in whether it meets the needs as you are currently using it, or if you would recommend changes to it based on your usage.
Travis Stenerson (Nov 10 2017 at 16:32):
Yes I've been hoping to speak to GuidanceResponse's continued relevance. I will submit a tracker item today that explains our use case and the issues we have run into with it.
Travis Stenerson (Nov 15 2017 at 19:52):
Submitted a tracker, I tried to spell out all the uses it covers.
tracker item 14179
Last updated: Apr 12 2022 at 19:14 UTC
