Referral intake, eligibility, and prior auth, done inside Oracle Health (Cerner)
Saga is live with organizations on Oracle Health (formerly Cerner). Its AI agents read inbound referrals and records, file them to the right chart, verify eligibility in real time, and submit and track prior authorizations inside Oracle Health through user access your team controls, with no API integration.
Built for → Health systems · Hospitals · Multi-site groups · Radiology & imaging
Patient access teams are re-keying what already arrived.
Referrals, orders, and records reach Oracle Health organizations by fax and portal every day. Staff still read each one, re-key it, verify coverage, and chase authorizations by hand, and every handoff is a chance for a patient to stall.
How Saga works in Oracle Health (Cerner)
Signs in like a staff member
Saga works in Oracle Health (Cerner) through a user account your organization provisions, using the same screens your team uses. No API integration or IT project is required.
Reads every inbound document
Referrals, faxes, orders, and records are read from your eFax inbox, from documents forwarded to Saga, or from the EHR’s incoming document queue.
Files to the right chart
Saga matches each document to the patient, or creates the new patient record, and writes structured data and the source document to Oracle Health (Cerner).
Verifies coverage
Real-time X12 270/271 eligibility checks confirm coverage and benefits, and the results are recorded to the chart before the visit.
Submits and tracks prior auths
Saga assembles requests from the Oracle Health (Cerner) chart, submits them through payer portals, and writes decisions back.
Routes exceptions to staff
Denials, appeals, and out-of-network cases wait in a review inbox for sign-off, and every task has a complete audit trail.
What Saga handles in Oracle Health (Cerner)
- New-patient referrals and referral packets
- Orders, records, and other inbound faxes
- Patient matching and new patient creation
- Real-time eligibility and benefits recorded to the chart
- Prior authorizations across medical, pharmacy, and DME benefits
- Requests for missing documentation, tracked to completion
Related: Referral intake · Eligibility verification · Prior authorization
Fewer hours on paperwork. More capacity for patients.
Saga and Oracle Health (Cerner)
Does Saga work with Oracle Health, formerly Cerner?
Yes. Saga runs in production for organizations on Oracle Health (Cerner), handling referral intake, eligibility verification, and prior authorization.
Does Saga need an Oracle Health API integration?
No. Saga works through user access your organization provisions and governs, the same way staff do, so there is no API integration to build or maintain.
What does a practice need to provide to use Saga with Oracle Health (Cerner)?
A Oracle Health (Cerner) user account for the agent, routing for inbound faxes or referrals, and your SOPs and payer rules. Saga typically goes live in under a month.
Does a person review what Saga does?
Yes. Each practice chooses which actions need staff sign-off, and denials, appeals, and out-of-network cases always do. Items awaiting approval sit in a review inbox, and every completed task has a full audit trail.
Comparing options? See how Saga compares with fax OCR, RPA, and outsourced intake →
See Saga working in Oracle Health (Cerner).
Live in under a month · writes back to your EHR · your data stays yours