Solutions
Context is the point
Not guessing from a single line of fax text. The agent reads your formulary and the patient's history before picking a DIN.
- No setup fee
- Live in 1–2 weeks
- PHIPA compliant
- Canadian data residency
Why DIN matching fails without context
OCR-only tools extract text from a prescription and attempt to match it to a DIN by string similarity. This approach breaks in common situations: brand vs. generic disambiguation, multi-strength products where the fax is ambiguous, drugs listed differently in your catalog than on the prescription, and recently approved generics not in a static database. The result is wrong DIN selections — and a potential patient safety risk.
What AutoRx reads before selecting a DIN
Patient profile
Demographics and prescriber from the Kroll queue — who the patient is before any drug decision.
Drug history
Relevant prior fills to inform strength selection and catch therapy conflicts.
Your Kroll drug catalog
Primary lookup — reflects what you actually stock and your preferred manufacturer settings.
Health Canada DPD
Fallback when a drug is not in your catalog; queried in real time, not from a static snapshot.
Mix catalog
For compounding pharmacies, ingredient and vehicle options for no-DIN scenarios.
The lookup order
Your Kroll drug catalog
Match against your local formulary — selects a DIN you actually carry.
Health Canada DPD fallback
If no catalog match, fall back to the federal drug product database in real time.
Exception queue
If no confident match anywhere, route to review with the closest candidates displayed for your team to confirm.
Compounding and no-DIN scenarios
Pairing DIN matching with custom rules
Get started with AutoRx
Ready to automate?
Most pharmacies go live within 1–2 weeks. No waitlist, no setup fee, and your existing Kroll setup stays exactly as-is.
Usually responds same business day
