• In the description below the logic flow diagram, it is not clear what the “yellow action steps“ are referring to in the diagram. Perhaps this language needs to be more aligned with the diagram above it. For example, “If the series of logical conditions all result in a true (yes) outcome, an alert (CDS Hooks card) will be returned to the EHR for display to the user. Alert (card) content is represented in brown shape in the diagram. Implementors may also configure user response options. Examples of possible user response options are represented by red ovals in the logic flow above.“
• Is it still the case that the service creates a “CarePlan/RequestGroup” as described here? “The CDS Service then processes the appropriate PlanDefinition resource, evaluating the criteria and constructing a response as a CarePlan/RequestGroup if the criteria evaluate to true.”
• Consider updating all STU3 references on this page to R4.
• CDS Hooks v.2 now supports user feedback. Consider removing this sentence “Note that as of the time of this writing, the CDS Hooks specification does not support notifying the CDS Service of how the user responded, only that they responded. This issue is actively being addressed as part of the specification. In lieu of CDS Hooks support, the local EHR integration should provide this functionality.”
• In the description below the logic flow diagram, it is not clear what the “yellow action steps“ are referring to in the diagram. Perhaps this language needs to be more aligned with the diagram above it. For example, “If the series of logical conditions all result in a true (yes) outcome, an alert (CDS Hooks card) will be returned to the EHR for display to the user. Alert (card) content is represented in brown shape in the diagram. Implementors may also configure user response options. Examples of possible user response options are represented by red ovals in the logic flow above.“
• Is it still the case that the service creates a “CarePlan/RequestGroup” as described here? “The CDS Service then processes the appropriate PlanDefinition resource, evaluating the criteria and constructing a response as a CarePlan/RequestGroup if the criteria evaluate to true.”
• Consider updating all STU3 references on this page to R4.
• CDS Hooks v.2 now supports user feedback. Consider removing this sentence “Note that as of the time of this writing, the CDS Hooks specification does not support notifying the CDS Service of how the user responded, only that they responded. This issue is actively being addressed as part of the specification. In lieu of CDS Hooks support, the local EHR integration should provide this functionality.”