Support patients whose practices use eClinicalWorks and the healow patient experience through the same connection flow as other FinchNode sources.
Patient-authorized eClinicalWorks / healow record access
FinchNode sends the patient through the supported source authorization flow, tracks synchronization, and exposes only the record categories the patient approved for your application.
Best fit: Patient-facing products that need read-only records from participating eClinicalWorks practices.
How the connection works
- Your backend creates a FinchNode Connect session.
- The patient selects their organization and authorizes through healow.
- FinchNode syncs available records and records the patient’s sharing decision.
- Your backend reads approved data through the FinchNode API.
Production availability
Availability depends on application approval, participating endpoints, patient authorization, and the FHIR data exposed by the practice.
FinchNode’s current integration is patient-directed and read-only. Actual data depends on the source, organization, approved scopes, patient record, and consent.
View all EHR integrations or learn about the EHR integration API.
Frequently asked questions
Is there a free EHR API for real patient data in production?
Yes. With a FinchNode account, developers get free production-grade access to real, patient-authorized health records through one unified EHR API. The $0/month plan includes 100 connected patient-months, 100,000 production API calls per month, one production application, and an unlimited synthetic sandbox. Production access requires a FinchNode account, production credentials, a supported live source, and patient authorization and consent. Availability depends on the EHR, organization, application approvals, scopes, and records returned.
How does FinchNode connect to eClinicalWorks / healow?
Your application creates a FinchNode Connect session. The patient selects their organization, authorizes access on the healow experience, and approves the record categories your application may read. FinchNode then exposes supported, consent-filtered data through one API.
Do patients give FinchNode their eClinicalWorks / healow password?
No. The patient signs in on the source authorization page. Their hospital, payer, or EHR username and password do not pass through FinchNode or your application.
What data can my app read from eClinicalWorks / healow?
FinchNode can normalize supported demographics, medications, conditions, allergies, vital signs, laboratory results, immunizations, and source-specific coverage or claims data. Actual availability depends on the source, organization, granted scopes, and patient consent.
Is the eClinicalWorks / healow connection read-only?
Yes. FinchNode’s current patient-directed integration is read-only. It does not provide EHR write-back, scheduling, provider-side bulk access, or a general-purpose HL7 interface.