FHIR Chat · docs / Issue #39 Formally document hook definitions · cds hooks

Stream: cds hooks

Topic: docs / Issue #39 Formally document hook definitions

Github Notifications (May 05 2017 at 23:53):

kpshek milestoned Issue #39

Github Notifications (May 05 2017 at 23:53):

kpshek opened Issue #39

In discussion with @brynrhodes and @Isaac Vetter regarding aligning Clinical Reasoning and CDS Hooks, one of the topics of discussion was around how hooks are defined today.

For instance, the medication-prescribe hook is very loosely defined today with just a brief mention of the context data that is sent on this type of hook request.

We should do the following:

1. Strengthen our documentation around our currently predefined hooks. The key data here is the value of the context in the CDS Service request.
2. Clearly document expectations for how future hooks should be defined.

Github Notifications (May 06 2017 at 05:00):

isaacvetter commented on Issue #39

I wanted to elaborate on this a bit ...

The hook in CDS Hooks is a clinical workflow event, typically in a user's synchronous workflow. Although the spec currently only defines three; there are many potentially standardizeable hooks. As part of the standardization of each of these events, we should identify the data that describes the event and define which FHIR resources best fit.

The medication-prescribe hook occurs when the user is in the process of prescribing a new medication
1. What's the purpose of the EHR calling the hook?
- Identify the workflow in which the event occurs.
- Identify the intent of the EHR for calling the hook. E.g. The EHR solicits feedback about the prescription-in-progress.
2. Clearly and authoritatively identify the FHIR resources that are included in the context attribute from the EHR to the CDS service.

The content in Proposed Hooks is a good start, except that each proposed hook should identify its required context.

Last updated: Apr 12 2022 at 19:14 UTC