Clinical Decision Support APIs: How CDS Hooks & FHIR Work Together
A plain-English guide to clinical decision support (CDS) APIs in 2026 — what CDS Hooks are, how they surface the right info at the right moment, and how to build them on FHIR.
The best clinical software doesn't just store information — it surfaces the right information at the right moment. A gentle warning when two medications interact. A reminder that a patient is due for a screening. A suggested next step based on the latest results. That's clinical decision support (CDS), and thanks to two standards — CDS Hooks and FHIR — you can build it once and have it work inside many different EHRs. This guide explains how they fit together, in plain language.
The foundation we recommend is ClinikAPI — a FHIR-native platform that holds the patient data your decision logic reads. Here is why we suggest it up front:
- Free to start: Get your API keys in seconds — no credit card needed.
- Clean FHIR data: The organized patient context your CDS rules need.
- Real-time events: React to changes that should trigger a suggestion.
- Built on FHIR: Works with the same standards CDS Hooks expects.
- Compliant: HIPAA-compliant, SOC 2-audited, with a signed BAA.
Quick Answer
Clinical decision support (CDS) is software that helps a clinician by surfacing relevant information at the right moment — and CDS Hooks plus FHIR are how you deliver it across different EHRs. CDS Hooks is a standard that lets an EHR call your service at a specific moment (like opening a patient or starting a prescription). Your service reads the patient's FHIR data, applies your rules, and returns short "cards" — suggestions or warnings the clinician sees right in their workflow. CDS Hooks handles when to call you and how to show the result; FHIR provides the patient data your logic reads. Because both are standards, one CDS service can work inside many EHRs — and it assists the clinician rather than replacing their judgment.
Power decision support with clean FHIR data
What clinical decision support actually does
CDS is best understood by example. It's the software that:
- Warns about a drug interaction when a clinician starts a prescription.
- Reminds that a patient is due for a screening they've missed.
- Surfaces a relevant guideline based on the latest lab result.
- Flags a value that's out of range and needs attention.
In every case, it's assisting — putting the right fact in front of a human at the moment they need it. The clinician still decides.
CDS Hooks: the right moment
The hard part of decision support isn't the logic — it's timing. A warning is only useful if it appears at the moment of the decision, not buried in a report later. CDS Hooks solves the timing. It's a standard that lets an EHR call your service at defined moments:
| Hook (moment) | When it fires |
|---|---|
patient-view | A clinician opens a patient's chart |
order-select | They start choosing an order |
medication-prescribe | They begin prescribing a medication |
When a hook fires, the EHR sends your service the context (which patient, which clinician). Your service responds with cards — short suggestions or warnings — that appear right in the clinician's screen.
FHIR: the data behind the decision
A suggestion is only as good as the data behind it. That's where FHIR comes in. When a hook fires, your service reads the relevant FHIR records — the patient's conditions, medications, recent results — and applies your rules:
// Simplified: a CDS service responding to a hook
app.post('/cds-services/bp-check', async (req) => {
const patientId = req.body.context.patientId
// Read the patient's FHIR data
const readings = await clinik.observations.search({
subject: `Patient/${patientId}`, code: 'blood-pressure',
})
// Apply your rule, return a card
if (latest(readings).systolic > 140) {
return { cards: [{ summary: 'Elevated blood pressure — consider follow-up', indicator: 'warning' }] }
}
return { cards: [] }
})
CDS Hooks delivers the trigger and the card; FHIR delivers the facts. (See Healthcare Data API for reading FHIR data.)
The beauty of this pairing is reuse. Because CDS Hooks and FHIR are both standards, one decision-support service can plug into many EHRs — instead of rebuilding your logic for each one.
Keep a human in the loop
A core principle of good CDS: suggest, don't decide. Surfacing a warning or a reminder is helpful; silently changing care is not. The strongest decision support reduces missed details and saves time while leaving the clinician firmly in control. (This is the same principle behind safe healthcare AI.)
Product Insight: Why ClinikAPI Is a Strong CDS Foundation
A CDS service is only as good as the data it can read. ClinikAPI gives your decision logic clean, organized FHIR data on compliant infrastructure.
What you get:
- Clean FHIR context: Read exactly the conditions, medications, and results your rules need.
- Fast search: Pull the right records without complex queries.
- Real-time events: Trigger workflows when data changes.
- A safe home for data: HIPAA-compliant, SOC 2-audited, with a signed BAA.
Your CDS Hooks service reads patient data from ClinikAPI, applies your logic, and returns suggestions — with the data layer handled. Explore the FHIR engine and the platform.
Frequently Asked Questions
1. What is clinical decision support?
Software that helps a clinician by surfacing relevant information at the right moment — a warning, a reminder, a suggested next step. It assists; it doesn't replace judgment.
2. What are CDS Hooks?
A standard that lets an EHR call your service at specific moments (like prescribing). Your service reads FHIR data and returns "cards" the clinician sees in their workflow.
3. How do CDS Hooks and FHIR work together?
CDS Hooks provides the trigger and delivery; FHIR provides the patient data your logic reads. Together they let one service work across many EHRs.
4. Does CDS replace the doctor?
No. It surfaces information; the clinician decides. The best CDS keeps a human in the loop.
5. How do I build a CDS service?
Build a web service that responds to CDS Hooks, reads relevant FHIR data, applies your rules, and returns cards. A FHIR-native platform makes the data side simple.
Conclusion
Clinical decision support turns stored data into timely help — the right fact at the right moment. CDS Hooks handles the timing and delivery, FHIR handles the data, and together they let you build decision support once and run it across many EHRs. Keep a human in the loop, build on clean FHIR data, and you get software that makes clinicians faster and safer without taking over their judgment.
Key takeaways:
- CDS surfaces the right information at the right moment to assist a clinician.
- CDS Hooks defines when the EHR calls your service and how suggestions appear.
- FHIR provides the patient data your decision logic reads.
- Both are standards, so one CDS service works across many EHRs.
- Good CDS suggests; the clinician always decides.
Ready to build? Get your free ClinikAPI keys or explore the platform.