Canadian EMR integration
TELUS Med Access Integration: API and Web Automation for Canadian Primary Care and Community Health
MedReception AI connects to TELUS Med Access through a hybrid integration architecture that combines the vendor REST API for supported endpoints with deterministic browser automation for legacy workflows. The result is a unified read and write layer that captures provincial billing fields, books real appointments, and respects Canadian data residency across Ontario, Alberta, British Columbia, and beyond.
Practices addressable
7,000+
Canadian clinics on Med Access nationwide
Data residency
Canada
All PHI processing inside Canadian regions
Compliance
PIPEDA + HIA
Federal plus provincial PHIPA, HIA, PIPA, LPRPDE
Provincial billing
12 schemas
OHIP, MSP, AHCIP, MSI, RAMQ and others
Product overview
What TELUS Med Access Is and Why the Integration Matters
TELUS Med Access is one of the most widely deployed cloud EMRs in Canada, serving primary care groups, community health centres, walk in clinics, and specialty practices. It is certified across multiple provinces and is a frequent choice for Family Health Teams in Ontario, Primary Care Networks in Alberta, and Community Health Centres across British Columbia. Because Med Access spans so many provincial billing rules and clinical workflows, a single nationwide automation layer needs to be aware of both the federal product and the provincial overlay.
Care settings supported
- Family Health Teams and solo family practices
- Community Health Centres and Indigenous primary care
- Walk in clinics and urgent care nodes
- Specialty groups including paediatrics, internal medicine, mental health
- Public health and population health programs
Provincial footprint
- Ontario, the largest installed base, OHIP billing
- Alberta, AHCIP billing and Netcare linkages
- British Columbia, MSP billing and Teleplan
- Manitoba, Saskatchewan, New Brunswick, Nova Scotia
- Quebec deployments with RAMQ and bilingual EN and FR fields
Integration architecture
Hybrid Vendor API and Browser Automation
The Med Access vendor API covers a meaningful slice of read endpoints and some write paths, but not every workflow your front desk uses is exposed programmatically. MedReception AI runs a probe first design that prefers the REST API where it exists and falls back to a sandboxed Playwright browser session for the rest. Both paths run inside Canadian AWS regions and use scoped credentials per tenant.
Vendor REST API path
- Patient demographics read and limited update
- Appointment slot availability lookup
- Encounter and visit reason metadata
- Provider and resource directory
- Webhook subscriptions where Med Access exposes them
Browser automation path
- Headed Playwright sessions for visual verification
- Same screens a Med Access user clicks, no DOM scraping shortcuts
- Per tenant session keeper with provincial timezone awareness
- Single attempt login with alert on failure, no brute retry
- Centralized alert manager surfaces broken sessions within minutes
Data residency
- All compute and storage in Canadian AWS regions
- PHI never leaves Canada in normal operation
- Cross border access strictly excluded by IAM boundary
- Audit logs retained per provincial retention rules
- Encryption at rest with tenant scoped keys
Reliability surface
- Sentinel alarms on every Lambda touching Med Access
- Daily synthetic booking against a test patient
- Drift detection on vendor schema changes
- Per province on call rotation for incidents
- Slack channel routing for critical versus review tier alerts
Provincial billing capture
One Integration, Twelve Provincial Billing Schemas
Med Access stores billing identifiers in province specific shapes. The MedReception AI integration normalizes these into a single internal patient record while preserving the original provincial format on write back. The receptionist agent asks for the correct identifier based on the clinic province and validates checksum or format where the province defines one.
Ontario, OHIP
- 10 digit OHIP number with 2 character version code
- Expiry date capture and renewal prompts
- Family Health Team rostering status read
- Service code suggestions on appointment reason
British Columbia, MSP
- 10 digit Personal Health Number
- Teleplan ready service code mapping
- Walk in versus attached patient flag
- BC Services Card alignment fields
Alberta, AHCIP
- 9 digit Personal Health Number
- Primary Care Network attribution capture
- Netcare cross reference fields preserved
- Out of province billing flag handling
Quebec, RAMQ and other provinces
- RAMQ 12 character alphanumeric for Quebec
- MSI for Nova Scotia, NB Medicare, MB Health
- SK Health Services number, NL MCP, PEI Health
- Territory health cards for Yukon, NWT, Nunavut
Read and write contract
What MedReception AI Reads and Writes in Med Access
The integration is intentionally scoped. The receptionist agent does not author chart notes, prescribe, or change clinical orders. It reads what it needs to identify the patient and find the right slot, and it writes only the operational artifacts a human receptionist would produce.
What we READ from Med Access
- Provincial billing identifier and expiry
- Patient demographics, preferred name, language
- Appointment slot availability per provider and resource
- Visit reason library and service code metadata
- Referral status and outstanding form requirements
- Roster, attribution, and walk in eligibility flags
What we WRITE to Med Access
- Confirmed appointment bookings with reason and duration
- Demographics updates, phone, address, language preference
- Intake form contributions captured before the visit
- Recall list contributions for callbacks and follow up
- Cancellation and reschedule events with audit trail
- Message threads visible to the clinic team for review
Canadian privacy compliance
PIPEDA Plus Provincial Health Privacy Acts
Canadian privacy law layers federal PIPEDA on top of provincial health privacy statutes. The Med Access integration is designed to satisfy both at once, with tenant level controls so each clinic can prove compliance to its own College and Information and Privacy Commissioner.
Federal layer
- PIPEDA, Personal Information Protection and Electronic Documents Act
- Consent capture before any PHI is processed by the agent
- Breach notification workflow ready for OPC reporting
- Data minimization, the agent only collects what is needed
Provincial layer
- Ontario, PHIPA, Personal Health Information Protection Act
- Alberta, HIA, Health Information Act
- British Columbia, PIPA and the E Health Act framework
- Quebec, LPRPSP and Bill 25 amendments
- Atlantic provinces, PHIA in Nova Scotia, NB PHIPAA, NL PHIA
Operational controls
- Per tenant data processing agreement
- Role based access scoped to clinic staff
- Immutable audit log of every read and write
- Right of access and correction workflow for patients
Hosting and transit
- Canadian AWS regions for all PHI compute
- TLS 1.2 or higher for every transit hop
- KMS managed keys with annual rotation
- No model training on tenant PHI, ever
Bilingual handling
EN and FR Field Handling for Quebec and Bilingual Clinics
For Quebec deployments and bilingual clinics in Ontario, New Brunswick, and Manitoba, the agent supports French as a first class language on the call and on the chart. Field labels, visit reasons, and confirmation messages all switch on the patient preferred language flag stored in Med Access.
Conversation language
- Detects EN or FR from caller speech in the first turn
- Honours preferred language stored in Med Access demographics
- Quebec deployments default to French with EN fallback
- Bilingual SMS confirmations in patient preferred language
Field and code handling
- French visit reason library mapped to EN service codes
- Accent and ligature preserved on write back, no normalization
- Quebec address format with postal code spacing respected
- Bilingual recall list messaging templates per clinic
Rollout sequence
From Discovery to Live Booking in Three Phases
Discovery and provincial scope
Confirm provinces, billing identifiers, language mix, and the subset of Med Access workflows in scope for automation.
API probe and automation harness
Validate which endpoints the vendor API exposes for this tenant, then build the browser automation fallback for everything else.
Live cutover with sentinel
Route inbound calls to the agent, watch the sentinel dashboard, and keep a human review queue for the first two weeks.
Product fit
Built for Canadian Primary Care
From a two provider Family Health Team in Ottawa to a multi site Community Health Centre in Vancouver, the same integration covers the workflow with provincial billing fields baked in.
AI receptionist for Med AccessTalk to a Canadian clinic specialist
See the Med Access Integration Live
Book a demo and we will show a real call landing as a real Med Access appointment in your province, with provincial billing fields populated.
Book a demoRelated Med Access resources
Keep Exploring the Med Access Footprint
Med Access EMR hub
Top level overview of every Med Access asset on this site.
TELUS Med Access receptionist
Front desk automation tailored to TELUS branded Med Access tenants.
Community Health Centres
How CHCs use Med Access plus the agent for high volume intake.
AI receptionist for Canada
National overview of the Canadian product, compliance, and rollout.
All EMR integrations
Index of every supported EMR and the integration pattern we use.
Pricing
Plans for Canadian clinics including provincial billing add ons.