TELUS Kroll, inside and out

AutoRx is built exclusively for TELUS Health Kroll. Not a generic pharmacy automation platform retrofitted for Kroll, a system designed from the ground up around Kroll's data model, write path, and error semantics. This page explains how the integration works, what it can read and write, and the questions pharmacies ask before connecting.

Why should you integrate Kroll instead of retyping into it?

Most prescriptions still arrive at Canadian pharmacies as faxes, scans, and digital documents, and someone on your team retypes each one into Kroll: patient, prescriber, drug, DIN, sig, quantity, refills. At a few minutes per prescription across hundreds of prescriptions a week, intake typing quietly becomes one of the largest repetitive labour costs in the pharmacy, and every retype is a chance for a wrong DIN or a misread instruction.

A Kroll integration removes the retyping, not the pharmacist. AutoRx reads the inbound document with AI, resolves the drug against your catalog, writes the prescription into Kroll's intake queue, and leaves clinical verification exactly where it belongs, with your pharmacist, who now verifies instead of transcribing.

Why native integration beats RPA screen bots

RPA (robotic process automation) tools automate Kroll by controlling the UI, clicking fields, typing values, and reading screen text. This approach breaks whenever Kroll updates its interface, which happens regularly. Every update requires a developer to remap the script, and until that happens, your automation is down.

AutoRx uses a Kroll agent that communicates with Kroll directly, not through screen simulation. When Kroll's interface changes, our team updates the integration proactively, usually before your team notices any impact. You never remap screens or rewrite scripts yourself, and your automation keeps running through Kroll updates.

What can the integration read from Kroll?

Before AutoRx writes any prescription to Kroll, it reads the context a careful human would check:

• Patient profile, demographics and prescriber details, so the write lands on the right patient
• Drug history, relevant prior fills to inform DIN selection and catch therapy conflicts
• Drug catalog, your Kroll formulary, so the agent selects products you actually carry
• Mix catalog, for compounding pharmacies, ingredient and vehicle options for no-DIN fills

When a product is not in your local catalog, AutoRx falls back to the Health Canada Drug Product Database (DPD) to resolve the DIN. This read-before-write design is how the system achieves a DIN match rate above 95% on the first attempt, and why it flags a mismatch as an exception instead of writing a wrong entry for your pharmacist to catch later.

What can it write, and what happens when a write fails?

Writes are queued and executed asynchronously into Kroll's intake queue. Transient Kroll errors (network issues, locks, an update in progress) retry automatically with exponential backoff. Permanent failures, a patient not found, a DIN not in catalog, surface immediately in the dashboard with the original document and a clear failure reason, so your team can resolve them in seconds instead of hunting for what went missing.

Completion events (success or final failure) are delivered via webhook to your systems. See webhooks for the payload format and /developers for integration materials.

Which intake tasks does this automate?

• Fax intake: inbound faxes are parsed by AI and entered into Kroll automatically, with exceptions queued for a human
• Digital prescriptions: scans, PDFs, and digital Rx documents flow through the same pipeline as faxes, one queue, one audit trail
• Prescription data entry and DIN matching: drug, strength, form, and quantity resolved against your catalog before the write
• Pharmacy-specific rules: your substitution preferences, default sigs, and workflow conventions applied consistently on every entry

Can your team see everything it does?

Every prescription, source document, parse result, Kroll write status, and retry history is visible in the operator dashboard. Filter by site, date, source, or outcome. No black box: if the system wrote it, you can see why, and if it refused to write, you can see what stopped it.

Compliance and data handling

All patient data is stored in Canadian data centres. AutoRx is PHIPA and PIPEDA compliant by design: processing happens under the pharmacy's authority as health information custodian, audit logs are available for your team and for regulatory review, and subprocessors and security controls are documented at the Trust Center.

Frequently asked questions

Related: How it works · DIN matching · The fax automation guide · Security · Subprocessors

Ready to see it on your own workflow? Book a 30-minute demo inside a Kroll sandbox.