FinchNode docs

How it fits together

Your server creates a Connect session. You send the patient to its link. They pick their health system, sign in there, and choose what to share with your app. FinchNode imports the records, and your server reads them.

your server ──POST /connect/sessions──▶ FinchNode ──link──▶ patient
                                                           │
                                          signs in at their health system
                                          approves sharing with your app
                                                           │
your server ◀──GET /users/{subject}/records── FinchNode ◀──┘
            ◀──webhook: consent.granted, sync.completed──

Each patient appears to your app as a subject: an ID that is stable for your app and different in every other app. Every read checks the patient's consent first, so a revoked share stops your reads.

Where to start

You want to	Start here
See real API responses without an account	Demo API
Get a synthetic patient's records with a sandbox key	Quickstart
Put Connect in front of your users	How Connect works
Give an AI agent access to records	MCP server
Look up an endpoint	API reference
Try TEFCA Individual Access	TEFCA Individual Access

What you get

• One API across the health systems FinchNode connects. Records arrive as FinchNode's normalized JSON, derived from FHIR R4 and keeping each source's codes.
• A hosted consent flow, so you never handle a patient's portal password.
• 10 record categories, from medications and labs to claims.
• Webhooks when consent changes or new records arrive.
• A sandbox of named synthetic scenarios, including failure cases, to test against.

What FinchNode doesn't do

• It reads records. It never writes back to a health system.
• It does not pull records in bulk for a provider or a population. Every connection starts with one patient's consent.
• It does not schedule appointments or replace an HL7 interface engine.
• Coverage differs by health system. What comes back depends on the organization, the scopes it grants, and the records it holds. See Health systems.

Background reading

The FinchNode engineering field notes describe what we learned connecting to EHRs.