Eric Cecava | The Physician Relations Problem Nobody Names

Eric Cecava training coworkers


Regional health systems that treat physician engagement as a recruitment function are building a problem that will surface years later

There is a conversation that happens regularly in regional health system leadership circles about the physician shortage, the recruitment challenges, and the difficulty of building a medical staff that meets the needs of a defined geographic area. Eric Cecava of Fort Gratiot, Michigan, who managed physician recruitment and contracting at McLaren Port Huron across a three-county service area in Michigan, thinks this conversation is asking the right question in the wrong frame. The problem most systems have is not physician recruitment. It is physician relations.

Recruitment Is a Transaction. Relations Is a Culture.

A health system that recruits physicians well but manages them poorly ends up in a cycle: attractive offers bring people in, inadequate engagement drives them out, and the gap that existed before the recruitment process ended up back where it started. The cost of that cycle, in recruiting fees, in onboarding investment, in the disruption to clinical programs and patient relationships, is substantial.

Physician retention is not a compensation problem, though compensation matters. It is a relationship problem. Physicians who feel that the health system's leadership understands their practice environment, takes their concerns seriously, and involves them in decisions that affect their work stay in organizations that might not be the highest-paying option in the market. Physicians who feel otherwise tend to leave as soon as a better compensation offer makes the decision easy.

Contracting Is Where the Relationship Is Formalized, Not Defined

Physician contracting establishes the terms of a working relationship: compensation model, productivity expectations, call obligations, and the other structural elements that govern how a physician practice functions within the health system. Those terms matter. But the contract is a formalization of a relationship, not the definition of it.

Cecava's work in physician contracting at McLaren Port Huron was conducted alongside his operational responsibilities for the integrated medical group, which meant that the contractual relationship was always understood in the context of the ongoing operational relationship. The physicians who understand why the contract is structured as it is, and who have had input into that structure, tend to be more effective partners in the operational work of building a medical group than the ones who signed a contract with a number on it and have not had a substantive conversation with leadership since.

Clinical Program Development Requires Physician Investment

The health systems that build new clinical programs successfully tend to involve the physicians who will staff those programs in the design of them. This is not a courtesy. The design of a clinical program determines how much it asks of the physicians who deliver it, what support structures they need, and whether the volume and compensation model reflects the actual work of the program. Getting those questions right requires physician input that cannot be substituted by administrative planning.

Cecava's work in clinical program development at McLaren Port Huron was conducted with this in mind. A program that physicians believe in and helped design has a fundamentally different probability of success than one that was developed by an administrative team and presented to the medical staff as a finished product. The latter tends to generate compliance rather than enthusiasm, and the difference between those two outcomes is visible in patient volume.

Quality Outcomes Follow the Relationship Quality

The connection between physician engagement and quality outcomes is not difficult to explain. Physicians who are invested in an organization's quality program participate in it differently than physicians who treat quality metrics as an administrative burden. The difference in participation shows up in how documentation is handled, how quality improvement projects are staffed, and whether the clinical culture treats quality as a professional commitment or a reporting requirement.

Cecava's operational responsibilities for quality outcomes at Adena Health System and McLaren Port Huron gave him a direct view of this connection. The quality programs that performed consistently were the ones where physician leadership was genuinely engaged, not the ones where quality was a metric being reported to a committee.

What Gets the Relationship Right

The physician relations approach that works, in Cecava's experience, starts with consistent, substantive communication. Not newsletters. Not annual physician satisfaction surveys. Regular conversations between health system leadership and medical staff leadership about what is working, what is not, and where the two sides need to reach agreement on direction.

It also requires follow-through on commitments made to the medical staff. Every broken promise to physicians, about capital equipment, support staff, scheduling flexibility, or operational improvements, is a withdrawal from a relationship that took time to build. Health system leaders who make those withdrawals consistently end up managing a physician relations problem that recruitment alone cannot fix.


Comments

Popular posts from this blog

Eric Cecava | What Changes When You Become Accountable for Everything

Eric Cecava | Why Geography Shapes Healthcare More Than Most Leaders Admit

Eric Cecava | Why the COO Job and the CEO Job Are Not the Same Job