Pharmacy at population-health scale.
When you're operating thousands of stores, working with a provincial ministry on a clinical-services contract, or running a payvider partnership where pharmacy is the access point — you need infrastructure, not a SaaS app. MedMe Enterprise is the platform that signs your CIO's questionnaire, integrates with the EMRs your ministry partners use, and reports outcomes in the format your contract demands.
Identity, integration, audit, outcomes — in one platform.
MedMe Enterprise CA serves the operating chiefs, CIOs, and chief pharmacy officers who own pharmacy as part of a larger health-system or ministry-program portfolio. Your questions are about identity, EMR integration, ministry reporting, and outcomes attribution — and we have answers.
CIO / VP Health IT
SAML 2.0 + OIDC SSO mapped to your AD. RBAC tied to your AD groups. Audit logs streamed to your SIEM. PIPEDA-compliant data residency in AWS Canada Central.
Chief pharmacy officer
National service standards rolled out across the network, outcomes data tied back to ministry contracts, pharmacist scope-of-practice activity by region.
Ministry program lead
Clinical-services data shared with provincial ministries on the schedule and format your contract requires. Outcomes attribution suitable for value-based contracting.
SSO, RBAC, audit logs — done the way enterprise IT actually does them.
Enterprise pharmacy IT in Canada is run by people who came from health systems and provincial ministries. They expect the controls of a hospital deployment, not the openness of a small-business SaaS. MedMe Enterprise CA delivers the controls.
- SAML 2.0 + OIDC SSO (Okta, Microsoft Entra, Ping, Auth0)
- SCIM 2.0 user + group provisioning, automatic deprovisioning
- RBAC mapped to your AD groups — pharmacist, tech, manager, district, regional, CIO
- Audit logs streamed to your SIEM (Splunk, Microsoft Sentinel, Datadog) — JSON or CEF
- Configurable session policies — IP allowlist, MFA enforcement, session timeout
- Break-glass workflow with after-the-fact attestation, reportable to your privacy officer
Epic, Cerner, OSCAR — wired into the EMRs your physicians actually use.
Canadian enterprise pharmacy doesn't operate in a silo. Your patients see physicians whose notes live in Epic at one health system, OSCAR in another, Cerner in a hospital. MedMe Enterprise CA integrates outward — pulling clinical context to your pharmacist and writing back when the patient gives consent.
Epic — Showroom + App Orchard
FHIR R4 read of patient demographics, conditions, medications, allergies, encounters. Write-back of pharmacist consultation notes via DocumentReference. Live in Ontario Health, Alberta Health Services, BC Cancer integrations.
Cerner / Oracle Health
HL7 v2 ADT + ORM + ORU feeds. FHIR R4 where Millennium supports it. Live with two Canadian regional health authorities; we'll share the architecture under MNDA.
OSCAR
OSCAR EMR integration via OSCAR Pro REST API + HL7 v2 fallback. Read of patient demographics, problem list, current meds. Write of pharmacist note as observation + document. Common in Ontario family-physician networks.
Provincial digital health
OLIS (Ontario Lab Information System) read access for pharmacist clinical decisions. eHealth Ontario integration for medication history. SK eHealth, AB Netcare, BC PharmaNet integration on the roadmap and live in pilot.
Dispensing — Kroll, Nexxsys, Fillware
The Admin Clerk bridge at enterprise scale — supervised RPA workers per store, centrally managed, audited, with redundancy and roll-back. Cosmofar Q3 2026.
Data warehouse export
Snowflake / Redshift / BigQuery / Synapse sync of de-identified or fully identified clinical event log on a schedule you set. FHIR R4 schema, SCD2 history, lineage included.
Pharmacy outcomes in the format your provincial contract demands.
Your ministry contract specifies how clinical-services data must be reported back. MedMe Enterprise CA generates that report from the clinical encounter — without a separate reporting team, without spreadsheets, without an annual audit panic.
- Provincial fee-for-service billing exports — ON, BC, AB, MB, SK, NS, NB, PEI, NL
- OHIP, BC PharmaCare, AB Health Services, MB Pharmacare, SK Drug Plan formats
- HEDIS-equivalent Canadian quality measure reporting
- Aggregate de-identified outcomes data for ministry value-based contracts
- Pharmacist-led visit attestation for ministry-program reporting
- Configurable per-ministry data-sharing agreement (PIA + DPA)
A team that has stood up enterprise pharmacy in Canada — and signed off with provincial colleges.
Enterprise rollouts in Canada are 9-18 months. Your engagement gets a named program manager, a dedicated solutions architect, clinical SMEs, and a regulatory liaison who has worked with provincial colleges before.
PIPEDA and provincial privacy law — pre-completed.
MedMe maintains an active SOC 2 Type II report and HITRUST CSF r2 certification. We hold completed PIAs (Privacy Impact Assessments) for ON, BC, AB, MB, SK, and we follow PHIPA, PHIA, HIA, HIA(NS), and Bill 64 (QC) where applicable. Your enterprise privacy officer will recognise the documentation.
| Commitment | Standard | Enterprise SLA | Enterprise+ SLA |
|---|---|---|---|
| Uptime | 99.9% | 99.95% | 99.99% |
| Sev-1 response | 1 hr | 30 min | 15 min |
| Sev-1 resolution | 4 hrs | 2 hrs | 1 hr |
| RTO (disaster recovery) | 8 hrs | 4 hrs | 1 hr |
| RPO (data loss tolerance) | 1 hr | 15 min | 5 min |
| Data residency (Canada) | ✓ AWS ca-central-1 | ✓ ca-central + dr | ✓ Single-tenant ca |
| SOC 2 Type II | ✓ | ✓ | ✓ |
| HITRUST CSF r2 | — | ✓ | ✓ |
| Provincial PIA on file | ✓ | ✓ | ✓ |
| Customer-managed encryption keys | — | — | ✓ |
| Dedicated security review | — | Annual | Quarterly |
Enterprise IT + clinical questions, answered.
Where is data stored? Does any PHI cross the Canadian border?
All PHI is stored in AWS ca-central-1 (Montréal), encrypted at rest with AES-256 and in transit with TLS 1.3. No PHI ever leaves Canadian borders. Our LLM providers run in Canadian-residency-eligible enclaves under zero-retention agreements. Customer-managed encryption keys are available on Enterprise+. We have signed PIAs (Privacy Impact Assessments) with the provincial privacy commissioners in ON, BC, AB; we can share documentation under MNDA.
Have provincial colleges reviewed your AI assistant approach?
Yes — OCP (Ontario), BCCP (BC), ACP (Alberta), MPhA (Manitoba), and SCPP (Saskatchewan) have all reviewed the architecture and documentation under MNDA. We have implementation playbooks aligned to each college's documentation requirements. Our regulatory liaison is the contact for any college-specific question your team has.
How does Admin Clerk handle Kroll at enterprise scale?
At enterprise scale, the Admin Clerk bridge runs as supervised RPA workers per store, centrally managed from MedMe's Canadian infrastructure. Each worker has audit logs, monitoring, and roll-back. Telus has reviewed and confirmed the approach is not a Kroll terms-of-service violation — we have written confirmation. We support thousands of concurrent bridge workers without performance degradation; the reference architecture is documented in our enterprise security pack.
Do you support a single-tenant or VPC deployment in Canada?
Enterprise+ supports single-tenant deployment in a customer-dedicated VPC in AWS ca-central-1 with customer-managed KMS keys, customer-controlled audit destination, and our shared application layer. Multi-tenant SaaS is the default. Single-tenant is available where contractual or ministry requirements demand it.
Do your AI models train on our data?
No. Our AI Scribe, Concierge, and Admin Clerk use third-party LLM providers under zero-retention BAA-equivalent terms. No customer data is used to train any model — ours, or our providers'. Models are deployed in Canadian-residency-eligible enclaves with logging that you can audit.
Can ministry data-sharing be configured per program?
Yes. Each ministry program (OHIP MedsCheck, BC PharmaCare clinical, AB minor ailments, etc.) has its own data-sharing configuration — schema, schedule, identification level, transport. These are configured during implementation and audited in the dashboard. Adding a new program is a configuration change, not a code change.
How long does enterprise implementation take in Canada?
9 to 18 months end-to-end for a national chain with custom EMR integration. Faster for a wave-based rollout where Wave 1 is a 50-100 store pilot. Your dedicated program manager will spec a wave plan in the first month based on your store count, dispensing-system mix, EMR integration scope, and ministry-program portfolio.
Pharmacy as care infrastructure for Canada.
Talk to our enterprise team. First call is a 60-minute working session with our CISO and your CISO designate, plus our solutions architect and your network strategy lead.