Production access is free and self-serve with an account. · Try the demo

FinchNode

Patient-authorized EHR integration

Try it in the console

Step through TEFCA Individual Access with a synthetic patient in the FinchNode console.

The TEFCA console uses your FinchNode sign-in. Open TEFCA (beta). The page offers two ways to run the flow: a synthetic walkthrough, and an exchange against test environments. To integrate a synthetic workflow into your own app with an API key, use the TEFCA sandbox API.

Run the synthetic walkthrough

The walkthrough covers consent through revoke with a synthetic patient. It simulates identity verification and doesn't contact the networks.

  1. Pick a scenario. Records available, No patient match, Some documents unavailable, or Source unavailable.
  2. Consent and start. Tick the consent box and start the session. The page collects no personal information.
  3. Discover. In Records available, FinchNode finds the synthetic patient and lists their record groups. The other scenarios show what no match, partial results, and an unavailable source look like.
  4. Retrieve. Select record groups and retrieve them.
  5. Export. Download the record groups as JSON.
  6. Revoke. Revoke consent to clear the session, or start over.

Record groups are synthetic FHIR collections from FinchNode's demo patient. The real exchange exports base64 documents instead; see Use the export.

A walkthrough session lives in memory on FinchNode's server and expires after 15 minutes. Refreshing the page resets the view but doesn't end the session. Each account can have 20 active walkthrough sessions at once; past that, starting one returns 429 until a session is revoked or expires. Use Start over to revoke the current session before trying another scenario.

Build using the TEFCA sandbox

Use the TEFCA sandbox API and sample app to discover and retrieve fictional records with a sandbox key. The Demo API serves fictional records without an account, and the sandbox quickstart covers Hosted Connect.

Use this walkthrough to explore the IAS experience. Its JSON export contains a single FHIR collection in bundle, combining the selected record groups and one patient resource. The provider test exchange exports base64 documents instead. Your app must handle those formats separately: branch on the export's mode, which is simulation for the walkthrough and sandbox for the exchange.

The provider test exchange runs in the signed-in console. The API-key workflow is a synthetic simulation. Both return exports separately from the Connect records API.

Run the exchange in test environments

When the identity and network test environments are enabled for your account, the same page runs the whole flow against them. You verify a synthetic identity, consent, then discover, query, retrieve, export, and revoke. Use synthetic test information only.

If they aren't enabled, the page says "Not available for your account yet." Ask hello@finchnode.com about access.