Referral intake, eligibility, and prior auth, done inside eClinicalWorks
Saga is live with practices on eClinicalWorks. Routing a fax is only the first step; Saga reads each referral, matches or creates the patient, files structured data to the eClinicalWorks chart, verifies eligibility, and submits and tracks prior authorizations, with no API integration.
Built for → Orthopedics & ASCs · Radiology & imaging · Infusion · Behavioral health
Routing a fax isn’t the same as finishing the referral.
Fax tools can sort documents into the right place, but someone still has to read each referral, find or create the patient, key demographics and insurance, check what’s missing, and start the prior auth. That’s where eClinicalWorks practices lose hours.
How Saga works in eClinicalWorks
Signs in like a staff member
Saga works in eClinicalWorks 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 eClinicalWorks.
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 eClinicalWorks 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 eClinicalWorks
- 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 eClinicalWorks
Does Saga replace our eClinicalWorks fax tools?
No. Saga works with documents wherever they arrive: your eFax inbox, documents forwarded to Saga, or the EHR’s incoming document queue. It then completes the referral in eClinicalWorks.
Is Saga live on eClinicalWorks today?
Yes. Saga runs in production for practices on eClinicalWorks, working through a user account rather than an API integration.
What does a practice need to provide to use Saga with eClinicalWorks?
A eClinicalWorks 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 eClinicalWorks.
Live in under a month · writes back to your EHR · your data stays yours