Oracle Health (Cerner) FHIR Integration: What to Know Before You Build
Oracle Health - formerly Cerner - exposes a FHIR R4 API with its own registration process, sandbox, and quirks. Most of what you know from another EHR's FHIR API transfers, but not all of it.
Oracle Health's FHIR API and developer program
Since Oracle's acquisition of Cerner, the EHR's developer-facing branding and portal have shifted to Oracle Health, but the underlying FHIR R4 API and app registration model follow the same general SMART on FHIR pattern used across major EHR vendors: register an app, declare scopes, and authenticate via OAuth 2.0 - either interactive SMART App Launch for provider/patient-facing apps, or a backend, system-to-system flow for integrations with no user in the loop.
Oracle Health provides a public sandbox environment with synthetic test data for initial development, similar in purpose to other major EHRs' sandboxes - register there first and validate your integration before pursuing a production connection with a specific health system.
Where it differs from other EHR FHIR APIs
Resource support and field population can differ meaningfully from other EHRs even for the same FHIR resource type - don't assume a mapping or parsing approach that worked against one EHR's FHIR API will work unchanged against Oracle Health's. Validate field population and search parameter support against Oracle Health's own sandbox directly rather than assuming parity.
As with other EHRs, production access typically requires going through the health system's own approval process in addition to Oracle Health's own app review - the vendor's technical approval and the specific health system's operational approval are two separate gates, and both need to be budgeted for in a project timeline.
What we build this on
Oracle Health (Cerner) is one of the major EHR platforms in our integration experience, alongside Epic, athenahealth, eClinicalWorks, and others - the underlying engineering discipline (defensive parsing, explicit resourceType checking, proper OAuth token lifecycle management, structured logging of every request) is the same regardless of which specific EHR's FHIR API you're integrating with, even though the vendor-specific details differ.
FAQ