Stream: cds hooks
Topic: Provenance of a decision
John Moehrke (May 06 2017 at 08:45):
Are decisions rendered by cds-hook backed by a Provenance record indicating that decision comes from an identified instance of cds, using a subset of resources as Provenance.entity?
Josh Mandel (May 06 2017 at 08:49):
They are not. Can you say more about the use case you have in mind @John Moehrke ?
John Moehrke (May 06 2017 at 09:20):
I likely need to understand more about cds-hooks... but I expect it is producing some kind of a decision. that decision is to be consumed and acted upon in some way. That consumption/action should be aware of where this decision comes from, and what it is based upon. This is what the Provenance resource could record. So That, resulting clinical decision and documentation can include the evidence of the decision, the author identity of that decision, and the evidence behind that decision. So That, investigation of that decision can be supported. Unlike where the decision must be simply trusted, or becomes disembodied.
Josh Mandel (May 06 2017 at 09:38):
Come stop by the CDS Hooks table and let's talk!
Phillip Warner (May 06 2017 at 09:53):
https://fhir.cygni.cc:8443/opencds-decision-support-service/hooks/cds-services
Phillip Warner (May 06 2017 at 09:53):
yes
Josh Mandel (May 06 2017 at 09:59):
Thanks @Phillip Warner! Any chance you can enable CORS on this service?
Phillip Warner (May 06 2017 at 09:59):
yeah--I'll have to remember CORS
Josh Mandel (May 06 2017 at 09:59):
In the test harness we're seeing
XMLHttpRequest cannot load https://fhir.cygni.cc:8443/opencds-decision-support-service/hooks/cds-services. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://demo.cds-hooks.org' is therefore not allowed access.
Josh Mandel (May 06 2017 at 10:00):
Check out the intro at http://docs.smarthealthit.org/tutorials/server-quick-start/
Josh Mandel (May 06 2017 at 10:00):
for a quick and dirty approach.
Phillip Warner (May 06 2017 at 10:00):
Access-Control-Allow-Origin: * would be fine?
Josh Mandel (May 06 2017 at 10:00):
Yes.
Josh Mandel (May 06 2017 at 10:00):
That alone should do the trick.
Phillip Warner (May 06 2017 at 10:00):
ok; I'll get that implemented and let you know
Josh Mandel (May 06 2017 at 10:01):
Awesome, thanks!
Phillip Warner (May 06 2017 at 10:09):
done
Josh Mandel (May 06 2017 at 10:11):
I think you also need
Access-Control-Allow-Methods: GET, HEAD, POST, PUT, DELETE, TRACE, OPTIONS
Josh Mandel (May 06 2017 at 10:12):
(at least GET, POST, OPTIONS)
Phillip Warner (May 06 2017 at 10:26):
OK, hopefully that works for you.
Josh Mandel (May 06 2017 at 10:27):
I see:
Allow: POST, GET, OPTIONS, HEAD
But I'm expecting:
Access-Control-Allow-Methods: GET, HEAD, POST, PUT, DELETE, TRACE, OPTIONS
Phillip Warner (May 06 2017 at 10:33):
I see
Phillip Warner (May 06 2017 at 10:42):
This should work now. I didn't add the OPTIONS to the hookInstance.
Simone Heckmann (Nov 21 2018 at 13:41):
We are currently discussing how to capture Provenance of Resources that have been created by algorithms in this stream: https://chat.fhir.org/#narrow/stream/156-data-extraction.20services
I believe most of the talking points may be relevant for CDS as well... Please join the discussion!
Last updated: Apr 12 2022 at 19:14 UTC
