EHR Connections
Pre-configured integration adapters for major EHR systems. Each connection supports OAuth 2.0 authentication flows, FHIR resource operations, and embedded launch workflows.
TL;DR / Key Takeaways
- •Pre-configured adapters for Epic, Oracle Health (Cerner), Athena, Allscripts, Meditech, NextGen, eClinicalWorks, and more.
- •Each connection supports OAuth 2.0, SMART on FHIR launch, and backend (B2B) authentication workflows.
- •Built-in FHIR resource operations, patient search, and clinical data retrieval — no custom integration code needed.
- •Add a new EHR connection in minutes via the ConnectHealth console.
AdvancedMD
AdvancedMD (Global Payments)
Read-only OAuth 2.0 + FHIR R4 (USCDI v3) integration adapter for AdvancedMD. Supports patient/provider standalone, EHR (embedded) launch, and SMART Backend Services Bulk export. FHIR access is read-only per Cures Act §170.315(g)(10) — write-back requires AdvancedMD's separate Partner API.
Allscripts (Veradigm)
Veradigm (formerly Allscripts Healthcare Solutions)
Complete OAuth 2.0 and FHIR R4 integration adapter for Allscripts/Veradigm EHR systems. Supports patient-facing, system-to-system, and embedded EHR launch workflows with full FHIR resource operations.
Athena
athenahealth
Complete OAuth 2.0 and FHIR R4 integration adapter for athenahealth EHR systems. Supports patient-facing, system-to-system (Basic Auth or JWT), and embedded EHR launch workflows with full FHIR resource CRUD operations.
Cerner
Oracle Health (Cerner)
Complete OAuth 2.0 and FHIR R4/STU3 integration adapter for Oracle Health (Cerner) EHR systems. Supports patient-facing, system-to-system, and embedded EHR launch workflows with full FHIR resource operations and bulk data export.
CharmHealth
MedicalMine, Inc.
Practice management EHR. ConnectHealth supports two independent CharmHealth flows: a proprietary OAuth 2.0 implicit-grant member SSO login (verified working end-to-end against a real CharmHealth account), and the standard SMART on FHIR authorization_code/client_credentials flow (generic plumbing wired the same way as every other EHR here; CharmHealth-specific endpoint/field details have not been confirmed yet).
eClinicalWorks
eClinicalWorks
Complete OAuth 2.0 and FHIR R4 integration adapter for eClinicalWorks EHR systems. Supports patient-facing, system-to-system, and embedded EHR launch workflows with mandatory PKCE, FHIR CRUD operations, batch/transaction bundles, and bulk data export.
Elation Health
Elation Health
OAuth 2.0 and FHIR R4 integration adapter for Elation Health EHR. Supports patient-facing (standalone) and system-to-system (backend) workflows using client credentials.
Epic
Epic Systems Corporation
Complete OAuth 2.0 and FHIR R4/STU3 integration adapter for Epic EHR systems. Supports patient-facing, system-to-system, and embedded EHR launch workflows with full FHIR resource operations and bulk data export.
Healthie
Healthie Inc.
API key + GraphQL backend-to-backend integration adapter for Healthie EHR. Supports server-to-server data access for patients, appointments, and webhook events. No OAuth required — uses a static API key with Basic Auth.
MEDITECH
MEDITECH
Complete OAuth 2.0 and FHIR R4/STU3 integration adapter for MEDITECH EHR systems (Expanse). Supports patient-facing, system-to-system, and embedded EHR launch workflows with full FHIR resource operations and bulk data export.
Open Dental
Open Dental Software, Inc.
REST API adapter for Open Dental practice management software. No OAuth, no FHIR — uses two static keys (Developer Key + Customer Key) via a custom Authorization header. BYOK (bring-your-own-key): ConnectHealth does not issue or hold these keys — each clinic obtains its own Developer Key and Customer Key directly from Open Dental (vendor.relations@opendental.com) and supplies both when creating the connection.
TouchWorks
Altera Digital Health
Complete OAuth 2.0 and FHIR R4 integration adapter for TouchWorks EHR (Altera Digital Health). Supports patient-facing, system-to-system (Basic Auth or JWT assertion), and embedded EHR launch workflows with full FHIR resource CRUD operations.