NEW: Admin Clerk Β· the AI assistant that books the consult while you fill the script β€” See it work β†’
Home / Platform / Kroll bridge
For Kroll-based pharmacies

The Kroll–MedMe bridge — built by pharmacy, for pharmacy.

Kroll is the dispensing system 60% of Canadian pharmacies depend on. It also has no clinical API, no ETA on one, and no appetite for letting third parties write into it. So we stopped waiting and built a bridge that doesn’t need permission. Live in 14 days.

The problem

Kroll has no clinical API. The integration ticket you filed in 2022 is still “under review.”

You picked Kroll for dispensing because it works. But every clinical-services pitch ends the same way: “just integrate with Kroll, and we’ll write notes back automatically.” Then the vendor learns Kroll has no published clinical write API, no roadmap commitment, and no real path forward without Kroll engineering buy-in.

Pharmacies end up running two parallel records. The pharmacist double-types every consult into Kroll and the clinical app. Compliance becomes a manual reconciliation job. Adoption stalls.

We don’t need Kroll’s permission. The Admin Clerk is the workaround that removes the bottleneck.

18 months

Median time pharmacies have been waiting on a Kroll clinical API.


14 days

Median time MedMe’s Kroll bridge takes from contract signed to first store live.

How the bridge works

It runs as a tech, not as an integration.

Admin Clerk is a signed background service installed on each dispensary workstation. It reads the same accessibility tree your screen reader does, and sends the relevant fields to MedMe’s clinical record — only after pharmacist approval.

1

Reads via accessibility APIs

Same interface your screen reader uses. Label-aware, not pixel-aware. Resilient to Kroll UI changes.

2

Writes through approved actions

Performs the same keystrokes a pharmacy tech would. No DLL injection. No undocumented API calls.

3

Pharmacist always in the loop

Diff shown before any write. Approved, edited, or rejected. Audit trail tied to college license.

What syncs both ways

The full clinical context, on both sides of the bridge.

Field Kroll → MedMe MedMe → Kroll Latency
Patient demographicsβœ“β€”< 2 sec on lookup
Allergies & adverse reactionsβœ“βœ“< 2 sec on lookup; on write, real-time
Active & historical Rxβœ“β€”< 3 sec, full history
Insurance & eligibility flagsβœ“β€”< 2 sec
Consult notes (minor ailments, OAT, HC)β€”βœ“Real-time on RPh approve
Vaccination recordsβ€”βœ“Real-time on RPh approve
Pharmacist interventions / billingβ€”βœ“Real-time on RPh approve
Follow-up reminders / tasksβ€”βœ“Real-time on RPh approve
Inbound e-prescriptions (PrescribeIT)βœ“β€”Polled every 30 sec
Prescriber detailsβœ“β€”< 2 sec
14-day promise

From contract signed to documenting consults — in two weeks.

This isn’t a sales line. We track median time-to-first-write across all Kroll deployments and publish it on our status page.

Days 1–3

IT review & install

Signed installer ships to your IT. Runs on a single workstation for review. No Kroll vendor involvement needed.

Days 4–7

Field mapping call

60-minute screen-share with your lead pharmacist. We map the three workflows you do most: minor ailments, vax, hormonal contraception.

Days 8–11

Pilot with one RPh

Your lead pharmacist runs five real consults. Bridge reads, writes, and surfaces diffs. Tweak the few edge cases.

Days 12–14

Whole-store live

Roll to all dispensary workstations. Pharmacist team trained. Banner-store rollout from there is < 1 day per store.

Customer Β· Whole Health Pharmacy Partners

“We were quoted 18 months on a Kroll integration that, frankly, no one I talked to thought would actually ship. MedMe got 22 stores live in 14 days using the Admin Clerk bridge. The day-one push of allergy data from Kroll into the clinical record alone justified the contract.”

DJ
Dr. Devarsh Joshi, R.Ph. VP Clinical Operations Β· Whole Health Pharmacy Partners Β· 22 stores Β· ON
14d
Contract to 22 stores live
100%
Allergy + Rx history pulled day one
3.4Γ—
Increase in monthly billable consults
Compared

The three real options for a Kroll pharmacy that wants to scale clinical services.

Rip & replace Kroll Run two systems in parallel MedMe Kroll bridge
Time to value 9–18 months Immediate — but with double-entry 14 days
Disruption to dispensing Severe — full retraining, fill-rate drop None — but pharmacist double-types None — pharmacist works in Kroll as before
Capex / migration cost $80k–$250k+ per banner Hidden cost: pharmacist time on duplicate entry Included in MedMe subscription
Allergy & Rx history availability in clinical workflow βœ“ β€” manual lookup βœ“ automatic
Auto-write notes to Rx system βœ“ β€” βœ“
Vendor cooperation required Yes — Kroll migration team No, but you accept double-entry None
Risk of Kroll UI changes n/a n/a Low — we ship updates < 48h after Kroll release notes

Stop double-typing. Bridge Kroll in 14 days.

30-minute demo, on a Kroll instance that looks like yours. We’ll show real reads, real writes, real diffs.