Questions We're Hearing About the CMS IDR Operations Final Rule 

CMS recently released the long-awaited Operations Final Rule governing the No Surprises Act Independent Dispute Resolution process.  

We know that pivoting your internal playbooks for the third or fourth time this year is exhausting. A 600-page document is the last thing anyone wanted to digest this month, so we have pulled out the most frequent questions we’re discussing with our peers this week, focused entirely on what this means for your workflow and cash flow.

Check back! We will add more as they come up. Have a question not answered below?  Let's Talk

When do the new rules take effect?

Various changes are on very different clocks.

The fee change is immediate: the new $15 administrative fee applies to disputes initiated on or after June 11, 2026. The rest of the rule's definitions kick in a bit later, on the general effective date in early August.

The operational updates will take a lot longer. The CARC and RARC changes depend on guidance that hasn't come out yet and guarantee payers at least 4 months to comply, so realistically you won't see them on remittances until sometime in 2027. This may be stretched out even further as expected payer push-back creates delays.

For all portal-driven changes (the new open negotiation and initiation notices, the updated batching rules, the eligibility review), roll out is expected gradually as the functionality comes online. CMS expects all of it to be up within about two years.

Does the reduced administrative fee make low-balance claims worth pursuing?

It helps, and it's a real drop: the administrative fee falls from $115 to $15 per party. For small claims, that's the difference between the fee eating most of the recovery and barely registering.

But the administrative fee was never the number that killed low-balance claims. The bigger cost is the certified IDR entity fee, which is larger and gets paid by the losing party. So on a single small claim, there's still a serious cash-flow risk even when win rates favor the initiating party..

Where this actually changes the calculus is in combination with batching. You can now bundle up to 50 line items into one dispute, which spreads the fixed costs across many claims at once. A $15 fee plus a 50-item batch is what makes pursuing small-dollar claims genuinely viable, not the fee drop on its own.

So: yes, but the fee cut is one piece of it. The real unlock for low-balance work is batching plus the lower fee together.

Can we rely on CARCs and RARCs alone to determine IDR eligibility, or do we still need our own checks? 

Both, in a sense. The codes will let you clear a portion of cases automatically, but they won't carry the whole load.

Start with the good news. When a payer's coding signals that a claim is eligible, you can largely trust it. The payer has no incentive to wave through a dispute against itself, so false positives just aren't a real worry here. That means a meaningful slice of claims can move straight through without a human touching them, which is a genuine reduction in eligibility-review work.

The rest still needs review, for two reasons. First, eligibility isn't a single fact a code can settle. A claim can be coded as in-scope and still be ineligible on timing, open negotiation, batching, or whether a state law applies instead. The code only speaks to one piece of the picture. And the codes are explicitly non-binding anyway: even a payer flag saying something is ineligible doesn't control, since the certified IDR entity can still find it eligible on its own review.

Second, this assumes payers actually code things correctly and consistently, and that's a generous assumption. Expect uneven compliance, especially early.

So: the codes will shrink the eligibility burden, not erase it. Lean on them to auto-clear the clean cases, and keep your own checks running for everything else.

Did they really not get rid of the cooling off period? 

Frustratingly, no. There were rumors it might go away, and it didn't. The standard cooling-off period is still 90 calendar days, and for a lot of workflows that's still longer than anyone would like.

But there's a meaningful carve-out worth leaning into. For batched disputes, the cooling-off period drops to 30 business days instead of the full 90. So the same batching mechanics that make low-balance claims viable also buy you a much shorter wait before you can come back around on similar claims.

That's the move here. If you're batching anyway, you're already capturing the shorter window. The cooling-off period is still longer than ideal on single disputes, but batching is the lever that softens it. And it's hard to miss the signal in that design: pairing the shorter cooling-off period with the higher batching cap is CMS pretty clearly nudging everyone toward batching.

Can our systems handle these changes? 

Yes. If anything, these updates align perfectly with our approach to supporting organizations with NSA solutions.

A more codified, portal-routed process is exactly what's ripe for automation: structured inputs, predictable rules, and a federal portal to engage with programmatically. The changes don't just keep us busy, they expand what we can automate. Standardized codes and a defined process give technology more to work with, not less. The portal is still rolling out, so we will quickly adapt our implementations as the guidance lands.

And to be clear, this is all good news for providers. The rule takes a messy process and makes it more structured, which is precisely the kind of thing we can turn into an advantage.

Want to continue the discussion? Let's Talk