Physician Liaison vs Physician Relations Manager | Which Do You Need?

These two titles get used interchangeably, and it causes real problems. I've sat in meetings where a hospital CEO says "we need a physician liaison" and the HR team posts a job for a physician relations manager, or the other way around. The titles sound similar enough that nobody catches the mismatch until someone's been hired and the work doesn't match the expectation.

The distinction matters because the roles require different skills, operate in different environments, and solve different problems. Getting it wrong doesn't just waste a salary. It wastes the time you spend discovering the mismatch, which in my experience is usually four to six months of someone trying to do a job they weren't built for before anyone acknowledges it.

The Liaison Is a Field Role

A physician liaison spends most of their time outside the hospital. Their territory is the referring physicians' offices within a defined geography or service line, and their job is to build and maintain the relationships that drive referral volume.

The work resembles sales more than most hospital administrators are comfortable admitting. A liaison is tracking which practices send patients to your facility and which send them elsewhere. They're visiting offices, meeting with physicians and office managers, identifying why referral patterns have shifted, and working to redirect patient flow back toward your service lines. The good ones do this relationally rather than transactionally. They become a resource for the referring physician's practice; someone who can expedite a referral, connect a patient with the right specialist, or resolve a scheduling issue that's been causing friction.

The clinical vocabulary matters here, not because a liaison needs to diagnose anything, but because credibility with physicians requires fluency in how they think and talk. A liaison who can discuss referral pathways for a complex cardiac patient in language the cardiologist recognizes is going to earn trust faster than one who sounds like a marketing brochure. This is something I think gets underweighted in hiring. The best liaisons I've worked alongside had enough clinical knowledge to follow a physician's reasoning and enough humility to know when they were out of their depth.

Compensation for physician liaisons typically falls between $55K and $78K base, based on what I've seen across roughly twenty liaison placements and job postings over the past two years. In competitive markets like Dallas, Boston, and the Bay Area, experienced liaisons are earning $85K-$100K when bonuses tied to referral growth are included. Our physician liaison compensation benchmarks go deeper on this by market and experience level.

The PRM Is a Strategy Role

A physician relations manager sits higher in the organizational chart and spends most of their time inside the hospital. They work with the CMO, the VP of Business Development, and service line directors to set the overall physician engagement strategy. If the CEO says "grow cardiology referrals by 15% next year," the PRM is the person who turns that directive into a plan: which markets to target, which referring physicians to prioritize, how many liaisons to deploy, and what the competitive landscape looks like.

The PRM builds dashboards, analyzes referral data, designs onboarding programs for new medical staff, and communicates the value of the physician relations program to leadership. This is the person who justifies the budget. Without a PRM (or someone functioning in that capacity), the liaison program often lacks strategic direction. Liaisons end up visiting whoever they feel like visiting rather than the practices where the data says the opportunity is greatest.

The skills are different from what makes a good liaison. PRMs need analytical thinking, comfort with data, organizational influence, and the ability to present to executives. Some PRMs are former liaisons who moved into strategy, but the transition isn't automatic. Being excellent in the field doesn't necessarily translate to being excellent in a conference room with a CMO.

PRM compensation runs $75K-$110K for manager-level roles and $120K-$140K at the director level in larger health systems, based on postings I've tracked and conversations with PRMs in my network. I should note that "director level" means different things at different organizations; I've seen that title applied to roles that are genuinely strategic and to roles that are basically a senior liaison with a nicer business card. More detail on the trajectory from liaison to PRM is in our physician relations manager career path guide.

Where It Gets Confusing

Smaller health systems frequently combine both roles into one position. They call it "physician relations coordinator" or "physician liaison/manager" and expect one person to do field visits four days a week and strategic reporting on the fifth. Some people can do both, but they're rare, and even the ones who can do both usually end up prioritizing one function over the other. Almost always, the field work wins because it's more immediately tangible, and the strategic work gets pushed to evenings and weekends or just doesn't happen.

I worked with a health system in North Carolina where exactly this happened. Their combined-role coordinator was extraordinary in the field. Referral volume in her service lines grew 23% in her first year. But the reporting, the data analysis, the strategic planning; none of it was getting done because she was out of the building from 8am to 4pm every day. When budget season came around, the C-suite almost cut her position because they couldn't see the ROI on paper. The numbers showed the ROI. Nobody had packaged them into a format the finance team could evaluate.

They eventually split the role. She stayed in the field. A PRM was hired to handle strategy and executive communication. Within six months, the PRM had built a business case that funded two additional liaisons. The program grew because both functions were finally being served.

That's a story I've seen play out in different variations at probably eight or nine health systems over the years. Not always with the same happy ending.

Deciding What You Need

The decision framework I use when health systems ask me is less about the title and more about the problem they're solving.

If the core problem is referral leakage, you need a field presence. Someone visiting practices, rebuilding relationships, resolving the specific issues that are causing physicians to refer elsewhere. That's a liaison. This is especially true if you've never had a physician relations program at all. Start with field activity, generate referral data, and build the strategic layer later when you have enough information to justify it.

If the core problem is that you already have liaisons doing field work but the program lacks direction, visibility, or executive support, you need a PRM. The liaisons might be doing excellent work that nobody in the C-suite can see or measure. A PRM creates the infrastructure that makes the program sustainable and scalable.

If you're a mid-size or large system with multiple service lines and markets, you probably need both. The PRM sets priorities and manages the team. The liaisons execute in the field. This is the model that actually scales, and it's the one I see most often in health systems that take physician relations seriously.

There's a fourth scenario I should mention. Sometimes health systems need a liaison urgently, whether because someone left, a new service line is launching, or a competitor is actively poaching referring physicians, and the hiring process takes longer than the situation allows. In those cases, contract physician liaisons can fill the gap. They maintain the field relationships while you search for the right permanent hire. MDliaison can connect you with experienced liaison professionals for exactly this kind of situation.

Getting the Role Right

I want to be careful about being too prescriptive here, because every health system's situation is different. The size of your market, the maturity of your referral network, the competitive dynamics, your budget; all of these shape which role makes sense and how you structure it.

What I will say is that the single biggest mistake I see is ambiguity. When the job description doesn't clearly define whether this person is primarily a field rep or primarily a strategist, you end up with a hire who's confused about their priorities, a manager who's frustrated with the results, and an executive team that questions whether physician relations is worth the investment.

Be clear about what you're hiring. The title is just a title. The job, the actual work the person will do every day, is what determines whether they succeed.

For more on how top-performing health systems structure their physician relations teams, our best practices guide covers what's working. And if you're exploring the career path from either direction, we've mapped the typical trajectory in our how to become a physician relations manager guide.