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.

Why native integration beats RPA

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.

AutoRx uses a Kroll agent that communicates with Kroll directly, not through screen simulation. When Kroll's interface changes, our system adapts automatically. Your automation keeps running.

Read layer: context before every write

Before AutoRx writes any prescription to Kroll, it reads:

• Patient profile — demographics and prescriber details from the queue
• 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 is how we achieve a DIN match rate above 95% on the first attempt.

Write layer: async queue with retries

Writes are queued and executed asynchronously. Transient Kroll errors (network issues, locks) retry 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.

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

Dashboard visibility

Every prescription — source, parse result, Kroll write status, retry history — is visible in the operator dashboard. Filter by site, date, source, or outcome. No black box.

Compliance and data handling

All patient data is stored in Canadian data centres. AutoRx is PHIPA and PIPEDA compliant by design. Audit logs are available for your team and for regulatory review. Subprocessors and security controls are documented at the Trust Center.

Related: How it works · DIN matching · Security · Subprocessors