Stream: cds hooks
Topic: docs / Issue #41 a user should be able to unsubscribe fro...
Github Notifications (May 06 2017 at 05:16):
isaacvetter opened Issue #41
In discussion with @brynrhodes and @kpshek regarding aligning Clinical Reasoning and CDS Hooks, one of the topics of discussion was around the ability of a user to "unsubscribe" from a card.
It would make a lot of clinicians happy if they were able to unsubscribe from a card. This information would also be valuable to CDS services.
It would make sense to enhance the analytics-endpoint to support this additional information.
Overall, the analytics-endpoint that's currently defined in the CDS Hooks specification has not yet seen significant adoption, although it's clearly a useful feature to CDS services.
Github Notifications (May 06 2017 at 12:17):
bdoolittle commented on Issue #41
I agree that that clinicians will undoubtedly want to have some control in the filtering of their CDS cards and that CDS services will find the user feedback valuable.
If the hooks spec supports an unsubscribe, should it also support a way for clinicians to subscribe to content (or content subscription may be performed outside the scope of the CDS-hooks workflow)?
Should a clinician be able to unsubscribe from any card? This gives the user more control, but may also prevent important feedback from being delivered at the point of care. Does this introduce a patient safety risk?
Last updated: Apr 12 2022 at 19:14 UTC
