Is Cerner the Same as Oracle Health?
Effectively, yes. Oracle acquired Cerner Corporation in 2022 for $28.3 billion and rebranded it Oracle Health. The underlying Cerner Millennium platform continues largely unchanged under the new name – so when you see “Cerner” in an older RFP and “Oracle Health” in a 2026 sales deck, they're referring to the same core EHR technology, now under different ownership and with a second, newer product line layered alongside it.
Cerner Isn't Being Discontinued – But It Is In Transition
This is the single most important thing to understand before planning any RCM automation around this platform: Cerner Millennium is not going away. It remains the production EHR for existing clients and continues to receive updates. But Oracle is simultaneously running a second track – a next-generation EHR built entirely from scratch on Oracle Cloud Infrastructure, announced in October 2024, with new AI and voice capabilities baked in from day one. It remains the production EHR for existing clients and continues to receive updates. But Oracle is simultaneously running a second track — a next-generation EHR built entirely from scratch on Oracle Cloud Infrastructure, announced in October 2024, with new AI and voice capabilities baked in from day one.
As of today, that new EHR is only available for ambulatory providers; acute-care functionality is targeted for 2026. Oracle also walked back an earlier requirement that clients migrate to Oracle Cloud Infrastructure before adopting the new platform – instead offering a “547 Deep Dive Assessment” so existing clients can evaluate readiness and sequencing on their own timeline, rather than being forced onto a hard migration deadline.
The backdrop to all of this: Oracle Health has cut its workforce by close to 50% since the acquisition, consolidated Cerner's Kansas City campus, and lost several large hospital clients – representing thousands of beds – mostly to Epic. None of that means the platform is going away. It does mean that if you're running Cerner/Oracle Health today, you're managing a vendor mid-transformation, not a stable, settled roadmap.
Does Oracle Health Have a Developer API?
Yes. The Oracle Health Developer Program (formerly Cerner Code) gives third-party developers free access to Millennium API documentation, best-practice guidelines, and a testing sandbox. For new integrations in 2026, Oracle's own recommendation is to use FHIR R4 (Ignite APIs) as the primary integration path, falling back to legacy HL7 v2 through COI only for real-time event data that FHIR Subscriptions can't yet reliably deliver. Millennium APIs remain available for core system-of-record operations that predate the FHIR push.
So, similarly to MEDITECH, the API access itself isn't the blocker. The blocker is what those APIs actually connect to – and how much of a provider's day-to-day RCM workflow still depends on a payer's own portal rather than anything Oracle Health exposes.
What Oracle Health's Native RCM Tools Do – and Don't Do – Today
Oracle Health's Revenue Cycle and Consumer Management platform is genuinely investing in automation. RevElate Patient Accounting unified Cerner's RCM offerings under one platform, and a partnership with AKASA layers AI-based automation on top – automating eligibility checks and denials, checking eligibility using insurance card data, amending eligibility-related denials, and automatically resubmitting corrected claims. Beyond that partnership, Oracle Health's own roadmap lists AI-driven denial appeal letter generation, AI-assisted inpatient coding (ICD-10-PCS, MS-DRG), and end-to-end charge master automation.
The catch: several of these are described as in-development or roadmap items, not universally live features every client can turn on today. And critically, they're native Oracle Health capabilities – built to work inside the Oracle Health/AKASA stack, not something a hospital can freely extend to automate every payer portal in its specific contracted mix, especially the smaller regional payers a national AI-RCM partnership is less likely to prioritize first.
Let’s talk!
In just 15 minutes, we’ll cut through the noise and see if automation works for you.
Why Mid-Transition Cerner Shops Can't Just Wait for the Native Roadmap
If you're running Cerner Millennium today, waiting for Oracle's native RCM AI roadmap to fully mature means betting on a vendor that is simultaneously: maintaining a legacy platform, building an entirely new cloud EHR, absorbing a nearly 50% workforce reduction, and defending market share against Epic. That's not a criticism of the technology — Oracle Health's revenue cycle ambitions are real and well-funded. It's a practical observation about sequencing: native RCM AI features tend to roll out to Oracle Health's largest, most strategic accounts first, and tend to prioritize the payers with the largest volume relationships, not necessarily the specific regional payer mix a mid-size hospital system actually bills against.
Meanwhile, the day-to-day revenue leakage — denied claims, stalled prior auths, eligibility errors caught too late — doesn't pause for a platform migration. A hospital mid-transition between Millennium and the new Oracle Health EHR has, if anything, less internal bandwidth to spare for chasing down manual RCM workflows, not more.
Where Computer-Use Automation Fits Alongside Oracle Health
This is the practical case for layering computer-use agents on top of whichever Oracle Health environment a hospital is running, rather than waiting for the native roadmap to arrive: the agent doesn't care whether the underlying EHR is Cerner Millennium or the new cloud-native platform, because it isn't trying to replace Oracle Health's own APIs — it's handling the payer-portal side those APIs were never meant to reach.
Concretely, that means:
- Eligibility verification pulled from Millennium or the new EHR, checked against whichever payer portal the patient's plan requires — not just the payers covered by an existing AKASA-style partnership.
- Prior authorization packets assembled from clinical documentation already in the EHR, then submitted through the payer's own portal without waiting on a native Oracle Health feature to support that specific payer.
- Denials management that reads every EOB regardless of which patient accounting system generated the original claim — useful precisely because a mid-transition hospital may be running both Cerner Patient Accounting and newer tools side by side.
None of this requires picking a side in the Millennium-vs-new-EHR transition. It works underneath whichever one is live on a given day.
FAQ
Is Cerner the same as Oracle Health?
Effectively yes. Oracle acquired Cerner in 2022 and rebranded it Oracle Health; the underlying Cerner Millennium platform continues largely unchanged, so the two names now refer to the same core EHR technology.
Is Cerner being discontinued?
No. Cerner Millennium remains the production EHR and continues to receive updates. Oracle Health has cut its workforce by close to half and lost several large clients (mostly to Epic) while building a separate cloud-native EHR in parallel — real turbulence, but not a sunset of the platform.
Does Oracle Health/Cerner have a developer API?
Yes — the Oracle Health Developer Program gives third-party developers free access to Millennium API documentation, a testing sandbox, and FHIR R4/HL7 v2/CCDA-based integration standards.
What is Oracle Health Millennium used for?
Millennium runs hospital clinical, financial, and operational workflows in one system — vitals a nurse records are visible to physicians instantly, and billing teams get automated charge capture without manual entry. Large systems often run one Millennium instance across multiple facilities.
Does Cerner/Oracle Health automate revenue cycle management?
Partially. Native tools like RevElate Patient Accounting and the AKASA partnership automate eligibility checks and some denial workflows, and Oracle's roadmap includes AI-driven coding and charge master automation — but several of these are still rolling out, and they cover the payers those native tools are built around, not necessarily a hospital's full payer mix.
Should we wait for Oracle Health's native RCM AI before automating anything?
Not if denials, stalled prior auths, and eligibility errors are costing revenue today. Computer-use automation on the payer-portal side works underneath whichever Oracle Health environment is currently live, without requiring a bet on migration timing.
Two EHRs, one revenue cycle. Let's automate the part that isn't waiting on Oracle's roadmap.
Ready to automate your business processes?
Karl – our CTO loves to discuss the ROI. Feel free to book a call with him.
In just 15 minutes, we’ll help you assess whether automation is right for you.
