Loading
Loading
PrefillX · Live ops console
PrefillX runs on your stack — Epic, Cerner, athena, eClinicalWorks — and ships an AI agent your pharmacy team will actually use.
press⌘Kto searchstatus.ignitehealth.aiv2026.04
ops.ignitehealth · refills.tail
okA live SSE stream of synthetic refill events. No PHI. Member IDs and NDCs are fabricated. The format is exactly what the production stream emits — one event per refill decision, with member, drug, decision, latency, rolling 90-day PDC, and state.
Live metrics · last 60 minutes
A representative slice of what the dashboard shows. Numeric ranges are illustrative and update from the synthetic stream; production tiles bind to your tenant.
Inbound refill events ingested per minute, rolling 60-second window.
End-to-end decision latency at the 95th percentile, last 60 minutes.
Share of protocol-eligible refills auto-approved in the rolling window. Auto-approval target1
Share routed to a pharmacist for review, with full chart context attached.
Successful FHIR connection rate to upstream EHR, last 60 minutes.
Share of decisions routed to each model class — foundation, classifier, rules-only fallback.
Blended unit cost across the routine and escalated paths, rolling 60-minute window.
Change in tenant-level PDC against yesterday's close, scoped to the targeted measure cohort. PDC lift methodology2
The loop · six stages
Stage 1 of 6 · 01
PrefillX listens to the FHIR feed and flags refill events that match the protocol-eligible criteria.
One refill · four stations
One refill, watched all the way through. The model proposes; the rules engine binds; the pharmacist signs; the audit log records.
Integrations · no rip, no replace
SMART on FHIR launch in Epic; pharmacist review opens in-context, not a tab.
FHIR R4 · SMART on FHIRFHIR R4 reads against Cerner; refill outbound through the SCRIPT network.
FHIR R4 · NCPDP SCRIPTMarketplace integration; practice-level enable; member-level scope; observable from day one.
FHIR R4 · Athena MarketplaceInbound FHIR feed plus pharmacy network return; no new pharmacy contracts.
FHIR R4 · NCPDP SCRIPTRefReq and RefRes over Surescripts; structured retries; reasoning-trace ID in every message.
SCRIPT 2017071 · RefReq / RefResSCRIPT 2017071 outbound; reasoning-trace propagated; structured error semantics throughout.
SCRIPT 2017071 · Telecomm B1API · try it in your language
The same request, the same response, four ways. Replace the placeholder bearer token with your sandbox key. Synthetic data only.
curl https://api.ignitehealth.ai/v1/refills \
-H "Authorization: Bearer sk_sandbox_REPLACE_ME" \
-H "Content-Type: application/fhir+json" \
-X POST \
-d '{
"resourceType": "MedicationRequest",
"id": "rx-481923",
"status": "active",
"intent": "order",
"medicationCodeableConcept": {
"coding": [{
"system": "http://hl7.org/fhir/sid/ndc",
"code": "00378-0532-77",
"display": "atorvastatin 20 mg tablet"
}]
},
"subject": { "reference": "Patient/M481923" },
"dispenseRequest": { "numberOfRepeatsAllowed": 5, "quantity": { "value": 30 } }
}'Sandbox · synthetic
Sandbox uses synthetic members and synthetic NDCs. No PHI is accepted. The response shape is identical to production.
Response
No response yet. Press Run against sandbox to fire a synthetic request.
Architecture · one diagram
Click or tab to any node to read its detail. The diagram is the answer to "what does PrefillX actually do."
Tab through the diagram, or click a node, to read its detail. Press Esc to clear the selection.
Engineering
2026-04-22
The architectural choice that lets PrefillX qualify as non-device CDS — and the trade-offs that came with it.
2026-04-08
A walk through how we keep p95 model latency under four seconds without compromising the reasoning trace.
2026-03-25
Why every PrefillX decision ships a structured trace — and how we sample for completeness. Audit completeness sampling1
Status: all systems operational
status.ignitehealth.ai →last 90 days · synthetic preview · production source pending
Ship the first integration
Your sandbox key arrives in your inbox the moment the form posts. The first call against synthetic data should clear in under two seconds.
no credit cardsynthetic data onlyBAA required for production
PrefillX is a clinical decision support tool intended to inform — not replace — the judgment of a licensed clinician. PrefillX is structured to qualify as non-device CDS under the 21st Century Cures Act §3060 enforcement-discretion framework. PrefillX is not a 510(k) device.