Regulatory deadlines in RCM tend to arrive from different directions at once — CMS interoperability rules, DME-specific list updates, dental code cycles, and No Surprises Act reforms all run on their own calendars, issued by different offices, with different lead times. It’s easy for one to slip through simply because it wasn’t on anyone’s radar next to the others. Here are five dates and cycles that belong on every RCM team’s calendar right now, in order of what’s coming next.
1. November 1, 2026 — No Surprises Act IDR batching takes effect
The Federal Independent Dispute Resolution Operations final rule allows parties to batch up to 50 related items or services into a single IDR dispute, but this specific provision — along with updated open-negotiation procedures — doesn’t take effect until November 1, 2026, even though most of the rest of the rule became effective back on August 3, 2026. If your team has a backlog of similar, individually small underpayment disputes with a given payer, this is the date those can start going in together instead of one at a time. Start tagging candidate claims now so you’re ready to file the day the provision goes live, rather than reconstructing your claims history after the fact.
2. December 4, 2026 — CARC/RARC compliance guidance expected under the IDR rule
Tied to the same IDR overhaul, additional compliance guidance on claim adjustment reason codes (CARCs) and remittance advice remark codes (RARCs) is expected by December 4, 2026. This is easy to overlook because it’s guidance rather than a hard rule change, but it’s likely to affect how denial and underpayment reason codes need to be documented to support an IDR-eligible dispute — worth a calendar flag for whoever owns your denial-code taxonomy, so the guidance gets reviewed as soon as it’s published rather than discovered months later during a dispute filing.
3. January 1, 2027 — CMS-0057-F electronic prior authorization APIs go live
This is the deadline most RCM teams have already heard about, and for good reason: by January 1, 2027, Medicare Advantage plans, state Medicaid and CHIP programs, and Qualified Health Plan issuers on the federal Exchanges must have all five required FHIR APIs operational — Patient Access, Provider Access, Payer-to-Payer, Prior Authorization, and Provider Directory. The operational requirements (72-hour/seven-day decision timeframes, specific denial reasons, public metrics reporting) have technically been in effect since January 1, 2026, so this date is really about the technology catching up to rules that are already supposed to be enforced. Use the remaining months to confirm your EHR or clearing house vendor’s readiness timeline in writing, not just verbally.
4. Your DME MAC’s next DMEPOS list update (recurring, watch for the Federal Register notice)
CMS’s Master List, Required Face-to-Face/Written Order Prior to Delivery List, and Required Prior Authorization List for DMEPOS items get updated on a recurring basis, each announced roughly 90 days ahead of its effective date. The most recent update took effect April 13, 2026, adding 18 codes to the Master List, 8 oxygen-related codes to the F2F/WOPD List, and 7 codes (5 orthoses, 2 pneumatic compression devices) to the Required Prior Authorization List, bringing that list to 74 total codes. There isn’t a fixed future date to put on the calendar yet for the next round, which is exactly the risk — build a recurring quarterly check of CMS’s DMEPOS prior authorization pages and your MAC jurisdiction’s bulletins into your compliance calendar rather than waiting for a vendor alert to tell you a new list has dropped.
5. The DMEPOS exemption annual cycle — June 1 through May 31
If your practice or supply company is pursuing (or maintaining) an exemption from DMEPOS prior authorization requirements, the annual evaluation cycle runs June 1 through May 31, with a supplier’s affirmation rate during that window determining exemption eligibility for the following cycle. This is a rolling deadline rather than a single date, but it’s exactly the kind of ongoing requirement that’s easy to lose track of amid one-time regulatory changes — put a recurring reminder on the calendar well before May 31 each year to review your affirmation rate and flag any documentation patterns that need correcting before the cycle closes.
Honorable mentions worth tracking, even though they’re not urgent yet
- CMS-9882-P (Transparency in Coverage proposed rule): comment period closed in late February 2026; watch for a final rule, but don’t build workflows around the proposed changes until CMS actually finalizes them.
- Hospital price transparency’s April 1, 2026 median/percentile methodology requirement has already passed, but if your organization hasn’t confirmed its machine-readable files were actually updated to the new format, that verification is overdue rather than upcoming.
- CDT 2026 code adoption by individual payers: most dental plans adopt the current CDT set on a rolling basis, so confirm each major payer’s timeline for recognizing the new anesthesia, denture, and implant-maintenance codes rather than assuming universal same-day adoption.
Teams that stay ahead of this kind of scattered regulatory calendar tend to keep one shared document — not five separate ones per topic — with dates, source links, and an owner assigned to each item. The single point of failure in most practices isn’t a lack of awareness that a rule exists; it’s that awareness living in one person’s inbox instead of somewhere the whole team checks on a schedule.
Takeaway
Between now and January 2027, RCM teams have at least five concrete dates or cycles to track: IDR batching (November 1, 2026), CARC/RARC guidance (expected December 4, 2026), the CMS-0057-F API deadline (January 1, 2027), the next DMEPOS list update (watch for the Federal Register notice), and the DMEPOS exemption’s annual June-to-May cycle. Put all five on one shared calendar with an owner assigned to each, rather than tracking them separately by topic.
For when Medicare denial risk needs to be disclosed to the patient in advance, see our ABN forms guide — note the form itself was updated in 2026.