Patient-authorized EHR integration
One EHR API. Free production access.
With a FinchNode account, developers get free, self-serve production access to real, patient-authorized records. Connect a patient's records with hosted authorization, consent, normalized records, and sync.
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
Connect patient-authorized records through one EHR API
FinchNode gives digital health teams one hosted flow for provider search, hospital authorization, purpose-bound consent, record sync, and a normalized server-side API.
The current platform is designed for read-only patient access in the United States. It has 17 EHR and payer integrations. Record availability depends on the organization a patient selects, the scopes it grants, and the patient authorization behind each connection.
Explore the unified EHR integration API or browse the integrations.
Free production access at $0/month
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.
Call the free synthetic EHR API without an account or key, or create an account to start the free plan.
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.
What is an EHR integration API?
An EHR integration API gives an application a consistent way to request health data from electronic health record systems. FinchNode focuses on patient-authorized, read-only access and normalizes supported FHIR data behind one API.
Which EHRs and hospital systems can FinchNode connect to?
FinchNode has 17 EHR and payer integrations. Record availability depends on the organization a patient selects, the scopes it grants, and the patient authorization behind each connection.
How do patients connect their hospital records?
Your application creates a Connect session and sends the patient to a hosted flow. The patient finds their provider, signs in on the provider or EHR authorization page, approves access, and separately consents to share the requested data with your application.
Does FinchNode receive a patient’s hospital password?
No. Patients enter their credentials on the hospital, payer, or EHR authorization page. Hospital usernames and passwords do not pass through FinchNode.
What health record data is available through the API?
The API supports demographics, medications, conditions, allergies, vital signs, laboratory results, immunizations, and source-specific coverage and claims data, subject to patient consent and source availability.
Does FinchNode support every kind of hospital integration?
No. FinchNode is designed for patient-directed, read-only record access in the United States. It is not a replacement for provider-facing HL7 feeds, EHR write-back, scheduling, or every enterprise interface workflow.