Stream: cds hooks
Topic: Decisions and redirect
Wolfgang Wiessler (Nov 21 2017 at 08:44):
@Kevin Shekleton and others. You recently posted on GitHub that decisions and the redirect field will be excluded from release 1.0 (https://github.com/cds-hooks/docs/pull/116). The official documentation now has a "1.0" sub-section, which still references decisions and redirect. (e.g. http://cds-hooks.org/specification/1.0/#redirect)
Could you clarify what the guidance is around that? The redirect seems to be required in order for the CDS service to notify the EHR that the interaction is done and the EHR can ask for the results.
Kevin Shekleton (Nov 21 2017 at 12:17):
Hi Wolfgang. PR #116 had not yet been merged to master which is why you still saw decisions & redirect still on cds-hooks.org. I just merged PR 116 into master so now cds-hooks.org reflects the removal of both decisions and redirect.
Kevin Shekleton (Nov 21 2017 at 12:21):
redirect was used for Decisions but with the limited implementer feedback we had received, there were proposals to change the strategy from URI redirects to Javascript postMessages (see PR #26 and PR #27). The consensus of the community was that we will focus on Decisions post 1.0 to gain additional implementer feedback and come up with a workable solution for the wide variety of EHRs that exist (both web based EHRs as well as native desktop EHRs).
Kevin Shekleton (Nov 21 2017 at 12:25):
With CDS Hooks today, CDS Services can return a card with a link to a SMART app. For the implementations I have seen, these SMART apps are opened embedded in the EHR.
Wolfgang Wiessler (Nov 21 2017 at 13:12):
We are currently using redirect and decisions, however in a non-compliant way (the create/delete with arrays of IDs is currently not workable for us).
In 1.0, is it up to the EHR and the 3rd party to agree on how the 3rd party communicates that the user is done with the interactions in the 3rd party app? And that a result is available?
Would you still expect the 3rd party app to create data via the EHR's FHIR Api?
Kevin Shekleton (Nov 21 2017 at 16:12):
CDS Services & SMART apps can certainly still create/write data back to the EHR. With CDS Services, they can do that via Suggestions. With SMART apps, they can use the FHIR API. For instance, Cerner's FHIR server supports several different writes today with some of the FHIR resources (see http://fhir.cerner.com for more details)
Kevin Shekleton (Nov 21 2017 at 16:14):
If you need to communicate something outside of the CDS Hook 1.0 spec, you would need to do it outside of our current API. We do an an issue to determine a strategy for extensions (#76) that will be in 1.0 and can be used in your use case
Last updated: Apr 12 2022 at 19:14 UTC
