What is CDS Hooks (Clinical Decision Support Hooks)?

CDS Hooks is an HL7 specification that lets an EHR call an outside decision support service at set moments in a clinician's workflow, such as opening a chart or signing an order, and show the reply as cards inside the EHR. The service is expected to answer in about half a second.

A hook is a workflow event. The specification gives examples such as patient-view (opening a patient's record), order-select (choosing orders to place) and order-sign (just before orders are signed). When a hook fires, the EHR, acting as the CDS client, calls each service registered for that event and sends context about what the clinician is doing. Hook names follow a noun-verb pattern, and each hook definition lists the context fields it carries, tied to a specific version of the specification.

How the pieces fit

  • Discovery: a service lists what it offers at {baseUrl}/cds-services.
  • Prefetch: the service declares FHIR queries it needs in advance, so the EHR can send that data with the call instead of the service querying back each time.
  • Cards: the reply. Information cards show text, suggestion cards offer a change the clinician can accept with one click, and app link cards open an app, often a SMART app, for more detail.

The current published version is 2.0.1 (STU 2), based on FHIR R4. It says services should respond on the order of 500 ms, and that access tokens given to a service should be short-lived and revoked when the exchange is done.

Example

When a clinician selects an imaging order, the EHR fires order-select. A service checks the order against appropriate-use criteria and returns a suggestion card proposing a different study, which the clinician can accept or dismiss without leaving the order screen.

Whether clinicians act on those cards depends more on design than on the protocol. Our article on CDS Hooks and clinician adoption covers that in depth.