Patient-authorized EHR integration
One API. Free, self-serve production access.
FinchNode has 17+ EHR and payer integrations. Production access is free and self-serve with a FinchNode account.
Free, self-serve production access.
With a FinchNode account, developers get free, self-serve production access to real, patient-authorized records.
Free ($0/month) includes one production application, a synthetic sandbox included with every account, hosted consent and patient controls, scheduled sync, and signed webhooks. Pro ($99/month) includes up to 5 production applications, email support, and everything in Free. Usage-based pricing is not in effect.
The public demo API serves twelve named synthetic scenarios from two synthetic sources, Northstar Health System and Quillhaven Medical Group, for free without an account. Create a FinchNode account for free, self-serve production access to real, patient-authorized records. The demo itself cannot access real patient data. Its /users/{subject}/records route returns normalized health records; the legacy /patients routes return category-grouped FHIR resources. Consent and sync metadata are explicitly simulated; real requests require a live key, current patient authorization, and available sources.
Free production access and the public synthetic demo
| What you get | Free production plan | Public demo API |
|---|
| Price | $0/month | $0 |
|---|
| Patient data | Real records with patient authorization and consent | Twelve named synthetic scenarios only |
|---|
| EHR access | Availability varies by organization and granted scopes | No live EHR connections |
|---|
| Applications and usage | 1 production application; no usage-based pricing; fair-use rate limits per API key | Rate-limited sample API |
|---|
| Getting started | Account and complete app settings; owner enables production | No account or API key |
|---|
Owners enable production when application settings are complete; FinchNode can suspend access. Live reads require production credentials and patient authorization and consent; availability varies by organization and scopes.
Create a free account · View plans and usage allowances
One API with free, self-serve production access
Free ($0/month) includes one production application, a synthetic sandbox included with every account, hosted consent and patient controls, scheduled sync, and signed webhooks. Pro ($99/month) includes up to 5 production applications, email support, and everything in Free. Usage-based pricing is not in effect.
Try the free EHR API sandbox without an account or key or explore 17+ EHR and payer 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, self-serve production access to real, patient-authorized records. Free ($0/month) includes one production application, a synthetic sandbox included with every account, hosted consent and patient controls, scheduled sync, and signed webhooks. Pro ($99/month) includes up to 5 production applications, email support, and everything in Free. Usage-based pricing is not in effect. Owners enable production when application settings are complete; FinchNode can suspend access. Live reads require production credentials and patient authorization and consent; availability varies by organization and scopes.
Is FinchNode only a synthetic demo or sandbox?
No. With a FinchNode account, developers get free, self-serve production access to real, patient-authorized records. The public demo API serves twelve named synthetic scenarios from two synthetic sources, Northstar Health System and Quillhaven Medical Group, for free without an account. Create a FinchNode account for free, self-serve production access to real, patient-authorized records. The demo itself cannot access real patient data. Its /users/{subject}/records route returns normalized health records; the legacy /patients routes return category-grouped FHIR resources. Consent and sync metadata are explicitly simulated; real requests require a live key, current patient authorization, and available sources.
Can one API really connect to multiple EHR vendors?
Yes. Your product integrates once and FinchNode handles the per-source connection details. Record availability depends on the organization a patient selects, the scopes it grants, and the patient authorization behind each connection.
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. A synthetic sandbox is included with every FinchNode account, 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.