How does Cerner integration work in 2026?
Cerner is now Oracle Health, and most of its hospitals run Oracle Health Millennium. Apps integrate through Millennium’s FHIR R4 APIs: register free in code Console, build against the open and secure sandboxes, then each health system provisions your app in its own domain through service requests to Oracle. Patient-access apps are provisioned to consumer endpoints automatically. Real-time events such as admissions, orders and results usually still flow over HL7 v2 interfaces built with the hospital’s interface team.
Two parties decide your go-live: Oracle and each hospital
People still search for “Cerner integration”, and many hospitals still say Cerner, but since Oracle bought the company in 2022 the EHR has been sold as Oracle Health and the platform underneath is the Oracle Health Millennium Platform. The developer documentation now lives on docs.oracle.com, while the tools around it keep their Cerner names. This guide covers how an outside company, typically a software vendor, a digital health start-up or a health system’s own IT team, gets data in and out of Millennium.
The part that surprises newcomers is who controls the timeline. Oracle publishes the APIs, runs the sandboxes and sets the fees. But for a clinician-facing or backend app, it is each health system that decides to switch your app on in its Millennium domain, logs the requests with Oracle and pays its own API fees. Your sandbox build can be finished in weeks while the hospital’s paperwork takes months. We have no partnership with Oracle; when we do this work, it runs under your accounts and your contracts with the hospital.
The route matters as much as the paperwork. FHIR suits apps and data pulls; HL7 v2 still carries most real-time event traffic in and out of Millennium, and documents travel through HIEs and now TEFCA. We build all of these through our FHIR interoperability, HL7 and EDI integration and HIE integration services.
Names you will meet: Cerner, Oracle Health, Millennium and Ignite
Old and new names sit side by side, and both appear in contracts, documentation and service tickets:
- Oracle Health Millennium Platform is the EHR platform most Oracle Health hospitals run. Its API documentation, “FHIR R4 APIs for Oracle Health Millennium Platform”, moved to docs.oracle.com; the old fhir.cerner.com address now redirects there.
- Cerner names in the tooling. You register apps in code Console at code-console.cerner.com with a CernerCare account, hospitals manage system accounts in Cerner Central, the sandbox hosts are on cerner.com, and hospitals log provisioning requests to a solution called “Cerner Ignite APIs for Millennium”.
- Oracle Health EHR is Oracle’s newer EHR, introduced in August 2025 for US ambulatory providers and ONC-certified that October, with acute-care functionality promised during 2026. It has its own FHIR R4 API documentation and developer portal, separate from Millennium’s. Ask every target customer which platform, or which mix, they run.
- Soarian Clinicals, an older Oracle Health EHR, has separate API documentation; registering a consumer app covers its patient-access endpoints as well as Millennium’s.
- DSTU 2 is gone. Oracle stopped new DSTU 2 registrations in September 2025 and ended DSTU 2 support in December 2025. Anything still calling /dstu2/ paths needs moving to R4.
Five ways to integrate with Oracle Health Millennium
| Route | Good for | Direction | Hospital-side work | What sets the pace |
|---|---|---|---|---|
| FHIR R4 app with SMART launch | Apps clinicians open from the chart, or patients use at home | Read, plus writes for selected resources | Provision your app in their domain, map codes, configure the launch in PowerChart or FirstNet | The hospital’s security review and service-request queue |
| FHIR system account and bulk data | Backend sync, population analytics, registries | Mostly read; bulk export for many patients | Provision a confidential client and pay Oracle’s certified API fees for their environment | Contract, fee approval and data-use review |
| HL7 v2 interface | Real-time admissions, orders, results, scheduling and charges | Both ways | Interface analysts build and test Millennium’s side | The interface team’s backlog and testing windows |
| CCD and documents | Summaries, referrals, discharge documents | Mostly outbound from Millennium | Enable document generation, Direct or HIE routing | Which document channels the hospital already runs |
| TEFCA or a regional HIE | Records from many organisations, not one hospital | Query and retrieve | None specific to you; you join the network | Network onboarding and your permitted purpose |
Many products end up using two routes: a SMART app for the clinician’s screen, plus an HL7 v2 feed so the app knows the moment a patient is admitted or a result is filed.
What the Millennium FHIR R4 API covers
Oracle’s endpoint list had 43 resource categories when we checked on 7 November 2026. In practical groups:
- Clinical: AllergyIntolerance, Condition, DiagnosticReport, DocumentReference, FamilyMemberHistory, Goal, Immunization, MedicationAdministration, MedicationDispense, MedicationRequest, NutritionOrder, Observation, Procedure, ServiceRequest, Specimen, CarePlan and CareTeam.
- People and places: Patient, Person, Practitioner, Organization, Location, Encounter and Device.
- Scheduling: Appointment, Schedule and Slot.
- Financial: Account, ChargeItem, Coverage, FinancialTransaction and InsurancePlan.
- Other: Communication, Consent, Questionnaire, QuestionnaireResponse, Provenance, Media and Binary.
Writes exist for a useful subset: create or update for Observation, Condition, AllergyIntolerance, Immunization and FamilyMemberHistory; create for DocumentReference, DiagnosticReport and Procedure; create or patch for Appointment, Encounter, Patient and MedicationRequest; plus Coverage, Communication, ChargeItem operations and Provenance. There is a batch and transaction endpoint at the service root, and Binary/$autogen-ccd-if returns a generated CCD for a patient.
Two limits shape most designs. First, there is no Subscription resource in the list, so the API will not push events to you; for “tell me when” you poll carefully or take an HL7 v2 feed. Second, a write being documented does not mean a given hospital has enabled it or mapped the codes your app sends. Confirm each write with each customer.
Authorisation: SMART on Millennium
Oracle’s authorisation framework documents support for SMART App Launch 1.0.0 and 2.0.0 and for SMART Backend Services. The details that catch teams out:
- SMART v2 scopes mean PKCE. If your token requests use v2-style scopes such as patient/Observation.rs, you must use PKCE with S256 in the authorisation code flow.
- No wildcard scopes. Request each resource scope your app needs, by name. Asking for far more than you use also slows down every hospital’s security review.
- Short tokens. Access tokens last 570 seconds. With online_access you can refresh while the user’s session lasts; with offline_access, until access is revoked or the grant goes unused for more than three months.
- Refresh tokens are not rotated. A refresh response does not contain a new refresh token, so keep the one from the original grant. Refreshing more often than once a minute may be throttled.
- Backend apps. System accounts are confidential clients. They can authenticate with a client secret, or with a signed JWT (RS384 or ES384) after registering a JSON Web Key Set, which is the method Oracle names for bulk data.
- Transport. TLS 1.2 or 1.3. If your TLS certificate expires or your DNS changes, Oracle may suspend your refresh tokens, so certificate renewal belongs in your runbook.
Sandboxes and code Console
All three sandbox endpoints share one tenant ID, ec2458f2-1e24-41c8-b71b-0e701af7583d, according to Oracle’s service root page:
| Sandbox | Base URL | Use |
|---|---|---|
| Open | https://fhir-open.cerner.com/r4/ec2458f2-1e24-41c8-b71b-0e701af7583d/ | Read-only, no authentication. Good for a first proof of concept. |
| Secure, provider and system | https://fhir-ehr-code.cerner.com/r4/ec2458f2-1e24-41c8-b71b-0e701af7583d/ | Authenticated testing of your declared scopes, including writes. |
| Secure, patient | https://fhir-myrecord.cerner.com/r4/ec2458f2-1e24-41c8-b71b-0e701af7583d/ | Patient-facing standalone launch. |
The first call most developers make is the CapabilityStatement, which needs no credentials:
curl -H "Accept: application/fhir+json" \
https://fhir-open.cerner.com/r4/ec2458f2-1e24-41c8-b71b-0e701af7583d/metadataWhen you are ready for authentication, register the app in code Console (it needs a free CernerCare account), choose provider, patient or system as the type, and read the authorisation endpoints from /.well-known/smart-configuration on the secure base URL instead of hard-coding them. Oracle’s build-and-test guide and the Oracle Health Developer Forums are the places to take questions.
Sandbox data is synthetic and tidy. Real domains have their own code sets, half-populated resources and local habits, which is why a hospital’s non-production domain is part of the plan, not a formality.
Who enrols in what, and who pays
| Party | What they do | Published fees (checked 7 Nov 2026) |
|---|---|---|
| You, the app owner | Accept Oracle’s API terms, register in code Console, build and test in the sandboxes. For provider or system apps, Oracle also asks for a gap analysis against its documentation and a working demo. | Sandbox access is free. Optional services through Oracle PartnerNetwork (OPN): membership at $500 a year, an OPN-members-only service at $3,000 a year, and Millennium environment access at $5,000 a year. Oracle says these are not required to build and deploy apps. Source: API access and fees. |
| The health system | Provisions your app in its domain through service requests, maps codes, completes approvals, configures the launch and signs your contract and business associate agreement. | For certified APIs in a standalone environment: a one-time $10,000 setup covering one production and one non-production environment, $5,000 for each extra non-production environment, then annual fees by size. Small (up to 2 million patient records) pays $15,000 for single-patient APIs and $7,000 for bulk data; extra-large (over 20 million) $30,000 and $28,000. Shared environments pay less, and Oracle’s ambulatory suites include the APIs. Source: certified API technology fees. |
| Patients and direct-to-consumer app developers | Use consumer endpoints the app is provisioned to. | Oracle’s certified health IT cost disclosure says they are not charged connection or usage-based fees. |
| Radiatus, if you hire us | Build and test under your accounts, prepare the hospital’s provisioning checklist, support their analysts. | Our own work is quoted per phase. We are not an Oracle partner and cannot obtain Oracle validation on your behalf. |
If a marketplace listing matters to your sales team, Oracle offers an Oracle Validated Integration with Oracle Health Millennium Platform through OPN’s Industry Healthcare Track, leading to a listing in the Oracle Healthcare Marketplace. You enrol in that yourself; Oracle lists additional fees for it. Developers who skip validation can still connect to the APIs, but must follow the marketing rules in Oracle’s API terms.
From sandbox to a live hospital domain
Oracle documents the provisioning steps in its FHIR application provisioning guide. Most of them are the hospital’s, which is why your contact there matters:
- You create the production app in code Console and send the hospital its application ID and client ID. If you also need a non-production copy, the hospital asks Oracle to transfer it to the sandbox authorisation server.
- The hospital gets its tenant ID: from Oracle Health Hosting if Oracle hosts its domain, or from Cerner Central if it hosts its own.
- The hospital logs a service request to “Cerner Ignite APIs for Millennium” to provision your IDs against that tenant, and a separate one for any codable concepts your app needs mapped. Oracle asks for one topic per request.
- For production, the hospital may need to complete Oracle’s Process for Executing Client Approval (PECA) form.
- If your app loads external websites inside a Citrix-delivered PowerChart, the hospital adds them to Citrix trusted sites.
- The hospital configures the SMART app to run in PowerChart or FirstNet, and you test in its non-production domain before production.
Two exceptions. Patient-access apps skip most of this: after registration they are provisioned to all active Millennium and Soarian consumer endpoints. And hospitals on shared domains (CommunityWorks, PowerWorks or Continuum) cannot use self-service provisioning, apart from a limited route Oracle calls its minimum viable strategy, so they go through their Oracle representative.
How long it takes, and what sets the pace
Planning ranges we use for one clinician-facing SMART app going live at one hospital. They are not Oracle figures, and your hospital may be faster or slower.
| Stage | Typical span | Usually waiting on |
|---|---|---|
| Sandbox build and demo | 3–6 weeks | Your own team; scope decisions |
| Contract, BAA and security review | 4–12 weeks, often in parallel with the build | The hospital’s legal, privacy and security teams |
| Non-production provisioning and testing | 3–8 weeks | Service-request queue, code mapping, PowerChart configuration |
| Production provisioning and go-live | 2–6 weeks | Approval forms, change-control windows, training |
The usual causes of delay: scopes broader than the app needs, which reopen the security review; codes that only work in the sandbox; nobody at the hospital owning the requests; and change freezes around upgrades. Each new hospital repeats the hospital-side stages, though the second and third go faster once your documentation pack exists.
HL7 v2 interfaces with Millennium
For real-time events, HL7 v2 remains the normal route into and out of Millennium: ADT for admissions, transfers and updates, ORM or OML for orders, ORU for results, SIU for scheduling, DFT for charges and MDM for documents. The Millennium side is built by the hospital’s interface analysts in Oracle Health’s own interface tooling, which job adverts and interface teams usually call Open Engine or OPENLink, or by Oracle services under the hospital’s contract.
What you bring:
- An interface specification for your side: message types, trigger events, required fields, your acknowledgement rules and how you handle corrections and merges.
- Sample messages, and a mapping of their codes to yours. Millennium sends the hospital’s own code values, so agree early who maintains the code translations.
- A listener on MLLP inside a VPN or TLS tunnel, with queuing, retries and monitoring, usually on an engine such as Mirth Connect or the Open Integration Engine. Our Mirth Connect services cover that side.
- A test plan for the hospital’s non-production domain, then a parallel run before the switch.
Ask at the start whether the hospital charges vendors for interface build and support, and how long its interface backlog is. If you need those messages as FHIR on your side, see our guide to HL7 to FHIR conversion.
Documents, HIEs and TEFCA
For a summary of a patient’s record, three options usually exist: the generated CCD from the FHIR API, documents sent through Direct or an HIE, or a national network. Oracle Health Information Network, an Oracle subsidiary, was designated a TEFCA QHIN in November 2025. If your product needs records from many organisations rather than one hospital, joining a QHIN or a regional HIE as a participant may beat a string of one-to-one integrations. Our HIE integration service covers the onboarding.
Pitfalls in Cerner FHIR API integration
- Building only against the open sandbox, then finding that the secure sandbox and real domains behave differently.
- Requesting every scope “just in case”; it slows each hospital’s review.
- Using SMART v2 scopes without PKCE.
- Discarding the original refresh token, or refreshing on every request.
- Letting a TLS certificate lapse and losing users’ offline access.
- Assuming one registration makes a provider app live everywhere; that only holds for patient access.
- Hard-coding sandbox codes that the hospital never mapped.
- Polling for changes so often that the integration looks like a load test; use an HL7 v2 feed for events.
- Forgetting that some customers are on shared domains, Soarian or the new Oracle Health EHR.
- Leaving old DSTU 2 code paths in the product.
Questions to ask a hospital before you build
- Which platform and domain will we connect to: Millennium hosted by Oracle, self-hosted Millennium, a shared domain, or Oracle Health EHR?
- Who will log and follow the service requests to Oracle, and what is their current backlog?
- Has the hospital already paid Oracle’s certified API setup, and does a system or bulk-data app change its fee tier?
- Which writes will it allow, and who maps our codes?
- Do we also need an HL7 v2 feed, and does the interface team charge for it?
- What security questionnaire, BAA and change-control windows apply?
Oracle Health integration packages
Typical effort in engineer-days for the work on your side. Hospital-side time is not included. We confirm a fixed price per phase after a short review of your product and target customers.
Integration plan
The problem
A hospital on Oracle Health wants your product, and you do not yet know which route, which scopes or what the hospital will have to do.
How we do it
We review your use case against Oracle’s documentation, choose the route (SMART app, system account, HL7 v2 or a mix), write the gap analysis Oracle expects from provider and system app developers, list the exact scopes and writes, and prepare a provisioning checklist your hospital contact can act on. Typical effort: 3–6 engineer-days.
What you get
- Route and scope decision
- Gap analysis against the R4 API
- Hospital provisioning checklist
- Timeline with named dependencies
SMART on FHIR app on Millennium
The problem
Your app works with one EHR, or only in a sandbox, and now has to launch from PowerChart at a real hospital.
How we do it
We implement provider launch or patient standalone launch with SMART v2 scopes and PKCE, token handling that respects Oracle’s refresh rules, the reads and writes you need, and tests in the secure sandbox. Then we support the hospital through non-production provisioning, code mapping and go-live. Typical effort: 15–35 engineer-days.
What you get
- Working launch and token handling
- Reads and writes tested in the sandbox
- Support through hospital provisioning
- Go-live runbook
Backend and bulk data feed
The problem
You need data from Millennium in your own platform on a schedule, not through a user’s screen.
How we do it
We set up the system account with JWT authentication and a registered key set, build incremental reads or bulk export into your data model, and add monitoring and retry. We also tell you up front which Oracle fee tier the hospital is likely to face. Typical effort: 10–25 engineer-days.
What you get
- System account with JWT auth
- Incremental or bulk extraction
- Mapping into your data model
- Monitoring and alerts
HL7 v2 interface with a Millennium hospital
The problem
The hospital wants to send admissions, orders or results, or receive yours, and its interface team is waiting for your specification.
How we do it
We write your interface specification, build the listener and mappings on your engine, agree code translations with the hospital’s analysts, and run testing in their non-production domain and a parallel run before cutover. Typical effort: 8–20 engineer-days per interface on your side.
What you get
- Interface specification
- Engine channels with queuing and alerts
- Test scripts and sign-off
- Parallel run and cutover
How an Oracle Health integration runs with us
For one product going live at its first Millennium hospital. Hospital-side stages run in parallel wherever the hospital allows.
Route and scopes
Use case, target hospitals and platforms, the route, the exact scopes and writes, and a checklist for the hospital.
Sandbox build
Registration in code Console under your account, the build against the secure sandbox, and a working demo.
Hospital paperwork
Contract, BAA and security review on the hospital side, with our answers to its technical questionnaire.
Provision, test, go live
Service requests by the hospital, testing in its non-production domain, production provisioning and a supported go-live.
Sources behind this guide
Oracle renames programmes and moves documentation often. Everything below was read on 7 November 2026; check again before you commit to dates or budgets.
FHIR R4 APIs for Millennium
Oracle’s endpoint reference on docs.oracle.com: 43 resource categories, the writes listed above, batch and transaction, and the generated CCD.
Millennium authorisation framework
SMART App Launch 1.0.0 and 2.0.0, Backend Services, PKCE for v2 scopes, token lifetimes and refresh rules.
FHIR application provisioning
The hospital’s self-service steps: tenant IDs, service requests, code mapping, approval forms and launch configuration.
Developer and certified API fees
Optional OPN services for developers, and the setup and annual fees Oracle publishes for health systems.
Oracle PartnerNetwork validation
Oracle Validated Integration and the Oracle Healthcare Marketplace listing, for vendors who want them.
TEFCA
Oracle Health Information Network’s QHIN designation, November 2025, for network-based record exchange.
Tools we use alongside it
- code Console
- SMART App Launch 2.0
- SMART Backend Services
- FHIR Bulk Data
- HL7 v2 over MLLP
- Mirth Connect
- Open Integration Engine
- HAPI FHIR
- Postman
Facts, versions and vendor details checked 7 November 2026.
Interfaces we run in our own product
Our own EHR product does not connect to Oracle Health, but it does run HL7 interfaces and watches them, which is the same discipline.
Guides and related pages
Guides
Technologies
Glossary
Cerner and Oracle Health integration: common questions
Yes. Oracle bought Cerner in 2022, and the EHR is now sold as Oracle Health, with Oracle Health Millennium Platform as the platform most of its hospitals run. Developer tools still carry Cerner names, such as code Console and CernerCare accounts. Oracle has also launched a newer Oracle Health EHR with its own API documentation, so check which platform each customer uses.
Create a free CernerCare account, register your app in code Console, and build against Oracle’s open sandbox (read-only, no authentication) and secure sandbox. Patient-access apps are then provisioned to Oracle Health consumer endpoints automatically. Provider and system apps go live only when each health system provisions them in its own domain through service requests to Oracle.
Sandbox access is free, and Oracle says its optional Oracle PartnerNetwork services for developers are not required to build and deploy apps. Those services were listed at $500 a year for membership, $3,000 a year for a members-only service and $5,000 a year for environment access when we checked in November 2026. Health systems pay separate setup and annual fees for certified APIs.
Oracle publishes a one-time $10,000 setup fee for one production and one non-production environment, $5,000 per extra non-production environment, and annual fees by size. A small standalone environment pays $15,000 a year for single-patient APIs and $7,000 for bulk data; extra-large pays $30,000 and $28,000. Shared environments pay less. Oracle says consumers and direct-to-consumer app developers are not charged connection or usage fees.
Our planning range for one clinician-facing app at one hospital is roughly three to six months from start to go-live. The sandbox build often takes three to six weeks; the rest is the hospital’s contract, security review, service requests to Oracle, testing and change control. Patient-access apps can be much faster because provisioning is automatic.
No. Any developer can register in code Console and use the APIs under Oracle’s terms. Oracle PartnerNetwork membership and Oracle Validated Integration are optional and lead to a listing in the Oracle Healthcare Marketplace. Radiatus is not an Oracle partner; we build and test under your own accounts.
Yes. Oracle documents support for SMART App Launch 1.0.0 and 2.0.0 and for SMART Backend Services. If you use SMART v2 scopes you must also use PKCE with S256. Wildcard scopes are not supported, so request each scope by name.
For a subset of resources, yes. Oracle documents creates or updates for resources including Observation, Condition, AllergyIntolerance, Immunization, DocumentReference, Appointment, Encounter, Patient and MedicationRequest. Each hospital still has to enable your app and map the codes you send, so confirm every write with every customer.
Use FHIR for apps and for reading or writing data on demand. Use HL7 v2 when you need to know about events as they happen, such as admissions, new orders or released results, because the Millennium R4 API does not offer subscriptions. Many products use both: a SMART app for the screen and an HL7 v2 feed for events.
Integrating with an Oracle Health hospital?
Tell us what your product does, which hospital or hospitals are asking for it, and what data you need. A senior integration engineer will reply with the likely route, the scopes and a typical effort range.






Compliance-first delivery