Pain Point, Solved 4.9 ★★★★★ Google Rating

Why Do Faxed and Incoming Referrals Sit Unscheduled in Epic Referral Work Queues?

All Pain Points

Ask AI about this page

Faxed and incoming referrals sit unscheduled in Epic work queues because Epic routes any referral missing a required field, referring provider, diagnosis, or insurance, to the Incoming Referrals Incomplete Information work queue, and that referral cannot move to scheduling until someone completes the record. The trouble is that most front desks have no one assigned to work that queue, so referrals age there while everyone assumes they are in the normal workflow. It is not an Epic defect; it is working as designed, the design just requires a human to chase the missing data, and that human is usually absent. The fix has four moves: work the incomplete-information queue every morning, chase the referring office for the missing field, complete the record so Epic routes it into the normal flow, and flag urgent referrals for same-day scheduling. We run those moves inside your Epic instance, so the referrals you were sent actually reach a schedule instead of aging out. The table of contents maps the whole method; the moves after it are the detail.

How to Clear the Epic Incomplete-Information Referral Queue
Key Pain Points and Discussions by Providers
Why This Keeps Happening
The Solution
How We Permanently Fix the Process
The Whole Thing in Four Sentences
Frequently Asked Questions
Where the Claims on This Page Come From

How to Clear the Epic Incomplete-Information Referral Queue

The goal is simple: every incoming referral either scheduled or actively chased for the one field it is missing, every day, so nothing ages silently. Here is what does that, move by move.

1. Assign the Incomplete-Information Queue an Owner

The first move is the one most practices skip: give the Incoming Referrals Incomplete Information work queue a named owner who works it every morning. Epic will keep routing incomplete referrals there whether or not anyone is watching, so an unowned queue is just a place referrals go to disappear. The moment someone owns it, the queue changes from a black hole into a daily task list, and referrals stop aging past the point where the patient gives up on you.

2. Read the Record for the One Field That Is Missing

A referral lands in this queue for a specific reason: no referring provider on file, no diagnosis code, no insurance, or a demographic that will not match a chart. Before chasing anything, open the record and identify exactly which required field is blocking it. Most incomplete referrals are missing one or two data points, not the whole packet, and knowing which one turns a vague follow-up into a targeted call to the referring office for the single thing Epic needs to release it.

3. Chase the Referring Office for the Missing Data

Once you know the gap, close it at the source. Call or message the referring office for the diagnosis, the provider NPI, or the insurance that is missing, and enter it into the referral record. This is the step that actually moves the referral: as soon as the record is complete, Epic drops it off the incomplete-information queue and routes it through the normal incoming-referrals workflow, where a scheduler can finally see it. The chase is the whole job, and it is exactly the job an unassigned queue never does.

4. Flag Urgent Referrals for Same-Day Scheduling

Not every referral can wait its turn. A suspected cancer, a post-procedure follow-up, a time-sensitive specialty consult, these cannot age two weeks in a queue while someone gets to them. As the queue is worked each morning, urgent referrals get pulled forward and handed straight to scheduling for a same-day or next-day slot. Triaging urgency inside the queue is what keeps the sickest patients from being the ones who wait longest, which is the worst version of this failure.

5. Hand the Referral Queue to a Dedicated Remote Coordinator

Specialty clinics that stop losing referred patients do it by handing the incomplete-information queue to a dedicated remote coordinator who works it inside Epic every morning, chases the missing data, completes the record, and flags urgent cases, live in 1 to 2 weeks. The in-office team goes back to the patients in the building, a trained backup covers every gap, and the queue nobody owned becomes a queue that gets cleared daily. Below is what it sounds like when that queue has no owner yet, in specialty teams’ own words.

Key Pain Points and Discussions by Providers

real reports from practice staff, lightly edited

“We found referrals aging two to three weeks in the incomplete-information queue. The patients assumed we never got the referral and several had already booked with the group across town. We did not lose them on care or on wait time. We lost them because a queue in our own system had nobody assigned to it.” – practice administrator, specialty clinic

“Epic did exactly what it is supposed to do. The referral came in missing an insurance, so it parked in the incomplete queue until someone completed it. The problem was that someone was nobody. It sat there working as designed and quietly dying.” – referral coordinator, GI clinic

“Our schedulers only see referrals that made it to the normal workflow. The ones stuck in the incomplete queue are invisible to them, so from their chair the schedule looked fine while a two-week backlog of referred patients was aging where they could not see it.” – front desk lead, cardiology practice

“The worst part was the urgent ones. A time-sensitive referral has no special lane in that queue, it just sits with everything else. We only realized when a patient who needed to be seen fast had been waiting eleven days in a work queue nobody opened.” – office manager, orthopedic clinic

“Every time our one referral person was out, the incomplete queue just stopped. Nobody else knew it existed. She came back to two hundred referrals and a stack of patients who had already gone elsewhere while she was on leave.” – practice manager, hospital-affiliated specialty group

Our Answer

Here is what we actually do. A dedicated remote coordinator works your Epic Incoming Referrals Incomplete Information work queue every morning: opens each stalled referral, identifies the exact field Epic is waiting on, chases the referring office for the missing provider, diagnosis, or insurance, and completes the record so Epic routes it into the normal incoming-referrals workflow where a scheduler can finally see it. Urgent referrals get pulled forward and handed straight to scheduling for a same-day slot. Our coordinators are credentialed medical professionals, overseas-trained physicians and US-licensed nurses, trained in Epic referral workflows, working inside your instance with AI drafting the first pass and a human verifying every record. Within the first weeks the queue that used to age referrals silently gets cleared daily. This is our remote referral and scheduling support, in one paragraph.

Why This Keeps Happening

If Epic is working correctly, why do referred patients still fall through? Because the design assumes a human is watching the queue, and often no human is. When an incoming referral arrives missing a required field, referring provider, diagnosis, or insurance, Epic routes it to the Incoming Referrals Incomplete Information work queue and holds it there until the record is completed. Once completed, it falls off the queue and flows normally. That is the system doing exactly what it should. The failure is organizational: the queue needs a daily owner to chase the missing data, and at most front desks that role was never assigned, so the referrals age in a place the schedulers never look.

The stakes are higher than a slow queue, because incomplete referrals turn directly into referral leakage. When a referral is not managed, patients skip the visit or seek care elsewhere, and MGMA has documented referral management failures and authorization bottlenecks as leading sources of front-end revenue loss, with a large share of referrals never completed at all. A referral stuck in the incomplete queue for two to three weeks is a patient who concludes you never received it and books with the competitor who called them back. You were handed the patient and lost them to a data-entry gap, which is exactly the failure a dedicated virtual medical assistant working the queue is built to prevent.

And the damage compounds because the invisible referrals are often the urgent ones. The incomplete-information queue does not sort by clinical acuity; a suspected malignancy sits next to a routine follow-up, both aging at the same rate, both invisible to the scheduler. So the patient who most needed to be seen fast can be the one who waits longest, purely because their referral happened to arrive missing a field. When your one referral coordinator is out, the queue stops entirely, and they return to hundreds of aged referrals and a stack of patients already seen elsewhere. The cost is not just revenue, it is a delayed answer for the patient who could least afford the wait.

⚠️ The quiet one that hurts most: The quiet one that hurts most: the queue is invisible to the people who would notice. Schedulers only see referrals that reached the normal workflow, so from their chair the schedule looks healthy while a backlog of referred patients ages in a work queue they cannot see. Nobody complains, because the patient assumes the referral was never received and simply goes elsewhere. There is no error message, no bounced fax, no alert, just a slowly growing pile of patients you were handed and quietly lost. Unless the incomplete-information queue has a named owner working it every day, the referrals you are losing are the ones nobody in your building even knows are stuck.

Most groups have already tried the obvious fixes before they talk to anyone. Each one fails the same way: the work lands back on the practice. The pattern, in one table:

What you tried	What actually happened	Who ended up doing the work
Assumed the referral fax meant the patient was in the workflow	Referrals missing a field parked in the incomplete queue, invisible to schedulers, aging for weeks	Nobody, the queue had no owner
Asked schedulers to keep an eye on referrals	Schedulers only see the normal workflow; the incomplete queue never reached their screen	A queue outside anyone’s view
Left the queue to one referral coordinator	It stopped every time she was out, then buried her with a backlog on her return	One person with no backup
Gave the incomplete queue to a dedicated remote coordinator	Worked every morning, missing data chased, records completed, urgent referrals flagged same day	Someone whose whole job it is

The Solution

So what does owning the queue actually look like inside Epic? Every morning a dedicated coordinator opens the Incoming Referrals Incomplete Information work queue and works it top to bottom. For each stalled referral they identify the one field Epic is holding on, the missing provider, diagnosis, or insurance, and they chase it at the source, calling or messaging the referring office and entering the data. The moment the record is complete, Epic drops the referral off the incomplete queue and into the normal flow, where a scheduler can see and book it. That daily clear is exactly what dedicated remote referral and scheduling support is built to deliver.

The second thing the coordinator does is triage. As the queue is worked, urgent referrals, a suspected malignancy, a post-procedure follow-up, a time-sensitive consult, get pulled forward and handed straight to scheduling for a same-day or next-day slot instead of aging with everything else. The queue stops sorting patients by the accident of which field their referral was missing and starts sorting them by how fast they need to be seen. That is the difference between a queue that quietly harms your sickest referrals and one that protects them.

Behind all of it, AI takes the first pass and a credentialed human verifies. The workflow reads each incomplete referral, identifies the missing field, and drafts the outreach to the referring office; a person confirms the record is right and owns the urgent flags. Because that work moves real referral and chart data through your Epic instance, every security control protecting it is documented and auditable, and the whole approach is described on our HIPAA and security page, because working a referral queue inside your EHR is only safe when the controls behind the access are real.

Who Actually Does This Work

Fair question: why would an outsourced coordinator work your Epic referral queue better than your own front desk? Because that queue is their entire morning, not the task they get to after the lobby clears. The people working your referrals are credentialed medical professionals: overseas-trained physicians and US-licensed nurses, trained in Epic referral workflows and the incoming-referrals lifecycle. They know exactly why a referral lands in the incomplete-information queue, which field to chase, and how to complete the record so Epic releases it into scheduling. That is not a task to squeeze between check-ins; it is the whole job, worked every day it needs working.

We are not a call center. We are a clinical operations partner, a healthcare BPO built on dedicated virtual staff: 500+ credentialed professionals, 24/7 coverage, and the AI-first-pass plus human-verify workflow you just read about behind every one of them. A typical practice is live in 1 to 2 weeks, at up to 70% below the cost of hiring locally, and no one on our side goes out without a trained backup already inside your Epic workflow, so the incomplete-information queue never stops because the one person who works it is on leave.

And the security piece your compliance officer will ask about: we are audited to SOC 2 Type II with zero exceptions and certified for ISO/IEC 27001:2022, HIPAA, and GDPR, with zero breaches in eight years. Every workstation runs inside a secure enclave on US-based servers, with screen captures and downloads blocked by policy, so PHI never sits on someone’s home laptop. Every client account carries a $5M E&O and cyber liability policy and a BAA signed before any work starts; the full detail lives in our HIPAA and security posture.

Put the routine and the people together, and a specific list of things simply stops happening.

✓ What stops happening: What stops happening: referrals aging two to three weeks in a queue nobody opened. Patients assuming you never got the referral and booking with the group across town. Urgent referrals waiting eleven days behind routine ones with no special lane. A scheduler’s screen that looks healthy while a backlog ages out of view. The one referral coordinator returning from leave to two hundred stalled records and a stack of patients already seen elsewhere.

2-Week Free Trial

Ready to Clear Your Referral Queue?

Book A Strategy Call Request Information

How We Permanently Fix the Process

A person alone is not the fix, and neither is a bot alone. The fix is a documented referral workflow that names the incomplete-information queue as an owned, daily task: who works it, in what order, which fields to chase, how to reach each common referring office, and how urgent referrals get pulled forward. Before we take a single referral for a new clinic, we review your Epic queue to see how deep the backlog runs and which referring sources most often send incomplete data, and we build the workflow against your real referral sources, not a generic template.

From there the workflow becomes a living playbook rather than tribal knowledge in one coordinator’s head. It records which field each referring office tends to omit, the fastest way to reach them, how the record is completed to release it into scheduling, and the escalation path for an urgent referral. It is written down, kept current, and owned by the team. When your coordinator is out, a trained backup works the same queue the same way, so the incomplete-information queue never stops and no referred patient ages out because one person was on leave.

That is the difference between clearing this week’s backlog and fixing the process for good, and it is what dedicated virtual medical assistant coverage actually buys you. A coordinator leaving used to mean the queue went dark and referred patients started drifting to competitors. Under this model the queue keeps getting worked, the playbook stays, the backup steps in, and an incomplete referral stops being the quiet reason you lose patients you were handed.

The Whole Thing in Four Sentences

Faxed and incoming referrals sit unscheduled in Epic because the system routes any referral missing a required field, provider, diagnosis, or insurance, to the Incoming Referrals Incomplete Information work queue, and it cannot move to scheduling until someone completes the record. That is Epic working as designed; the failure is that most front desks assign no one to work the queue, so referrals age invisibly while schedulers see only the normal workflow. Assuming the fax meant the patient was booked, or leaving the queue to one coordinator with no backup, both fail the same way. The fix is a daily owner who chases the missing data, completes the record, and flags urgent referrals for same-day scheduling. A hospital-affiliated specialty group runs exactly this model with us today, names withheld, no patient data shown.

If you want to check us out before talking to anyone: our security posture is independently auditable, we are an MGMA 2026 Corporate Member, and 800+ providers run back office work with us.

Ready to clear your referral queue? Try us risk free: two weeks, your real Epic incomplete-information queue, a dedicated coordinator chasing the missing data and completing the records, and if it does not earn the handoff, you walk away. From here down is the sales part, and it is short: here is exactly what it costs.

Transparent Weekly Pricing

One Flat Weekly Rate. 45 Hours of Coverage.

No hourly meters, no setup fees, no long-term contracts. Your dedicated team member covers your desk 45 hours every week, and a trained backup steps in at no charge whenever they are out.

Single

$399/ week

One dedicated remote coordinator working your Epic incomplete-information referral work queue daily, single hospital-affiliated specialty clinic

Clear Your Epic Referral Queue This Month

You have seen the whole method. The pilot proves it on your own incomplete-information queue, with a tracker your team can watch every day.

Start My 2-Week Free Trial

Request Information or call directly: (800) 489-5877

Request Information

Single specialty or multi-site? One payer or many? Tell us your situation and we will map the right coverage within 24 hours.

Frequently Asked Questions

Why do incoming referrals sit unscheduled in Epic?

Because Epic routes any referral that arrives missing a required field, referring provider, diagnosis, or insurance, to the Incoming Referrals Incomplete Information work queue, and it cannot move to scheduling until the record is completed. That is the system working as designed. The referral ages only because most front desks assign no one to work that queue, so the missing field never gets chased and the referral never reaches a scheduler.

What makes a referral land in the incomplete-information queue?

A missing or unmatched required data point: no referring provider on file, no diagnosis code, no insurance, or demographics that will not match to a chart. Usually it is one or two fields, not the whole packet. Epic holds the referral in the queue until that gap is filled, then drops it into the normal incoming-referrals workflow automatically.

Why do schedulers not catch these stalled referrals?

Because schedulers only see referrals that reached the normal workflow. A referral parked in the incomplete-information queue is invisible from their chair, so the schedule can look healthy while a backlog of referred patients ages out of view. That invisibility is why the queue needs its own named owner rather than a general assumption that someone will notice.

How do we stop losing referred patients to this backlog?

Assign the incomplete-information queue a daily owner who opens each stalled referral, identifies the missing field, chases the referring office for it, and completes the record so Epic releases it into scheduling, while flagging urgent referrals for same-day booking. Worked every morning, the queue clears daily instead of aging patients until they book elsewhere.

How much does remote referral queue coverage cost?

Staffingly charges a flat weekly rate per dedicated remote coordinator, with lower per-person rates for teams of 5 or more and 10 or more. Every plan covers 45 hours of coverage per week with a trained backup included, and there is no percentage of anything. The pricing section on this page shows how the flat rate compares with typical US market rates for this work.

Will AI be completing our referral records?

AI drafts the first pass, reading each incomplete referral, identifying the missing field, and drafting the outreach to the referring office, and a credentialed human verifies every record and owns the urgent flags before anything is scheduled. The judgment stays with people; automation removes the repetitive queue-reading so the coordinator spends their time chasing data and protecting urgent cases.

Do we have to change anything in our Epic build?

No. Our coordinator works inside your existing Epic instance and the referral work queues you already have, so there is no build change and no new platform for your staff to learn. They work the incomplete-information queue where it already lives, which is why a typical clinic is live in 1 to 2 weeks rather than months.

How fast will the referral backlog clear?

Usually within the first couple of weeks. Once a dedicated coordinator is working the incomplete-information queue every morning, chasing the missing fields, and completing the records, the aged referrals start flowing into scheduling and the queue stops growing, so referred patients reach a slot before they give up and book elsewhere.

How does one flat weekly rate cover 45 hours every week?

Your dedicated specialist works a 9-hour day, Monday to Friday, which is 45 hours of coverage each week. The ninth hour is part of the flat weekly rate, not billed as overtime. Over a year that is 2,340 hours of coverage, against the standard US full-time work year of 2,080 hours (40 hours x 52 weeks, the same basis the U.S. Office of Personnel Management uses to compute hourly rates of pay). That is how $399 per week works out to $8.87 per hour.

Written By

Dan Nandan

Founder and CEO, Staffingly, Inc. · Piscataway, NJ

Dan Nandan has spent 25+ years in IT consulting and healthcare BPO, was among the first in the US to build an RPO/BPO delivery network in India, and has been featured in Computerworld. He runs the operations and the dedicated virtual teams behind the workflows on this page; the team-voice answers above come from the remote specialists who work them every day.

Connect on LinkedIn

Where the Claims on This Page Come From

Sources & References

MGMA Closed-Loop Referral Management Guidance. Practice-management guidance on referral ownership, front-end revenue leakage, and why unmanaged referrals are lost to competitors. mgma.com
MGMA Referral Management Volume and Revenue Resources. Benchmarks on the volume and revenue impact of monitoring and completing patient referrals. mgma.com
Epic Referral Workflow Education, University of Iowa Health Care. Vendor-neutral education describing how incoming referrals route to the Incomplete Information work queue and return to the normal workflow once completed. epicsupport.sites.uiowa.edu
AMA Practice Management and Patient Access Resources. Physician-practice references on referral handling, patient access, and administrative workload. ama-assn.org
HFMA Revenue Cycle and Front-End Resources. Guidance on front-end revenue leakage, referral completion, and the revenue tied to timely scheduling. hfma.org