Updated October 14, 2026. Cerner is now part of Oracle Health. The name still appears in search queries and in installed systems, while Oracle’s current public materials describe Oracle Health EHR and the Oracle Health Millennium Platform. This article summarizes what the vendor says publicly and offers a practical way to evaluate fit. It is not a hands-on product test or an endorsement.
There is no single EHR that is best for every organization. A useful review starts with your care settings, specialties, existing technology, staffing, workflows, and budget—not a generic feature checklist. Product names, packaging, availability, and capabilities can change, so confirm details with Oracle and in the contract for the specific product and version you are evaluating.
What is Oracle Health (Cerner)?
Oracle acquired Cerner in 2022 and brought its healthcare business under the Oracle Health name. Oracle’s materials describe a portfolio of clinical, operational, financial, interoperability, and data products. “Cerner” remains a familiar shorthand, but it does not identify one universal configuration: organizations may use different applications, versions, integrations, and implementation arrangements.
Oracle describes the Millennium Platform as an EHR platform for clinical, operational, and financial transactions. Its current portfolio also includes Oracle Health EHR offerings, interoperability tools, and other applications. These names should not be assumed to mean every feature is included in every customer’s deployment.
What does the vendor currently describe?
Oracle’s public EHR materials describe functions such as viewing and documenting patient information, workflow-integrated clinical information, patient timelines, referral and care-coordination workflows, and clinical decision support. Its current product pages also discuss AI-enabled functions. These are vendor descriptions, not independent evidence that a capability is available, enabled, or effective in a particular organization’s environment.
Oracle’s interoperability materials describe exchange products and developer access, including FHIR APIs for supported use cases on the Millennium Platform. Actual exchange depends on the product, API version, permissions, configuration, technical work, partner systems, and applicable agreements. Ask which specific interfaces and standards are included, supported, and live for your proposed configuration.
How to evaluate it for your organization
- Start with real workflows. Map a typical visit from scheduling and check-in through documentation, orders, referrals, billing, and follow-up. Ask to see those scenarios in a demonstration using the products and roles you would actually deploy.
- Check setting and specialty fit. Confirm support for your organization type, specialties, locations, and care settings. Ask which capabilities are native, separately licensed, configured, or delivered by a partner.
- Test usability with end users. Have clinicians, front-desk staff, billers, and administrators complete representative tasks. Measure task completion, clicks or handoffs where useful, training needs, and accessibility—not just a polished demo.
- Validate interoperability in detail. List the systems that must exchange data, the information exchanged, direction and frequency, matching and reconciliation process, interface costs, and who owns troubleshooting. Request a test plan and acceptance criteria.
- Plan implementation and migration. Get a written scope for data conversion, workflow design, testing, training, go-live coverage, downtime procedures, and post-launch optimization. Ask for references with a similar size and care model.
- Calculate total cost of ownership. Request a quote that separates subscription or license charges, implementation, interfaces, data migration, hardware, training, support, and optional modules. Model renewal terms and the internal staff time needed to operate the system.
- Review security and compliance evidence. Ask for current documentation relevant to your deployment, including responsibilities shared between vendor and customer, access controls, audit capabilities, incident response, data use, retention, and business associate terms. Do not infer a deployment’s security from a general product-page claim.
- Set measurable acceptance criteria. Before contracting, define the workflows, integrations, reporting, performance, training, and support response commitments that must be demonstrated for go-live and ongoing service.
