Production-grade access is free with an account. · Synthetic demo · no account needed
Patient-authorized EHR integration
Build with free production access to real, patient-authorized records, plus a separate accountless synthetic demo, working examples, and FHIR implementation guides.
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.
| 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.
Technical implementation guides with explicit evidence boundaries, runnable examples, and links to primary specifications.
Call the accountless synthetic demo API or open the fully synthetic FinchNode Visualizer.
Engineering field report · August 2026 · 14 min read
A transparent implementation report covering the patterns that repeated, the behaviors that did not, and the evidence boundary behind FinchNode’s current integration work.
Working implementation guide · 13 min read
A security-first walkthrough of discovery, authorization, callback validation, and token exchange for a standalone patient-facing application.
FHIR R4 tutorial · 11 min read
A practical TypeScript pattern for reading common patient resources without assuming that every FHIR server behaves identically.
Epic implementation guide · 10 min read
The production work around an Epic connection extends beyond the authorize URL: application registration, organization routing, exact callbacks, patient context, scopes, and source-specific validation all matter.
Oracle Health implementation guide · 10 min read
A developer guide to the parts of an Oracle Health connection that live outside the resource request itself.
Data architecture guide · 12 min read
Normalization should reduce application branching while retaining the evidence needed to explain, reconcile, and refresh every clinical fact.
FHIR operation guide · 9 min read
The operation can simplify record retrieval, but it does not promise every resource, identical server behavior, or a small response.
Reliability guide · 10 min read
A production integration needs a failure model that separates authentication, authorization, unsupported behavior, source outages, and incomplete synchronization.
Consent architecture guide · 9 min read
Source authorization answers whether data can be retrieved. Application consent answers whether a specific product may receive and use selected categories for a stated purpose.
TypeScript architecture guide · 11 min read
A timeline is not a giant sorted array. It is a source-aware projection over records with different clinical dates, update times, identities, and completeness.
Standards comparison · 10 min read
These standards overlap, but they solve different integration problems. The right choice begins with the workflow and access relationship—not whichever acronym is newest.