How is referral leakage measured?

It's typically measured as the share of referrals that do not result in a completed, in-network visit, over a defined period. Doing that well requires knowing both the numerator (referrals that left or were never completed) and the denominator (all referrals made), which is why organizations rely on claims data or encounter data to see where patients actually went. There is no single standardized industry figure — methods and definitions vary.

What causes referral leakage?

Two broad drivers. One is network design and patient choice — the patient genuinely needed or wanted an out-of-network provider. The other, often underestimated, is broken follow-up: referrals that stall because no one closes the loop, the patient is never scheduled, or the referring physician loses visibility and sends the next patient elsewhere. The second category is the one better information flow can actually move.

Does a community physician portal reduce referral leakage?

It can address one specific driver — the visibility gap. When referring physicians can see their patients' results and referral status, they have less reason to route the next patient elsewhere, which supports network integrity. To be clear about scope: a community physician portal is not a referral-analytics or referral-routing platform, and leakage has causes a portal can't change. It improves the information flow that contributes to leakage, not the network economics around it.

Referrals & physician engagement

What is referral leakage (and how do you measure it)?

Updated June 2026 · Reviewed by David Higginson, CHIME Innovator of the Year

"Referral leakage" gets used loosely and measured inconsistently. Here's a precise definition, an honest look at how it's quantified, and where information flow actually moves the number.

Referral leakage (also called patient leakage) is when a patient referred for care is seen outside the referring organization's network, or the referral is never completed. It's usually measured as the share of referrals that don't result in a completed, in-network visit, using claims or encounter data to see where patients actually went. It matters on two fronts: continuity of care for the patient, and lost downstream activity for the network the patient left.

How it's measured

The concept is simple; the measurement is where rigor matters. Leakage is a fraction — referrals that left or were never completed, over all referrals made — so you need both halves. The denominator (all referrals) is often the hard part, because referrals leave a hospital through phone, fax and online intake and aren't always captured in one place. The numerator (where the patient ended up) usually comes from claims or encounter data. Because organizations define and bound this differently, there is no single standardized leakage percentage — published industry estimates range widely, commonly cited anywhere from roughly 20% to more than 50% depending on specialty and method. Treat any single figure as an estimate, not a constant.

What actually drives it

There are two broad causes, and they call for different responses:

Network design and patient choice. The patient needed or chose an out-of-network provider. This is a network-strategy and access question.
Broken follow-up and lost visibility. The referral stalls — never scheduled, never closed — or the referring physician can't see what happened and routes the next patient elsewhere out of habit. Industry analyses repeatedly find a large share of leakage sits here, not in deliberate out-of-network choice.

Where physician visibility fits

The second driver is the one better information flow can move. When a referring physician can see their patient's results and the status of the referral they sent, two things change: care coordination improves, and the physician has a concrete reason to keep sending patients to a hospital that keeps them informed. That supports network integrity — the inverse of leakage.

An honest scope note

A community physician portal improves the visibility that contributes to leakage. It is not a referral-analytics or referral-routing platform, and it won't change the network economics or patient-choice factors behind leakage. Better information flow is one lever, not the whole machine.

Where this fits at Bluefish

HealthPoint addresses the visibility lever: it gives referring physicians real-time results and referral status tracking across intake channels, and surfaces cancellations and no-shows that otherwise vanish. For the broader picture, see what a community physician portal is.

Sources: figures above are industry estimates and vary by source and method — for example Linear Health, Personify Health, and PerfectServe. They are not standardized or government figures.

Frequently asked questions

What is referral leakage?: Referral leakage (also called patient leakage) is when a patient referred for care is seen outside the referring organization's network — or the referral is never completed at all. It represents both a continuity-of-care gap and lost downstream revenue for the network the patient left.
How is referral leakage measured?: It's typically measured as the share of referrals that do not result in a completed, in-network visit, over a defined period. Doing that well requires knowing both the numerator (referrals that left or were never completed) and the denominator (all referrals made), which is why organizations rely on claims data or encounter data to see where patients actually went. There is no single standardized industry figure — methods and definitions vary.
What causes referral leakage?: Two broad drivers. One is network design and patient choice — the patient genuinely needed or wanted an out-of-network provider. The other, often underestimated, is broken follow-up: referrals that stall because no one closes the loop, the patient is never scheduled, or the referring physician loses visibility and sends the next patient elsewhere. The second category is the one better information flow can actually move.
Does a community physician portal reduce referral leakage?: It can address one specific driver — the visibility gap. When referring physicians can see their patients' results and referral status, they have less reason to route the next patient elsewhere, which supports network integrity. To be clear about scope: a community physician portal is not a referral-analytics or referral-routing platform, and leakage has causes a portal can't change. It improves the information flow that contributes to leakage, not the network economics around it.