Stream: cds hooks
Topic: context-update hook
Bas van den Heuvel (Apr 01 2022 at 11:28):
CDS hooks currently does not allow a CDS Service to act on a change in the patients clinical record.
What would trigger such hook? A change to a resource in the Patients compartment?
What context elements should such hook contain?
Josh Mandel (Apr 01 2022 at 14:51):
CDS Hooks is about hooking into a provider workflow UX; if you are interested in receiving notifications about changes to data, wouldn't subscriptions fit the bill better?
Bas van den Heuvel (Apr 04 2022 at 07:58):
Josh, good suggestion, a hook design based on Subscriptions would be very flexible, maybe a little bit too much.
The intend of the hook(s) I would like to explore are workflow UX events where the provider changes the clinical record. E.g. add a condition, observation, risk assessment, ...
So far as I see this is currently not covered by the current hooks.
Josh Mandel (Apr 04 2022 at 14:06):
Thanks, that clarifies the concept for me. It's not about whether the record changed but rather whether the current user has taken a step to change the record. That would make sense as a new hook definition from my perspective.
John Silva (Apr 05 2022 at 14:37):
Is there overlap with FHIRcast here?
Bas van den Heuvel (Apr 06 2022 at 12:24):
Not directly. The workflow actions might trigger FHIRcast events but I do not see FHIRcast dependencies for such hook(s).
Last updated: Apr 12 2022 at 19:14 UTC
