EMR integration
Status: Preview · Scope: cds_hooks
Bring Augsidius into the clinician's workflow from your EMR's backend. The building blocks are the four served models; this page shows how to wire them into an EMR.
What to call, and when
| Moment in the workflow | Call | Show |
|---|---|---|
| Chart opened, visit started | aug-cds with the visit summary |
Critical cards as a banner; the rest in a side panel |
| Medicine drafted, before signing | aug-cds with the case and the planned medicine |
Contraindication and interaction cards before the order is signed |
| History being taken, results arriving | aug-care-model with a session per encounter |
Missing observations as one-tap Present / Ruled out buttons; next best actions |
| Note written or dictated | aug-extract |
Coded problems, medicines and results to confirm into the record |
| Clinician has a question | aug-evidence-qa |
Cited answer in a side panel |
| Before discharge | aug-cds with the discharge summary |
Documentation gaps and outstanding safety cards |
Cards inside the EMR
aug-cds returns cards in the HL7 CDS Hooks 2.0 card format (summary, detail, indicator, source, suggestions, overrideReasons, links). If your EMR already renders CDS Hooks cards, pass each card object to that component as-is. Test suggestions carry a draft FHIR ServiceRequest so the EMR can pre-fill an order.
The request side is Augsidius's own: your EMR backend calls /v1/chat/completions with the case summary at the moments above. You do not need to host a CDS Hooks service, configure discovery, or send FHIR prefetch bundles.
Building the case summary
Most EMRs can assemble a good summary from structured data in a few lines:
{age} {sex}. Known: {active problems}. Medicines: {current medicines with doses}.
Allergies: {allergies}. Presenting: {chief complaint and history}.
Exam: {findings, including relevant negatives}. Results: {recent labs with values}.
Plan: {draft orders and medicines about to be started}.Include relevant negatives ("no rash", "no neck stiffness") and values ("K 5.9", "eGFR 25") — both change the result.
Security
- Call Augsidius from your server. Keep the API key in your server's secret store; it must never reach the browser or the clinician's device.
- Use a separate project and key per EMR deployment, with an IP allowlist (Graphite → API keys).
- Case text is processed to answer the call and is not stored. See Safety, privacy & intended use.
- Send the minimum necessary: no names, phone numbers or ids in the case text. Use your own encounter id to correlate responses, together with
x-request-id.
Feedback
Send what clinicians did with each card to POST /v1/feedback (see Decision cards → Feedback). Results appear in Graphite → Feedback.