Built for Canadian pharmacy

AutoRx exists because Canadian pharmacies running Kroll had no purpose-built automation. The tools that existed were either generic RPA scripts that broke on every Kroll update, OCR-only intake tools that still required manual entry, or US-based platforms with compliance postures built for HIPAA rather than PHIPA and PIPEDA.

We built AutoRx specifically for Kroll — reading your drug catalog and mix catalog before every write, matching DINs against your formulary and Health Canada's DPD, and routing exceptions to your team with the original document attached. The result is a 95%+ success rate, under 30 seconds per prescription, and an error rate below 0.1%.

Canada-first by design

All patient data is stored exclusively in Canadian data centres. We are PHIPA and PIPEDA compliant by design — not as an afterthought. Our AI is trained on Canadian prescription formats, Canadian drug naming conventions, and the specific patterns that show up in Telus Health Kroll workflows. We do not bolt on Canadian compliance; it is the starting point.

How onboarding actually works

Most pharmacies are live in 1–2 weeks. The work breaks into four concrete steps:

1. Kroll agent install and connection — a lightweight agent runs on the dispensing terminal and authenticates against your Kroll instance. No firewall changes, no patient data leaving your premises.
2. Fax intake channel setup — we work with your existing fax-to-cloud provider (eFax, Concord, Documo, or similar) to route inbound prescriptions to AutoRx. Your fax number stays the same; if you do not have a fax-to-cloud provider, we can recommend one.
3. Test batch in review mode — we run a real batch of your prescriptions through AutoRx with every write held for staff approval, so your team can sanity-check DIN selection, sig parsing, and prescriber routing before any automatic writes go through.
4. Staff walkthrough and first week of live operation — every team member who touches the dispensing workflow gets a walkthrough of the operator dashboard, exception queue, and escalation paths. Our team monitors alongside you for the first week and is on call for the second.

What we build

AutoRx is a multi-agent AI system, not a single OCR pipeline. Different agents handle different parts of the problem: one reads the inbound document and extracts patient and prescription fields, one matches the extracted drug data against your Kroll catalog and Health Canada's Drug Product Database, one writes the record into Kroll, and one watches for exception patterns and routes anomalies. Each agent reads context before acting — your formulary, your patient history, your prior dispensing patterns — so the system makes decisions a competent technician would make rather than mechanically transcribing whatever the fax says.

We work with independent pharmacies, banner chains, long-term care facilities, and compounding pharmacies. The integration pattern is the same in each segment; the operator-side workflow and reporting surfaces are tuned for the differences (per-site queue visibility, banner-wide rule sets, compound-mix mapping).

How we work with customers

We are a small, product-obsessed team. When you go live, your account does not get handed to a generic support queue — our engineering team stays involved through onboarding and beyond. Roadmap input from operating pharmacies is the primary driver of product priorities; if a customer tells us a workflow is slowing them down, that goes to the top of the queue.

AutoRx is a focused product, not a custom-development engagement. The Kroll integration, fax intake, DIN matching, dashboard, and webhooks are part of the platform from day one — there is no per-pharmacy script to maintain, no agency hourly billing for changes, and no scope creep priced as a separate contract.

Get in touch

Contact us for demos, partnerships, and press. Product updates appear on the blog; published security and privacy policy documents live in the Trust Center.