Loading
CDS Hooks 2.0 · order-select and order-sign
Prescribers don’t open another app before they sign an order, so Domino goes where they already are. EHRs call outside services at the moment of prescribing through CDS Hooks, the HL7 standard behind order-entry alerts. Domino answers with the same graph check as the prescriber check, as standard cards with a one-click way to hold the order, and the prescriber’s answer comes back into the care team’s memory.
Demo EHR · Medication order entry
Fictional EHR · speaks CDS Hooks 2.0 to Domino
88 y · female · p-rosa
Active medications (8)
New medication order
Try for this patient.
On the wire
CDS Hooks 2.0 · JSONChoose a medication in the EHR. The exact requests the EHR sends and Domino’s answers appear here.
Connect a real EHR or the CDS Hooks sandbox
Point any CDS client at Domino’s discovery endpoint. It lists two services, domino-order-select and domino-order-sign, with the prefetch they need.
Order-entry checks in this clinic
cards shown at signing · CdsCard nodes
Any patient, not just Domino’s
A patient Domino holds is checked against their record in the graph. Anyone else is checked from what the EHR shares (prefetch): their active medicines and conditions become a temporary check-up patient that expires in two hours. No name is kept.
Overrides become memory
The override reasons mirror Domino’s signed decisions: intentional, not a cascade, or going ahead and reviewing later. Every card and the prescriber’s answer is a CdsCard node linked to the patient, the drug ordered and the drug whose side effect it would treat.
Careful by design
Medicines are matched by name through FalkorDB’s full-text index, and only when the generic or brand name is really there: no card is better than a card about the wrong drug. Calls are rate-limited, stored cards are capped, and an EHR cannot name itself in the team’s feed.
The protocol details, the graph model and the limits are in How it works