Stream: cds hooks
Topic: Passing service discovery URL to sandbox
Josh Mandel (Apr 27 2018 at 15:12):
I'm coming late to this party, but: for the use case of pre-populating a specific CDS Service in (so users don't have to manually click "Add a CDS Service"), how come the sandbox is configured to take a serviceDiscoveryURL as an access token parameter rather than just a regular URL parameter?
Using a regular URL parameter would allow more flexible sandbox configuration even outside the context of a SMART-launched sandbox -- but maybe I'm missing a design consideration here @Kevin Shekleton @Dan Gottlieb @Vladimir Ignatov ?
Josh Mandel (Apr 27 2018 at 15:14):
To put this more concretely: why not pass a serviceDiscoveryURL like
https://sandbox.cds-hooks.org?serviceDiscoveryURL=:url
Instead of embedding this parameter in an access token response that the sandbox only sees when it's launched as a SMART app?
Dan Gottlieb (Apr 27 2018 at 16:20):
@Josh Mandel I agree that's a better approach - iirc, we used the context to limit modifications to the current sandbox code while it's being rewritten...
Radu Craioveanu (Apr 28 2018 at 21:40):
@Dan Gottlieb , @Josh Mandel
Are there any CDS Services available in production today? If so, who is providing them, and what version of FHIR are they using? If nothing in FHIR available in production quality, what are options do I have to use an external service to do Allergy Checking at the time of Medication Order. I also need to do Duplicate Medication Checking, but I think I can do that internally.
Kevin Shekleton (May 02 2018 at 20:19):
@Radu Craioveanu - There are none in production today as we have not released a version of the CDS Hooks specification. However, we are currently balloting our first release of CDS Hooks through HL7 for the May 2018 ballot cycle!
Last updated: Apr 12 2022 at 19:14 UTC
