Mastering Managed Care

New Negotiators Don't Lose Deals Over Rates. They Lose Them Over Words.

Kevin W. Barron — Tue, 13 Oct 2026 05:00:00 +0000

IN THIS ISSUE

The feature: the contracting vocabulary new negotiators get caught without
If you're new to this: what a carve-out is
Most-discussed on LinkedIn: why BlueCard keeps landing hospitals in court
New: the Mastering Managed Care podcast

Emma was six weeks into her first managed care role when the payer's negotiator said, "Given the exclusivity clause in your current agreement, we'd need a carve-out before adding that provider." Emma nodded and wrote it down. She had no idea what an exclusivity clause was, and she wasn't about to ask in front of her own VP.

She found out three months later, when a physician group her health system wanted to add couldn't be credentialed under the existing contract without the payer's written consent, consent the payer wasn't in a hurry to give. The clause Emma nodded along to had quietly limited her organization's network for the next two years.

Nobody handed Emma a glossary on day one. Nobody handed most of us one. We learned the vocabulary the way she did, by getting caught not knowing it in a room where the other side already did.

The gap that isn't about intelligence

Here's what I want to be direct about: this isn't a competence problem. Emma is sharp. The gap is that managed care contracting has its own dense, specific vocabulary, and that vocabulary is exactly where a payer's negotiator has the advantage over a new hire on the provider side. Every term you don't know fluently is a term you can't push back on in real time, and a negotiation happens in real time. You don't get to pause the meeting and go look something up.

I've sat across the table from analysts and benefits managers in their first year who were perfectly capable of doing the math once they understood what they were being asked to agree to. The problem was never the math. It was that nobody had given them the vocabulary before they needed it under pressure.

That's on us as an industry, not on the new negotiators walking into these rooms every day.

The terms worth knowing before your next meeting

These are the eight terms I'd put in front of anyone new to this work, the ones that show up often enough in a contract to change what you're actually agreeing to. Print it, save it, or hand it to the newest person on your team.

TAKE THIS TO YOUR NEXT MEETING

Eight contract terms every new negotiator needs

Exclusivity clause: a provision that limits one party from contracting with others. Providers use these to keep a payer from adding competing providers, sometimes backed by financial penalties. This is the clause that caught Emma.
Negotiated rates: the actual reimbursement structure, whether a fee schedule, case rate, global rate, or DRG or APC-based payment. Outside government-set rates, it's almost always a negotiated mix.
Risk-sharing arrangement: a contract where payer and provider share financial risk. Full risk puts gains and losses on the provider. Upside-only protects against losses but caps the savings a provider keeps.
Value-based payment: reimbursement tied to quality and cost outcomes rather than volume. Metrics and targets are negotiated up front, and savings are split at a pre-agreed percentage.
Utilization review: the process of deciding whether a service was medically necessary and appropriate. Payers and providers often apply different criteria, which is where many disputes start.
Network adequacy: whether a plan's network can actually meet its members' needs. Several states now require public hearings when adequacy is in question.
Credentialing: verifying a provider's qualifications before they can join a network. Large medical groups sometimes handle it themselves under a Delegated Credentialing Agreement, which needs its own contract terms.
Medical loss ratio: the share of premium dollars a payer must spend on care and quality improvement. It shows whether the premiums collected match what's actually going out the door for care.

This list is the floor, not the ceiling. But it's the floor that keeps you from agreeing to something you don't understand.

Know someone who negotiates payer contracts? Share Mastering Managed Care with them. Three referrals unlocks the Payer Negotiation Prep Checklist.

Get your referral link

What it costs to skip this

Emma's story is a clause. Some new negotiators lose more than that. I've heard of a first-year benefits manager agreeing to a risk-sharing structure she thought was upside-only because nobody had explained the difference, and her organization ate a loss the following year that a five-minute vocabulary check would have prevented. The cost of not knowing these terms isn't hypothetical. It shows up on a P&L twelve months later, long after the meeting where it was decided.

Emma didn't make that mistake twice. She built her own glossary after the exclusivity clause, added a term every time she heard one she didn't recognize, and six months later corrected a payer's negotiator mid-meeting on a definition of medical loss ratio he'd gotten wrong. She got the concession that followed.

Knowing the vocabulary doesn't win you the negotiation by itself. Not knowing it loses you parts of the negotiation you never even realized were on the table.

Call to Action: If there's a term that caught you off guard in your first year of contracting, tell me what it was in the comments. I'm building a running list from practitioner stories, and yours might save the next new negotiator the same mistake.

And send this to the newest person on your team before their next payer meeting, not after it.

If you're new to this

Carve-out: a service, provider, or population pulled out of a contract's standard terms and handled separately, often with its own rates or its own vendor. Behavioral health, transplant, and lab are common examples. Emma's payer wanted one before adding a new provider.

Try this week: Pick one of your contracts and list every carve-out in it, along with who manages each one and how it's paid.

Most-discussed on LinkedIn last week

Last week's post that drew the most conversation. Follow me on LinkedIn to join the discussion.

What are your thoughts on the BlueCard program? I have a few.

HCA Healthcare's recent lawsuits against Anthem Georgia and Independence Blue Cross caught my attention on Becker's because of who's being sued and why. Both are out-of-state Blues Home Plans. The hospitals went after them directly because BlueCard didn't do its job. (Read the Becker's article.)

In BlueCard terms, the Home Plan is the Blue plan that issued the patient's coverage (the one on their ID card), and the Host Plan is the Blue plan where the care is delivered and that holds the provider's contract.

BlueCard has real value. One Host Plan contract gives providers access to Blues members nationwide. But providers can't opt out of it (I've tried), and in 30+ years of contracting it's given me more headaches than almost any other payer program.

In every state I've worked in since the early 1990s, the Host Plan has shown relatively little interest in enforcing its provider contracts against Home Plans. The Home Plan denies or underpays, the Host Plan says it's just passing along the decision, and the provider is stuck holding a contract with the one party that won't (or can't) back it up.

Last year's $2.8 billion provider antitrust settlement was supposed to help. It promised BlueCard improvements, better claims data, and five years of court-appointed monitoring. That's progress. But it didn't fix the core problem. Home Plans still make the payment and medical necessity calls, Host Plans still hold the contract, and providers still can't opt out. When hospitals still have to sue a plan they never signed with just to get paid, something remains broken in my opinion.

Until Host Plans hold Home Plans to the terms of their provider contracts, expect more of these disputes and enforcement actions.

Of course, these are only my opinions and they don't represent my employer or any organization I'm affiliated with. Your mileage may vary.

NEW: THE PODCAST

Mastering Managed Care is now a podcast. Start with Episode 0, a short welcome on what the show covers and who it's for. Audio editions of each week's feature are coming soon.

Listen to Episode 0

About the Author: Kevin W. Barron, MBA, FHFMA, FACHE is a nationally recognized healthcare contracting and payer relations executive with over 30 years of experience in healthcare finance. He is an author, speaker, and mentor to emerging leaders in healthcare finance. Subscribe to his free weekly newsletter at KevinWatsonBarron.com

Disclaimer: This article is provided for general informational and educational purposes only. It reflects my personal views and observations based on professional experience in healthcare finance, managed care, payer relations, and revenue cycle operations. It should not be interpreted as legal, financial, regulatory, actuarial, or reimbursement advice. The content is not intended to represent the official position of my employer, any payer, provider, professional association, or other organization with which I may be affiliated. Readers should consult their own legal, financial, compliance, actuarial, or operational advisors before making decisions based on the issues discussed. Any references to payers, providers, regulations, market trends, or reimbursement practices are intended for discussion and education only and should not be construed as a statement about any specific contract, negotiation, patient matter, or confidential business arrangement.

AI Isn't Coming for Your Contracting Job. Complacency Is.

Kevin W. Barron — Tue, 06 Oct 2026 05:00:00 +0000

Kraig had redlined the same clause a hundred times. Anti-assignment language, section 4.2, three paragraphs of boilerplate he could recite from memory. So when his analyst ran the draft through a new contract review tool and it flagged the same issue, plus two exposure points Kraig hadn't caught, in under four minutes, he didn't feel relief. He felt exposed.

His team had built its reputation on being the ones who caught what everyone else missed. That was the whole pitch, internally and externally. If a piece of software could catch it faster and cheaper, what was the pitch now?

That question is landing on desks across managed care departments this year, and most people are answering it the wrong way. They're treating it as an IT rollout to survive rather than a redefinition of the job to get ahead of. Those are not the same problem, and the difference is going to determine who's still negotiating contracts in five years and who's administering the software that replaced their function.

The part you don’t want to hear, and neither does Kraig

Here's the uncomfortable truth: a meaningful share of what fills a contract analyst's week, first-pass redlining, clause comparison, rate modeling, compliance checks against a preferred-language library, is exactly the kind of structured, repeatable work that AI tools are already good at. Not someday. Now. I've watched review cycles that used to take days get compressed into hours, with the software doing a more consistent job of flagging boilerplate risk than a tired analyst on their fourth contract of the day.

That's the external problem, and it's real. But it's not the one that actually threatens careers.

The one that threatens careers is internal. It's the analyst, the manager, even the VP, who quietly decides the tool is a threat to be resisted rather than a floor to build on. Who lets someone else on the team become the one who "gets" the AI stuff while they stay in their lane. Who mistakes speed at rote tasks for the whole job, forgets that the whole job was never just the redline, and lets that misunderstanding cost them the seat.

I've spent over thirty years in this field, five states, hundreds of contracts, and I have never once seen a negotiation won by whoever found the anti-assignment clause fastest. I've seen negotiations won by the person who understood what the payer actually needed, read the room when a stated position was a bluff, and knew which of eighty-five preferred provisions to trade away to protect the one that mattered. None of that shows up in a redline. All of it is still yours to own.

What actually changes, and what doesn't

The work that's automatable was never the differentiating work. It was the entry fee. AI is about to make that entry fee nearly free, which means the people who defined their value by how fast they could clear it are about to find that value gone. The people who defined their value by what they did after the redline was done are about to find themselves with more time to do more of it.

So the plan isn't to compete with the tool. It's to move up and out of the tool's lane, deliberately, before the decision gets made for you. That starts with learning the tools well enough to direct them instead of waiting on them, because whoever understands the tool's blind spots ends up managing whoever only knows its outputs. It continues with doubling down on the negotiation skills that were always human: reading counterparts, building the relationships that get a stalled negotiation unstuck with one phone call, and knowing when the data says one thing and the market says another. And it means going looking for the complexity AI can't touch yet, risk-based arrangements, novel partnership structures, the kind of contracting that requires judgment calls no training set has seen before, because that's where your seat gets more secure, not less.

Before you build a plan, run the honest version of this self-check:

Can you name, specifically, which parts of your current role are pattern-matching that a tool could learn this year?
Do you know how to direct an AI tool's output, or only how to receive it?
When was the last time you led a negotiation that required reading a person, not just a spreadsheet?
Are you the one your organization would ask to evaluate a new AI contracting tool, or the one it would explain the tool to?
If your routine tasks disappeared tomorrow, what would you spend that time on that a machine can't?

If more than one of those has an uncomfortable answer, that's not a verdict. It's the starting line.

What's actually at stake

Do nothing, and the risk isn't dramatic. It's quiet. It's the org chart redrawing itself over eighteen months, with the AI-fluent analyst getting pulled into the room for the complex renewal and you getting handed the routine ones. It's the slow realization that you've become the person who explains the old way of doing things to people who no longer need it explained.

Do something, and the upside is just as real. Six months after that redline moment, Kraig's team wasn't smaller. It was doing different work. The tool handled first-pass review on two hundred contracts a quarter that used to eat a third of his staff's time. Kraig spent that recovered time redesigning the value-based arrangements in his portfolio, work nobody was automating, and walked into his next executive committee meeting with a rate improvement story that had nothing to do with how fast anyone could find a clause.

The tools are not the threat. The refusal to change what you spend your time on is.

Start this week: pick one tool your organization already has access to, learn what it's actually good at, and hand it the most repetitive piece of your job. Then go spend the time you got back on the part of the work only you can do.

You were never valuable because you were fast. You were valuable because you knew what fast couldn't see.

Call to Action: If you've already started shifting how your team spends its time because of AI, or you're watching your organization get this wrong, tell me about it in the comments. I read every one, and the practitioner stories are what make this newsletter worth writing.

And forward this to the colleague who's still hoping this whole AI thing is a phase. It isn't, and neither is their contract review backlog.

The Denial Nobody Owns Is the One Costing You the Most

Kevin W. Barron — Tue, 29 Sep 2026 05:00:00 +0000

Mark ran patient access. Every denial came back with the same note: "insufficient documentation." He sent it to coding. Coding sent it back. Billing quietly wrote off the balance every 90 days without asking why. Six months of this, and everyone had a clean explanation for their piece of it.

Patient access had verified eligibility correctly at the time of service. Coding had matched the codes to the documentation they were actually given. Billing had submitted the claim exactly per the payer's stated rules. Every department was right. The denial kept happening anyway.

That's the denial nobody owns: the one that falls through the cracks between departments, where each function can honestly say "not my problem," and be correct, from its narrow view. Nobody caused it. Nobody's incentivized to fix it. So it just gets reworked, appealed, or written off, month after month, without anyone treating it as a pattern instead of a nuisance.

When someone finally pulled patient access, coding, billing, and contracting into the same room with the same denial data, the actual cause surfaced fast: a documentation requirement buried in a contract term that patient access had never seen and coding didn't know existed. Once contracting explained what the payer actually required, the fix took days. The denials had nearly disappeared within six months. The problem was never inside any one department. It was in the handoff between them, and it took contracting sitting at the table, not just signing the contract, to find it.

Payer contracting doesn't operate upstream of the revenue cycle. It operates inside it. Every rate negotiated, every payment model innovated, every risk arrangement structured eventually has to survive contact with patient access, clinical documentation, coding, billing, collections, revenue integrity, and IT. A denial nobody owns is what happens when contracting negotiates a term and nobody translates that term into what the rest of the revenue cycle needs to know. The strategy looks strong on paper. It quietly underperforms everywhere else.

Where contracting has to show up, not just sign off:

Patient access — needs contracting's payer intelligence in real time to verify coverage correctly, not just at renewal
Clinical documentation — reimbursement logic negotiated into a contract only works if coders and physicians understand the documentation it depends on
Coding — code-level nuances buried in a contract's fine print are invisible to coders unless contracting translates them
Billing — timely filing limits, bundling rules, and modifier requirements differ by payer, and billing needs contracting's terms in usable form, not buried in a PDF
Collections — write-off patterns are often the clearest signal that a contract term isn't performing as negotiated, but only if collections and contracting are comparing notes
Revenue integrity — chargemaster and pricing decisions have to reflect what's actually in the contract, or the two functions quietly work against each other
Denials management — the most valuable root-cause data in the building often traces straight back to a contract term, but only if contracting is in the room to hear it

Evidence that closing the cracks moves the number

Emory University's hospitalist program offers one of the better-documented examples. When Emory implemented a shared charge-capture and communication platform across physicians, billers, and administrators, giving every function visibility into the same real-time data, the collaboration reduced denial rates by 4 to 7 percent and cut denied-charge write-offs by 12 to 17 percent over three years, while reducing charge lag from 60 to 90 days down to two.[^1] The win wasn't the software. It was three roles that used to work off three separate versions of the truth finally working off one.

How to find the denials nobody owns before they compound:

Bring contracting into denial, billing, and collections huddles, not just renewal cycles, so negotiated terms get pressure-tested against reality
Ask, for every recurring denial category: which department would say "not my problem," and are they technically right? Those are the cracks.
Design payment innovation with the departments that will execute it: IT, billing, coding, and revenue integrity, before it goes to the payer, not after
Maintain a shared knowledge base connecting contract terms to operational requirements, so a rate change in one system doesn't become a surprise in another
Route write-off and adjustment trends from collections back to contracting as negotiation intelligence, not a monthly report nobody acts on

The denials nobody owns are where revenue strategy quietly leaks the most, because no single department's KPI ever flags them. You can negotiate the most innovative payment methodology in the industry. If contracting isn't collaborating with the full revenue cycle, from patient access through collections, some of that innovation will show up as a denial nobody owns within a year.

Mark's team didn't need new software. They needed contracting at the table, translating what the contract actually required instead of leaving it in a file nobody else could read.

Call to Action: Where has a denial nobody owned been quietly costing your organization? Tell me in the comments, a win or a challenge, and share this with a colleague who owns a piece of the revenue cycle but has never been in the room when the contract was negotiated.

[^1]: Ingenious Med, "Emory Healthcare Case Study," https://ingeniousmed.com/emory-healthcare-case-study/

About the Author

Kevin W. Barron, MBA, FHFMA, FACHE is a nationally recognized healthcare contracting and payer relations executive with over 30 years of experience in healthcare finance. He is an author, speaker, and mentor to emerging leaders in healthcare finance. Follow Kevin on LinkedIn or subscribe to his weekly newsletter at https://www.KevinWatsonBarron.com

Nobody Was Checking. One Analyst Found $2 Million.

Kevin W. Barron — Tue, 22 Sep 2026 05:00:00 +0000

Elena had been on the team for six weeks in 1997 when she found it. It wasn't a payer error, and it wasn't fraud. The hospital's system had been logging admission dates in a way that quietly trimmed per diem days off inpatient claims, and it had been doing so for years.

Nobody had flagged it because nobody was looking. Elena was the first person whose whole job was to look.

By the time she'd traced the pattern, corrected the claims, and worked it through with the payer, the recovery came in just under two million dollars. One implementation miss, on one hospital's inpatient book; nearly 30 years ago. Now put the same kind of miss inside today's multi-billion-dollar portfolio of commercial, government, and risk-based contracts, and the story turns into a question you have to answer: is your revenue strategy performing the way you designed it?

After thirty-plus years in payer relations and managed care contracting, I've watched organizations invest heavily in payment model innovation, actuarial talent, and strategic pricing. Those initiatives earn a slide in the strategic plan. What gets skipped, almost every time, is the discipline of verifying that they perform once they leave the model and land on a paid claim. That discipline is contract performance auditing, and it belongs at the center of revenue strategy, not on the margins of revenue cycle operations.

You can design the most sophisticated payment methodology in the industry: value-based arrangements, bundled episodes, risk-adjusted rate structures, whatever comes next. Until someone confirms it pays the way it was negotiated, it's an assumption. Assumptions at portfolio scale are expensive.

A contract auditor's job is to notice what a large, busy organization can't: a methodology that doesn't function as designed, a policy change buried in fine print, a system issue on your own side compounding across every claim it touches. Policing the payer is beside the point. Elena's finding was our mistake, not theirs. Performance risk compounds the same way whether it started in your system or the payer's, and whether the model behind it was innovative or not. The only difference is scale, a $2 million finding in one hospital or a nine-figure pattern across an integrated system.

The recovery was the smaller payoff. Once Elena's findings started shaping negotiation prep, the contracting function moved from reactive to strategic. Later on, a recurring error she caught on a single imaging code turned into a six-figure recovery before we'd opened the renewal conversation, and it changed how we wrote payment terms in the next contract. That feedback loop, one that tells you whether existing models work and where the next one should be built differently, is the innovation that never makes a keynote.

It also builds accountability into the strategy at every layer of the portfolio, from the front-line biller to the executive setting enterprise revenue strategy. Accountability here has nothing to do with blame. It's the natural extension of trusting a team with a mandate: you measure whether the mandate is paying off.

If your organization is investing in strategic pricing, payment model innovation, and actuarial sophistication, and no one is auditing whether any of it performs on the claims floor, your revenue strategy is resting on assumptions.

Share this with a colleague building out a revenue strategy function, and tell me in the comments: how does your organization verify that its negotiated payment innovations are performing as designed?

About the Author

Front-Line Staff Are Costing You Millions. It's Not Their Fault.

Kevin W. Barron — Tue, 15 Sep 2026 05:00:00 +0000

Priya had fought the same denial code for eight months. Resubmit, wait, get denied, escalate. Nobody had ever explained why that specific payer rejected that specific code, because nobody outside the payer actually knew.

Then her team brought the payer to the table, not to negotiate a rate, but to teach. Three sessions in, Priya understood the logic behind the denial for the first time. The appeal she filed that week didn't come back.

Healthcare organizations chase innovation everywhere: AI-driven prior auth, predictive denial models, new revenue cycle platforms. One of the highest-leverage innovations available costs nothing to build and sits inside relationships you already have. Payer-specific staff education isn't a training line item. At portfolio scale, it's part of your revenue strategy.

Why this is a strategy gap, not a training gap

Payers write the rules that decide how claims get submitted, processed, and paid, and those rules aren't static or intuitive. Generic training leaves gaps. Gaps become denials, delays, and leakage in the strategy you spent months negotiating. Payer-specific education closes it at the source:

Member identification — payers clarify network quirks generic training misses
Authorization requirements — nobody explains a payer's process better than the payer
Coding accuracy — CPT, ICD-10, HCPCS aligned to what each payer actually expects
Billing rules — clean claims the first time, not the third
Portal usage — turns a clunky tool into leverage
Denial resolution — root-cause training, not repeat rework

When staff understand the why, they stop executing a script and start protecting the strategy. That shift, from task-follower to revenue guardian, is the innovation.

What it returns

A 1% drop in denial rates at an average-sized hospital can mean millions recovered and strategy realized, not just an efficiency gain
Faster cash flow when days in A/R shrink the same way they do under a well-negotiated rate
Staff who spot patterns and feed contracting real intelligence for the next negotiation
Deeper payer trust that compounds into faster resolution and better terms

How to build it, without a platform investment

Name a champion on your payer relations team with the authority to speak for both sides
Partner directly with payers, because most already offer provider education, and it's rarely requested
Tailor content to your highest-denial categories and biggest-exposure contracts
Build a reference tool (payer contacts, terms, auth requirements) that outlasts the training and survives turnover
Measure it like any strategic initiative: denial rates, days-to-pay, staff confidence over time

For an executive overseeing an integrated, multi-billion-dollar payer portfolio, this is the same discipline that governs payment model innovation and strategic pricing, applied one layer deeper. You can build the most innovative payment methodology in the industry. If the staff executing it don't understand why it works, you haven't operationalized an innovation. You've issued an assumption.

Priya's eight-month denial didn't need a new platform. It needed someone from the payer's side willing to explain the rule, and someone on ours willing to ask.

Question: where has payer-led education paid off for your team, and where is revenue strategy still missing that connection? Tell me in the comments.

About the Author

Most Medical Necessity Denials Come From a Silo, Not a Clinical Problem

Kevin W. Barron — Tue, 10 Feb 2026 06:00:00 +0000

Naomi ran Utilization Management at a hospital that had just seen a sharp spike in denials from one of its largest national payers, almost all tied to late inpatient notifications. Her team was following the same notification process they'd used for two years. What they didn't know was that the payer had updated its notification window as part of the latest contract renewal, and the contracting team that negotiated that change had never told UM about it. The denials weren't a clinical failure. They were a communication failure between two departments that had every reason to be talking regularly and weren't.

Naomi's team spent the next quarter appealing denials that a single conversation, months earlier, would have prevented entirely.

Why this gap costs more than it should

Utilization management and managed care contracting sit closer to each other operationally than almost any other two departments in a hospital, since UM lives inside the exact notification and medical necessity requirements that contracting negotiates. And yet these two teams often operate in near-total isolation from each other, each assuming the other has the information it needs.

The external problem is real: contract terms change regularly, payer policies shift even more often, and neither department has a natural, built-in reason to loop the other in on every update. But the internal problem is what actually drives the denial rate up. It's treating UM and contracting as separate functions with separate concerns, when a notification requirement or a medical necessity criterion is exactly the kind of detail that has to travel between them the moment it changes. Naomi's team wasn't undertrained. They were uninformed, through no fault of their own.

I sit on my organization's contract performance evaluation team alongside our UM executive counterpart specifically because this collaboration only works when it's structural, not occasional.

Five (5) ways to close the gap

Start with a shared, current understanding of contract terms. UM needs to know the specifics of medical necessity criteria and notification requirements for every active contract, and that's a two-way responsibility: contracting has to push that information out clearly, and UM has to flag questions or friction points as they come up, not after a denial pattern emerges.
Build joint training between the two teams. Shared sessions on industry standards, regulatory changes, and documentation best practices close the knowledge gap before it turns into a denial, and the learning should run in both directions, since UM often spots operational friction before contracting ever sees it in the numbers.
Design integrated workflows with real compliance checkpoints built in, so payer notification requirements and medical necessity documentation get captured consistently and leave a clear trail if a denial needs to be contested. Some payers deserve particular attention here. National payers with especially complex notification requirements are worth a dedicated process review on their own, since a generic workflow often isn't tight enough to catch their specific triggers.
Set a real communication cadence between UM and contracting, not an occasional one. Regular meetings, a shared platform for updates, and a fast path for flagging payer policy changes keep both teams current instead of finding out about a change after it's already cost money. Monthly, at minimum, with more frequent contact whenever something specific comes up, is what actually keeps pace with how often payer terms shift.
And review denial data together. A joint look at medical necessity and notification denials surfaces the trends and root causes that neither department sees clearly on its own, and that shared analysis is exactly what should inform documentation improvements, targeted training, and even renegotiation of contract terms that no longer match clinical reality.

What changes when the two teams actually operate as one

Skip this collaboration, and every payer policy change becomes a discovery process, usually made through a spike in denials rather than a heads-up before it ever became a problem, the way Naomi's team learned about that notification window change.

Naomi's organization built a monthly standing meeting between UM and contracting after that experience, with a shared tracker for any payer requirement change as soon as it surfaced. The next time that same national payer updated its notification terms, contracting flagged it in the tracker within a week, UM adjusted its process before the new terms took effect, and the denial rate for that payer dropped by more than half over the following two quarters.

Set a standing monthly meeting between your UM and contracting leadership if one doesn't already exist, and build a shared way to flag payer requirement changes the moment either team learns about them.

Denials for medical necessity and notification failures rarely start as clinical problems. Most of them start as information that never made it from one department to the other in time.

Call to Action: If closer collaboration between UM and contracting has reduced denials at your organization, tell me what worked in the comments. I'll reply to every one.

Send this to whoever leads Utilization Management or contracting at your organization, whichever one you're not.

About the Author: Kevin W. Barron, MBA, FHFMA, FACHE is a nationally recognized healthcare contracting and payer relations executive with over 30 years of experience in healthcare finance. He is an author, speaker, and mentor to emerging leaders in healthcare finance. Follow Kevin on LinkedIn or subscribe to his weekly newsletter at https://www.KevinWatsonBarron.com

The Negotiation Isn't the Hard Part of a Payer Contract. The Implementation Is.

Kevin W. Barron — Tue, 17 Feb 2026 06:00:00 +0000

Roman negotiated a contract renewal he was genuinely proud of, better rates, cleaner language, a faster dispute process. He gathered his revenue cycle leadership team to celebrate and brief them on what was coming. Ninety minutes into that meeting, it became clear that coding had one understanding of the new reimbursement schedule, billing had a different one, and nobody had touched the payer code build in the hospital information system yet. The excitement in the room was real. So was the confusion underneath it.

The contract Roman signed was strong. The organization's ability to actually execute it wasn't there yet, and nobody had built a plan to close that gap.

Where deals actually succeed or fail

A signed contract is a starting point, not a finish line, and the distance between signature and steady-state performance is exactly where a well-negotiated agreement either delivers what it promised or quietly underperforms for a year. I learned this early in my career, gathering what we'd now call the revenue cycle leadership team after finalizing a complex agreement, only to discover that every person in the room had a different understanding of the terms and what they meant operationally. The excitement was there. The alignment wasn't, and confusion and delays followed until we built the discipline to prevent it.

The external problem is that implementation touches nearly every department in a hospital, coding, billing, IT, revenue cycle, service lines, all with their own priorities and their own version of the contract's meaning. But the internal problem is what actually causes the delay: treating implementation as an afterthought to negotiation instead of a phase that requires the same rigor. Roman's team wasn't incompetent. They just didn't have a shared, sequenced plan for what needed to happen between signature and go-live.

The negotiation is rarely where a contract fails. Implementation is where it either delivers or doesn't.

The three-phase checklist that closes the gap

Pre-implementation starts with a thorough review of the agreement itself, highlighting key terms, reimbursement schedules, compliance requirements, and anything that changed from a prior version. From there, build a real training plan, coordinated with your centralized revenue cycle training team where one exists, tailored to the specific needs of different service lines and revenue cycle functions. Present the new terms, and the reasoning behind them, at your next revenue cycle leadership meeting or contracting committee, and leave room for questions. This is the step Roman's team skipped, and it's the one that would have caught the misalignment before it cost anyone time.
Implementation is where the operational work happens. Update hospital information systems to reflect the new terms, and if it's a new payer, build the payer code, insurance plan code, and contract structure needed for accurate payment calculation from day one. Confirm coding and billing systems are configured correctly for any specific revenue codes or CPT codes the agreement requires. Integrate the new terms into existing workflows, work queues, denial reports, payer scorecards, anything already driven by payer or plan code. And establish real, ongoing communication with the payer: confirmed quarterly Joint Operating Committees run by your contracting team, and monthly claims-focused calls between your business office and the payer's claims and provider relations staff.
Post-implementation is where you find out whether the first two phases actually worked. Build real performance monitoring, monthly, quarterly, and rolling twelve-month reporting on the metrics that matter: expected versus actual payment, days to bill, days to first payment or denial, claim rejections, denial ANSI codes, initial and overturned denial rates, and direct cost, total cost, contribution margin, and profit margin where relevant to your contract administration. Use that data to spot trends before they become problems. Build standing feedback loops so staff can flag issues as they surface, not months later. And keep training and support running as staff adjust, rather than treating the initial rollout as the only moment that mattered.

What changes when implementation gets the same rigor as negotiation

Skip this discipline, and even a strong contract underperforms quietly for months, the way Roman's did, while different departments operate on different understandings of terms nobody clearly aligned on.

Roman rebuilt his process around all three phases for the next major agreement. Revenue cycle leadership got a dedicated training session before go-live, systems were configured and tested two weeks ahead of the effective date, and a performance dashboard was running from week one instead of being built reactively after denials started climbing. Six months in, the contract's actual performance matched what Roman had modeled during negotiation, because for the first time, the whole organization had actually implemented the same agreement.

Before your next contract goes live, build out these three phases as an actual project plan, not a mental checklist, and assign an owner to each phase.

The true challenge in managed care contracting was never getting the deal signed. It's making sure the deal you signed is the one your organization actually delivers.

Call to Action: What would you add to this checklist? Tell me in the comments; I read every one and this list only gets better with more practitioners weighing in.

Send this to whoever owns implementation on your team before the next contract crosses the finish line.

About the Author: Kevin W. Barron, MBA, FHFMA, FACHE is a nationally recognized healthcare contracting and payer relations executive with over 30 years of experience in healthcare finance. He is an author, speaker, and mentor to emerging leaders in healthcare finance. Follow Kevin on LinkedIn or subscribe to his weekly newsletter at https://www.KevinWatsonBarron.com

Payer JOC Meetings Fail When They're Just a Formality

Kevin W. Barron — Tue, 24 Feb 2026 06:00:00 +0000

Celeste inherited a Joint Operating Committee that met twice a year, whenever both sides could find a shared hour, with no standing agenda and whoever happened to be free from each side sitting in. A claims processing issue had been quietly compounding for four months by the time it finally made it onto a JOC agenda, because there simply hadn't been a forum to raise it sooner. By the time the two sides addressed it, the backlog had grown large enough that fixing it took a formal escalation instead of the routine conversation it should have been.

The JOC existed on paper. It just wasn't doing the job a JOC is supposed to do.

Why the meeting exists and why it quietly stops working

A Joint Operating Committee is built to be a working session, not a checkbox, a standing forum where the operational and relational complexity of a contract gets managed in real time instead of piling up until it becomes a crisis. When it's running well, it's where credentialing issues, care management questions, and claims problems get resolved months before they'd otherwise surface in a formal dispute.

The external problem is that JOCs are easy to schedule and easy to let drift, since nothing forces the structure to stay sharp once the initial contract excitement fades. But the internal problem is what actually causes the drift. It's treating the meeting as a formality that happened rather than a working session that produced something, the way Celeste's predecessor did. A JOC without a standing cadence, real leadership in the room, and a tracking system for what gets decided isn't managing the relationship. It's just occupying a slot on a calendar.

I've led these meetings for decades, and the difference between a JOC that prevents problems and one that just documents them always comes down to the same handful of structural choices.

Seven (7) practices that make a JOC actually work

Set a real cadence and hold it. Quarterly is the floor, not the target, and consistent timing is what keeps rapport and operational awareness current instead of stale.

Get real leadership in the room, from both sides. Executive presence turns a status update into a decision-making session, because issues that need authority to resolve actually get resolved instead of tabled for someone else to escalate later.

Work toward genuine goal alignment. Payer and provider incentives don't naturally point the same direction, and naming that directly is what turns a JOC from two sides trading complaints into a shared effort at solving them.

Circulate a detailed agenda well before the meeting, with clear objectives, discussion points, and what each side needs to prepare. A JOC without an agenda turns into whichever issue is loudest that quarter instead of the issues that actually matter most.

Keep communication open between meetings, not just during them. Monthly executive check-ins build the kind of trust that makes the quarterly JOC itself more productive, since neither side is walking in cold.

Track every action item with a real follow-up system. Documenting a decision isn't the same as resolving it, and accountability only exists if progress actually gets monitored between sessions.

And keep compliance in view throughout. Every discussion and decision needs to hold up against legal and regulatory standards, with counsel or a compliance officer looped in whenever a decision touches that line.

What changes when the JOC actually functions

Skip this structure, and problems compound quietly for months at a time, the way Celeste's claims backlog did, surfacing only once they're big enough to force a formal escalation instead of a routine fix.

Celeste rebuilt the JOC around all seven practices over the following two quarters. Executive leadership from both sides started attending consistently, a standing agenda went out two weeks ahead of every meeting, and a shared tracker kept every action item visible between sessions. The next claims issue that came up got flagged in a monthly check-in and resolved before it ever needed to appear on a formal agenda at all.

Pull your organization's current JOC cadence, agenda practice, and leadership attendance, and compare it against these seven items. Fix whichever one is weakest before your next scheduled meeting.

A JOC that's running well rarely makes headlines inside your own organization, because it's quietly solving problems before they become the kind of thing anyone needs to escalate.

Call to Action: If your JOC structure has changed how quickly your organization resolves issues with a payer, tell me what worked in the comments. I'll reply to every one.

Send this to whoever runs your organization's JOC meetings before the next one gets scheduled.

About the Author: Kevin W. Barron, MBA, FHFMA, FACHE is a nationally recognized healthcare contracting and payer relations executive with over 30 years of experience in healthcare finance. He is an author, speaker, and mentor to emerging leaders in healthcare finance. Follow Kevin on LinkedIn or subscribe to his weekly newsletter at https://www.KevinWatsonBarron.com

The Termination Clause Is the Most Overlooked Protection in a Payer Contract

Kevin W. Barron — Tue, 03 Mar 2026 06:00:00 +0000

Holden's organization had one payer under a regional network agreement that had been paying late for two years straight, chronically, well past any reasonable grace period. Holden wanted it gone. The contract's only termination language was a single without-cause provision covering the entire multi-payer agreement, no single-client mechanism, no clearly defined "for cause" trigger tied to payment performance. Cutting the underperforming payer meant either living with it or terminating the whole agreement and disrupting every other payer relationship riding on the same network lease. Holden lived with it for the rest of the term.

The problem wasn't that his organization lacked leverage. It was that nobody had negotiated a termination clause specific enough to use that leverage without collateral damage.

Why this clause gets underwritten

Termination provisions read like boilerplate until the moment you actually need one, and that's exactly the problem. They function like a parachute for a stunt pilot: irrelevant on every ordinary flight, and the only thing that matters on the one that isn't. Most contract reviews spend far more attention on rates and reimbursement terms than on the language governing how the relationship ends, because ending the relationship feels like the least likely outcome at signature.

The external problem is real: termination clauses are inherently about a hypothetical future, and hypotheticals are easy to underweight against the concrete rate numbers sitting on the same page. But the internal problem is what actually traps organizations like Holden's. It's negotiating a termination provision broad enough to sound protective without being specific enough to actually use when a single payer, not the whole agreement, is the problem.

I've come to treat these provisions as some of the most consequential language in any contract, precisely because they're the ones nobody thinks about until the day they need them most.

The four termination provisions worth understanding

Without cause termination lets either party end the agreement without stating a reason, after a defined notice period. I favor this provision, but the notice period is where the real decision sits. Ninety to 120 days is typical, but with a payer you don't know well, or one you've had friction with before, thirty to sixty days protects you better, as long as applicable law doesn't dictate otherwise.

For cause termination activates when one party fails to meet specific contractual obligations, most often, from a provider's perspective, late payments or a failure to honor agreed rates. The entire value of this provision depends on how clearly "cause" is defined. Leave it vague, the way Holden's contract did, and you've negotiated a protection you can't actually invoke. Notice periods here typically run thirty to ninety days, usually with a chance for the payer to remedy the issue before termination takes effect.

Single client termination is the more precise tool, and it's the one Holden's contract lacked. Common in multi-client or regional PPO network agreements leased to third-party administrators or employers, it lets a provider remove one underperforming payer client without terminating the entire agreement. This is exactly the mechanism that would have let Holden cut the chronically late payer while keeping every other relationship under that network intact. Notice periods and remedy opportunities here usually run thirty to ninety days as well.

Mutual termination lets both parties agree to end the contract by consent, less common but genuinely useful. I've used this specifically when a wholesale contract replacement was needed mid-term, giving both sides a way out of an agreement that no longer served either party without a drawn-out dispute.

Of the four, single client termination is the one most providers underuse, and it's the one that protects the integrity of a network relationship while still holding an individual bad actor accountable.

What changes when the clause actually fits the problem

Skip specific termination language, and you end up exactly where Holden did: leverage over a bad payer relationship that you can't actually use without breaking three good ones in the process.

Holden's team renegotiated that network agreement at the next cycle, this time with a single client termination provision explicitly built in, tied to a clearly defined set of payment-performance triggers. When the same payer's performance didn't improve the following year, Holden's team removed them from the agreement in sixty days, kept every other payer relationship under that network intact, and didn't lose a single day of leverage doing it.

Pull your organization's current payer agreements and check specifically for a single client termination provision. If it's missing from a multi-client network agreement, that's the gap to close at your next renewal.

A termination clause you never use is doing its job. A termination clause you can't use when you finally need it was never doing its job at all.

Call to Action: If you have a termination provision you've relied on, or one that let you down when it mattered, tell me about it in the comments. I'd like to learn from what's actually worked for other organizations.

Send this to whoever reviews your organization's network agreements before the next renewal comes up.

About the Author: Kevin W. Barron, MBA, FHFMA, FACHE is a nationally recognized healthcare contracting and payer relations executive with over 30 years of experience in healthcare finance. He is an author, speaker, and mentor to emerging leaders in healthcare finance. Follow Kevin on LinkedIn or subscribe to his weekly newsletter at https://www.KevinWatsonBarron.com

Strong Negotiations Are Built on Relationships, Not Just Rate Sheets

Kevin W. Barron — Sat, 07 Mar 2026 06:00:00 +0000

Theo ran his first three contract renewals the same way: show up prepared, present the numbers, negotiate the terms, leave. Clean, efficient, professional. Then a claims processing error on the payer's side threatened to delay a batch of reimbursements right before quarter close, and Theo needed a favor, a faster review, a little flexibility on timing. The payer's negotiator gave him the standard process and nothing more. They'd never had a reason to give him anything more. Theo had never given them one either.

He got the resolution eventually, on the payer's normal timeline, three weeks later than he needed it.

What efficiency quietly costs you

Negotiating efficiently feels like the professional move, and in the moment, it often is. But a negotiation conducted purely transactionally builds a contract and nothing else, and contracts don't return your calls when something goes wrong outside the terms you negotiated.

The external problem is real: healthcare has less time for the kind of relationship-building it used to have. I came up in an era of long business lunches, and I still remember a payer representative I got to know over shared plates of barbecue shrimp at a favorite New Orleans restaurant before every negotiation cycle. Those lunches are mostly gone now, replaced by tighter schedules and video calls squeezed between other meetings. But the internal problem, the one that actually costs organizations when things go wrong, is treating that shift as permission to skip relationship-building altogether instead of finding a faster way to do it. Theo didn't lack the time to build trust with his counterpart. He just never thought to spend any of the time he had on it.

I've relied on the goodwill built during negotiations more times than I can count, in moments that had nothing to do with the original contract. That goodwill doesn't show up in a rate sheet. It shows up exactly when you need it most.

Five (5) practices that build the relationship, not just the deal

Start with open communication. Be upfront about what you can and can't share, including your general goals, before the negotiation gets adversarial. I open most contract negotiations with a one-on-one conversation specifically to set that tone before either side starts positioning.
Build trust through reliability. Follow up on every commitment, even the small ones, because nothing destroys credibility faster than a promise that quietly goes unkept. Consistent follow-through is what turns a one-time deal into a relationship the other side actually wants to maintain.
Practice real empathy and active listening. Give full attention, without the distraction of a phone or a half-finished email, and actually hear what the other party's constraints and motivations are. That's often where the actual path to agreement shows up, not in the numbers either side started with.
Manage conflict directly and promptly. Address disagreements as they surface instead of letting them harden into resentment. I learned this early, growing up in a loud, part-Sicilian family where nothing went unaddressed for long, and it's served me well at the negotiating table ever since.
And negotiate for long-term value, not just the win in front of you. A mindset built around mutual benefit, where both sides feel genuinely invested in the outcome, is what makes the next negotiation easier instead of harder.

What changes when the relationship exists

Skip this, and every negotiation stays transactional, which means every future problem outside the contract's explicit terms gets handled at arm's length, the way Theo's claims delay did.

Theo rebuilt his approach after that experience. He started opening negotiations with the kind of one-on-one conversation meant to set tone rather than terms, followed up on every small commitment he made, and stayed reachable between negotiation cycles instead of only during them. The next time a processing issue threatened a deadline, his counterpart called him directly, flagged the problem before it became urgent, and the two of them resolved it in a day.

Before your next negotiation, plan one specific way to build the relationship, not just the deal, whether that's a direct conversation up front or genuine follow-up after the terms are signed.

The rate sheet gets you through this negotiation. The relationship is what gets you through the next one, and the one after that, especially the times something goes wrong that no contract clause covers.

Call to Action: If a relationship you built during a negotiation ever paid off somewhere you didn't expect, tell me about it in the comments. Those are exactly the stories worth passing on.

Send this to the negotiator on your team who treats every deal as a one-time transaction.

About the Author: Kevin W. Barron, MBA, FHFMA, FACHE is a nationally recognized healthcare contracting and payer relations executive with over 30 years of experience in healthcare finance. He is an author, speaker, and mentor to emerging leaders in healthcare finance. Follow Kevin on LinkedIn or subscribe to his weekly newsletter at https://www.KevinWatsonBarron.com

Payer Contracts Should Pay for Social Needs, Not Just Diagnoses

Kevin W. Barron — Tue, 10 Mar 2026 05:00:00 +0000

Yolanda's care team had the same patient back in the emergency department for the fourth time in six months, same chronic condition, same discharge instructions, same result. The medical care was correct every time. What kept bringing him back was that he was living in a car and couldn't refrigerate his insulin. Yolanda's case managers knew that. Nobody's contract paid for the intervention that would have fixed it, because nobody had negotiated for it.

The clinical team treated the diagnosis four times. Nobody's payment structure treated the actual cause once.

The gap between what drives outcomes and what gets funded

Social Determinants of Health, economic stability, education, healthcare access, housing and neighborhood conditions, and social and community context, drive a documented share of patient outcomes, often more than the clinical care itself. Providers and case managers already know this. They see it every day in patients who come back for reasons no medication addresses.

The external problem is that traditional managed care contracts are built around clinical service codes, not social risk factors, so there's no natural place in most agreements for an SDOH intervention to get paid for. But the internal problem is what actually keeps patients cycling back through the system. It's contracting teams and case management teams operating on separate tracks, one negotiating rates for diagnoses and procedures, the other trying to solve housing and food insecurity with no budget line connected to the contract at all. Yolanda's team wasn't failing the patient. Their contract had simply never been built to fund what he actually needed.

I've watched this gap cost health systems money twice over, once in unreimbursed social work, and again in the readmissions that a small upstream investment would have prevented.

Six ways to build SDOH into the contract itself

Start by negotiating funding for routine SDOH assessments directly into care protocols and rates. A documented, funded assessment at the point of care gives case managers the data to target interventions before a crisis, not after one.

Build risk adjustment based on SDOH factors into the payment model itself, whether through a per-member-per-month mechanism or a structure similar to what many Medicare Advantage plans already use to fund complete assessments. This puts resources where socioeconomic risk is actually concentrated instead of spreading funding evenly across a population with very uneven need.

Negotiate SDOH-focused incentive programs, payer-funded bonuses or direct grants for providers who successfully connect patients to a broader support network of nonprofits and government agencies. This rewards the kind of holistic intervention that a fee schedule alone never will.

Push for contractual support for community partnerships, funding built into the contract for joint initiatives with organizations like a local food bank or a housing ministry. These partnerships often don't exist until a contract creates the funding mechanism that makes them worth building.

Get specific reimbursement for SDOH-related services written in directly: patient education, social work consultations, mobile screening programs, school-based clinics, and extended hours that make care actually reachable for single-parent households. Without this, expanded access work happens on borrowed time and unfunded staff hours.

And build performance metrics that measure SDOH outcomes, reduced emergency visits tied to improved housing stability or community connection, alongside the clinical metrics already in the contract. This is what turns an SDOH investment from a good instinct into a documented result that justifies the next contract's funding.

What changes when the contract actually pays for it

Skip this, and every patient like Yolanda's keeps cycling back through a system that treats the diagnosis correctly and the cause not at all, at a cost that shows up in both readmission rates and the payer's own utilization numbers.

Yolanda's health system built SDOH assessment funding and a community partnership provision into its next major payer renewal. The partnership connected patients to housing resources within days instead of relying on a case manager's personal network of contacts. The same patient who'd cycled through the ED four times in six months didn't return once in the year after his housing situation stabilized, and the payer's own utilization data showed the reduction clearly enough to justify expanding the program in the next contract cycle.

Pick one SDOH factor that shows up most often in your own readmission data, and bring a funding mechanism for it to your next contract negotiation.

Addressing social determinants isn't a departure from good managed care contracting. It's what managed care contracting is supposed to be doing all along, funding what actually keeps a patient well, not just what treats them when they're not.

Call to Action: If your organization has built SDOH funding into a payer contract, tell me what worked and what the payer pushed back on in the comments. These specifics are what help the next negotiation go further.

Send this to whoever leads case management or community health at your organization, before your next contract cycle starts.

About the Author: Kevin W. Barron, MBA, FHFMA, FACHE is a nationally recognized healthcare contracting and payer relations executive with over 30 years of experience in healthcare finance. He is an author, speaker, and mentor to emerging leaders in healthcare finance. Follow Kevin on LinkedIn or subscribe to his weekly newsletter at https://www.KevinWatsonBarron.com

The 20 Payer Contract Clauses That Put Providers Most at Risk

Kevin W. Barron — Sat, 14 Mar 2026 05:00:00 +0000

Felix signed a payer contract renewal eighteen months ago that read clean on every page his legal team flagged. Nine months in, the payer used a retroactive denial provision buried in the claims administration section to pull back reimbursement on a batch of claims going back fourteen months. Nobody on Felix's side had negotiated a shorter lookback period, because nobody had specifically checked for one. The clause wasn't hidden. It just wasn't on anyone's list of things to check.

Felix's team didn't lose that money because they negotiated poorly. They lost it because a 100-page contract has more places to hide risk than any one reviewer can hold in their head without a checklist telling them where to look.

Why the risk can survive legal review

Payer contracts get reviewed by smart people, and risky provisions still make it through, because most contract review happens clause by clause without a structured list of the specific provisions known to cause problems. A reviewer can read every page carefully and still miss a retroactive denial window, an overbroad audit right, or a downcoding provision, because none of those individually look alarming without knowing what to compare them against.

The external problem is real: healthcare contracts are dense, and payers have every incentive to write ambiguity into the clauses that benefit them most. But the internal problem is what actually causes the loss. It's reviewing a contract without a specific list of known risk points to check it against, the way Felix's team did. General diligence catches general problems. It doesn't reliably catch the twentieth provision on a list nobody was using.

I've built my own checklist of preferred contract provisions over years of doing this work, because the alternative is relearning the same lesson every time a new risk surfaces in a signed agreement.

The 20 provisions worth checking on every, single contract

Fee schedule changes — make sure the contract prevents unilateral, material rate changes without notice.
Retroactive denials — limit how far back a payer can reach to deny a paid claim, based on what your organization can tolerate.
Out-of-network penalties — address penalties for out-of-network services directly, including anything touching EMTALA-covered care.
Administrative fees — check for hidden costs tied to claims processing. Rare, but worth confirming they're absent.
Auditing rights — limit how broad a payer's medical record audit rights are, and cap the lookback period.
Prior authorization requirements — clarify vague or overly restrictive language, and use any gold-card programs available to you.
Term and termination — push for mutual notice periods, longer ones where the relationship supports it, and check whether statute already dictates timelines for governmental payers.
Dispute resolution — confirm the process is clear and unbiased, and understand which forms of resolution, informal through litigation, you're agreeing to accept.
Downcoding — prevent unjustified downcoding of services, particularly around emergency care and MS-DRG assignments. Loop in coding leadership to review this language specifically.
Bundling — watch for overly broad service bundling that quietly reduces reimbursement.
Exclusivity clauses — rare outside narrow network or ACO arrangements, but confirm nothing restricts your ability to contract elsewhere.
Payment timelines — check reimbursement timelines against state and federal requirements.
Data sharing — get data ownership and sharing terms explicit, with input from your data security team or CIO.
Referral restrictions — reasonable for some coverage types, but confirm access to your own primary care providers isn't cut off.
Indemnification clauses — avoid indemnification terms that put unreasonable burden on your organization. Legal review here is non-negotiable.
Credentialing delays — push for timely credentialing language, since delays here translate directly into delayed revenue.
Coverage determinations — make sure medical necessity language is clear, using state or federal definitions where they exist.
Late payment penalties — build in real penalties and interest for payer payment delays, to the extent the law allows.
Technology requirements — don't accept technology mandates without your IT team's review and sign-off, and confirm training is included.
Network adequacy provisions — avoid vague adequacy language, and confirm every provider you need is actually participating before you sign.

That's a checklist, not a formality. Every one of these has cost a provider organization real money somewhere, usually because it wasn't checked on the way through.

What changes when the list gets used

Skip this kind of structured review, and a contract that looks clean can still cost you fourteen months of reimbursement on a clause nobody thought to check, the way Felix's did.

Felix's team built their own version of this checklist after that retroactive denial and started running every new contract against it before signature. On the next renewal, the retroactive denial window came back on their checklist immediately, they negotiated it down to six months, and the coding team caught a downcoding provision in the same review that would have cost them on emergency claims. Both got fixed in redlines instead of in a claims recovery effort a year later.

Print this list of twenty and run it against the next contract that crosses your desk, line by line, before it goes to signature.

A contract that reads clean isn't the same as a contract that's safe. The difference is whether someone checked it against the specific risks known to hide in this kind of agreement.

Call to Action: If one of these twenty provisions has ever cost your organization money after signature, tell me which one in the comments. I want to hear which ones are catching people most right now.

Send this to whoever reviews contracts on your team before the next one lands on their desk.

About the Author: Kevin W. Barron, MBA, FHFMA, FACHE is a nationally recognized healthcare contracting and payer relations executive with over 30 years of experience in healthcare finance. He is an author, speaker, and mentor to emerging leaders in healthcare finance. Follow Kevin on LinkedIn or subscribe to his weekly newsletter at https://www.KevinWatsonBarron.com

School Won't Teach You to Negotiate Payer Contracts. Mentors Will.

Kevin W. Barron — Tue, 17 Mar 2026 05:00:00 +0000

Lucas walked into his first payer negotiation with an MBA, a strong grasp of healthcare finance theory, and a spreadsheet modeling three different rate scenarios. Twenty minutes in, the payer's negotiator floated a risk-corridor structure Lucas had never encountered in any class, tied to a dealbreaker buried in section 12 that Lucas didn't recognize as a dealbreaker at all. He nodded, said he'd need to review it, and left the room without knowing whether he'd just protected his organization or given something away.

His degree had taught him the theory behind managed care. Nobody had taught him what to actually do in that room.

Why I believe the classroom stops short

Healthcare finance and payer contract negotiation draw on analytical thinking, strategic planning, policy knowledge, and interpersonal skill all at once, and academic programs genuinely lay a foundation in the first three. What they consistently fall short on is the fourth, and the hands-on tactics that only show up once you're actually across the table from a payer. That's not a flaw in the curriculum. It's a limit of what a classroom can teach.

The external problem is real: managed care theory and negotiation tactics are hard to package into a syllabus, because so much of what matters depends on reading a specific room, a specific payer, a specific moment in a specific negotiation. But the internal problem is what actually slows careers down. It's early-career professionals like Lucas walking into rooms without anyone having walked them through it first, and organizations that treat mentorship as a nice-to-have instead of a deliberate part of how new negotiators get built.

I ask "why" more than almost any other question in this work, in negotiations and in mentoring both, because understanding why a strategy works is what separates someone who can execute a tactic from someone who can adapt one when the room doesn't go the way they planned. That's the part no textbook covers, and it's exactly the part mentorship is built to teach.

What mentorship actually does

A mentor functions as a navigator through payer contracts in a way no case study can replicate. They walk a mentee through real negotiations, successful and failed both, and explain the why behind each decision, not just the how. That distinction matters more than it sounds like it should. Understanding why a strategy worked is what lets someone adapt it to a different negotiation later. Understanding only how to execute it once teaches nothing beyond that one situation.

The learning itself works differently than a classroom too. A mentor puts a mentee into real negotiation scenarios, gives real-time feedback, and builds understanding of things like value-based agreements, risk-sharing structures, and reimbursement negotiation through direct exposure rather than a lecture. That's also where the soft skills get built, the ones that matter as much as any spreadsheet: communication, empathy, problem-solving, and the relationship-building that lets someone prioritize issues and spot a genuine dealbreaker instead of missing it the way Lucas did.

None of that shows up on a transcript. All of it shows up in the room.

What changes over the long run through mentorship

Skip mentorship, and every new negotiator relearns the same lessons the hard way, one missed dealbreaker and one uncertain moment at a time, the way Lucas did in that first meeting.

Lucas found a mentor after that negotiation, a senior contracting executive willing to walk him through what that risk corridor actually meant and why section 12 mattered more than it looked. Eighteen months later, Lucas caught a similar structure in his own negotiation, recognized it immediately, and countered it before the payer had finished explaining it. He's since started mentoring two analysts on his own team, which is the part of this that compounds. Mentees who get this kind of guidance don't just become more confident negotiators. They become the next mentors.

If you're early in this field, find one experienced negotiator willing to walk you through an actual negotiation this quarter. If you're the experienced one, offer that to someone before they ask.

Mentorship doesn't replace formal education. It's what turns that education into something you can actually use across a negotiating table.

Call to Action: If a mentor changed how you handled a negotiation early in your career, tell me about them in the comments. If you're looking for that kind of guidance and don't know where to start, reach out to me directly. I mean that.

Send this to the newest negotiator on your team, and consider being the mentor this article is describing.

About the Author: Kevin W. Barron, MBA, FHFMA, FACHE is a nationally recognized healthcare contracting and payer relations executive with over 30 years of experience in healthcare finance. He is an author, speaker, and mentor to emerging leaders in healthcare finance. Follow Kevin on LinkedIn or subscribe to his weekly newsletter at https://www.KevinWatsonBarron.com

Bring Revenue Cycle In Before You Negotiate, Not After You Sign

Kevin W. Barron — Tue, 24 Mar 2026 05:00:00 +0000

Renata closed a contract renewal she was proud of. Better rates, cleaner escalator language, a faster dispute resolution clause than the old agreement had. Four months into the new term, denials on a specific procedure code started climbing, and nobody on her negotiation team could explain why until billing finally got looped in. The new contract's global rate structure didn't map cleanly onto how that service line actually coded the episode. Revenue cycle had known that would be a problem. Nobody had asked them before the contract was signed.

Renata spent the next six months fixing in claims what could have been fixed in redlines.

The disconnect that shows up on the wrong side of the P&L

A contract negotiation team can build financially sophisticated terms and still hand the organization a problem, because the terms that look right on paper have to survive contact with how coding, billing, and collections actually operate day to day. That gap between what gets negotiated and what gets billed is exactly where revenue quietly leaks out of an otherwise well-negotiated agreement.

The external problem is structural: revenue cycle and contracting sit in different departments, often reporting up through different leaders, with different daily priorities and their own versions of urgent. But the internal problem is what actually costs the money. It's treating revenue cycle as a department that implements a contract after the fact instead of a partner that helps design it before the fact. Renata's team didn't lack expertise. They lacked a seat at the table early enough for that expertise to matter.

I've watched organizations recover more revenue from fixing this one disconnect than from almost any single negotiation tactic. The contract terms were rarely the problem. The sequence was.

Six practices that close the gap

Early engagement matters more than any other item on this list. Bring revenue cycle leaders in from the start of negotiations, formally, with an actual agenda covering existing contract shortfalls, remedies, and priorities for the new agreement, not just an informal hallway conversation. Their view into coding, billing, and reimbursement mechanics is exactly the perspective that catches a problem like Renata's before it's written into a contract.

Ground the whole process in data-driven decision making. Past contract performance, denial rates, and reimbursement trends from both revenue cycle and contracting should inform the same negotiation, and it's worth casting a wide net for that data. Useful numbers sometimes sit with departments or individuals nobody thought to ask.

From there, move to collaborative goal setting. Shared, specific, measurable goals tied to the organization's actual strategic priorities keep both teams accountable to the same outcome instead of two separate ones. Contracting by committee isn't efficient, but a real consensus on priorities before negotiations start is worth building.

Keep clear communication running throughout, not just at the start. Weekly or biweekly status updates, more often only if the pace of negotiations genuinely demands it, let both teams catch a needed reprioritization while there's still time to act on it.

Build in expertise exchange between the two teams where it's feasible. Cross-training revenue cycle and contracting staff on each other's day-to-day work builds better contract terms over time and, in the short term, builds the working relationships that make the next negotiation faster.

And close every negotiation with a post-negotiation review. Bring every revenue cycle department into a debrief, walk through the negotiated terms, set clear expectations, and capture what was learned so the next contract benefits from it instead of repeating the same gap.

If aligning revenue cycle and contracting is something your organization is working through, I write about exactly this kind of operational detail every week in Mastering Managed Care. Subscribe before your next renewal cycle starts.

What changes when the sequence is fixed

Skip this alignment, and even a well-negotiated contract can bleed revenue quietly for the length of its term, the way Renata's did, with nobody catching the gap until claims start coming back wrong.

Renata rebuilt her process around these six practices for the next major renewal. Revenue cycle leadership sat in the first planning meeting, not the fourth. The team caught a coding mismatch in a draft rate structure before it ever reached signature, fixed it in redlines instead of in denials, and closed the negotiation with a shared debrief that fed directly into planning for the contract after that one.

Before your next negotiation kicks off, put revenue cycle leadership on the invite for the first planning meeting, not a later one.

The benefit of getting this right isn't just cleaner terms. It's a contract that's financially sound and operationally survivable from day one, instead of one that needs six months of cleanup to become what it was supposed to be at signature.

Call to Action: If a coding or billing detail has ever surfaced after a contract was already signed, tell me what happened in the comments. These are exactly the stories that help the next negotiation catch the problem earlier.

Send this to whoever leads your revenue cycle team before your next contract kickoff meeting, not after it.

About the Author: Kevin W. Barron, MBA, FHFMA, FACHE is a nationally recognized healthcare contracting and payer relations executive with over 30 years of experience in healthcare finance. He is an author, speaker, and mentor to emerging leaders in healthcare finance. Follow Kevin on LinkedIn or subscribe to his weekly newsletter at https://www.KevinWatsonBarron.com

Withholding Data From a Payer Doesn't Protect Your Leverage

Kevin W. Barron — Fri, 24 Apr 2026 05:00:00 +0000

Victor sat on six months of utilization data that would have explained an odd spike in denials before he ever brought it to the payer. His reasoning felt sound at the time: show your hand early and you give the other side something to negotiate against. So he held it, pushed through three rounds of back-and-forth on a rate dispute that the data would have settled in the first round, and watched the negotiation drag two extra months while both sides burned time arguing over a question the numbers had already answered.

When he finally shared the data because the deadlock left him no other option, the payer's negotiator asked the obvious question: "Why didn't we start here?"

Victor didn't have a good answer, because there wasn't one.

The instinct that costs more than it protects

Withholding information in a negotiation feels like leverage. It rarely is. What it actually does is extend the negotiation, since both sides end up negotiating around a gap instead of a shared set of facts, and extended negotiations cost real money in delayed revenue, unresolved claims, and staff hours nobody budgeted for.

The external problem is real: payers and providers have genuine reasons to be cautious with each other, competitive position, contractual sensitivity, a history of disputes that made both sides guarded. But the internal problem is what actually drives up cost. It's the assumption, on either side, that transparency is a concession rather than a strategy. Victor wasn't protecting his organization by sitting on that data. He was extending a negotiation his own numbers could have shortened.

I've hosted Joint Operating Committees with payer partners for years specifically because the relationships that work best are the ones where neither side is negotiating from behind a curtain. Transparency isn't the soft option in this work. It's the one that actually closes faster.

What transparency looks like in practice

Five things build real transparency into a payer-provider relationship, and they hold up whether you're mid-negotiation or years into a standing contract.

Start with transparent data sharing. Claims data, utilization patterns, quality metrics, and financial performance need to move both directions, openly, because that's what lets both sides spot the real problem instead of arguing around it. Skip this and you lengthen negotiations, lose revenue to the delay, and miss data irregularities that would have changed a payment decision months earlier.

Pair that with clear contract language. A contract functions like a set of marriage vows and a divorce decree in one document, the part you hope lasts and the part you hope you never need. Ambiguous language turns into disputes and legal costs later, so responsibilities, reimbursement terms, quality expectations, and dispute resolution all need to be explicit from the start.

Build in regular communication on a standing cadence, not just during active negotiations. I run Joint Operating Committees for this reason: they give both sides a place to resolve trended claim issues, work through quality initiatives, and surface cost-saving opportunities before those things turn into disputes.

Set performance metrics with real accountability on both sides. The metrics need to be measurable and tied to goals both parties actually agreed to, with a framework for addressing shortfalls and recognizing wins. Bring in your internal quality and outcomes experts before you agree to a pay-for-performance provision. They'll tell you which targets are realistic and which ones will quietly cost you money for two years before anyone admits it.

And when a negotiation genuinely stalls, consider third-party facilitation. A neutral mediator or consultant can bridge a gap that both sides have stopped being able to see clearly on their own. I haven't needed this often, but I wouldn't hesitate to bring in a neutral party for a valuable payer relationship that's genuinely stuck.

What it costs to hold back, and what changes when you don't

Remember this: Victor's two extra months weren't free. They cost his organization delayed revenue, a strained relationship with a payer his system needed to keep, and a reputation for being difficult to negotiate with that outlasted the actual dispute.

The next contract cycle, Victor opened with the data instead of holding it. He walked into the first meeting with the utilization numbers, the quality metrics, and a proposed JOC cadence for the life of the contract, all before either side had made a single ask. The negotiation closed in one round, and the payer's negotiator brought up the earlier dispute unprompted, this time as an example of how much faster things moved once both sides stopped guessing.

Before your next negotiation, make a list of everything you'd normally hold back until asked, and bring it to the table first instead.

Transparency in this work isn't a sign of weakness. It's the thing that turns a negotiation into a relationship, and a relationship is what actually gets you better terms the next time around.

Call to Action: If you've ever seen a negotiation shortened by sharing information early instead of holding it back, tell me what happened in the comments. I want to hear how it changed the outcome.

Send this to the colleague on your team who's still holding data back until the last possible round.

About the Author: Kevin W. Barron, MBA, FHFMA, FACHE is a nationally recognized healthcare contracting and payer relations executive with over 30 years of experience in healthcare finance. He is an author, speaker, and mentor to emerging leaders in healthcare finance. Follow Kevin on LinkedIn or subscribe to his weekly newsletter at https://www.KevinWatsonBarron.com

Managed Care 101: What It Means and What It Doesn't

Kevin W. Barron — Tue, 31 Mar 2026 05:00:00 +0000

Derek had eight months of contracting experience and a strong set of year-over-year savings numbers when he stood up in front of the medical executive committee to present his team's managed care results. He opened with the framing he'd used in every internal meeting that quarter: "Our job is to control what we spend on care." Halfway through his second slide, the chief of surgery cut him off. "So when you say control spending, are you telling this committee that keeping my patients healthy is secondary to your budget?" The room went quiet. Derek hadn't said anything false. He'd just said something incomplete, and in that room, incomplete sounded like a confession.

He spent the rest of the meeting playing defense on a point he actually agreed with.

The gap that isn't in the numbers

Managed care gets reduced to a cost story more often than it should, and usually by the people whose job is to defend it. That's an easy trap, because cost containment is the part of the job that shows up in a spreadsheet and gets asked about most in an executive meeting. It's also only one of three things managed care is actually built to do, and leaving the other two out of the room is exactly what turns a clinical leader into an adversary instead of a partner.

The external problem is that managed care genuinely is complicated, spanning contract negotiation, claims administration, quality reporting, and regulatory compliance all at once, and no single term captures that. But the internal problem, the one Derek ran into, is more specific: when the people representing managed care internally talk about it as pure cost control, they hand every clinical stakeholder in the room a reason to distrust them. Nobody wants to hear that their patients' care is being run through a budget exercise, even when that's not actually what's happening.

I've been doing this work since 1992, and the negotiators and analysts who earn trust fastest, from physicians, health plan sponsors, and plan members alike, are the ones who can explain what managed care is actually built to balance, not just what it's built to save.

The three fundamentals worth reiterating here

Managed care rests on three tenets, and all three need to be in the room together, every time.

Cost containment is the discipline of negotiating contracts that align payer and provider incentives so that high-quality care stays financially sustainable for everyone delivering it. It's real, and it's necessary, but it's not the whole story.

Utilization management exists to get the right care, at the right time, in the right setting, catching both under-treatment and over-treatment before either one hurts the patient or the system. This is the piece that gets left out of the cost conversation most often, and it's the one that actually protects clinical judgment instead of overriding it.

Quality assurance is the non-negotiable third leg. Managed care stakeholders monitor and evaluate the care being delivered specifically so cost discipline never comes at the expense of the outcome the patient actually needs. Leave this out of the framing and every cost conversation sounds like a threat to the thing it's supposed to protect.

Say all three in the same breath, every time, and the room stops hearing a budget pitch. They hear the actual system they're part of.

What changes when you lead with all three

Lead with cost alone, and you'll spend every meeting rebuilding trust you didn't need to lose. That's what cost Derek the rest of his presentation, a room full of clinical leaders who now assumed his numbers were the whole agenda instead of one piece of it.

Derek rebuilt his next presentation around all three tenets before he opened with a single savings figure. He started with utilization management data showing where the right care had been delivered in the right setting, moved to quality outcomes tied to that care, and closed with the cost impact as the result of getting the first two right, not the goal that drove them. The same chief of surgery asked two clarifying questions and signed off on the next quarter's targets before the meeting ended.

Before your next stakeholder conversation about managed care, write out all three tenets and check that your talking points actually cover all of them, not just the one that's easiest to measure.

Managed care has been evolving since long before either of us got into this field, and it'll keep evolving. The fundamentals underneath it haven't changed since 1992, and neither has the cost of leaving two-thirds of them out of the room.

Call to Action: If you've ever had a managed care conversation go sideways because cost was the only thing on the table, tell me what happened in the comments. I want to hear how you got the room back.

Send this to whoever on your team is presenting managed care results to clinical leadership next.

About the Author: Kevin W. Barron, MBA, FHFMA, FACHE is a nationally recognized healthcare contracting and payer relations executive with over 30 years of experience in healthcare finance. He is an author, speaker, and mentor to emerging leaders in healthcare finance. Follow Kevin on LinkedIn or subscribe to his weekly newsletter at https://www.KevinWatsonBarron.com

Becker's Podcast: Pushing Back on Aggressive Payer Tactics

Kevin W. Barron — Mon, 16 Jun 2025 05:00:00 +0000

I joined Becker's Healthcare Podcast to talk payer relations and revenue cycle strategy. The episode was also published episodes of Becker's Revenue Cycle, and Becker's CFO Podcast

How aggressive payer tactics are changing, and what it takes to navigate them
Building smarter contract oversight to catch issues before they erode revenue
Why aligning contracting within Revenue Cycle has delivered measurable results — for both patient care and financial performance
A mission-first approach to revenue cycle operations, and why purpose matters as much as process

▶️ Listen to the full episode: https://blubrry.com/beckershealthcarepodcast/146330394/

>Listen on Blubrry

The Hidden Cost of Winning the Rate (MGMA Insights Podcast)

Kevin W. Barron — Wed, 29 Jul 2026 05:00:00 +0000

Kevin W. Barron on the MGMA Insights Podcast — Key Takeaways

Rates aren't the whole story. Negotiation success gets measured by rate increases, but operational clauses — prior auth, medical necessity definitions, documentation standards — quietly erode reimbursement over time. "It may take months to negotiate a contract, but years to live through what you negotiated."
Integration over silos. At University Health, contracting, auditing, and contract management all sit inside the revenue cycle — an uncommon structure that keeps the team accountable for outcomes, not just terms.
Negotiation is relationship management. Know your deal-breakers, but make sure the other side gets some wins too. With payer consolidation and thin staffing, reaching the right person takes texts, calls, emails, and LinkedIn — whatever works.
The real leaks happen post-signature. As University Health's medical group has grown toward 900 providers across more specialties, operational complexity — not the negotiated rate — is where revenue quietly slips away.
Underpayments are harder to catch than denials. Shifting fee schedules (CMS-driven or payer-driven) create variances that require constant reconciliation against what's built into Epic's Resolute Billing System.
AI is already changing the work. What used to take 5 hours to redline an 80-page contract now takes 2–3 minutes with AI tools — but human expertise is still essential to interpret and validate what the AI produces.
Purpose drives the day-to-day. "Our whole goal is to make the mission sustainable — we want to be here 50 years from now." A visible reminder on his desk: "This is my why."

Resources

Never Split the Difference by Christopher Voss
Epic Resolute Billing System
MGMA Payer Contract Playbook
MGMA Analyzing Payer Contracts Playbook
MGMA DataDive (Signature benchmarking resource)
"The race for more revenue in medical groups: What’s your gameplan?" (MGMA Stat article)
MGMA Annual Conference | Sept. 27-30 | San Antonio, TX

Media Attribution

Three Decades. Three Pillars. One System for Payer Strategy.

Kevin W. Barron — Tue, 07 Apr 2026 05:00:00 +0000

In today's challenging operating environment, C-suite teams don't just need better contracts. They need a better system, one that turns payer relationships into strategic assets.

In three decades of healthcare finance and payer strategy, I've seen the same pattern play out at every organization, regardless of size or market. The most persistent and expensive payer challenges almost always trace back to the same three things: People, Portfolio, and Process.

Most leaders zero in on contract language, rate disputes, or regulatory shifts. Those matter. But they're not the whole picture, and CFOs who stop there are managing symptoms. The real competitive advantage comes from aligning internal capability with external contracting strategy in a way that's disciplined, measurable, and repeatable.

That's the problem the People-Portfolio-Process Model was built to solve. I've used it to manage multi-billion-dollar payer portfolios, improve reimbursement, and protect relationships over the long term. It isn't theory. It's the operating system behind measurable gains and operational stability in some of the most complex payer environments in the country. I know, because I built it.

People

The quality of your team sets the ceiling on your outcomes. That's not about credentials alone. It's about whether the people at the table have the skill set, the decision-making authority, and the collaborative instincts to execute under pressure. In payer negotiations, the person across from the payer can move the outcome as much as the terms on the page.

Portfolio

Every payer agreement is part of a portfolio, not a standalone deal. A balanced portfolio aligns with your mission, protects your margins, and strengthens your position in the market. When one agreement quietly undercuts another, you lose leverage without ever seeing it on a term sheet, and the drift compounds.

Process

Even strong people and strong contracts underperform without disciplined process. Process is what carries strategic intent into operational execution. It's the difference between a negotiated rate and a collected rate, between a compliance requirement on paper and one that actually holds up under audit.

When People, Portfolio, and Process are aligned, you negotiate from a position of strength, execute with precision, and sustain results well past the next rate cycle.

Take this to your team this week. Audit your payer strategy against the 3P Model:

Do you have the right people at the table, with both expertise and authority?
Is your portfolio balanced, mission-aligned, and managed as one system rather than a stack of individual deals?
Is your process predictable, data-driven, and resilient to leadership turnover?

The organizations getting this right aren't negotiating harder. They're negotiating smarter, with a system built to outlast any single deal or any single negotiator.

About the Author

Your Payer's Directory Is Wrong. Your Contract Doesn't Care.

Kevin W. Barron — Tue, 08 Sep 2026 05:00:00 +0000

A patient with a new Medicare Advantage card calls the number listed for your cardiology group. It rings at a suite the practice vacated sixteen months ago. The next name is a nephrologist filed under cardiology. The third answers, and the scheduler says that physician stopped taking new patients last spring.

The patient calls a competitor and books the appointment. Nobody in your organization ever learns what happened.

A CMS national review of Medicare Advantage directories found that 48.74% of provider locations carried at least one inaccuracy: wrong phone, wrong address, or outdated patient acceptance status. The industry spends more than $2 billion a year maintaining that data.

Wes manages provider data for a 600-physician group. Every month he sends a roster file to fourteen payers. Four confirm receipt. One returns a usable error report. He finds out whether the rest landed when an office manager calls him, angry, because patients can't reach her physician. Or worse, because the only number that does reach him is the personal cell he gave a scheduler once, now published in a payer directory nobody at the practice has ever looked at.

Wes isn't failing. He's doing the job as designed, which is to verify the data, transmit the file, and hope the payer holds up its end.

The rules he can't enforce

The No Surprises Act requires plans to verify directory data every 90 days, process updates within two business days of receipt, and respond to inquiries within one business day, with penalties reaching $100 per day per affected individual. That's a real standard, but enforcement runs between the plan and a regulator. Wes isn't a party to it.

Under the CY 2026 Final Rule, MA organizations must submit directory data to CMS for Medicare Plan Finder and annually attest to its accuracy. The plan certifies a data set built from your roster. You don't see the filing and you don't approve it, and when it's wrong your patients absorb the access failure while you absorb the volume loss.

The rules nobody in your building wrote

Ask who owns the provider directory and count the answers. Credentialing owns verification. Medical staff services owns the file. Marketing owns the website. IT owns the transmission. Payer Relations owns the contract that never mentions any of it.

That's not an oversight. It's the decision made by not consciously making one, and it holds because provider data errors have never cost enough, visibly enough, to earn an owner.

What to do

Name one owner of the roster of record. If the answer takes more than four words, you don't have one.

Audit the directory the way a patient uses it. The provider portal usually looks fine. The public directory is what directs the patient. Quarterly, per payer.

Pull your roster of record for one TIN.
Pull the payer's public-facing directory for that same TIN. The public site, not the portal.
Compare five fields: name and NPI, service location, accepting-new-patients status, specialty and subspecialty, and a phone number that reaches a live scheduler.
Score it. Discrepancy rate by field and by payer, with screenshots and date stamps.
Send it to the plan's provider data team in writing with a correction deadline, and log their response against the two-business-day standard.

The window

Your payers are about to be graded in public on data you supply. Beginning with the 2027 plan year, CMS publishes MA directories directly to Medicare Plan Finder. Beginning with 2028, the REAL Health Providers Act adds annual accuracy analyses and public accuracy scores.

Pull one payer's public directory for one TIN this week and check five fields. Whatever you find is your baseline. Run it again next quarter, and the quarter after that.

Walk into your next renewal with four quarters of scored discrepancies and the plan's provider data director takes your call. Walk in with nothing and you'll be handed someone else's remediation plan, built to fix their score rather than your access problem.

Nobody negotiates the directory because nobody files it under contracting. Your patients never read the contract. They read the directory.

About the Author

Mastering Managed Care

New Negotiators Don't Lose Deals Over Rates. They Lose Them Over Words.

The gap that isn't about intelligence

The terms worth knowing before your next meeting

Eight contract terms every new negotiator needs

What it costs to skip this

If you're new to this

Most-discussed on LinkedIn last week

AI Isn't Coming for Your Contracting Job. Complacency Is.

The part you don’t want to hear, and neither does Kraig

What actually changes, and what doesn't

What's actually at stake

The Denial Nobody Owns Is the One Costing You the Most

Why this blind spot is so expensive

Where contracting has to show up, not just sign off:

Evidence that closing the cracks moves the number

How to find the denials nobody owns before they compound:

Nobody Was Checking. One Analyst Found $2 Million.

Front-Line Staff Are Costing You Millions. It's Not Their Fault.

Most Medical Necessity Denials Come From a Silo, Not a Clinical Problem

Why this gap costs more than it should

Five (5) ways to close the gap

What changes when the two teams actually operate as one

The Negotiation Isn't the Hard Part of a Payer Contract. The Implementation Is.

Where deals actually succeed or fail

The three-phase checklist that closes the gap

What changes when implementation gets the same rigor as negotiation

Payer JOC Meetings Fail When They're Just a Formality

Why the meeting exists and why it quietly stops working

Seven (7) practices that make a JOC actually work

What changes when the JOC actually functions

The Termination Clause Is the Most Overlooked Protection in a Payer Contract

Why this clause gets underwritten

The four termination provisions worth understanding

What changes when the clause actually fits the problem

Strong Negotiations Are Built on Relationships, Not Just Rate Sheets

What efficiency quietly costs you

Five (5) practices that build the relationship, not just the deal

What changes when the relationship exists

Payer Contracts Should Pay for Social Needs, Not Just Diagnoses

The gap between what drives outcomes and what gets funded

Six ways to build SDOH into the contract itself

What changes when the contract actually pays for it

The 20 Payer Contract Clauses That Put Providers Most at Risk

Why the risk can survive legal review

The 20 provisions worth checking on every, single contract

What changes when the list gets used

School Won't Teach You to Negotiate Payer Contracts. Mentors Will.

Why I believe the classroom stops short

What mentorship actually does

What changes over the long run through mentorship

Bring Revenue Cycle In Before You Negotiate, Not After You Sign

The disconnect that shows up on the wrong side of the P&L

Six practices that close the gap

What changes when the sequence is fixed

Withholding Data From a Payer Doesn't Protect Your Leverage

The instinct that costs more than it protects

What transparency looks like in practice

What it costs to hold back, and what changes when you don't

Managed Care 101: What It Means and What It Doesn't

The gap that isn't in the numbers

The three fundamentals worth reiterating here

What changes when you lead with all three

Becker's Podcast: Pushing Back on Aggressive Payer Tactics

The Hidden Cost of Winning the Rate (MGMA Insights Podcast)

Resources

Media Attribution

Three Decades. Three Pillars. One System for Payer Strategy.

Your Payer's Directory Is Wrong. Your Contract Doesn't Care.

The rules he can't enforce

The rules nobody in your building wrote

What to do

The window