Assort Health and Oracle Health (Cerner): What a Voice Agent Can Reach in Millennium

On the Millennium Platform APIs, using the scheduling resources, with Assort holding the application registration.

Oracle documents FHIR R4 Appointment, Schedule, Slot and Patient resources on the Millennium Platform, with Oracle namespaced scopes and a developer sandbox. A scheduling agent registers an application, requests read scopes for slots and schedules and write scopes for appointments, and is enabled on your tenant. Booking, rescheduling and cancellation then happen through the API with the patient still on the phone. Patient matching uses demographics against the Patient resource, and this is where most scheduling agents differ in quality: a wrong match books the wrong chart.

Oracle offers validated integration status and a marketplace listing to applications that pass its review; Assort does not appear to hold either. Oracle also references API access fees for third party applications; the published amounts were not verifiable in September 2026, so get Oracle's position in writing. Where a vendor cannot use the API for a step, the fallback is robotic process automation on a Millennium session, which works and is fragile across upgrades. Ask which steps use which.

Answers the phone, and the value is measured at the front desk rather than in the chart.

Assort's agent handles inbound calls around the clock: scheduling and rescheduling, intake questions, insurance capture, routing of clinical questions to the right queue, and outbound reminders and recalls. Its published customer outcomes are call centre metrics: a 97 percent reduction in hold time at SENTA, an 89 percent reduction at Chesapeake Health, a 5 percent increase in appointment volume across customers. Those are vendor reported figures and should be read as such.

On Oracle Health the agent's usefulness depends on how much of that it can complete without a person. If slot search and booking are live over the API, a call ends with an appointment in Millennium. If booking is worklisted, a call ends with a task for staff, which still saves hold time and saves less labour. The AI phone agent use case page sets out the metrics to capture, and the patient scheduling page covers the booking rules that have to be encoded before an agent can be trusted with them. Nothing here touches the clinical note, which keeps the governance lighter than an ambient scribe, though patient identity and appointment accuracy carry their own safety weight.

• Application registration and scopes on your Millennium tenant, including Appointment write. At a CommunityWorks or Oracle hosted site that enablement is scheduled by Oracle.
• Scheduling rules. Visit types, durations, provider preferences and location logic have to be explicit before an agent books against them. This is operations work, and it is the part that takes longest.
• Telephony. Call routing from your existing phone system to Assort and back, with fallbacks to staff.
• The business associate agreement. Assort signs one. Settle call recording retention, transcript storage, subprocessors and whether calls train shared models. The HIPAA and AI compliance page covers what to insist on.
• Disclosure and state law. Several states regulate AI that interacts with patients, including disclosure that the caller is speaking to an AI. Check the healthcare AI law checker for your states.

Run a scheduling only pilot with one location and one set of visit types before you widen scope. That sequencing is what a deployment roadmap produces.

Not published, checked September 2026:

• Any Oracle Health or Cerner integration page, reference customer or case study.
• Oracle Healthcare Marketplace listing or validated integration status.
• Which functions use the Millennium APIs and which use robotic automation or staff worklists.
• Patient matching rules and failure handling.
• Pricing, which is on request; the Assort Health pricing page records what is public.

Set against that, Assort's athenahealth integration is well documented and its call volume figures are large, so the company knows how to build against an EHR. The Oracle Health gap is one of published evidence, not necessarily of capability. Close it by asking for a live demonstration on a Millennium sandbox and a reference you can telephone. If neither is available, an Oracle Health practice is an early customer for this pairing and should negotiate as one, with pilot pricing and an exit clause.

1. Show slot search and appointment booking on a Millennium sandbox, and name the FHIR scopes the application uses.
2. Which steps are API driven, which are robotic automation, and which create a task for staff?
3. How is the caller matched to a Millennium patient, and what happens when there is no match or several?
4. Give an Oracle Health reference, or state that we would be the first and price accordingly.
5. Which clearinghouse handles eligibility, and are results written back to Millennium?
6. How are calls recorded, stored and retained, and does any recording train shared models?
7. What is the price per call, per minute or per location, the minimum term, and the exit terms?

Our EHR integration questions for AI agents has the general list in procurement ready form.

A test of the integration claim before you depend on it, and a comparison across the phone agents that do publish Oracle Health work.

Voice agents are a crowded market, and several vendors on our AI phone agents comparison compete with Assort on Millennium sites. They differ on how much of a call they complete without staff, how they match patients, how they handle clinical questions, and what they charge. Our vendor selection service runs that comparison on your call mix and your Millennium configuration with no vendor commission, and it starts by making each vendor demonstrate the integration rather than describe it.

If you are about to sign, book a call first and we will tell you what to get into the contract.