Free Network Build Assessment
Score your buildWhen a network changes mid-year, some notices to CMS and to members are not optional. This guide covers the events to watch, the notice rules we can source, how to test the result in HPMS, and how to protect current member care while you fix a gap.
Medicare Advantage compliance teams often talk about mid-year network "amendments" as if there were one standard filing. We can't point to a CMS rule that sets up a formal network adequacy amendment, with its own form and clock, so check your contract, your CMS Account Manager, and current HPMS memos before you plan around one. What the sources we can cite do require is more specific, and it is not optional.
Under CMS's December 2024 network adequacy guidance, a gap the plan discloses itself must be reported to its CMS Account Manager. For terminations a plan considers significant, Chapter 4 of the Medicare Managed Care Manual asks for notice to the Account Manager at least 90 days before the effective date. Under 42 CFR 422.111(e), enrollees must get notice of a provider termination 45 calendar days ahead for primary care and behavioral health providers, and 30 days for other specialties.
Any of these events should prompt the team to rerun adequacy for the affected counties and types, and to ask whether CMS and members have to be told:
Other changes, such as adding providers or improving coverage in counties that already pass, carry no such urgency, but keep your HSD data current as they happen.
Three kinds of events are worth building monitoring around, so that the team catches them before they become compliance gaps.
Hospital system exits and large group practice departures have the widest impact. When a hospital system terminates its contract mid-year, the plan can lose many providers across multiple types at once. Plans without redundancy may find themselves below the standard in several counties at the same time.
Behavioral health provider attrition is a common specialty-level trigger. In markets with thin behavioral health networks, an individual departure can tip a county below the standard for psychiatry or clinical social work even when the loss involves a single provider. Note the 45-day enrollee notice for behavioral health terminations.
Primary care physician retirements and panel closures are a persistent trigger. A PCP who closes their Medicare panel, even without formally terminating their contract, is no longer an option for a member who needs a new doctor. Monitoring that relies solely on contract status will miss this until it shows up in claims data or member complaints.
You don't need to wait for a CMS review to see the effect of a change. Any organization with a contract ID can upload HSD tables to the Network Management Module in HPMS at any time to test compliance, and the Automated Criteria Check (ACC) then scores every provider and facility type in every county. CMS also offers an informal Consultation upload before the formal triennial review.
Upload complete, current tables, with names and addresses typed the same way as before, since CMS guidance warns that differences can cause processing problems and network deficiencies. Then read the result and the ZIP Code Report for Failed Counties to see where the misses cluster. Keep in mind that a termination CMS considers significant, a network access complaint, or a gap you disclose can pull a full review forward, and a triggered full review may reset the triennial clock.
Earlier notice is better for everyone. The 90-day Chapter 4 notice and the enrollee notice periods run backward from the termination's effective date, so a plan that learns about a termination late has very little room. Build intake so that contracting, credentialing, and provider relations feed one termination record with an effective date, and let the notice clocks start from it.
Also watch the overlap with your other deadlines. Contracts due for triennial review are prompted to upload in mid-June, applications come due early in the calendar year, and bids are due the first Monday in June. A gap that opens in the months before those dates can collide with them, so plan your team's capacity accordingly.
If CMS asks about a network change, plans should be prepared to provide the following without significant delay:
A plan that can produce complete records quickly is in a far better position than one whose documents don't match the dates and events it has described.
Telling CMS about a change doesn't replace the plan's duty to the members affected by it. Both have to be managed at once, and the network operations team needs a workflow that addresses both.
For members in active treatment with a terminated provider, the plan cannot simply remove the provider from the system and move on. It should identify affected members, notify them of the change, and coordinate the transition to an in-network provider. Check the current continuity of care requirements in 42 CFR 422.112 and your contract for what you must offer during that transition.
The most effective approach is to treat network monitoring, CMS notice, and member care continuity as a single process. When monitoring identifies an event, the plan's response protocol should start the CMS notice review, the member impact analysis, and the member notice workflow together. When these functions are siloed, the compliance timeline and the member care timeline tend to collide at the worst possible moment.
Blueprint automates the network build workflows described in this article: from adequacy modeling to provider outreach tracking. See it with your state and line of business.