Why Your PRM Software Is Not Fixing Your Referral Leakage
Elena Russo
I have yet to meet a director who bought PRM software because they enjoy software procurement. They bought it because referral leakage was hurting performance and they needed better control.
The hard truth is this: PRM can give you excellent visibility and still leave outcomes unchanged.
That is not a contradiction. It is an architecture problem.
What the Evidence Says About Referral Behavior
Before getting into what PRM does and doesn't do, it's worth grounding this in what actually drives referral behavior, because the answer shapes everything else.
A 2020 peer-reviewed study published in the Journal of Service Management (ScienceDirect) used logistic regression on multi-source healthcare data to isolate what predicts whether a PCP refers within a given hospital network. The finding: a physician's likelihood of making an in-network referral is directly influenced by the breadth and depth of their provider connectivity, meaning the quality and frequency of their relationships with specialists and health system staff.
That is a relationship problem, not an information problem. Software that improves your information about a relationship problem does not solve the relationship problem.
What PRM Software Solves Well
PRM software is very good at:
- Tracking referral pattern changes by physician and geography
- Logging liaison visit history and contact frequency
- Surfacing territory variance that would otherwise require manual data pulls
- Supporting manager-level accountability and coaching conversations
Those capabilities are valuable. They are often necessary once teams scale beyond minimal coverage. In programs with three or more liaisons, coordination without a PRM becomes genuinely difficult.
What PRM Software Cannot Do
PRM does not make physician visits.
PRM does not repair strained referral relationships after a patient experience issue.
PRM does not build trust with a practice manager who has had two bad handoff experiences in one quarter.
In other words, PRM identifies relationship risk. Liaisons resolve relationship risk. These are different functions, and no amount of dashboard sophistication converts one into the other.
Why Referral Leakage Persists After PRM Rollout
In many organizations, the issue is not weak analytics. The issue is under-coverage.
SHSMD and AAPL benchmarking data suggests that roughly 150–250 actively managed referring physician relationships per liaison represents the productive range. Above 300 relationships, visit frequency typically drops below the threshold needed to maintain relationship depth. When a liaison is spread too thin, cadence drops. When cadence drops, relationship depth degrades. When relationship depth degrades, referral behavior shifts away.
No dashboard fixes that by itself. A clean report on a deteriorating relationship is still a deteriorating relationship.
MGMA's referral management research confirms what this implies: most organizations "overlook the possibility that referrals may not always stay within their network," and the ones that address leakage most effectively do so through active relationship management, not through monitoring alone. The monitoring tells you where the leakage is. Relationship-building is what closes it.
| PRM Software | Physician Liaison Coverage | |
|---|---|---|
| Identifies referral leakage trends | Yes | Supports with field context |
| Tracks visit and contact history | Yes | Executes visits |
| Recovers physician relationships | No | Yes |
| Influences real referral behavior | Indirect | Direct |
| Scales only with enough field capacity | Yes | Yes |
The Better Operating Model
Treat PRM and liaison coverage as complements, not substitutes.
In practical terms:
- Ensure baseline territory coverage can sustain meaningful relationship cadence
- Use PRM to prioritize and monitor
- Expand software sophistication as coordination complexity grows
If you invert that sequence, you buy insight before you buy execution. That is how teams end up with clean reports and stagnant referral outcomes. For organizations with one or two liaisons managing under 300 relationships, basic CRM tracking is often sufficient in the early stages. A full PRM implementation before you have the liaison coverage to act on its data means paying for insight you cannot execute.
A Useful Internal Diagnostic
Before approving more software spend, ask:
- Are we losing outcomes because we cannot see, or because we cannot act?
- Is liaison capacity aligned with territory relationship volume?
- Would one additional liaison move KPI trendlines faster than one additional analytics module?
Most teams that answer honestly know what to do next.
Need physician liaison coverage to execute on PRM insight?
MDliaison places experienced physician liaison contractors with local territory relationships in 2-3 weeks.
Tell us about your territoryFrequently Asked Questions
Can PRM software reduce referral leakage on its own?
It can improve visibility into where leakage is occurring, but peer-reviewed research on referral behavior (including a 2020 logistic regression study in the Journal of Service Management) confirms that in-network referral rates are driven by the breadth and depth of provider relationships, which requires human coverage to build and maintain.
What is the difference between PRM software and physician liaison coverage?
PRM software provides analytics, tracking, and coordination infrastructure. Liaison coverage provides the field execution and relationship management that actually shifts referral behavior. They serve different functions and work best together.
Should we prioritize PRM investment or liaison hiring first?
It depends on your bottleneck. If your team can't act on the data you already have, more data visibility won't help. Most underperforming referral programs are coverage-constrained before they are information-constrained.
Why does visit cadence matter so much in referral programs?
Because referral behavior is relationship-driven. The JoSM peer-reviewed study confirms that in-network referral likelihood is directly influenced by the breadth and depth of provider connectivity. Without consistent contact, that connectivity degrades even when your dashboards look healthy.