Does Suki Work With Oracle Health (Cerner)?

On the Millennium Platform APIs, with Suki holding the app registration.

Oracle's developer programme is the only supported way for a third party to reach a Millennium instance programmatically. A vendor registers an application, builds against FHIR R4 with Oracle namespaced scopes, tests in Oracle's sandbox, and can then submit for validated integration status and a listing on the Oracle Healthcare Marketplace. Oracle describes validation as a review of security and functional use of the APIs. Suki's listing is the outcome of that process.

The listing describes Suki Assistant as available through a native mobile or tablet app and a desktop app. That is a useful tell. A SMART on FHIR launch inside the Millennium chart, which is the path that puts an application in context inside PowerChart, is not something Suki's public page claims for Oracle Health. In practice, most Suki deployments run the Suki app beside the chart, with schedule and patient context pulled through the APIs so the clinician does not have to search for the encounter. Ask whether an in chart launch is available on your Millennium version, and if the answer is a roadmap date, plan on the app beside the chart.

Suki says implementation typically takes eight to twelve weeks and that your team's part is to provide sandbox accounts, support configuration and testing, and confirm wireless coverage. Those three items are honest, but the sandbox account request goes through your Oracle Health account team, and at a CommunityWorks hospital that step is Oracle's to schedule rather than yours. Oracle's developer pages reference API access fees; the published amounts were not verifiable in September 2026, so get the position in writing from Oracle before you sign with Suki.

Three things, in order of how much integration each one needs.

• Reads the schedule and patient context. The clinician opens Suki, sees the day's encounters, and starts recording against the right patient. This is a read over the APIs and it is the part that works everywhere.
• Generates a draft note and returns it. After the visit, Suki produces a structured note. It is then sent to Oracle Health for the clinician to review and sign. Whether it arrives as an editable document in the note workflow or as a completed document to be reviewed is the question Suki's page does not answer.
• Dictation and coding suggestions. Suki's dictation works at the cursor in the desktop app. Coding suggestions are generated from the note and, on the public material, are surfaced in Suki rather than pushed into Millennium's charge workflow.

For a buyer, the practical question is who touches the note after Suki produces it. If it lands as an editable document, the clinician finishes in the chart. If it lands as a finished document, edits happen in Suki and the note is resent, which is a workflow clinicians tolerate less well. The ambient scribe use case page covers what to measure in a pilot, and the answer here changes the measurements.

Four approvals, and they run on separate clocks.

First, the application registration on your Millennium instance. Suki's app has to be enabled for your tenant with the scopes it requests. Ask Suki to list those scopes; a vendor that has genuinely built on the platform can do this without a meeting.

Second, the business associate agreement. Suki states it signs one. Get it moving in week one, in parallel with the technical work, because the agreement is where you settle audio retention, transcript retention, subprocessors and model training. The HIPAA and AI compliance page sets out what to insist on and what is negotiable.

Third, a security review that goes beyond a questionnaire. An ambient scribe records clinical encounters, which is a different risk from a scheduling widget. Cover device management for the mobile app, where audio is processed, and how long it persists.

Fourth, the clinical informatics sign off on what the note looks like when it arrives and who validates it against real encounters. Set the number of encounters and the specialties in advance, and use our HIPAA compliant AI scribe checklist to make sure the compliance items are not left to the end.

Not published, checked September 2026, and therefore questions for the vendor:

• Which Millennium document type the note is written to, and whether it is editable in the note workflow or reviewed as a completed document.
• Whether an in chart SMART launch is available for Oracle Health or whether the app runs beside the chart only.
• Whether Oracle Health specific reference customers exist at hospitals of your size and hosting model.
• Whether coding suggestions reach the Millennium charge workflow or stay in Suki.
• What Suki pays Oracle for API access, if anything, and whether that is passed through in your subscription.

Two further points. Oracle sells its own Clinical AI Agent into the same workflow and has bundled it with CommunityWorks in some community hospital deals. Before you run a Suki pilot, find out in writing whether Oracle's product is arriving in your contract anyway, because that changes the comparison. And Suki's Oracle marketplace listing quotes an average of 1,688 USD in incremental monthly revenue per user; that is a vendor figure, not an independent one, and the ROI calculator will let you test it against your own visit volumes.

Put these in the request for proposal, not in the demo.

1. Name the Millennium document type and note workflow the draft lands in. Show it on our Millennium version.
2. List the FHIR scopes the Suki application requests on Oracle Health.
3. Is there an in chart launch, and on which Millennium code level?
4. Give three Oracle Health references, including one CommunityWorks or Oracle hosted site.
5. Where is audio processed and stored, for how long, and is any of it used to train shared models?
6. What does the subscription cost per clinician, what is the minimum term, and are Oracle API fees included? The Suki pricing page records what is public.
7. What is the exit: how do we get transcripts and notes out, and what is deleted when?

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

Two things a vendor demo cannot give you: a comparison run on your encounters, and a decision made before the contract rather than after.

Suki is one of at least four ambient scribes with a credible Oracle Health integration, alongside Ambience, Nabla and Oracle's own Clinical AI Agent, with Microsoft and Abridge running shallower paths. They differ on where the note lands, how the app launches, what they cost, and how they handle audio. Those differences do not show in a demo and do show in month three. Our AI medical scribe comparison sets them side by side, and our vendor selection service runs the evaluation on your Millennium instance, your specialties and your hosting model, with no commission from any vendor.

If you have a shortlist and a signature date, book a call and we will tell you what to ask for in the contract before you sign it.