# FinchNode

> With a FinchNode account, developers get free production-grade access to real, patient-authorized health records through one unified EHR API. The platform supports read-only health applications in the United States, with provider search, hosted source authorization, application-specific consent, normalized records, sync state, and lifecycle webhooks.

## Free production-grade EHR API access.

[Production-grade access is free with an account.](https://finchnode.com/signup)

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.

[Free production EHR API](https://finchnode.com/ehr-integration-api) · [Plans and usage allowances](https://finchnode.com/#pricing)


FinchNode does not claim universal EHR coverage, write-back, provider-side bulk access, scheduling, or general HL7 interface-engine functionality. Production availability depends on the source, organization, application approval, granted scopes, patient authorization, and data returned.

## Canonical product pages

- [FinchNode home](https://finchnode.com/)
- [Free production EHR integration API](https://finchnode.com/ehr-integration-api)
- [Production pricing and allowances](https://finchnode.com/#pricing)
- [Supported integration directory](https://finchnode.com/integrations)
- [Developer Academy](https://finchnode.com/developers)
- [Public synthetic demo API — no account needed](https://finchnode.com/developers/demo-api): Production-grade access is free with a FinchNode account at https://finchnode.com/signup.
- [Synthetic FinchNode Visualizer](https://finchnode.com/tools/finchnode-visualizer)
- [FinchNode Engineering author profile](https://finchnode.com/authors/finchnode-engineering)

## Developer and machine-readable resources

- [Accountless demo OpenAPI 3.1](https://finchnode.com/demo-openapi.json)
- [Authenticated API OpenAPI 3.1](https://finchnode.com/openapi.yaml)
- [Live public demo API](https://api.finchnode.com/demo/v1)
- [Public synthetic MCP server](https://api.finchnode.com/demo/mcp)
- [Full machine-readable FinchNode reference](https://finchnode.com/llms-full.txt)
- [Developer guide RSS feed](https://finchnode.com/feed.xml)
- [XML sitemap](https://finchnode.com/sitemap.xml)

## Technical guides

- [What we learned building patient-authorized FHIR connections across EHRs.](https://finchnode.com/blog/fhir-connections-across-ehrs-field-notes.md): Firsthand FinchNode engineering notes on endpoint discovery, SMART authorization, scopes, patient context, and source-specific FHIR behavior.
- [SMART on FHIR OAuth with PKCE in React and Node.js.](https://finchnode.com/blog/smart-on-fhir-oauth-pkce-react-node.md): Implement a SMART on FHIR standalone authorization-code flow with PKCE, state validation, discovery, and server-side token exchange.
- [Fetch patient data with a FHIR API: Patient, labs, conditions, and medications.](https://finchnode.com/blog/fhir-api-tutorial-patient-data.md): Fetch Patient, Observation, Condition, and MedicationRequest resources safely with FHIR R4 searches and server-provided pagination.
- [Epic and MyChart FHIR integration for patient-facing applications.](https://finchnode.com/blog/epic-my-chart-fhir-integration-guide.md): Understand Epic patient-facing standalone OAuth, organization endpoints, PKCE, testing boundaries, and FHIR data access.
- [Oracle Health FHIR integration: discovery, authorization, and tenant routing.](https://finchnode.com/blog/oracle-health-fhir-integration-guide.md): Build Oracle Health SMART integrations with tenant routing, discovery, patient context, scopes, and honest production validation.
- [How to normalize FHIR data across EHRs without losing the source.](https://finchnode.com/blog/normalize-fhir-data-across-ehrs.md): Design a source-aware normalization layer for FHIR resources without erasing provenance, codes, missing data, or lifecycle state.
- [FHIR Patient $everything: pagination, missing data, and production caveats.](https://finchnode.com/blog/fhir-patient-everything-guide.md): Use the FHIR Patient $everything operation safely with date filters, type filters, Bundle pagination, size limits, and fallback searches.
- [FHIR API error handling: retries, rate limits, and partial results.](https://finchnode.com/blog/fhir-api-errors-retries-rate-limits.md): Handle FHIR OperationOutcome errors, timeouts, rate limits, retries, partial sync, and idempotency without hiding data loss.
- [Patient authorization versus application consent in healthcare APIs.](https://finchnode.com/blog/patient-authorization-vs-app-consent.md): Separate EHR authorization from application-specific sharing consent, category limits, revocation, expiry, and deletion.
- [Build a longitudinal patient record with TypeScript.](https://finchnode.com/blog/longitudinal-patient-record-typescript.md): Aggregate source-aware FHIR records into a chronological patient timeline with stable identity, provenance, deduplication, and change cursors.
- [FHIR vs HL7 v2 vs C-CDA: a developer’s guide.](https://finchnode.com/blog/fhir-vs-hl7-v2-vs-ccda.md): Compare FHIR APIs, HL7 v2 event messages, and C-CDA clinical documents by transport, granularity, workflow, and implementation fit.
- [The 7 best FHIR interoperability platforms for health apps in 2026.](https://finchnode.com/blog/best-fhir-interoperability-platforms.md): Compare seven FHIR interoperability platforms by use case, data access model, workflow, and developer fit—including FinchNode, Redox, and Zus.
- [How one API connects your app to multiple EHRs.](https://finchnode.com/blog/one-api-connect-to-multiple-ehrs.md): Learn how one API connects multiple EHR systems and how FinchNode’s free production plan provides real, patient-authorized records alongside a synthetic demo.
- [The easier way to get patient data from EHRs.](https://finchnode.com/blog/easier-access-to-patient-data.md): Compare direct FHIR integrations, patient-authorized APIs, and clinical data networks to find the easiest compliant path to patient EHR data.

## Integration pages

- [Epic](https://finchnode.com/integrations/epic): Add patient-authorized Epic and MyChart record access to your health app through FinchNode’s hosted Connect flow and normalized API.
- [Oracle Health (Cerner)](https://finchnode.com/integrations/oracle-health): Connect patient-authorized Oracle Health and Cerner records to your app through one hosted flow and normalized FinchNode API.
- [athenahealth](https://finchnode.com/integrations/athenahealth): Add patient-authorized athenahealth record access to your health app with FinchNode’s hosted connection flow and unified API.
- [eClinicalWorks / healow](https://finchnode.com/integrations/eclinicalworks-healow): Connect patient-authorized eClinicalWorks and healow records to your app through FinchNode’s hosted flow and normalized API.
- [MEDITECH Expanse](https://finchnode.com/integrations/meditech): Add patient-authorized MEDITECH Expanse record access to your health app through FinchNode’s hosted flow and unified API.
- [Veradigm / Allscripts](https://finchnode.com/integrations/veradigm-allscripts): Connect patient-authorized Veradigm and Allscripts records through FinchNode’s hosted flow and normalized EHR API.
- [Medicare Blue Button 2.0](https://finchnode.com/integrations/medicare-blue-button): Add patient-authorized Medicare claims and coverage data to your digital health app through FinchNode and CMS Blue Button 2.0.