The Centers for Medicare & Medicaid Services (CMS) has announced that the Federal Independent Dispute Resolution (IDR) process is moving to a new, centralized IDR Gateway, replacing the single-use web form providers have relied on since the No Surprises Act (NSA) took effect. The transition is expected in late 2026, and CMS says more detail on registration and implementation is coming in the months ahead.
We sat down with Aspirion’s Liana Hamilton, President of Payment Variance Recovery, and Nikki Ritchson, Senior Director, Payment Variance, to unpack what the IDR Gateway actually changes, who needs to act, and how hospital revenue cycle teams should be preparing while the details are still taking shape.
Q. In plain terms, what is the IDR Gateway and why is CMS building it?
Liana Hamilton: The current federal IDR process runs on individual, single-use web forms—every dispute is its own standalone submission, with no persistent account or dashboard behind it. The IDR Gateway replaces that with a single, centralized platform. Instead of submitting disputes into a void and waiting to hear back, organizations will have an actual account: a dashboard where they can initiate and respond to disputes, see status and entity assignments in one place, and track where each case sits in the process. That’s a meaningful upgrade in visibility, and it’s consistent with what we’ve seen from CMS elsewhere—an effort to bring more structure and accountability to a process that has, frankly, been clunky to administer at scale.
Q. CMS is also adding new security and identity verification requirements. What should revenue cycle leaders know about that?
Nikki Ritchson: This is a piece people shouldn’t overlook. The Gateway will introduce identity verification and access controls, and—notably—it will restrict participation to U.S.-based users. For organizations that rely on any offshore support in their dispute workflows, that’s a real operational consideration, not a footnote. Teams need to understand now who on their staff, or their vendor’s staff, is actually touching IDR submissions, because the new platform is going to enforce that boundary at the account level.
Q. Who actually needs to sign up for a Gateway account—every provider?
Liana Hamilton: Not necessarily, and this is where we’re already fielding questions from clients. If your organization directly processes disputes, represents parties, or submits IDR web forms today, you’ll need an account in the new Gateway. But if you rely on a third-party administrator—like Aspirion—to manage that work on your behalf, you generally won’t need to create a separate account yourself. What you do need is assurance that your administrator is completing the required registration. The account has to sit with whichever party is actually managing the dispute activity. We’d encourage every organization to confirm, in writing if needed, who on the vendor side owns that responsibility.
Q. What is Aspirion doing to prepare, and what does that mean for clients who rely on you for IDR support?
Nikki Ritchson: We’re already working through this. Given how central NSA and IDR work is to what we do for hospital and health system partners, we’re evaluating ownership and governance of our future Gateway account, mapping out user access and security verification needs—including the U.S.-based requirement—and stress-testing how this changes our current dispute workflows and the way we coordinate with clients and vendor partners. The goal is a seamless transition for our clients: they shouldn’t feel friction from this change, they should just see the same disputes moving through a better system.
Q. CMS says registration details are still coming. What should hospital revenue cycle teams do in the meantime—and what shouldn’t they do?
Liana Hamilton: Don’t wait to think about it, but also don’t try to act on incomplete information. Continue using the existing Federal IDR web form process—that hasn’t changed yet, and CMS has been clear the current system remains in place until the Gateway launches in late 2026. What teams should be doing now is internal: get clarity on who within your organization, or which vendor, owns your dispute submissions today, and start asking your third-party administrators how they’re preparing for account ownership and identity verification under the new rules. When CMS releases registration details, the organizations that move fastest will be the ones who already know who’s responsible for what.
The bottom line: this is a real operational shift, not a cosmetic redesign. The IDR Gateway should make dispute management more transparent for providers—but only for organizations that get their account ownership and access questions sorted out before the switch happens.
The federal IDR landscape keeps evolving, and staying ahead of it takes both close attention to CMS guidance and workflows built to adapt quickly. Aspirion’s out-of-network recovery team is monitoring the IDR Gateway rollout closely and will share updates as CMS releases additional detail. Reach out to our team to learn how we can help your hospital or health system prepare for the transition.
