What eClinicalWorks' Certified FHIR APIs Actually Cover
eClinicalWorks documents its FHIR APIs across two distinct portals, and understanding which one applies to your specific use case matters before scoping any integration work.
Two Separate Developer Portals for Different Audiences
Provider-facing FHIR documentation lives on eClinicalWorks' own developer portal, while patient-facing access runs through the Healow platform, and each has its own specific credentialing and documentation you'll need to navigate separately.
FHIR Coverage Stops at the USCDI-Aligned Subset
The free, certified FHIR API surface is limited to the USCDI-aligned data set required for certification, meaning financial data, full scheduling, and many operational endpoints simply aren't available through the standard FHIR pathway.
SMART on FHIR OAuth Across Both Portals
Both the provider-facing and patient-facing FHIR surfaces use OAuth 2.0 with SMART on FHIR authorization, giving a consistent authentication pattern even though the underlying data access and audience differ between the two portals.
Open Sandboxes With Synthetic Data for Testing
eClinicalWorks provides open sandbox environments using synthetic data for both portals, letting you build and test integration logic before needing actual practice enablement or real patient data access.
How We Navigate Per-Practice Enablement Requirements
Even a fully certified FHIR application still needs each specific practice to enable API access before real data actually flows, and planning around that requirement matters for realistic project timelines.
Confirming Certification Requirements Upfront
We confirm exactly what certification your specific application needs before development begins, since building against the wrong certification tier can mean rework later when a practice's enablement process reveals a mismatch.
Coordinating Practice-Level Enablement Directly
Per-practice enablement requires direct coordination with each specific eClinicalWorks customer, and we help manage that process so technical readiness and administrative enablement happen on a realistic, coordinated timeline together.
Building and Testing Against the Open Sandbox First
We build and validate integration logic against eClinicalWorks' open synthetic-data sandbox before any real practice enablement, catching issues in a safe testing environment rather than during limited production access windows.
Documenting the Enablement Process for Future Practices
For integrations meant to scale across multiple eClinicalWorks practices, we document the enablement process clearly, so replicating the connection for additional practices doesn't require reinventing the coordination process each time.
Where Negotiated Interfaces Become Necessary
For data and workflows outside the certified USCDI subset, eClinicalWorks requires a separately negotiated commercial interface rather than free API access, and planning for this distinction avoids scoping surprises later in a project.
Financial and Revenue Cycle Data Sits Outside FHIR
Charges, claims, remittances, and other financial or revenue cycle data fall outside the free, certified FHIR surface entirely, requiring a negotiated interface with associated fees rather than a standard API integration approach.
Full Scheduling Needs a Negotiated Path Too
Beyond basic patient-facing scheduling through Healow, full practice management scheduling functionality typically requires the same negotiated commercial interface path as financial data, rather than being available through certified FHIR.
Custom Extracts and HL7 v2 Remain Commercial Arrangements
Proprietary, non-FHIR integrations including custom data extracts and HL7 v2 interfaces are negotiated commercially per integration, so budget both time and cost for this path if your project needs data outside the certified subset.
We Scope Realistically Around What's Actually Free vs Negotiated
Rather than assuming FHIR alone covers your project, we clarify upfront which specific data your integration needs falls into the free certified tier versus the negotiated commercial tier, avoiding budget surprises partway through.
Scoping an eClinicalWorks integration project?
Start with a free Mirth Health Check to review your requirements, send us the exact error if you're troubleshooting an existing integration, or check pricing for our support plans.