Roll out clinical services across the banner — without 250 IT projects.
Banner pharmacy is a coordination problem disguised as a technology problem. Each store has a different pharmacist, a different patient mix, sometimes a different dispensing system. MedMe Banner gives you one platform to roll out a clinical service from head office and have it landing in every store the same Tuesday — with banner-wide AI customisation that fits your service standards.
You're rolling out clinical services. The stores aren't.
Every banner ops director we talk to says the same thing: head office wants a clinical service, the stores have variable buy-in, and the dispensing-system patchwork makes a uniform rollout impossible. MedMe Banner is the layer that makes uniform rollout possible.
VP Pharmacy / Banner ops
Push a new minor-ailment protocol to every store from head office. Track which stores have adopted it. Coach the laggards. Without flying.
Director of clinical services
Banner-wide AI assistant customisation — your service standards, your formulary, your pharmacist scope-of-practice rules. Same experience in every store.
CFO / commercial
Per-store ROI dashboard. Volume-based pricing in the master agreement. The billable services already happening in your network — visible.
Push a service to 87 stores from one screen.
Your DCS designs a new shingles vaccine campaign. Today, that means an internal memo, a webinar, a flurry of emails, and a hope that 60% of stores actually run it. With MedMe Banner, the protocol templates, intake form, AI Concierge script, and reporting roll out to every store as a single deployment. You see who's running it on day 3, not month 3.
- Service templates published from head office, versioned
- Intake forms, AI Concierge scripts, AI Scribe templates per service
- Per-store, per-province customisation (different scope of practice)
- Adoption tracking — who's using the new protocol vs the old one
- Pull a service back if you find a clinical issue — instantly
- Audit trail of every change, who made it, when it deployed
Your district managers see what they need to coach.
Banner ops doesn't scale by adding more head-office people. It scales by making your district managers more effective. MedMe Banner gives them per-store visibility scoped to their region.
District manager scorecard
Per-store metrics scoped to the DM's region: encounters per shift, AI assistant utilisation, no-show salvage, pharmacist scope-of-practice activity.
Protocol-adherence tracking
If your DCS published a new asthma protocol, you see which stores are using it and which are still doing it the old way. No clipboard audits.
Provincial-billing tracker
Per-province, per-service-fee tracking — ON, BC, AB, MB, SK, NS, NB, PEI, NL, QC. Different fee schedules, different documentation requirements, all reconciled in one dashboard.
The AI assistants speak your banner's voice. Not ours.
Generic AI assistants are an embarrassment in banner pharmacy. Your shoppers know what your brand sounds like, your pharmacists are trained on your service standards, and your AI shouldn't be reading from a vendor's script. MedMe Banner lets your DCS author the AI's tone, content, and behavior across every store.
- Banner-specific Concierge greeting and intake script
- Banner formulary baked into Scribe + Admin Clerk recommendations
- Service-line specific protocols (your DCS authors, IT doesn't gate)
- Provincial scope-of-practice rules per region (no overlap mistakes)
- Brand voice tuning — "we say 'how may we help' not 'how can I help'"
- Banner-wide updates push to every store on a single deploy
Banner pricing built into the master agreement.
Your hundredth store should not cost the same as your fourth. We codify volume pricing in the contract — automatic at the tier transitions, no annual renegotiation. CAD throughout.
| Tier | Stores | Per store / mo (CAD) | What's included |
|---|---|---|---|
| Banner starter | 4 – 12 | $279 | All AI assistants, Kroll bridge, named CSM |
| Banner growth | 13 – 49 | $249 | + Banner-wide AI customisation, district dashboards |
| Banner scale | 50 – 124 | $219 | + Dedicated implementation, banner-formulary integration |
| Banner network | 125 – 250 | $199 | + Provincial regulatory liaison, on-site QBRs |
| National enterprise | 250+ | Custom | SSO, EMR integrations, ministry/payor reporting |
Pricing assumes 36-month banner agreement. All tiers include unlimited users, unlimited consultations, and unlimited Kroll bridge usage. PIPEDA + provincial privacy compliance included.
"I ran clinical services at a 142-store Quebec banner before joining MedMe. I know what your DCS is dealing with on a Wednesday afternoon. I'm your banner success lead, not a ticket queue."
A team that has stood up clinical services at scale in a Canadian banner.
Banner accounts get a dedicated cross-functional team — banner success lead, solutions architect, clinical SME, implementation engineer. Each one has stood up pharmacy clinical services at a Canadian banner before. They know the Phenelle order entry, the Kroll formulary edge cases, the OSCAR EMR integration patterns, and the provincial scope-of-practice differences.
- Monthly banner business reviews — quarterly on-site for 50+ stores
- Direct Slack / Teams channel between your team and ours
- Roadmap input — your asks influence our build queue
- Provincial regulatory liaison (we keep up with college changes so you don't have to)
Whole Health: 38 stores, 3.8× services per shift.
"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."
Banner ops questions, answered.
How long does a 38-store banner rollout take?
The Whole Health rollout was 8 weeks — but that's the fast end. A typical 30-50 store banner rollout is 10-14 weeks in waves. Wave 1: 3-5 pilot stores, weeks 1-3. Wave 2: 8-12 stores, weeks 4-7. Wave 3: remainder, weeks 8-12. We don't believe in single-Monday rollouts and we won't sell you one.
What if our stores run a mix of Kroll, Nexxsys, and Fillware?
Common scenario. Admin Clerk supports all three out of the box. The bridge config is per-store, set at implementation. We have banner customers running Kroll in 22 stores, Nexxsys in 8, and Fillware in 4 — all on one MedMe instance, with a single banner-wide AI configuration. Cosmofar bridge launches Q3 2026; if you have stores on Cosmofar, we'll quote the Cosmofar stores into your contract at no incremental cost once the bridge is live.
Can our DCS author content without filing an IT ticket?
Yes. The DCS authoring console is a no-code interface — protocols, intake forms, AI Concierge scripts, AI Scribe templates. Your DCS publishes; the change deploys to every store in your banner. IT is the safety net, not the gate. We do support a "stage-then-publish" workflow for banners that want a clinical-IT review step.
How do you handle provincial scope-of-practice differences?
The platform is province-aware. A pharmacist in BC has access to a slightly different minor-ailment list than a pharmacist in ON. Documentation requirements are different in MB than in NS. The AI assistants are configured per province. Your DCS designs the banner-wide service; the platform handles provincial variation automatically.
Are you PIPEDA + provincial privacy compliant across all our regions?
Yes. PIPEDA is the federal floor; we've also reviewed and aligned with PHIPA (ON), PHIA (MB), HIA (AB), HIA (NS), HEIA (NL), Bill 64 (QC), and the BC Personal Information Protection Act. Data residency is AWS Canada Central (Montréal) — no PHI ever leaves Canadian borders. Compliance documentation is available under MNDA. If your banner operates in QC and needs French-language assistant interface, that's supported.
What's the contract term for Banner?
Banner agreements are typically 36 months, with a 60-month option for additional volume discount. Both include written exit + data-export clauses. Volume pricing kicks in at the contract level, not per store added — so you don't get punished for waves.
Can stores opt out?
This is a banner-by-banner conversation. Some banners want every corporate-owned store on MedMe and franchise stores opt-in. Some want a phased approach. Some want platform-only at corporate plus AI assistant rollout to franchise. We support all of these — your master agreement defines per-store activation rules.
Run your banner's clinical services like a single network.
Talk to a banner solutions architect. First call spec's a wave plan for your store count and dispensing-system mix, plus a volume-pricing quote.