The system that wouldn’t integrate, finally does.
AI Admin Clerk reads from and writes to your Rx system the same way a tech does — through the screen. No vendor integration request. No 18-month roadmap. Goes live in 14 days, on Kroll, Nexxsys, Fillware, and PharmaClik HQ.
Kroll → Admin Clerk → MedMe. One pharmacist. One workflow.
Admin Clerk runs locally on your dispensary workstation, watches what’s on screen, and ferries the right fields back to the MedMe clinical record. The pharmacist never alt-tabs.
Kroll
Rx system of record
AI Admin Clerk
On-device · RPA + LLM
MedMe
Clinical record + billing
Bidirectional. Reads patient profiles, allergies, and Rx history out of Kroll — writes consult notes, vaccination records, and follow-up reminders back. All on the pharmacy workstation. None of it leaves Canada.
Built like a tech — only it never gets tired, and it never types the wrong DIN.
READS From your Rx system
- Patient demographics — name, DOB, address, phone, language, gender, health card / PHN
- Allergies and adverse reactions — structured + free-text, including pharmacist-entered notes
- Active and historical Rx — DIN, strength, sig, prescriber, fill history, last-pick-up date
- Insurance & eligibility — primary, secondary, OBEC/PharmaNet/Netcare flags
- Prescriber details — name, CPSO/CPSBC/CPSA license, address, fax, NPI/CPSID
- Outstanding refills, dose changes, and adherence flags
WRITES Back into your Rx system
- Consult notes — provincial-format minor ailments, hormonal contraception, OAT, smoking cessation
- Vaccination records — lot, dose, site, administered-by, fully formatted for provincial portal sync
- Follow-up reminders — scheduled task entries that fire in your existing Rx workflow
- Pharmacist interventions — documented for billing and college-audit defence
- Adherence interventions — auto-paste structured progress notes back into the patient profile
- Travel-health and minor-ailment Rx — queued in Kroll for verification & dispense
Live across the four Rx systems Canadian pharmacies actually run.
If you’re on something we don’t list, we’ll scope it — most additions take 2–4 weeks because Admin Clerk doesn’t need vendor cooperation to start mapping fields.
The pharmacy’s computer does the work. Patient data never leaves the building unless you say so.
Admin Clerk is on-device. The clerk reads the screen via accessibility APIs, parses fields with a small local model, and sends only the structured clinical record — not the raw screen — to MedMe’s Canadian-region cloud.
- Runs as a signed background service on the dispensary workstation
- Reads via accessibility tree, not screen-scraping pixels — resilient to UI changes
- Field-level audit log: every read, every write, every retry
- Patient identifiers tokenized before any cloud call
- Zero outbound network calls during read; outbound only on confirmed write
- Pharmacist always sees the diff and can approve / reject any write
“We’d gotten quotes from three vendors saying a Kroll integration was ‘impossible without Kroll engineering buy-in.’ MedMe shipped a working bridge across all 22 of our stores in 14 days. We’re documenting 60-plus minor-ailments consults a week per store now — with notes that auto-write back into Kroll.”
The questions every pharmacy owner asks first.
Does Admin Clerk need permission from Kroll, Nexxsys, or our Rx vendor?
No. Admin Clerk runs as a local accessibility tool on the workstation you already use. It reads the same on-screen fields a tech does and writes through the same UI. There’s nothing for your Rx vendor to approve, and they don’t need to see our code.
Is this technically RPA, screen-scraping, or AI? What’s actually doing the work?
It’s a hybrid. The pickup of structured fields uses platform accessibility APIs (the same ones screen readers use) so it’s resilient and well-defined. A local language model handles the unstructured stuff — allergies in free text, prescriber notes, sig parsing. Decisions about what to write are policy-driven and require pharmacist approval before any change is committed back to your Rx system.
What happens to patient data? Does it leave Canada?
No PHI leaves Canadian regions. The clerk runs on your workstation. When it sends data to MedMe’s cloud, it goes to AWS Canada (Central) or Azure Canada Central. Identifiers are tokenized at the edge. We’re PIPEDA, PHIPA (Ontario), FIPPA (BC), and PHIA (NS, MB) compliant, with SOC 2 Type II.
Will it slow down our dispensary computer?
The clerk uses approximately 180–240 MB of RAM and idles below 2% CPU between active reads. It only spins up when a clinical service is in flight. Banner customers running it on 8-year-old workstations have not reported lag.
What if Kroll updates their UI?
We track Kroll release notes and ship clerk updates within 48 hours of any breaking UI change — usually before customers notice. Because we read the accessibility tree (label-based, not pixel-based), most cosmetic Kroll updates don’t touch our integration at all.
Can the pharmacist override what the clerk writes?
Always. Every write surfaces a diff. Pharmacist taps approve, edits, or rejects. Nothing posts back to Kroll without an explicit RPh action — with full audit trail tied to their college license number.
How long does deployment actually take?
Median 14 days from contract signed to first store live. We send a signed installer, your IT runs it, we map the first three workflows together on a 60-minute call, and you’re documenting consults the same afternoon.
Stop waiting on a Kroll integration that isn’t coming. Bridge it in 14 days.
Book a 30-minute demo — we’ll show Admin Clerk reading and writing live on a Kroll instance that looks like yours.