EHR / EMR Systems
Oracle Cerner Integration
Oracle Cerner (Cerner Millennium) is one of the two largest EHR platforms, widely used across US hospitals and NHS trusts. Like Epic, modern Cerner integration centres on FHIR R4 and SMART on FHIR, with a developer program and app marketplace governing distribution. This guide walks through the practical path to integrating with Cerner: the APIs, the authorisation model, the developer onboarding, and the compliance work that surrounds any access to patient data.
How Cerner integration works
Cerner exposes FHIR R4 endpoints secured with SMART on FHIR, alongside its older proprietary and HL7 v2 interfaces. Apps authenticate via OAuth 2.0, request scoped access, and read or write FHIR resources within either a provider (Cerner PowerChart) launch context or a patient-facing context. Cerner's developer documentation and sandbox let you build and test against representative data before approaching a live site. As with any EHR, the exact resources, scopes, and FHIR version available depend on the customer's specific deployment and configuration.
The Cerner developer program
Cerner runs a developer program (the code program and associated console) that provides sandbox access, API documentation, and a route to publish apps for health systems to adopt. Registering gives you the credentials and tooling to build; production use at a given organisation still requires that site to approve and configure your app. Plan for the partnership and security review alongside the engineering — the integration code is rarely the slowest part of going live.
Compliance and data handling
Cerner integrations handle Protected Health Information, so HIPAA in the US and UK GDPR / NHS DSP Toolkit in the UK apply throughout. Expect to sign a Business Associate Agreement with each covered entity, encrypt data in transit and at rest, use least-privilege scopes, log all access for audit, and govern any flow of patient data into AI models. Building to these standards early is what gets you through a hospital's procurement and security assessment.
How to integrate with Oracle Cerner
- 1
Join Cerner's developer / code program
Register on Cerner's developer console to obtain sandbox access, API documentation, and client credentials.
- 2
Review the endpoint's FHIR capabilities
Confirm FHIR R4 support and the available resources and SMART scopes for the target deployment via its capability statement.
- 3
Build the SMART on FHIR flow
Implement OAuth 2.0 authorisation for provider or patient launch, handling tokens, refresh, and launch context.
- 4
Map resources and test in the sandbox
Map your data to Cerner's FHIR resources and validate reads and writes against the sandbox before touching production.
- 5
Pass review and enable per customer
Sign the BAA, complete the security review, and have each health system approve and configure your app for live use.
Common use cases
- Clinical copilots and documentation tools embedded in Cerner PowerChart
- Reading clinical data to drive decision support, triage, or analytics
- Writing notes, orders, or observations back with clinician sign-off
- Patient engagement apps using Cerner's patient-facing FHIR access
Workflow example
Decision-support alert in Cerner
- App launches in PowerChart with the patient context via SMART on FHIR.
- It reads relevant FHIR resources (Conditions, Observations, MedicationRequests).
- A model evaluates risk and surfaces a patient-specific, evidence-linked alert.
- The clinician acts on or dismisses the alert; the interaction is logged for audit.
Frequently asked questions
Is Cerner integration different from Epic?
The fundamentals are similar — both use FHIR R4 and SMART on FHIR with a developer program and marketplace. The differences are in documentation, sandbox tooling, available scopes, and per-vendor processes, so each still needs its own implementation and testing.
Can apps write data back to Cerner?
Yes, for supported resources and with appropriate scopes, apps can write back to Cerner — subject to the EHR's safety logic, audit, and clinician confirmation. Write access generally requires more review than read-only access.
Does the NHS use Cerner?
Yes. Oracle Cerner is deployed in a number of NHS trusts, so UK integrations must also meet UK GDPR and NHS Data Security and Protection Toolkit expectations in addition to the technical integration.
Building on Oracle Cerner? We deliver FHIR R4 and SMART on FHIR integrations ready for health-system review. Book a discovery call to plan yours.