The Payer Mix Shift Nobody Priced In
A 90-physician multispecialty group ended the fiscal year at a 4.2% operating margin, down from 7.9%. Leadership assumed volume growth would carry the year, but two things moved: the group's commercial payer mix fell from 48% to 39% as a large self-insured employer switched to a narrow-network plan the group is not in, and Medicare Advantage penetration rose from 22% to 31%. Days in accounts receivable climbed from 38 to 51, and denials rose from 6.1% to 9.4%, concentrated in MA prior-authorization and medical-necessity categories. The group has $2.3M in cash reserves against roughly $1.1M in monthly operating expenses. The CFO wants to draw on a line of credit to cover a planned EHR upgrade; the COO wants to freeze hiring; the physician compensation committee is due to reset productivity targets in six weeks and several partners are threatening to leave if their bonuses fall.
1. Which of the three competing moves (line of credit, hiring freeze, compensation reset) should leadership sequence first, and why?
Read the worked answer
Revenue-cycle recovery should come first, because it is the only lever that improves cash without borrowing, without cutting capacity, and without touching partner compensation - and it addresses a problem the data already localizes.
Reasoning:
- Denials are the fastest dollar. Moving denials from 9.4% back toward 6% on a $1.1M monthly expense base implies meaningful recovered revenue within 60–90 days, and the concentration in MA prior-auth and medical necessity makes the fix targeted, not systemic: front-end eligibility and auth workflows plus a physician-advisor review queue for medical-necessity denials.
- AR days are a cash-conversion problem, not a margin problem. 51 days versus 38 is roughly two weeks of revenue sitting idle; reworking the oldest buckets (MA and self-pay) improves the reserve position the CFO is worried about.
- Sequencing matters. Drawing on the credit line before fixing collections raises the cost of capital for a problem that may be self-funding. A hiring freeze before understanding where the capacity constraint sits risks cutting the staff who would fix the denials.
- Compensation reset is the highest-trust-risk lever and should be informed by the first two moves, not preempt them.
Recommended order: (1) 90-day revenue-cycle sprint with weekly denial dashboards, (2) hold the credit line as a backstop with a defined draw trigger, (3) revisit hiring and compensation with better data.
2. The compensation committee proposes cutting productivity targets to protect partner income. Evaluate this against the group's strategic position.
Read the worked answer
Lowering productivity targets to cushion bonuses protects individual income by shrinking the group's capacity to generate revenue - the opposite of what a payer-mix squeeze requires. The group's problem is not that physicians are working too hard; it is that each unit of work is being reimbursed worse because the mix shifted toward MA and away from commercial.
The committee should separate two questions that are being fused:
- Is the current wRVU target achievable under the new mix? Possibly not - MA prior-auth friction and denial rework consume clinical time that doesn't generate wRVUs. If so, the right adjustment is to credit the non-wRVU work (auth and denial management, care coordination) rather than to lower the clinical target.
- Should the group pay partners more per unit while margin falls? No. A comp reset that raises per-wRVU rates during a margin decline borrows from the group's future to settle a present dispute.
Better design: Hold the wRVU target, add a modest quality/access modifier tied to the metrics the group needs (auth turnaround, denial rate, panel access), and phase any rate change over two years. Communicate the payer-mix math openly - partners threatening to leave are more likely to stay if they can see the arithmetic than if they are told 'the numbers are tight.' Also flag the retention risk honestly: if a small number of high-revenue partners leave, the group should model that scenario before assuming the threat is credible.