Solutions
Same engine, digital front door
Post structured Rxs via API. Get a queue ID immediately. Receive completion on webhooks.
- Live in 2 days
- PHIPA compliant
- Canadian data residency
Who uses the digital Rx API
Partners that send prescriptions programmatically rather than by fax.
EMR and EHR platforms
Clinics that generate structured prescription data and want direct-to-pharmacy delivery without fax.
Clinic software
Provincial or regional clinic platforms with prescribing modules.
Banner hubs
Banner chains that centralize prescription routing across multiple sites.
Long-term care
LTC facilities that generate bulk prescription batches at cycle fill time.
What the API accepts
On successful ingestion, the API returns a queue ID immediately. Your system can use this ID to query status or correlate with the completion webhook.
The same pipeline, digital front door
Once a digital Rx is ingested, it runs through the identical pipeline as a fax prescription: Kroll context read, AI-assisted DIN matching, async write, exception routing. There is no separate quality bar for digital submissions, your clinical users and pharmacy staff see one consistent standard regardless of how a prescription arrived.
Completion and error handling
For integration documentation and sandbox credentials, start at /developers.
Frequently asked questions
- How do EMRs and clinics send prescriptions to AutoRx?
- Partners post structured JSON to the AutoRx Digital Rx API with patient identifiers, prescriber details, and one or more prescription lines. The API validates fields at ingestion and returns a queue ID immediately, then runs the prescription through the same Kroll pipeline as a fax: context read, DIN matching, async write, and exception routing.
- Is the digital Rx API processed differently from faxes?
- No. Once ingested, a digital prescription runs the identical AutoRx pipeline as a fax prescription, with the same Kroll context read, DIN matching, and exception handling. There is no separate quality bar, so your clinical users and pharmacy staff see one consistent standard regardless of how a prescription arrived.
- How does my system know when a Kroll write is done?
- When a write completes, successfully or with a final failure, AutoRx fires a webhook to your configured endpoint with the queue ID, Kroll write status, and failure reason if any. Your system closes the loop without polling. See the AutoRx webhooks documentation for the full payload schema.
- Where are the API docs and sandbox credentials?
- Integration documentation, the full payload schema, and sandbox credentials are at the AutoRx developer portal at /developers. The API is REST-based with HMAC-signed webhooks, designed as a drop-in for EMR, EHR, banner-hub, and long-term-care systems.
Get started with AutoRx
Ready to automate?
Most pharmacies go live within 2 days. No waitlist, and your existing Kroll setup stays exactly as-is.
Usually responds same business day