Waystar and Oracle Health: How Claims and Eligibility Data Flow From Millennium

On interfaces between Millennium patient accounting and Waystar's clearinghouse, mostly HL7 and X12, with the newer AI features running on Waystar's side of that line.

Revenue cycle integrations on Millennium are older than the FHIR APIs and look different. Claims leave the patient accounting module as 837 files, remittances return as 835 files, eligibility runs as 270 and 271 transactions, and claim status as 276 and 277. Waystar sits between Millennium and more than 5,000 payer connections, scrubs claims against its edit library, routes them, and returns responses. Where the interface is configured for it, remits and status post back into Millennium automatically; where it is not, staff work Waystar's queues and key the result.

The point of the table is the last column. Every row has an owner on your side, and at a CommunityWorks hospital some of those interfaces are Oracle's to change. Ask Waystar which rows are live at a reference site like yours, not which rows exist.

Three things that matter and one that is newer.

It cleans and routes claims. Waystar publishes a 98.5 percent or better average clean claim rate and a library of 2.5 million continuously updated edits on its MEDITECH page; the same engine serves Millennium customers. It automates eligibility and coverage detection at the front end, which is where preventable denials start. And it posts remits and works denials with AI driven prioritisation and appeal automation. Those three are the core of revenue cycle automation and denial management, and they have been in production on Cerner sites for a long time.

The newer item is prior authorization. Waystar sells authorisation automation that checks whether an auth is required, submits through payer portals and tracks status. On Millennium the trigger is an order or a scheduled procedure, and how that trigger reaches Waystar, whether by interface or by worklist, decides how automated it really is. The prior authorization automation page sets out what to measure, and the prior auth cost calculator shows what the manual process is costing you now.

• Interface changes on Millennium. Any new or modified 837, 835, 270/271 or HL7 feed is an interface analyst task. At an Oracle hosted or CommunityWorks site, that work is requested from Oracle and sits in Oracle's queue.
• The business associate agreement. Waystar signs one. Claims data is protected health information; settle retention, subprocessors and how AI features use your data. The HIPAA and AI compliance page lists what to insist on.
• Payer enrolments. Moving clearinghouses means re-enrolling with payers for electronic remits and eligibility. This is calendar time, not engineering time, and it is the step that slips.
• Governance for automated actions. A denial appeal or an authorisation submission generated by AI is an action with a payer, not a draft. Your compliance officer should agree what is auto submitted and what a person reviews, and the CMS prior authorization rule is changing payer behaviour on the other side of that transaction through 2026 and 2027.

Run these in parallel with named owners. A deployment roadmap is how you keep payer enrolment and interface work from serialising.

Not published, checked September 2026:

• A transaction level statement of what is automated in each direction on Millennium versus worked in Waystar queues.
• Oracle Healthcare Marketplace listing or current Oracle partner status.
• Pricing. Waystar prices on request against claim or transaction volume; the Waystar pricing page records what is public.
• Which AI features are available on Cerner sites specifically, and whether prior authorization automation is interfaced to Millennium orders or driven from a worklist.

There is also an Oracle side question. Oracle sells revenue cycle products of its own and is rebuilding its EHR with AI throughout, including patient accounting. Waystar's position is that it is payer agnostic and best of breed; Oracle's is that a single vendor is simpler. Neither is wrong, but you should know which argument your Oracle account team is going to make before you sign a multi year Waystar agreement.

1. For each transaction in the table above, is it interfaced, batch or manual at a reference Millennium site of our size?
2. Which interfaces need to change on our instance, and who makes the change on our hosting model?
3. How long does payer re-enrolment take for our top twenty payers, and who does it?
4. Which AI features (denial prioritisation, appeal drafting, authorisation automation) are live on Cerner customers today, and how are automated submissions reviewed?
5. What is the price per claim or per transaction, the minimum, and the term? What happens to the rate as volume grows?
6. What does the exit look like: how do we get our claim history and remits out, and in what format?

Our EHR integration questions for AI agents covers the general list; the revenue cycle specific items are the ones above.

A denial and days in accounts receivable baseline that is yours, and a comparison that is not run by a clearinghouse.

Waystar is a strong default on Millennium, and defaults are where money leaks. Availity, Oracle's own revenue cycle stack and specialist prior authorization tools all overlap with parts of what Waystar sells, and the right answer depends on your payer mix, your denial profile and how much interface capacity you have. Start with the denial rate benchmark and the days in AR benchmark to see where you stand, read the prior authorization software comparison for the authorisation piece, and use our vendor selection service if you want the evaluation run on your numbers with no vendor commission.

If you have a renewal date, book a call before it and we will tell you what to negotiate.