ehr

Millennium interfaces documented before the next move.

We work on Oracle Health Millennium, formerly Cerner, and on planning for Oracle's next-generation EHR. In practice that means interface inventories, moves to Oracle Cloud Infrastructure and FHIR integrations. We also write review rules for the Clinical AI Agent and staff Millennium analysts.

OH
platform dossierOracle Health EHREHR
Vendor
Oracle (acquired Cerner, 8 Jun 2022)
Platforms
Millennium; next-generation Oracle Health EHR
New EHR
US ambulatory since 13 Aug 2025; acute care planned 2026
Hosting
Millennium migrations to Oracle Cloud Infrastructure
release watch
  • Clinical AI Agent expansion19 Aug 2026
  • TEFCA QHIN designation20 Nov 2025
connects with
in short·15-second read

Cohash works on Oracle Health EHR platforms, including Millennium, which Oracle took over when it acquired Cerner in June 2022.

We document and rebuild interfaces, plan moves to Oracle Cloud Infrastructure, help weigh Oracle's next-generation EHR (available for US ambulatory care since August 2025), build FHIR integrations, set review rules for the Clinical AI Agent and supply Millennium analysts and developers.

you probably need this if
  • Millennium is scheduled to move to OCI and the interface list is out of date.
  • Ambulatory leaders want a view on Oracle's new EHR.
  • Clinicians use the Clinical AI Agent and nobody measures edits or rejections.
Ask an engineer facts checked 2026-10-20 · 7 sources
how it runs
  1. 01Interface and extract inventory
  2. 02Move or evaluation plan
  3. 03Testing and AI review rules
  4. 04Cut-over and handover
you keep
  • Interface and reporting extract inventory with owner and spec
  • OCI move impact list per interface and extract
  • Next-generation EHR comparison for your ambulatory sites
+ 2 more documents
who does it
Oracle Health Millennium application analystMillennium interface engineer (HL7, FHIR)Millennium report writer (CCL)
oracle-health · release timeline
  1. 13 Aug 2025 Next-generation EHR for ambulatory care Available for US ambulatory providers, with acute care functions planned for 2026. source ↗
  2. 18 Nov 2025 ONC certification of the new EHR Oracle's next-generation EHR received ONC certification. source ↗
  3. 20 Nov 2025 TEFCA QHIN designation Oracle Health designated a Qualified Health Information Network under TEFCA. source ↗
  4. 19 Aug 2026 Clinical AI Agent expansion Adds professional fee coding suggestions, dictation and chart review for US users. source ↗
  5. today · Oct 22, 2026
the story · oracle health ehr estate

From the first call to a setup your own team can run.

Here's what usually prompts a call about your Oracle Health EHR estate, what we do about it and in which order, and where you end up.

  1. chapter 01 · where it hurts

    Why teams reach out

    • Millennium is scheduled to move to OCI and the interface list is out of date.
    • Ambulatory leaders want a view on Oracle's new EHR.
    • Clinicians use the Clinical AI Agent and nobody measures edits or rejections.
  2. chapter 02 · what we change

    How we solve it

    • Interface inventory and rebuild
    • OCI migration planning
    • Next-generation EHR evaluation
    • FHIR and API integrations
    • Clinical AI Agent review
    • Specialist staffing
  3. chapter 03 · how it runs

    Our approach

    • Interface and extract inventory
    • Move or evaluation plan
    • Testing and AI review rules
    • Cut-over and handover
  4. chapter 04 · where you end up

    What changes

    • The move proceeds with a current inventory, and no feed depends on a server that is being shut down.
    • Leaders see how the agent performs on their own visits and can adjust where it's used.
    • Interface and reporting extract inventory with owner and spec
    • OCI move impact list per interface and extract
what we do

Our Oracle Health EHR work

6 kinds of Oracle Health EHR work, each run by engineers who have done it on live tenants.

  1. HL7 and FHIR interfaces documented with owner, spec and failure handling, and rebuilt where they block a move or an upgrade.

  2. What changes when Millennium moves to Oracle Cloud Infrastructure, including interfaces, reporting, downtime plans and the testing your team still owns.

  3. A comparison of your current Millennium setup with Oracle's new EHR for ambulatory care, covering data migration, interfaces and timing.

  4. Apps and systems connected through Oracle Health's published FHIR and Millennium APIs with scoped OAuth access.

  5. Review rules for notes, coding suggestions, dictation and chart summaries, with tracking of edit and rejection rates.

  6. Millennium analysts, interface engineers and report writers, onsite in the US or remote where your policies and Oracle agreements allow.

capability 01 / 06in production

Interface inventory and rebuild

HL7 and FHIR interfaces documented with owner, spec and failure handling, and rebuilt where they block a move or an upgrade.

capability 02 / 06in production

OCI migration planning

What changes when Millennium moves to Oracle Cloud Infrastructure, including interfaces, reporting, downtime plans and the testing your team still owns.

capability 03 / 06in production

Next-generation EHR evaluation

A comparison of your current Millennium setup with Oracle's new EHR for ambulatory care, covering data migration, interfaces and timing.

capability 04 / 06in production

FHIR and API integrations

Apps and systems connected through Oracle Health's published FHIR and Millennium APIs with scoped OAuth access.

capability 05 / 06in production

Clinical AI Agent review

Review rules for notes, coding suggestions, dictation and chart summaries, with tracking of edit and rejection rates.

capability 06 / 06in production

Specialist staffing

Millennium analysts, interface engineers and report writers, onsite in the US or remote where your policies and Oracle agreements allow.

typical situations

Oracle Health EHR situations we walk into

We pieced these together from Oracle Health EHR situations that come up a lot. They're patterns. You won't find a specific client in them.

case file 01

Millennium moving to OCI with an interface list from years ago

composite · not a client story
  1. Beforethe situation

    A health system has a date for moving Millennium to Oracle Cloud Infrastructure. The interface list was last updated years ago, and several feeds run through scripts on servers that won't move.

  2. What we dothe work

    We rebuild the interface inventory from the interface engine and server configurations, find feeds that depend on local scripts and plan their replacement. Each interface is tested in non-production before the move.

  3. Afterwhere you end up

    The move proceeds with a current inventory, and no feed depends on a server that is being shut down.

case file 02

Clinicians using AI drafts with no measurement

composite · not a client story
  1. Beforethe situation

    Ambulatory clinicians use the Clinical AI Agent for notes, and coding suggestions arrived in the August 2026 update. Nobody tracks how often drafts are edited or how suggested codes compare with coders' choices.

  2. What we dothe work

    We agree review rules with clinical and coding leaders, then build a report on draft edits and on coding suggestions against final codes. Results go to the governance committee.

  3. Afterwhere you end up

    Leaders see how the agent performs on their own visits and can adjust where it's used.

approach

How a Oracle Health EHR engagement runs

We don't start a step until the last one has produced something you can check.

  1. step 01

    Interface and extract inventory

    We write down every HL7 and FHIR interface and reporting extract, plus the downstream consumers, and give each an owner and a spec.

  2. step 02

    Move or evaluation plan

    Whether it's an OCI move or a new-EHR evaluation, we mark what changes for each interface and extract, then estimate how much testing that means.

  3. step 03

    Testing and AI review rules

    Interfaces are tested in non-production, and Clinical AI Agent use gets review rules and a tracking report.

  4. step 04

    Cut-over and handover

    We're there for cut-over and the downtime procedures, and we leave the interface runbooks and the inventory behind.

architecture

Where Millennium connects across a hospital

Departmental systems exchange HL7 messages with Millennium through the interface engine, and apps use FHIR. Oracle Health connects to TEFCA as a QHIN, and reporting extracts feed the data platform.

Where Millennium connects across a hospital Departmental systems exchange HL7 messages with Millennium through the interface engine, and apps use FHIR. Oracle Health connects to TEFCA as a QHIN, and reporting extracts feed the data platform. 01 · CLINICAL SYSTEMS 02 · INTEGRATION 03 · ORACLE HEALTH 04 · DATA HL7 messages HL7 messages FHIR calls visit context TEFCA exchange reporting extracts Lab and pharmacy HL7 orders · results Third-party apps FHIR · OAuth 2.0 IN Interface engine HealthShare HealthConnect OH Oracle HealthMillennium EHR on OCI Clinical AI Agent notes · coding · chartreview Oracle Health QHIN TEFCA exchange Snowflake quality and financereporting
Read the diagram as text
  1. Lab and pharmacy → Interface engine: HL7 messages
  2. Interface engine → Oracle Health Millennium: HL7 messages
  3. Third-party apps → Oracle Health Millennium: FHIR calls
  4. Oracle Health Millennium → Clinical AI Agent: visit context
  5. Oracle Health Millennium → Oracle Health QHIN: TEFCA exchange
  6. Oracle Health Millennium → Snowflake: reporting extracts
use cases

Typical Oracle Health EHR projects

The work teams usually bring us, and the platforms Oracle Health EHR has to talk to while we do it.

  1. ORA-01 Millennium is moving to Oracle Cloud Infrastructure, and nobody ever wrote down what the interfaces actually do common request
  2. ORA-02 Ambulatory leaders are asking about Oracle's new EHR common request
  3. ORA-03 Clinicians use the Clinical AI Agent and nobody tracks how often drafts are edited common request
  4. ORA-04 A third-party app needs Millennium data through FHIR common request
  5. ORA-05 Your Millennium analysts have left and the backlog is growing common request
you keep

What a Oracle Health EHR engagement leaves behind

These are working documents, written against your configuration, so your team can run them without us.

  • inventory01

    Interface and reporting extract inventory with owner and spec

    yours to keep
  • document02

    OCI move impact list per interface and extract

    yours to keep
  • document03

    Next-generation EHR comparison for your ambulatory sites

    yours to keep
  • inventory04

    FHIR app register with scopes and approvals

    yours to keep
  • report05

    Clinical AI Agent review rules and edit-rate report

    yours to keep
talent and delivery · oracle health ehr

Certified engineers, wherever you need them.

Some clients want a project team, some want a couple of engineers on theirs. Either works. Onsite, nearshore or offshore, with handovers across time zones that keep things moving.

Onsite

Engineers at your sites in the US

Nearshore

Overlapping hours with US teams

Offshore

Overnight progress on your backlog

All time zones

Coverage handed over across time zones

24-hour coverage · US Central time
OnsiteUS business hours
Nearshoreoverlapping US hours
Offshoreovernight progress
Combinedhandover, not hand-off
roles we staff
  • Oracle Health Millennium application analyst
  • Millennium interface engineer (HL7, FHIR)
  • Millennium report writer (CCL)
  • Oracle Health integration developer
  • EHR data migration engineer
01Is Oracle Health the same as Cerner?

Oracle completed its acquisition of Cerner on 8 June 2022, and Cerner's products are now sold under the Oracle Health name. Many hospitals still call the platform Millennium.

02Should we move to Oracle's next-generation EHR?

It depends on your care settings and timing. Oracle made it available for US ambulatory providers in August 2025, with acute care planned for 2026. We compare it with your current setup and plan the data and interface work before you decide.

03What changes when Millennium moves to OCI?

Oracle runs the infrastructure. Your team still owns interfaces, reporting extracts, downtime procedures and testing. We list each one and plan the changes with your Oracle contacts.

04Is there a public Oracle Health certification?

We haven't found a public certification program for Millennium. We screen analysts and engineers by the solutions and interfaces they have built and supported.

05Do you also work on Epic?

Yes. Some organizations run both after mergers. We have a separate Epic page that covers Epic's access rules.

services

Related services

Projects on Oracle Health EHR usually end up touching one of these, so they're worth a look.

sources 7 sources linked last checked 2026-10-20 content fingerprint 20db2c6c
  1. 01Oracle: Cerner acquisitionoracle.com ↗
  2. 02Oracle: new era of AI-driven EHRs (13 Aug 2025)oracle.com ↗
  3. 03Oracle: ONC certification of Oracle EHR (18 Nov 2025)oracle.com ↗
  4. 04Oracle: North York General migrates EHR to OCI (25 Apr 2025)oracle.com ↗
  5. 05Oracle: Oracle Health TEFCA QHIN designation (20 Nov 2025)oracle.com ↗
  6. 06Oracle: Clinical AI Agent expansion (19 Aug 2026)oracle.com ↗
  7. 07Oracle Health documentationdocs.oracle.com ↗
Reviewed by the Cohash team Oracle Health EHR is a trademark of its owner, used here to identify the platform. how we handle facts and data →
next step

Tell us what you're running. We'll tell you what we'd do first.

A 30-minute working session with a senior engineer. No slides.

useful to bring
  • The platform and the version you're on
  • Where you need to get to, and by when
  • What's custom: rules, plugins, integrations
  • Any audit finding or deadline driving it