Cerner / Oracle Health integration
Cerner / Oracle Health FHIR Integration
Cerner Millennium (now Oracle Health) exposes a FHIR R4 surface with SMART on FHIR for clinician-facing apps and backend services for population-level access. The integration shape mirrors Epic: the SMART launch happens in Oracle Health and gives the app its EHR token; the same app authenticates separately against Fire Arrow's OAuth/OIDC provider for its own backend calls. Fire Arrow itself does not implement the SMART app launch profile.
What you can build
- Standards-based connectivity to Oracle Health
Oracle Health-side: FHIR R4 plus SMART on FHIR for clinician launch and backend services. No vendor-specific protocol required.
- Fire Arrow as the app's own FHIR backend
OAuth/OIDC against the customer's identity provider (typically Microsoft Entra ID), with rule-based authorization, GraphQL, and audit on every call. Fire Arrow does not implement SMART app launch.
- Per-tenant configuration
Client registration and SMART scope assignment per Oracle Health tenant. Fire Arrow's rules remain consistent across tenants.
How it works
- 1 Register the app with Oracle Health
App registration via the Oracle Health developer portal; client id and SMART scopes per environment.
- 2 Launch the app from Oracle Health
Oracle Health-triggered SMART launch passes context (patient, encounter, user) to the app and issues an Oracle Health-scoped access token.
- 3 Read / write Oracle Health through FHIR R4
Standard FHIR R4 calls against the Oracle Health FHIR endpoint with the Oracle Health token, scoped by the user's SMART scopes.
- 4 Authenticate the user against Fire Arrow
Separate OAuth/OIDC flow against the customer's identity provider (typically Microsoft Entra ID). The Fire Arrow token is independent of the Oracle Health token.
- 5 Maintain the app's own state in Fire Arrow
Outcomes, Tasks, and supplemental resources the EHR does not hold live alongside in Fire Arrow, accessed through standard FHIR REST or GraphQL with the Fire Arrow token.
Who this is for
Integration teams connecting their Fire Arrow-based product to Cerner Millennium and Oracle Health environments.
Two integration shapes
The clinician-facing pattern is a SMART on FHIR launch on the Oracle Health side. Oracle Health authenticates the user, passes context to the app, and issues an Oracle Health-scoped access token. The app uses that token against Oracle Health's FHIR endpoint. To talk to Fire Arrow, the same app authenticates the user against Fire Arrow's OAuth/OIDC provider (typically the customer's Entra ID tenant) and uses the resulting Fire Arrow token on every Fire Arrow call. Fire Arrow itself is not a SMART app endpoint.
The backend services pattern uses SMART backend services on the Oracle Health side with a registered client identity. The Fire Arrow side uses standard OAuth 2.0 / OIDC client credentials, an Entra ID service principal, or an admin-issued API token. Both sides log the calls they served.
Vendor-specific extensions and quirks
Oracle Health (like Epic) ships extension namespaces and vendor-specific search parameters alongside the standard FHIR R4 surface. Apps that depend on these handle them in the integration layer; the data Fire Arrow stores remains standard FHIR R4 with the integration layer translating where needed.
Validation, terminology, and code system handling are typically the responsibility of the integration layer, with Fire Arrow accepting the resulting standard resources.
Related docs
FAQ
Does Oracle Health expose write access?
Write access is supported for a subset of resources in standard configurations. The exact set depends on the Oracle Health tenant's enablement.
How does this differ from Epic integration?
Mechanically the integration shapes are the same: SMART on FHIR launch for clinicians on the EHR side, backend services for population workflows, and a separate OAuth/OIDC flow against Fire Arrow for the app's own backend calls. The differences are in the available scopes, extension namespaces, and vendor-specific search parameters between Epic and Oracle Health.
Can I integrate with both Epic and Oracle Health from one product?
Yes. The integration layer translates vendor-specific shapes into the standard FHIR resources Fire Arrow holds. Cross-customer products typically maintain a small adapter per EHR vendor.
