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

FinchNode

Patient-authorized EHR integration

Connect your app to Oracle Health (Cerner) records.

Let patients find their Oracle Health organization, authorize on its patient portal, and share approved record categories with your application.

Patient-authorized Oracle Health (Cerner) record access

Supported record categories

  • Basic details
  • Medications
  • Conditions
  • Allergies
  • Vital signs
  • Lab results
  • Immunizations

Oracle Health (Cerner) patient-facing applications use OAuth 2.0 and SMART on FHIR so patients can authorize access without giving their credentials to your product. FinchNode packages that connection into a hosted flow and one normalized API.

Best fit: Patient-facing health applications that need read-only record access across participating Oracle Health Millennium and Soarian organizations.

The connection journey

  1. Your backend creates a FinchNode Connect session.
  2. The patient selects their organization and authorizes through Oracle Health patient portals.
  3. FinchNode syncs available records and records the patient’s sharing decision.
  4. Your backend reads approved data through the FinchNode API.

Production availability

Live availability depends on the selected Oracle Health organization’s endpoint and the scopes and data that organization makes available.

FinchNode’s current integration is patient-directed and read-only. Actual data depends on the source, organization, approved scopes, patient record, and consent.

View all EHR integrations or learn about the EHR integration API.

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.

How does FinchNode connect to Oracle Health (Cerner)?

Your application creates a FinchNode Connect session. The patient selects their organization, authorizes access on the Oracle Health patient portals experience, and approves the record categories your application may read. FinchNode then exposes supported, consent-filtered data through one API.

Do patients give FinchNode their Oracle Health (Cerner) password?

No. The patient signs in on the source authorization page. Their hospital, payer, or EHR username and password do not pass through FinchNode or your application.

What data can my app read from Oracle Health (Cerner)?

For Oracle Health (Cerner), request supported categories such as Basic details, Medications, Conditions, Allergies, Vital signs, Lab results, Immunizations. Actual availability depends on the source, organization, granted scopes, and patient consent.

Is the Oracle Health (Cerner) connection read-only?

Yes. FinchNode’s current patient-directed integration is read-only. It does not provide EHR write-back, scheduling, provider-side bulk access, or a general-purpose HL7 interface.