Pillar Guide · 2026

Kroll automation, explained

Kroll automation moves prescription intake from manual keyboard work into an AI pipeline that reads Kroll context and writes back natively. This guide covers what Kroll automation is, how the AutoRx pipeline runs, why native integration beats RPA, what a typical rollout looks like, and what it costs.

What is Kroll automation?

Kroll automation is software that handles prescription intake, parsing, and entry into TELUS Health Kroll without manual keyboard work. It typically combines AI-driven fax / OCR parsing, DIN matching against your local formulary and the Health Canada DPD, and an async write path that delivers each prescription into Kroll plus a webhook to the pharmacy's downstream systems.

AutoRx is the Canadian Kroll-native version: it reads Kroll first (patient, history, formulary, mix catalog), picks the right DIN, writes back asynchronously, and routes anything low-confidence to your team through the operator dashboard.

How the AutoRx Kroll pipeline runs

Every prescription — fax or digital — follows the same five-step path. Full step-by-step detail in how AutoRx works.

1. 1. Intake

   Fax + digital prescriptions arrive in the AutoRx queue from your existing fax-to-cloud provider or EMR partners.

2. 2. Parse + normalise

   Vision + comprehension agents extract patient, drug, sig, prescriber, and quantity fields — handwriting and multi-drug faxes included.

3. 3. Read Kroll context

   Before any write, AutoRx pulls the patient profile, recent drug history, your local Kroll drug catalog, and mix catalog (compounding).

4. 4. AI decisions

   Grounded in real Kroll context, the agent picks the DIN, strength, sig mapping, and mitte. DPD fallback runs when a product is not local.

5. 5. Write + webhook

   Async write with exponential-backoff retries. Final success / failure events post to your configured webhook endpoint.

Native integration vs RPA bots

Two technical approaches dominate the Canadian Kroll automation market: native integration and RPA (robotic process automation, also called screen-scraping). The technology choice has direct operational consequences once Kroll updates roll out.

Native Kroll integration vs RPA bots walks through the technical difference in depth. The short version: RPA writes to Kroll by simulating a user (clicking fields, typing text on the rendered UI). Every Kroll release can change a button, a field name, or a modal — and every such change breaks the RPA script until a developer re-maps it.

AutoRx uses a Kroll agent that communicates with Kroll directly through its data layer, not screen simulation. When Kroll's interface changes, the agent adapts in most cases without intervention. When deeper attention is needed, the AutoRx team resolves it proactively — usually before any pharmacy notices an impact.

What a Kroll automation rollout looks like

Most single-pharmacy AutoRx Starter rollouts land in 1–2 weeks. The critical readiness items are formulary cleanup in Kroll, fax-line routing, and a brief staff walkthrough of the operator dashboard for exception review. The readiness checklist covers everything before go-live.

Compliance posture is established upfront: PHIPA and PIPEDA-aligned by design, Canadian data residency, and a full DPA before any prescription moves. Full controls live in the Trust Center.

Banner and multi-site rollouts scope per-site and per-banner rules — details under Banner & chain. Compounding pharmacies use the AutoRx mix catalog integration — see Compounding pharmacy.

Pricing

AutoRx Starter is $1,000 CAD/month per Kroll pharmacy and covers up to 2,500 prescriptions per month. Enterprise pricing applies for multi-terminal or banner rollouts. Full plans and a cost comparison against RPA bots and additional staff are on the pricing page.

Kroll automation FAQ