Skip to content
◆ Saga for Epic

Referral intake, eligibility, and prior auth, done inside Epic

Saga is live with organizations on Epic. Its AI agents work referral, eligibility, and prior authorization tasks in Epic through user access your organization grants and controls. They read inbound documents, file them to the right chart, verify coverage in real time, and submit and track prior auths, with no API integration.

Built for → Health systems · Multi-site groups · Orthopedics & ASCs · Radiology & imaging

The problem

Work queues grow faster than central teams can staff them.

Referral, authorization, and records work queues in Epic organizations keep growing. Every item still needs someone to read the document, check the chart and coverage, and act in Epic and the payer portal, and hiring can’t keep pace.

How it works

How Saga works in Epic

01

Signs in like a staff member

Saga works in Epic through a user account your organization provisions, using the same screens your team uses. No API integration or IT project is required.

02

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.

03

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 Epic.

04

Verifies coverage

Real-time X12 270/271 eligibility checks confirm coverage and benefits, and the results are recorded to the chart before the visit.

05

Submits and tracks prior auths

Saga assembles requests from the Epic chart, submits them through payer portals, and writes decisions back.

06

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.

Coverage

What Saga handles in Epic

  • 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

Results

Fewer hours on paperwork. More capacity for patients.

94%
Less manual back-office work
48%
Increase in labor capacity
Aggregate results across early multi-site deployments; your figures are modeled against your own volumes during onboarding.
Questions

Saga and Epic

Does Saga need an Epic API or App Market listing?

No. Saga works in Epic through user access your organization provisions and governs under your existing security and access policies, so there is no API project to stand up.

Can we limit what Saga is allowed to do in Epic?

Yes. Saga acts only with the access you grant its user account, and your organization chooses which actions need staff sign-off. Denials, appeals, and out-of-network cases always do.

What does a practice need to provide to use Saga with Epic?

A Epic 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 Epic.

Live in under a month · writes back to your EHR · your data stays yours