Let patients find their Epic organization, authorize with MyChart, and share approved record categories with your application.
Patient-authorized Epic record access
Epic patient-facing applications use OAuth 2.0 and SMART on FHIR so patients can authorize access without giving their credentials to your product. FinchNode packages that connection into the same hosted flow and API your team uses for other supported sources.
Best fit: Digital health products that need read-only, patient-authorized Epic records without owning a separate MyChart connection experience.
How the connection works
- Your backend creates a FinchNode Connect session.
- The patient selects their organization and authorizes through MyChart.
- FinchNode syncs available records and records the patient’s sharing decision.
- Your backend reads approved data through the FinchNode API.
Production availability
Live availability depends on FinchNode’s approved Epic production application, the selected organization’s endpoint, and the scopes and data that organization makes available.
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 Epic?
Your application creates a FinchNode Connect session. The patient selects their organization, authorizes access on the MyChart 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 Epic 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 Epic?
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 Epic 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.