Get information to doctors in the places they're already working
A decision support API supports an existing health care workflow such as prescribing medication, by providing contextually relevant information, automation, and guidelines related to that workflow via a standardized API.
With decision support APIs we can build examples like:
- Presenting drug costs transparently to doctors when they are writing prescriptions
According to Dr. Joe Kimura, Chief Medical Officer at Atrius Health:
The amount of information we need to understand is getting so untenable that it’s unreasonable to expect the average clinician to integrate all of it into their decision-making effectively and reliably
Decision Support APIs help to create health care workflows that reduce burn out for doctors and raise the quality of care for patients.
The CDS Hooks specification describes the RESTful APIs and interactions to integrate Clinical Decision Support (CDS) between CDS Clients (typically Electronic Health Record Systems (EHRs) or other health information systems) and CDS Services.
A decision support API built with CDS Hooks is a RESTful HTTP API. CDS Services and CDS Clients negotiate the exchange of decision support requests and responses. The framework defines a number of
hookswhich are pre-agreements about the minimum data requirements for a pre-defined workflow like viewing a patient record or signing a prescription order.
The CDS Hooks workflow
CDS Services advertise their capabilities through a Discovery endpoint. Clients (like an EHR) trigger these capabilities. Clients provide FHIR Resources as required by the
hookin the form of
prefetchparameters. Services execute their own rules and return one or many Cards that present information, provide actionable suggestions, and initiate SMART App launch sequences.
Learn more about how to launch a CDS Hooks API in our Sero user guide.
CDS Hooks are actively used, required for use, or suggested for use in a number of places in addition to private sector projects.