Patient-authorized EHR integration
One API for multiple EHRs. Free in production.
With a FinchNode account, patient-facing health apps get a free production tier. Integrate once to connect real, patient-authorized records across 17 supported EHR families with one hosted flow and normalized data model.
Free production-grade EHR API access.
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.
The public demo API serves fixed fictional records for free without an account. Create a FinchNode account for free production-grade access to real, patient-authorized records within the included plan allowances. The demo itself cannot access real patient data.
Free production access and the public synthetic demo
| What you get | Free production plan | Public demo API |
|---|
| Price | $0/month within included allowances | $0 |
|---|
| Patient data | Real records with patient authorization and consent | Fixed fictional patient records only |
|---|
| EHR access | Supported live sources; availability varies by organization | No live EHR connections |
|---|
| Included usage | 100 connected patient-months; 100,000 production API calls/month; 1 production app | Rate-limited sample API |
|---|
| Getting started | Account, production credentials, and source availability | No account or API key |
|---|
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.
Create a free account · View plans and usage allowances
One API for multiple EHRs with free production access
The $0/month plan includes 100 connected patient-months, 100,000 production API calls per month, one production application, and an unlimited synthetic sandbox.
Try the free EHR API sandbox without an account or key or explore 17 supported EHR integrations.
One patient-access integration contract
Instead of exposing vendor-specific authorization and FHIR behavior in your product, create one Connect session. The patient selects a provider, authorizes at the source, reviews available data, and chooses what to share.
Your backend can read supported demographics, medications, conditions, allergies, vital signs, laboratory results, immunizations, and source-specific coverage or claims. Access is filtered by active consent and fails closed after revocation or expiry.
What FinchNode handles
- Provider and hospital search
- SMART on FHIR authorization
- Hosted consent and receipts
- Normalized records
- Scheduled sync and signed webhooks
- Synthetic sandbox data
Popular EHR integrations
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.
Is FinchNode only a synthetic demo or sandbox?
No. With a FinchNode account, developers get free production-grade access to real, patient-authorized health records through one unified EHR API. The public demo API serves fixed fictional records for free without an account. Create a FinchNode account for free production-grade access to real, patient-authorized records within the included plan allowances. The demo itself cannot access real patient data.
Can one API really connect to multiple EHR vendors?
Yes, for FinchNode’s supported patient-access use case. FinchNode handles source-specific authorization and FHIR behavior, then exposes consent-filtered records through a consistent API. Data availability still depends on the source and patient authorization.
Do I need to build a separate OAuth flow for every EHR?
No. Your product creates one FinchNode Connect session. FinchNode’s hosted flow handles provider search, source authorization, connection state, and the patient consent experience for supported systems.
Is the FinchNode EHR API based on FHIR?
Yes. FinchNode connects to supported sources using SMART on FHIR and FHIR R4 where available, then presents stable, normalized resources through its developer API.
Can I test an EHR integration before going live?
Yes. FinchNode includes an unlimited synthetic sandbox so teams can build and test the Connect flow, API reads, consent lifecycle, and webhooks before enabling production connections.
Is this API for patient-facing or provider-facing apps?
FinchNode is for products whose users authorize access to their own records. Provider-facing workflows, bulk population access, write-back, HL7 feeds, and embedded clinical apps require different integration paths.