Our earlier article covers account setup and cutover controls. This guide is for the person who will own the Gateway inside a practice, hospital or billing company: how to structure the organization, who should be an administrator, how Tax IDs and workspaces fit together, and what to audit every month.
Who needs to be in the Gateway
CMS's guidance is that organizations and individuals that process disputes, represent parties or submit IDR web forms should sign up. That includes provider organizations that file their own disputes and third-party billing companies or IDR vendors that file on behalf of clients. Staff who never touch disputes do not need accounts. CMS has also said access is restricted to users based in the United States, which matters for teams with offshore staff; see our guide to offshore billing workflows.
Designing the organization structure
| Decision | Recommended approach | Why it matters |
|---|---|---|
| How many administrators | At least two per organization | One administrator is a single point of failure when someone is on leave or leaves the company. |
| Which Tax ID creates the organization | Follow CMS's technical guidance for organizations with multiple Tax IDs | Duplicate organizations for the same entity cause access and reporting confusion. |
| How a billing company appears | As its own organization, filing each dispute under the client's information | Keeps the vendor's staff, permissions and audit trail separate from each client's. |
| How to separate clients or offices | Use workspaces or equivalent groupings inside the organization | Staff should see only the disputes they work on. |
| Shared mailboxes | Use named individual accounts; route notifications to a monitored team inbox | Shared logins break identity verification and the audit trail. |
Identity verification and access hygiene
Every user verifies their identity before getting access. Treat Gateway credentials like banking credentials: one person per account, no sharing, and immediate removal when someone changes role or leaves. Read and follow the Gateway's rules of behavior; they are a condition of access, and breaching them can cost the organization its access during an active dispute window.
- Inventory everyone who currently submits web forms or receives IDR emails.
- Decide who needs Gateway access and at what level, and who does not.
- Create the organization and invite at least two administrators.
- Set up workspaces or groupings that mirror how your team divides work.
- Move filers one team at a time and confirm each can submit before January 15, 2027.
- Schedule a monthly access review that removes leavers and checks permissions.
Mapping existing disputes
Disputes filed through legacy web forms must be connected to your Gateway organization so your team can monitor them there. CMS's user guides describe a bulk mapping process for confirming which disputes belong to you, using a template file. Before you upload, reconcile the list against your own case log: confirm each dispute number, the parties, and whether the dispute is open or closed. A clean map is what makes Gateway reports trustworthy later.
Monthly administrator checklist
- Active users match the current team roster; leavers removed.
- Every organization still has at least two working administrators.
- Dispute notifications reach a monitored inbox.
- New disputes appear in the right workspace.
- Open disputes with deadlines in the next 10 business days are assigned to a named person.
- CMS Gateway notices reviewed for new functions, such as portal-based open negotiation.
What the Gateway does not do yet
The Gateway is being built in phases. Functions such as the federal IDR registry and portal-based open negotiation depend on future CMS announcements. Keep your current open negotiation process and records until CMS confirms the portal handles that step, and follow our final rule compliance checklist for what is still pending.
Roles and responsibilities
| Role | Responsibilities | Who should hold it |
|---|---|---|
| Administrator | Invites and removes users, sets permissions, manages workspaces and organization details | Two to four trusted staff, including one outside the IDR team for continuity |
| Dispute processor | Prepares and submits dispute forms, responds to entity requests | IDR specialists and analysts |
| Read-only reviewer | Monitors dispute status and reports | Managers, finance and compliance |
| Fee payer | Pays administrative and entity fees on time | Finance staff with clear deadlines |
Exact role names and permissions are set by CMS's user guides; map your internal roles to the access types the Gateway offers rather than giving everyone the highest level.
A cutover plan to January 15, 2027
- Week 1: confirm administrators and complete identity verification for them.
- Week 2: invite dispute processors and confirm each can sign in.
- Week 3: file new disputes through the Gateway while legacy forms remain available as a fallback.
- Week 4: map existing disputes and reconcile them against your case log.
- Before January 15: stop using legacy forms entirely and remove any workarounds.
Designing notifications
Dispute notices drive deadlines. Route Gateway notifications to a monitored team inbox and to the named owner of each dispute. Test that notifications arrive before relying on them, and document who checks the inbox on holidays and weekends, since business-day deadlines continue around them.
Offboarding and audit
- Remove Gateway access the same day an employee leaves or changes role.
- Keep a log of who was invited, by whom and when.
- Review administrator actions quarterly.
- Confirm vendors remove their staff from your workspaces when an engagement ends.
