What is referral leakage? A guide for healthcare leaders

Quick answer

Referral leakage is what happens when a patient is referred for care but never completes it inside the intended network or practice. Sometimes the patient goes out of network. More often, the referral simply stops moving. A fax arrives and gets lost in a queue. A follow-up call never happens. Industry research puts leakage rates between 20% and 70% depending on service line, and roughly two-thirds of the underlying failures trace back to document workflow rather than patient preference.

What is referral leakage in healthcare?

Referral leakage is the loss of revenue and continuity of care that occurs when a referred patient does not complete their care within the intended provider or network. It has two common forms.

The first is external leakage, where a patient is referred to an in-network specialist but ends up seeing an out-of-network provider instead. This is what most health systems track and worry about publicly.

The second is internal leakage, and it is far more common than the industry admits. This is where the referral itself never gets processed. A fax arrives at the specialist’s office. It sits in a queue. Someone was supposed to call the patient. Nobody did. The patient never books, and the referral quietly dies.

Both forms cost the same. The patient does not receive care, the provider does not receive revenue, and no one on the sending or receiving side realizes the failure until well after the fact.

How much does referral leakage cost?

The numbers researchers have published are large, but they are also uneven across service lines. A few figures with solid primary sources:

• Physical therapy is the clearest data point. A 2021 analysis of 3.4 million commercial claims by Luna, published through HealthLeaders Media, found that 55% of patients sought physical therapy outside their referring health system after surgery, representing an estimated $2.5 billion in lost potential revenue across the systems studied.
• Executive-level revenue impact is well-documented, if dated. A 2018 Fibroblast survey of healthcare executives found that 43% reported losing more than 10% of annual revenue to patient leakage, with another 19% reporting losses of 20% or more. Eighty-seven percent of executives called leakage a priority, but 23% did not formally track it.
• Leakage rates vary widely by specialty. Industry research summarized by Kythera Labs in 2025 puts referral leakage rates between 20% and 65% depending on service line, with imaging, diagnostics, and specialty care carrying the largest financial impact.

What causes referral leakage?

Most healthcare leaders assume leakage is a patient behavior problem. It is not. It is a workflow problem.

The causes cluster into a few patterns.

Fax and document workflow failures. Healthcare still runs on fax. When a referral fax fails silently, arrives incomplete, or lands in an undifferentiated queue with hundreds of other documents, the referral is effectively lost before it is ever seen. Staff cannot follow up on documents they do not know exist.

Lack of visibility into the queue. Most healthcare organizations cannot search their inbound fax history. When a patient calls to ask whether their referral was received, staff often cannot confirm it, even when the document is somewhere in the queue. That single friction point drives patients to look elsewhere.

Manual sorting and routing. In a typical intake workflow, staff open each document, identify what it is, look up the patient, match it to the correct record, and route it into the EHR by hand. At Eye Associates, that process took about four minutes per document before automation. At volume, this becomes the bottleneck that determines how fast a practice can schedule new patients.

No closed loop. Most referral workflows are built for sending, not for completing. The referring practice’s job ends when the referral goes out. The receiving practice does not have a systematic way to confirm receipt, flag stalled cases, or route the document to the right queue. Nobody owns the space in between.

Prior authorization delays. According to the AMA’s 2024 Prior Authorization Physician Survey, physicians and their staff spend an average of 13 hours per week on prior authorization work, completing an average of 39 prior authorization requests per physician per week. Ninety-four percent of physicians say prior authorization contributes to burnout, and 82% report patients commonly abandoning treatment due to prior auth delays. When authorization takes days and nobody is proactively managing it, patients move on.

Poor referring-provider visibility. Referring physicians often lack detailed information about in-network specialists. Between 91% and 96% of physicians say knowing a specialist’s specific area of focus and availability is highly important when making a referral, according to survey research summarized by PerfectServe.

None of these causes are patient behavior. They are all operational.

How is referral leakage different from patient leakage?

The terms are often used interchangeably, but they are not the same thing.

Patient leakage is the broader category. It refers to any patient who receives care outside your network or system, for any reason. That includes referrals gone astray, but also emergency care, patient preference, geographic barriers, and cases where your network genuinely does not offer the needed service.

Referral leakage is the narrower and more addressable subset. It is patient leakage that happens specifically because a referral was sent but never completed. This is the version that operational teams can actually fix, because it has a defined starting point (the referral going out) and a defined endpoint (the patient booked, seen, and documented in the EHR).

Most executives think they have a patient leakage problem. What they usually have is a referral leakage problem, which is a document workflow problem in disguise.

Where does referral leakage actually happen?

Understanding where in the workflow leakage occurs matters, because different failure points require different fixes.

At the send. The referring practice sends a fax to the wrong number, sends an incomplete document, or sends the referral to a specialist who cannot see the patient in a reasonable timeframe.

In the queue. The referral arrives at the receiving practice but sits in an unstructured inbound queue with hundreds of other documents. If the practice cannot classify, sort, and route referrals faster than they arrive, the queue grows and older referrals age out.

At the match. Even when a document is processed, matching it to the correct patient record can fail. A misspelled name, a missing date of birth, or a document that references multiple patients all create friction. Staff either match manually (slow) or send the document to an exception queue (where it can sit indefinitely).

At the outreach. Once the referral is in the system, someone has to call or message the patient. In a busy practice, this step is often where high-value referrals die. If outreach happens on day seven instead of day one, the patient has often already scheduled elsewhere.

At the prior auth. For any referral that requires prior authorization, delays compound with delays everywhere else. Patients wait, hear nothing, and drop off.

At the scheduling handoff. Even after outreach, the patient still has to be booked, confirmed, and shown up. High no-show rates are often blamed on patient behavior when they are really a symptom of long delays earlier in the process.

The clinical stakes of these operational failures are real. According to CRICO’s Comparative Benchmarking System, 23% of outpatient malpractice cases filed between 2012 and 2016 involving a missed or delayed diagnosis had a breakdown in referral management. Nearly three-quarters of those patients suffered a high-severity injury or died.

Referral leakage is not one problem. It is six or seven small problems compounding into one large one.

How do you measure referral leakage?

Most organizations do not measure referral leakage accurately, because they measure the wrong endpoints.

A minimum viable measurement approach includes four numbers:

Referral volume received. How many referrals arrived in a given month, across every channel (fax, direct message, patient portal, phone).

Referral processing rate. Of those received, how many made it into the EHR as a linked patient record within 24 hours. Referrals not processed within a day carry high leakage risk.

Referral conversion rate. Of the referrals processed, how many resulted in a scheduled and completed visit. This is the number most organizations do not have and cannot calculate without a closed-loop system.

Average value per completed referral. This is the number that turns leakage from an operational problem into a financial one. For most specialties, this can be estimated as a blended figure across the specialty mix.

Multiplying leaked volume by average value gives you the annual dollar cost of leakage. That is the number to take to leadership.

Adoption of tools to measure this is uneven. A February 2025 MGMA Stat poll found that 76% of medical groups are using their EHR or referral management software to track referrals, while 21% still rely on manual tracking. Even among the 76% using tools, closed-loop reporting remains a common gap.

What can healthcare leaders do about referral leakage?

Once you understand that referral leakage is a workflow problem, the fixes become tractable.

Make the inbound queue searchable. The single highest-leverage fix is being able to find a fax in seconds when a patient calls. Even when documents have not been fully processed, staff who can search and confirm receipt can convert an anxious phone call into a booked appointment.

Automate document classification and routing. Intelligent document processing (IDP) reads inbound faxes, identifies the document type, extracts patient information, suggests the correct patient match, and routes documents into the correct EHR workflow. At Eye Associates, this shifted per-document handling from about four minutes to one to two, and surfaced 25% more referral volume in the first month by eliminating silent fax failures.

Build a closed-loop follow-up process. Somebody has to own the space between “referral received” and “patient booked.” Whether that is a dedicated referral coordinator, an automated outreach sequence, or a combination, the closed loop is what separates practices with low leakage from practices with high leakage.

Track and report leakage as a financial metric. Leakage should show up on the same dashboards as revenue, denials, and no-shows. When leadership sees leakage as a line item alongside revenue, priorities shift.

Address the fax layer explicitly. As long as referrals arrive by fax, fax reliability is patient access. Silent fax failures are not an IT issue. They are a revenue issue. Modern cloud fax platforms with delivery confirmations, retry logic, and searchable histories are the foundation everything else sits on.

The bottom line

Referral leakage is one of the largest addressable revenue losses in most healthcare organizations. It is usually blamed on patient behavior, network design, or physician habit, but the majority of it traces back to document workflow: faxes that fail silently, queues that cannot be searched, and manual sorting that cannot keep up with volume.

The fix is not a new referral policy. It is a modern intake infrastructure. Practices that treat referral intake as a workflow problem, and invest in the tools to solve it, consistently recover meaningful revenue and improve patient access at the same time.

Frequently asked questions