How Kroll Data Entry Actually Works in a Canadian Pharmacy

TL;DR. Kroll data entry is the process of turning an inbound prescription (usually a fax) into a structured record in TELUS Health Kroll: patient, prescriber, drug and DIN, sig, quantity, refills, and billing. Done by hand it takes minutes per prescription and is the most repetitive job behind the counter. This post walks through the actual steps, the places errors sneak in, and what the workflow looks like when software does the typing and people do the judging.

Ask anyone who has worked a pharmacy intake bench: the job is not hard, it is relentless. Prescriptions arrive all day, most of them by fax even in 2026, and every single one must be entered into Kroll before anything else can happen: no entry, no fill, no billing, no patient served.

This post explains what that entry work actually involves, because the people who buy pharmacy software are not always the people who do the typing, and the gap between those two views is where bad purchasing decisions happen.

The manual workflow, step by step

A typical faxed prescription goes through these steps at the Kroll intake screen:

1. Find the fax. Physically or in FaxRx, locate the next document, decide whether it is a new Rx, a renewal, a transfer, or clinic noise.
2. Identify the patient. Search Kroll by name and birthdate. Decide which “J. Smith” is the right one, or create a new profile from the fax header.
3. Identify the prescriber. Match the doctor and clinic, check the license reference if anything looks off.
4. Read the drug. Decipher the handwriting or the clinic’s EMR font. Determine drug, strength, form.
5. Pick the DIN. Search the catalog, choose the product the pharmacy actually stocks, watch for the strength trap (metformin 500 vs 850 is one keystroke apart).
6. Type the sig. Translate the prescriber’s shorthand into the patient-facing instruction.
7. Enter quantity, refills, and billing. Days supply, insurance plan, and everything adjudication needs.
8. Queue it for the pharmacist, who clinically verifies the entry against the source fax.

An experienced assistant does this in two to five minutes per prescription. On a 300-Rx day with two-thirds arriving as documents to be keyed, intake typing alone consumes multiple staff-hours, every day, forever.

Where the errors actually come from

Kroll data entry errors are not random typos. They cluster in predictable places:

• Wrong patient, when profiles are near-duplicates and the fax header is vague.
• Wrong DIN or strength, the classic pick-list slip, especially on lookalike names and multiple available strengths.
• Sig drift, where shorthand becomes an instruction that does not quite say what the prescriber meant.
• Missed renewals versus new Rx, entering a fresh prescription when the fax was authorizing refills on an existing one.
• Fatigue effects: error rates are not flat across a shift, and the busiest hours produce both the most entries and the most mistakes.

Every one of these lands on the pharmacist’s verification queue as a catch-it-or-miss-it moment. Verification exists precisely because entry is fallible, but verification is also the pharmacist’s most interrupted task.

What changes when software does the typing

AI prescription intake flips the workflow: the fax goes to the software first, and Kroll receives a structured, already-checked entry.

The important design detail is what a good system does BEFORE writing to Kroll. It reads the patient profile and drug history to land on the right person, resolves the drug against the pharmacy’s own catalog (falling back to Health Canada’s DPD when needed) instead of guessing from OCR text, applies the pharmacy’s own defaults and rules, and writes into Kroll’s intake queue only when the entry is coherent. Anything ambiguous, bad handwriting, an unusual compound, a missing quantity, goes to an exception queue for a human, with the source document attached.

The pharmacist still verifies every prescription. What changes is the ratio: instead of staff typing 200 documents so a pharmacist can catch the five that were entered wrong, staff resolve a handful of flagged exceptions and the pharmacist verifies entries that were checked against the catalog at creation time.

For the intake bench, the job shifts from typing to triage. For the pharmacy, the hours come back. For a detailed walk through the technology side, see how AutoRx works and the Kroll integration page; for the buying side, the fax automation evaluation guide covers vendor questions and compliance.

The questions worth asking about any “Kroll data entry” solution

• Does it write into Kroll natively, or is it an RPA bot driving the screens?
• What is the first-attempt DIN accuracy on YOUR fax mix, and what happens to the rest?
• Where does patient data live, and is the answer Canadian data centres with PHIPA and PIPEDA posture in writing?
• Can your team see every entry it made, beside the source document?

If a vendor answers all four without flinching, you are most of the way to a good decision.