Nabla and Oracle Health (Cerner): What the Integration Actually Does

On the Millennium Platform APIs, with an embedded launch that Nabla has not described in technical detail.

The Aultman release uses the words embedded and natively integrated but does not name the mechanism. On Millennium there are two candidates. A SMART on FHIR launch inside PowerChart puts a third party application in context inside the chart with patient and encounter identity passed through OAuth scopes; this is the path Oracle documents for in workflow applications. An MPages component achieves a similar effect with more build work on the customer side. Ask Nabla which one Aultman uses, because the answer tells you how much of the 60 day build was on Aultman's side.

For the note itself, the release says structured notes with ICD-10 codes flow directly into the electronic health record. Whether that is a write into DynamicDocumentation, the surface where Millennium clinicians edit notes, or a document delivered into the record for review, is not stated. Ambience has published that its output lands in DynDoc and is editable in Note Viewer; Nabla should be asked to match that specificity.

Application registration follows Oracle's developer programme: register the app, request FHIR R4 scopes with Oracle's namespacing, test in the sandbox, enable on the customer tenant. Oracle offers a validated integration status and an Oracle Healthcare Marketplace listing to applications that pass its review. We could not confirm a Nabla listing in September 2026. That does not disprove the integration, which Aultman demonstrates, but it means the Oracle side of the validation is something to ask for. Oracle also references API access fees for third party applications; get that position from your Oracle account team in writing.

Captures the encounter, drafts a structured note, and attaches codes.

• Context. The clinician opens Nabla in the workflow with the patient already identified, so recording starts against the right encounter.
• Note. After the visit Nabla produces a note structured to the clinician's template, with history of present illness, examination, assessment and plan. Aultman highlighted chronic disease documentation being organised automatically.
• Codes. ICD-10 codes are embedded in the note. This is the item that brings coding and compliance into the approval, because a suggested diagnosis code influences the claim even when a clinician confirms it.
• Dictation and commands. Nabla supports dictation and natural language edits to the draft; whether those work inside Millennium or only in the Nabla surface is a question for the demo.

The measurements that matter in a pilot are time to signed note, edit rate per section and after hours documentation time. The ambient scribe use case page sets out how to capture them, and the coding element should be validated separately using the approach on the medical coding automation page.

Four approvals in parallel, and a fifth if codes are turned on.

The application registration on your Millennium tenant with the scopes Nabla requests. The embedded launch, which changes what clinicians see and therefore needs clinical informatics sign off and a build slot; at an Oracle hosted or CommunityWorks site that slot is scheduled by Oracle. The business associate agreement, which Nabla signs and which should settle audio and transcript retention, subprocessors and model training in week one; the HIPAA and AI compliance page lists what to insist on. A security review that covers device management for any mobile use, where audio is processed, and access logging.

The fifth is coding governance. If ICD-10 codes are embedded in the note, your compliance officer and coding lead need to agree how they are presented, who accepts them, and how acceptance is audited. Aultman's 60 day timeline is achievable when these run together with named owners; it is not achievable when each waits for the last. Our HIPAA compliant AI scribe checklist is the shortest way to make sure the compliance items are not left until the end.

Not published, checked September 2026:

• The launch mechanism at Aultman (SMART launch, MPages component or other) and how much of the build sat with the customer.
• The Millennium document type the note is written to, and whether it is editable in Note Viewer.
• An Oracle Healthcare Marketplace listing or validated integration status.
• Oracle Health references other than Aultman, and any at a CommunityWorks hospital.
• Organisation pricing. Nabla publishes an individual clinician plan and prices organisations on request; the Nabla pricing page records what is public.

And the first party question applies here as everywhere on this platform. Oracle sells its own Clinical AI Agent into the same workflow and has bundled it with CommunityWorks in some community hospital contracts. Nabla's proposition is a fast, embedded deployment at a competitive price; that argument is strong against a paid competitor and weaker against a bundled one. Find out in writing what Oracle is putting in your contract before you run a Nabla pilot.

1. Which launch mechanism does Aultman use, and what did Aultman's team build?
2. Which Millennium document type does the note land in? Show it on our code level, edited in Note Viewer.
3. List the FHIR scopes the Nabla application requests on Oracle Health.
4. Give a second and third Oracle Health reference, including one on our hosting model.
5. Can ICD-10 embedding be switched off for the pilot, and how are accepted codes audited?
6. Where is audio processed and stored, for how long, and does any of it train shared models?
7. What is the organisation price per clinician, the minimum term, and are Oracle API fees included?

Our EHR integration questions for AI agents has the full list in a form you can paste into a request for proposal.

A comparison on your encounters, and a check that a single strong reference generalises to your hospital.

Nabla's Aultman deployment is a genuine production proof on Millennium, and it is one site. Ambience has published a DynDoc write back with several named systems, Suki holds an Oracle marketplace listing, and Oracle's own product arrives with the platform. They differ on launch, note landing, coding, audio handling and price, and those differences decide whether clinicians are still using the tool at month six. Our AI medical scribe comparison sets them side by side, and our vendor selection service runs the evaluation on your instance and your specialties with no commission from any vendor.

If you have a shortlist and a date, book a call and we will tell you what to get into the contract first.