The new out-of-network arbitration rule took effect. Almost none of it did.
The effective date was August 3. Three things landed. The provision written for anesthesiology got its date the same day, from a notice rather than the rule, and still has no definition.
Somewhere this year an anesthesia group decided which of its underpaid out-of-network claims are worth arbitrating. Not this week. Once, in one meeting, for every claim that follows.
Out-of-network strategy in this specialty sits near one of two ends. At one end the group has built or rented a mechanism that files every eligible claim as a matter of course. The volume is the strategy, and nobody looks at claims one at a time. At the other end sits a number: a charge threshold, above which a claim is filed individually and below which it is written off. Most groups I have seen are nearer the second end, and that threshold is the entire out-of-network policy.
The threshold gets set in a room. Revenue cycle, the billing vendor or the outside firm that would do the filing, a practice administrator, and one clinician, usually the medical director, usually the person at the table with the least time to be there. They set a number once, and it governs thousands of claims until somebody revisits it.
The number is not really about the merits of any claim. It is about float.
Independent dispute resolution (IDR) is the No Surprises Act process for these claims: each side submits an offer and an outside arbiter picks one. Until June 11, taking a single claim there meant fronting a non-refundable $115 administrative fee plus the arbiter’s own fee, which runs $375 to $800 at the arbiters CMS certifies. The arbiter’s fee comes back if you win, so the group is out five hundred to nine hundred dollars a dispute and the only real question is for how long. In the last quarter of 2024 the median determination took eighty-one business days from the day the case was assigned, which is closer to four calendar months, and the disputed payment itself is not due until thirty days after that. Providers prevail in roughly 85 percent of these in the aggregate, so the expected loss is small. The float was not, and the float is what the threshold is priced against.
Batching was supposed to be the answer to that: a stack of small claims filed as one dispute, one fee covering all of them. Lower the cost per claim and the threshold comes down with it. But the criteria did not fit the way an anesthesia group actually bills, so the threshold stayed where it was.
What falls below that line is revenue the group never collects. It impacts how many sites the group can staff, how many rooms one person covers, and how many call nights get spread across the same number of people.
I lead an anesthesia company. The provision I am going to spend the middle of this piece calling undefined names anesthesiology among the four specialties it was written for, which means I have a stake in whether it ever gets written. Read the rest knowing that.
On August 3 a final rule rewriting that process reached its effective date. The trade press said so, the law firm alerts said so, and the specialty societies had already welcomed the rule back in May. A clinician reading any of it would reasonably conclude that the rule governing that room had arrived.
Almost none of it had.
What arrived on August 3 was three things: a definition of bundled payment arrangements, a set of modifications to what has to be disclosed alongside the qualifying payment amount, the payer’s own benchmark number, and the provisions governing the arbiter’s fee, which set when it is paid and what happens if it is not, rather than what it costs. Useful, narrow, and not the reason anyone was watching. The one change that had already altered the filing arithmetic landed two months earlier, on its own schedule. The administrative fee fell from $115 to $15 per party, for disputes initiated on or after June 11, and the Departments that jointly run this — Treasury, Labor and HHS — reached that date by waiving the delayed-effective-date requirements of both the Administrative Procedure Act and the Congressional Review Act so it could take hold five business days after publication. When the government wants a provision to move, it moves.
The date a rule takes effect and the date it reaches the work are different days, and only one of them gets reported.
Everything else sits in the applicability paragraph, which is where rules keep their real calendar. Some of it carries a date. The revised definition of a batched dispute applies beginning November 1. So do the provisions on continuing negotiations and certain withdrawals. But most of the rule hangs on a different kind of clock, and to see it you need one term first. Every dispute has to open with a negotiation period, a thirty-business-day window in which the two sides are required to try to settle before an arbiter ever sees it. That window is the hook the rest of the rule hangs from. And the operative sentence reads that the amendments “are applicable to disputes with open negotiation periods beginning 90 calendar days after the Departments issue guidance announcing that the functionality supporting these provisions has become available.”
Not ninety days after the rule. Ninety days after the government says the software works.
That sentence governs open negotiation, dispute initiation, arbiter selection, the offer and payment-determination deadlines, the eligibility review, and the batching criteria. The Departments state their own expectation in the preamble: all of that functionality is anticipated twenty-four months after the effective date. That is August 2028. The guidance comes on a rolling basis beginning this summer, and rolling means there is not a date. There is a sequence of them, and the order belongs to the agency.
Four days after the effective date the Departments published an implementation timeline guide, and it adds two things the rule did not specify. It sets the build order: the registry first, then the suspension of resubmissions, then open negotiation, initiation, arbiter selection, withdrawals, and extensions. And it says the Departments expect to implement that functionality in Spring 2027, which sits well inside the preamble's twenty-four months. A build order is not an applicability date. Each provision still waits on its own notice and on the ninety days that run from it, and the eligibility review is absent from the order entirely.
Now the part that matters to those of us named in the rule. Buried in the batching criteria is a provision written for four specialties by name. The regulatory text reads: “For anesthesiology, radiology, pathology, and laboratory qualified IDR items and services, the qualified IDR items and services were furnished to one or more patients and were billed under service codes belonging to the same Category I CPT code range, as specified in guidance published by the Secretary.”
The last clause is the entire provision. The provision that finally lets an anesthesia group batch the way its billing actually works turns on a grouping of codes that the rule does not define and hands to guidance. No such guidance has been issued as of this writing. Category I codes are the ordinary procedure codes, and the rule says range where the CMS fact sheet summarizing it says section, which in CPT taxonomy are not obviously the same thing. The provision has a date and no content.
One thing it does settle. Batching under that provision turns on the code range, not on the credential of the clinician who furnished the case. The payment modifiers that identify who delivered the anesthetic sit on top of the same base code and do not move a claim out of its range, so on its face the provision reaches the case whoever gave the anesthetic.
It acquired the date on August 3, and not from the rule. On the same day the rule took effect, CMS posted a notice announcing that batching functionality would be available November 1, and that all batching provisions would apply to disputes with open negotiation periods beginning on and after that date. That notice is the first of the rolling functionality announcements, and it reaches batching alone; the eligibility review sits in the same sentence of the rule, on the same trigger, and has no announcement of its own. Anyone who had read only the rule, carefully and correctly, would have had to tell their group there was no date for batching. That is what we told ours. Last Monday there was one. It came from a notice on a webpage, and it is now the operative fact.
Three constraints bound what a batch can carry, and a fourth bounds what can follow it. The notice caps a batch at fifty line items. The rule requires that every item was furnished inside a single thirty-business-day service window, and that the batch went through its own thirty-business-day open negotiation period ending within four business days of initiation. Then the notice starts a thirty-business-day cooling-off clock after a determination, during which the filer may not come back at the same party over the same item or service. Three of those windows run thirty business days and none of them is the same window. There is a version of this that is a real improvement for a group whose claims share a code range and a month, and a version that is a filing-window problem. Which one it turns out to be depends on a definition that does not exist yet.
And November 1 is not the date a group can batch. It is the date the clock starts. The notice applies the batching provisions to disputes whose open negotiation period begins on or after November 1. That negotiation window runs thirty business days, and initiation follows within four business days of its close. So the first batch filed under the provision written for anesthesiology is a December event, and the letters that open those negotiations go out in November, against a grouping of codes that does not exist.
The strongest objection to everything above is that I have described delay as though it were injury, and the parties being made to wait are winning.
That objection is correct on the facts, and the facts are not close. In the second half of 2025, providers, facilities and air ambulance services prevailed in roughly 85 percent of payment determinations; plans and issuers prevailed in about 14 percent. The prevailing offer came in above the qualifying payment amount 87 percent of the time. Defaults, where one side never submitted an offer, accounted for 17 percent of determinations, and 90 percent of those went the providers’ way.
And the volume is not a rounding error against expectations. The Departments planned for a process that would take tens of thousands of disputes a year and received 489,000 in the first year alone, fourteen times what they had projected. In the last six months of 2025, disputing parties filed 1.37 million. By the end of January 2026 the cumulative figure was over 5.1 million. Three filers accounted for 38 percent of that half-year’s filings. Ten accounted for two-thirds.
That concentration is worth sitting with for a few minutes, because it is the first of the two ends this piece opened on. Filing at that scale is a business, run by outside firms on providers’ behalf, and it is the end where no threshold exists because none is needed. Payer-side counsel describes the volume problem in exactly those terms: “the submission of large volumes of disputes and offers in excess of billed charges” by “providers and their third-party intermediaries.” The group with a threshold is not one of those firms. It is the party the process was nominally built for, and it is the party the threshold exists to protect from the process.
Of the disputes initiated in that period, eligibility was challenged on 42 percent and 19 percent were found ineligible. A government building screening functionality slowly for a process that drew fourteen times its projected volume in its first year and has grown since is not obviously an injustice. It is a queue.
But hold the two halves of this rule next to each other, because the structure concedes something. The provision that lowers the cost of filing was accelerated by waiver and took effect in June. The provisions that screen what gets filed — the eligibility review, arbiter selection, the offer and determination deadlines — wait on a portal. That is not a conspiracy and I would not argue it as one. But the fee cut did not simply arrive faster. The Departments waived two statutory delay requirements to make it arrive faster, and no waiver can build a portal. The result is the same either way: the cost of filing fell in June, and the review that screens what gets filed has no date.
The concepts in the rule are sound, but the mechanics most of it waits on don’t exist. There is now a functional bottleneck sitting just past a cheaper way to initiate disputes. The container holding the queue is going to need to be very large.
Go back to the room where the number gets set. That threshold was priced against a $115 fee and a determination that took the better part of four months. Since June 11 the fee has been $15. And the determinations have gotten faster — 62 percent of them closed within thirty business days in the second half of 2025, against 37 percent in the first half, which puts the median inside the window. Both inputs to that number moved this year. The number has not.
All of which is the part worth carrying out of a payment-policy fight and into any room where someone announces a date. The effective date is the least useful number in a rule. It is the one that gets into the headline, the summary email, and the slide, and it tells you when the document is law rather than when it changes anything. The date that matters is in the applicability paragraph, and sometimes it is not a date at all but a condition — a guidance document, a portal that has to be built, a go-live that has to be announced — held by the agency rather than the calendar.
So the next time someone brings you a rule with a date on it, ask the second question. Not when does this take effect. When does this reach the work, and who decides.
This piece sits alongside the benchmark is the whole game, which covered how the qualifying payment amount is built. The map that holds all of it lives here.
From the room you can’t see.



The paragraph I would put in front of every clinician is the one about what that threshold actually governs: how many sites get staffed, how many rooms one person covers, how many call nights get divided among the same people. From the head of the bed that arithmetic shows up as whether there is somebody in the room next door at two in the morning, and it is completely invisible to the patient on the table - who also never chose me, which is the reason this specialty got named in the statute in the first place. Your line that batching turns on the code range rather than on the credential of the clinician who furnished the case is worth underlining, because the modifiers sit on top of the same base code and plenty of people assume otherwise. And the closing question is the one I am going to steal: not when does this take effect, but when does it reach the work, and who decides.