Integration Roadmap¶
Last Updated: 2026-02-16
Status: Phase 1 COMPLETE | Phase 2 PLANNED
Overview¶
This page documents the prioritized rollout plan for multi-EMR integration support, including effort estimates, business development requirements, and go-to-market strategy.
Planned Sections¶
Phase 1: OSCAR Family (COMPLETE)¶
- OSCAR McMaster
- Juno EMR
- OSCAR Pro
- MedAccess (OSCAR-based variants)
Market Coverage: ~25% of Canadian physicians
Effort: ~1211 lines of code (OscarSoapAdapter)
Business Model: Self-service onboarding (4-step wizard with EMR type selector, automated connection test + config pull)
Status: Production -- deployed and live with v4.0.1, full onboarding support operational
Onboarding Flow: Clinic selects "OSCAR EMR" -> enters SOAP/OAuth credentials -> tests connection -> auto-pulls schedule codes + appointment types -> validates integration with live data checks
Phase 2: Accuro EMR (PLANNED)¶
Target Launch: Q2 2026
Market Coverage: +17% (cumulative ~42%)
Effort Estimate: - Adapter implementation: ~600 lines - OAuth 2.0 integration: ~200 lines - Testing with sandbox: 2-3 weeks - Total: 6-8 weeks
Business Requirements: - Contact inquiry@AccuroEMR.com - Business agreement with QHR Technologies - 6-month sandbox access - Privacy and security review - Production agreement post-UAT
Technical Prerequisites: - OpenAPI/Swagger client generation - OAuth 2.0 client credentials flow - REST endpoint mapping (150+ endpoints) - Availability template conversion logic
Phase 3: Med Access EMR (FUTURE)¶
Target Launch: Q3-Q4 2026
Market Coverage: +5% (cumulative ~47%)
Effort Estimate: - Adapter implementation: ~700 lines - GraphQL client setup: ~300 lines - TELUS partnership approval: 3-6 months - Total: 4-6 months
Business Requirements: - TELUS partnership approval (walled garden) - Integration Request Form with TELUS - Cloud Connect middleware provisioning - FHIR R4 profile mapping - Compliance certification
Technical Prerequisites: - GraphQL client (Apollo/urql) - JWT RS512 signing - TELUS CHR Enterprise API access - Schema mapping (OSCAR <-> TELUS data model)
Note: Even Cortico (most established OSCAR booking platform) has not achieved official Med Access integration. This is the hardest target.
Phase 4: US Market Expansion (FUTURE)¶
Target Launch: 2027+
Market: Epic, Cerner, Athenahealth (US EHRs)
Protocol: FHIR R4 (SMART on FHIR)
Effort Estimate: - FhirR4Adapter: ~800 lines - SMART on FHIR OAuth flow: ~400 lines - FHIR Schedule/Slot/Appointment resource mapping - Multi-tenant FHIR server testing - Total: 6-12 months
Business Requirements: - Epic App Orchard approval - Cerner Code approval - HIPAA compliance certification - Business Associate Agreements - US-based data hosting
Priority Rationale¶
| EMR | Priority | Rationale |
|---|---|---|
| OSCAR Family | 1 (DONE) | Largest single target, self-service access, SOAP API proven in production |
| Accuro | 2 | Second largest market, documented API, clear business path |
| Med Access | 3 | Walled garden, TELUS approval required, even Cortico can't access it |
| US FHIR | 4 | Different market, different compliance regime, long sales cycles |
Current Status: Phase 1 is COMPLETE and in production with v4.0.1. The OSCAR Family adapter (OscarSoapAdapter) covers ~25% of Canadian physicians with full self-service onboarding. The EMR type selector in onboarding already supports Accuro, TELUS PS Suite, and "Other" as selectable types (saved for future integration). Phase 2 (Accuro) planning is underway.