NEW: Admin Clerk · the AI assistant that books the consult while you fill the script — See it work →
Home/ Customers/ Whole Health
Banner · 38 stores Ontario + Manitoba Minor ailments Kroll bridge

Whole Health pharmacists are doing 3.8× more clinical services per shift — banner-wide.

A 38-store Canadian banner across Ontario and Manitoba ran on Kroll for everything. Their pharmacists were spending half their day in Kroll order-entry instead of doing clinical work. The Admin Clerk fixed it. Eight weeks after deployment, the banner was running 3.8× more services per shift — and pharmacists stopped complaining.

SK
Sandra Kaur, RPh Director of Clinical Services, Whole Health
3.8×
more services per shift
8 weeks
to banner-wide rollout
47 min
saved per pharmacist per day
0
Kroll tickets to Telus
The context

38 stores. 92 pharmacists. One dispensing system that wouldn't budge.

Whole Health is a 38-store Canadian pharmacy banner with locations across southern Ontario (29 stores) and Manitoba (9 stores). Founded in 2008 as a 3-store group in the Greater Toronto Area, the banner grew through a combination of organic openings and acquisitions of small independents who wanted access to a stronger purchasing co-op and shared marketing. By 2025, Whole Health employed 92 pharmacists, 138 technicians, and roughly 200 front-store staff across the network.

Like most Canadian banners of this size, Whole Health ran on Kroll. Every store. Every prescription. Every patient record. Kroll had been the right choice when the banner was 3 stores — and it was still the right choice for the dispensing workflow at 38. But Kroll was never built to be a clinical-services platform, and it was never built to integrate with anything outside Telus's own ecosystem.

The problem started in earnest when Ontario expanded the pharmacist scope of practice for minor ailments in early 2023, and Manitoba followed in 2024. Suddenly, every Whole Health store had a list of 14 conditions they could legally treat, document, prescribe for, and bill the province for. The opportunity was real. The execution was painful.

"Our pharmacists were highly trained, the protocols were ready, the patients were walking in. The bottleneck was that documenting a minor-ailment encounter took 17 minutes — five for the consult, twelve for the data-entry shuffle into Kroll afterward. The math didn't work."

Sandra Kaur, the Director of Clinical Services who joined Whole Health in 2022 from a Quebec banner, had been pushing for a clinical-services platform for over a year. The problem wasn't the platform options — there were several. The problem was that none of them integrated with Kroll.

The challenge

Kroll won't integrate. Pharmacists became data-entry clerks.

The shape of the problem was simple, and Sandra had been documenting it for months. A typical minor-ailment consultation at Whole Health in 2024 looked like this:

  • Patient walks in, asks the tech about a UTI symptom.
  • Tech books a 15-minute consult with the pharmacist on a paper sign-up sheet (no online booking integrated with Kroll).
  • Pharmacist conducts the consult, takes paper notes (Kroll doesn't have a clinical-services note format).
  • Pharmacist writes a prescription manually, signs it, scans it.
  • Tech enters the prescription into Kroll for fill (separate workflow from the consult).
  • Pharmacist later — usually end of shift — types the consult notes into a free-text field in Kroll, files the paper notes, attaches the scan, prepares the provincial billing form on a separate screen, double-checks the billing code, submits.

Sandra timed the workflow across 22 stores during a regional review in late 2024. Average end-to-end time per minor-ailment encounter: 17 minutes. Of those, only about 5 minutes were the actual clinical consult. The remaining 12 were the documentation shuffle.

At 17 minutes per encounter, a Whole Health pharmacist could realistically do 3-4 minor-ailment consults per shift in the available windows between dispensing peaks. The province was paying $19 per encounter. Even at full utilisation, this was a marginal-revenue activity that was actively painful to execute. Most stores ran 1-2 per day, and many ran zero.

Multiple vendors had pitched Whole Health on a "clinical platform" over 2024. Every pitch hit the same wall in the demo: "How do you integrate with Kroll?" and the answer was always some variation of "we're working with Telus" or "you'd export from Kroll daily" or "a tech enters the data twice." None of which solved the actual problem.

MedMe's pitch was different in one specific way. The MedMe team brought a working demo of AI Admin Clerk reading and writing Kroll in real time, with full audit trail, in a sandbox environment Whole Health had set up. The demo wasn't a slide. It was a real Kroll instance with Admin Clerk pulling patient demographics into a MedMe consult, the pharmacist documenting, and Admin Clerk pushing the prescription back into Kroll for fill — all without a tech doing data entry. End-to-end time: 6 minutes. That demo was the buying decision.

What they did with MedMe + Admin Clerk

Banner-wide rollout in 8 weeks. Three waves. No store left behind.

Whole Health signed in early 2025 and went live across all 38 stores in 8 weeks. Sandra ran the rollout as three waves with deliberate pause points between waves to incorporate learning.

Weeks 1–2: Banner setup + DCS authoring

The first two weeks were spent without any store actually live. Sandra and her team used MedMe's authoring console to set up the Whole Health banner-wide configuration: which 14 minor-ailment conditions to enable per province (Ontario's list differs from Manitoba's), the banner-specific intake forms, the AI Concierge greeting in Whole Health's brand voice, the AI Scribe note templates aligned to OCP's documentation requirements, and the provincial billing-form auto-population logic.

Weeks 3–4: Wave 1 — 4 pilot stores

Four pilot stores went live in week 3 — two in Ontario (a downtown Toronto store and a small-town Bracebridge store), two in Manitoba (Winnipeg main and a rural Brandon store). MedMe's implementation engineer was on-site at each store for the first 3 days. Pharmacists ran their first AI-assisted minor-ailment encounters with shadow-mode Admin Clerk (auditing but not yet writing to Kroll). On day 4, Admin Clerk went live to Kroll. By end of week 4, all 4 pilot stores had completed at least 25 encounters each, with end-to-end documentation time averaging 6.5 minutes.

Weeks 5–6: Wave 2 — 14 stores

The Wave 2 rollout was 14 stores added across both provinces. Each store had a 2-day onsite from a regional implementation engineer (MedMe sent 4 engineers to handle the parallel rollout). Pharmacist training was condensed to two 30-minute live sessions per store, with MedMe Academy backstopping any gaps. Average end-to-end documentation time across Wave 2: 6.1 minutes.

Weeks 7–8: Wave 3 — remaining 20 stores

The final wave brought 20 more stores live in 2 weeks. By this point, the Whole Health internal team had become its own implementation engine — Sandra had identified 6 internal champions across the network (3 per province) who handled most pharmacist questions in real time. MedMe's role narrowed to integration troubleshooting and the Kroll bridge configuration.

By week 8, all 38 stores were live. Average end-to-end documentation time banner-wide: 6.0 minutes. Encounters per pharmacist per shift went from a banner-wide average of 1.4 (under the old workflow) to 5.3 (post-rollout) — a 3.8× lift. The math finally worked.

The unexpected finding: the Admin Clerk → Kroll bridge generated zero support tickets to Telus across the entire 38-store network in the first 6 months. Telus had reviewed the architecture during pre-sales and confirmed it didn't violate Kroll terms of service. Whole Health's IT team had braced for a wave of integration issues that never came.

The results — first six months

Four numbers that mattered to Sandra and to the Whole Health board.

3.8×
more billable services per shift
1.4 → 5.3 encounters per pharmacist per shift
8 weeks
banner-wide rollout
All 38 stores live, 3 waves
47 min
saved per pharmacist per day
Banner-wide average
0
Kroll tickets to Telus
First 6 months post go-live
In Sandra's words

The full quote.

"We were running on Kroll across all 38 stores, and our pharmacists were spending half their day in Kroll order-entry instead of doing clinical work. The Admin Clerk fixed that. Eight weeks after we deployed across the banner, our pharmacists were doing 3.8× more billable services per shift — and they stopped complaining about the data-entry. That alone made the rollout worth it. The number I tell my CFO when she asks is that we saved roughly 47 minutes per pharmacist per day banner-wide. With 92 pharmacists, that's 72 hours of clinical capacity per day that we got back. We didn't hire anyone to do this. We just stopped wasting their time."

— Sandra Kaur, RPh, Director of Clinical Services, Whole Health

Lessons from the Whole Health rollout

Five things Sandra tells other Canadian banner directors.

1. The Kroll integration question is the buying decision. Insist on a working demo.

Whole Health had been pitched on multiple "clinical platforms" before MedMe. Every pitch handled the Kroll question with a slide. MedMe handled it with a working demo in our own Kroll sandbox. If a vendor can't show you a real read-and-write Kroll integration in your sandbox environment during pre-sales, the integration doesn't exist. Don't sign.

2. Spend two weeks on banner setup before any store goes live.

The most useful thing Whole Health did was use weeks 1-2 of the engagement entirely on banner-wide configuration — without a single store live. Intake forms, AI Concierge scripts, AI Scribe templates, banner brand voice, provincial billing logic. By the time Wave 1 went live in week 3, the platform already felt like Whole Health's, not MedMe's. The pharmacists in the pilot stores didn't have to imagine anything.

3. Run waves with deliberate pause points.

Whole Health didn't run all 38 stores at once and didn't run them sequentially over months. The wave structure — 4 / 14 / 20 stores with built-in pause points — let the team incorporate learning between waves. Wave 2 was meaningfully better than Wave 1 because the team had two weeks to refine. Wave 3 didn't need an MedMe engineer on-site at most stores because Whole Health's internal champions had developed.

4. Identify internal champions at the regional level. Not store-level.

Sandra picked 6 internal champions across the banner — 3 in Ontario, 3 in Manitoba — and trained them deeply during Wave 1. By Wave 3, those 6 people were handling roughly 80% of pharmacist questions in real time. MedMe support handled the integration edge cases. This split kept the rollout fast without overwhelming MedMe and without leaving pharmacists waiting.

5. Don't underestimate how much pharmacist morale matters.

The number Sandra didn't put in the case study, but tells other DCS leaders, is the morale shift. In the 6 months pre-MedMe, Whole Health had lost 7 pharmacists to other banners — exit interviews routinely cited "I trained for clinical, I'm doing data entry." In the 6 months post-MedMe, they lost zero pharmacists to other pharmacy banners. The retention story alone justified the platform — separately from the productivity numbers.

Get your pharmacists out of Kroll order-entry — and back into clinical.

30-minute demo, no slides. We'll demo the Admin Clerk → Kroll bridge in your sandbox, document a real minor-ailment encounter, and show you the time savings live.