Updates for offices that will never be on Millennium
A visit closes, a patient is discharged, a referral is accepted. When a visit closes, the referring office gets its update by fax, email or portal note without a nurse calling them.
Oracle bought Cerner in 2022 and has been moving everything to the Oracle Health name since. The clinical record underneath is still Millennium, the developer console is still at a cerner.com address, and staff at many community hospitals still say Cerner. What hasn't changed is the work around it: referral updates to outside offices, and reports that need numbers the platform doesn't hold.
Staff still call it Cerner. The clinical record is solid, but intake and outside systems still need integration around it.
Stuck on Oracle Health? Let's solve it →Same business, new name. Oracle Health is the current name for the Cerner business. The core EHR is the Millennium Platform. Smaller and community hospitals often run it hosted, through CommunityWorks.
For developers: the Cerner developer program is now the Oracle Health Developer Program. You still register in code Console with a CernerCare account, and the FHIR APIs are documented as Millennium Platform APIs. Oracle has retired DSTU2, so build on R4.
Oracle splits apps by who uses them, and the two kinds take different paths.
A consumer app is used by patients to pull their own records. A provider or system app is used by clinicians, or runs as a backend service with no user. The rest of the process depends on this choice.
Accept Oracle's terms for its health APIs, sign in with a CernerCare account (you can create one on first use), and register the app with the scopes it needs.
Oracle runs open and secure sandboxes for testing authorization and the scopes you declared. Use R4. For population exports, register a separate Millennium Bulk Data SMART app.
Watch for: consumer apps are switched on for every active Millennium and Soarian Clinicals consumer endpoint once registered. Provider and system apps are not.
Oracle asks you to document what your app does that the platform doesn't, and to show a working demo against a sandbox. After that the app is visible to Oracle Health clients to consider.
A client that wants your app provisions it in its own environment, through its IT team and Oracle. Plan for its security review and its testing window, which set the real timeline.
Watch for: Oracle Validated Integration, through Oracle PartnerNetwork, is optional. Its fees buy extra services; Oracle says they aren't required to develop or deploy an app.
A visit closes, a patient is discharged, a referral is accepted. When a visit closes, the referring office gets its update by fax, email or portal note without a nurse calling them.
Clinical and operational extracts from the platform, lined up with billing, staffing or a referral CRM, refreshed on a schedule rather than rebuilt in a spreadsheet each month.
If you're the one building for Millennium hospitals, n-frames builds the FHIR client, the gap analysis Oracle asks for, and what your product does with the data once a hospital switches you on.
Multi-clinic health group · Oracle Health as the record · outside offices sending patients in
Referring offices called the front desks every day to ask whether their patient had been seen. The answer was already in the system, but nobody's job was to send it.
When a visit is completed, the referring office gets a status update automatically.
The daily status calls from referring offices stopped.
Oracle Health is Oracle's healthcare business and the name now used for the EHR built on Cerner's Millennium clinical record. Oracle completed its purchase of Cerner in 2022 and has been rebranding the products and moving parts of them onto Oracle's own cloud since.
It's the same platform with a new owner and name. Long-time staff still call it Cerner or Millennium, and several developer tools, such as code Console and CernerCare accounts, still carry the Cerner name.
Both are enterprise EHRs covering clinical, scheduling and billing work for hospitals. Cerner built a strong base among community and mid-sized hospitals, partly through CommunityWorks, while Epic leads among large academic and multi-specialty systems. For integration the pattern is similar: standards-based FHIR APIs, plus each hospital deciding what to switch on. Our Epic API page covers that side.
Yes, through HL7 interfaces and the Millennium Platform FHIR APIs. Patient-facing apps are enabled broadly once registered; clinician and backend apps need each hospital to provision them. That's the channel n-frames builds through: a hospital's own IT, or its Oracle-certified analysts, approves the access, and we build what uses it.
Oracle doesn't publish EHR pricing. It's quoted per organization, based on size, modules and whether it's hosted, for example through CommunityWorks. On the developer side, registering an app and using the APIs doesn't require Oracle's paid partner services.
No. Oracle's terms let any developer register in code Console and build. PartnerNetwork membership and Oracle Validated Integration are optional extras that come with added services and marketing rights.