Stream: cds hooks
Topic: CDS Hooks interface for inquiring about patient consent
Mohammad Jafari (May 13 2020 at 23:23):
In choosing how to deliver patient preferences (based on consent) to a client, it seemed like, among existing options, CDS hooks specs provide a suitable interface since they aim at conveying the result of some external analysis to a client in a way that can be integrated with a workflow context (e.g., research or treatment decision).
I thought I'd reach out to this community and see if there are any thoughts or feedbacks on this. We have a workable prototype here:
https://github.com/sdhealthconnect/leap-cds#cds-hook-interface
Dennis Patterson (May 14 2020 at 13:59):
Hi Mohammad! It sounds like rather than having the CDS Service listening for certain workflows (usually defined as hooks) and returning consent information for those hooks, you're wanting a web service to be called whenever the CDS Client wants to look up a consent, across a variety of different events. i.e. the hook is more around the purpose of the CDS Service (retrieving consent) and the actual action/workflow information is sent as context instead.
Am I understanding? I still have more to read in your documentation, so please clarify if I'm misrepresenting!
Mohammad Jafari (May 19 2020 at 16:46):
Thanks. I think your characterization is correct. The Consent Decision Service does not return fine-grained feedback besides permit/deny and optionally some obligations (e.g., redact or mask some data item). I recognize that the CDS hooks interface is designed based on the assumption that the service returns much more detailed feedback even at the UI level.
So based on this, are you suggesting that the CDS hooks interface is not a suitable vehicle for delivering consent decisions?
Last updated: Apr 12 2022 at 19:14 UTC
