Mid-Year Network Changes: What Requires CMS Notification and What Doesn't

The Regulatory Basis for Mid-Year Network Change Reporting

The requirement to notify CMS of material mid-year network changes derives primarily from 42 CFR 422.100, which establishes the ongoing obligation of Medicare Advantage organizations to maintain an adequate network throughout the benefit year — not merely at the time of annual submission. The regulation does not permit plans to submit an adequate network in October for a January benefit year start and then allow that network to erode without oversight. The obligation is continuous, and the notification framework reflects that ongoing accountability.

CMS has elaborated on the practical requirements for mid-year notification through Medicare Managed Care Manual Chapter 4, which addresses network adequacy, and through HPMS memoranda issued across recent benefit years. Together, these sources define what constitutes a reportable change, what the required timeline for notification is, and what documentation CMS expects to receive. Plans that are not tracking these sources continuously often discover their reporting obligations only after a compliance issue has materialized.

It is worth noting that state Medicaid programs operating managed care plans have parallel mid-year notification requirements under 42 CFR 438.68 and state-specific contracts, which may be more or less prescriptive than the Medicare Advantage framework depending on the state. Plans operating in both markets need to maintain separate tracking systems for each regulatory framework's notification triggers.

What Constitutes a "Material Change" Requiring CMS Notification

CMS uses the concept of materiality to distinguish between routine provider-level fluctuations that occur in any large network and changes significant enough to warrant regulatory notification. While CMS has not published a bright-line definition of materiality in every context, the practical standard that has emerged from guidance and audit experience is whether the change creates or risks creating a gap in a required adequacy standard — a county-specialty combination that was meeting threshold before the change and may not meet threshold after it.

Changes that consistently fall into the material category include the termination of a health system contract affecting multiple specialties across multiple counties, the closure of a large multi-specialty practice, the loss of the only or one of very few contracted providers in a required specialty category in a given county, and any change that eliminates access for a defined geographic segment of the plan's membership.

Changes that are generally not material in isolation include individual provider retirements in markets with robust provider supply, address changes for providers who continue to serve members at alternate locations, and changes to provider tax identification numbers or group affiliations that do not affect the provider's participation or service delivery. The key question is always whether the change affects member access in a way that implicates adequacy thresholds.

The 30-Day Advance Notice Requirement for Significant Provider Terminations

For terminations that meet the materiality threshold, CMS requires plans to provide advance notice before the termination takes effect. The standard period is 30 days prior to the effective date of a significant provider termination, although CMS's guidance acknowledges that involuntary terminations — where a provider terminates on short notice — may not allow for 30-day advance notice. In those cases, plans are expected to notify CMS as soon as practicable after learning of the termination.

The 30-day advance notice requirement is not merely an administrative technicality. It exists to give CMS an opportunity to assess the adequacy impact of the termination and, if necessary, engage with the plan on corrective action before members lose access. Plans that notify CMS in advance and include a remediation plan in their notification — describing the steps being taken to fill the adequacy gap — are treated more favorably in compliance reviews than plans that notify after the fact with no remediation plan.

Operationally, meeting the 30-day requirement demands that your network operations team has a systematic process for identifying when a planned or anticipated termination is approaching materiality. This is not a process that can be run reactively. If a hospital system gives 90 days notice of contract termination, the network team needs to assess materiality within the first week — not on day 85 — so that the CMS notification can be submitted with adequate lead time and the gap-filling contracting can begin immediately.

Plans should also be aware that the 30-day notice requirement may interact with contractual notice provisions in their provider agreements. If a provider agreement requires 90 days notice for termination but the provider gives only 30, the plan may have contractual remedies against the provider while simultaneously having an obligation to notify CMS promptly. These two timelines must be managed in parallel, not sequentially.

Member Notification Obligations for Mid-Year Changes

CMS notification is only one of the two notification obligations triggered by material mid-year network changes. The second — and often more operationally intensive — obligation is member notification. Under 42 CFR 422.111 and 422.112, MA plans must provide advance notice to affected members when a provider they have been seeing terminates from the network.

The member notification requirement specifies that affected members must receive notice at least 30 days before the provider's termination date. The notice must include information about how to select a new provider and how to request continuity of care for ongoing treatment. For members in active treatment — particularly those receiving chemotherapy, undergoing post-surgical recovery, or managing a chronic condition with a specific specialist — the continuity of care provisions under 42 CFR 422.112(b)(3) may require the plan to allow the member to continue seeing the terminating provider for a defined transition period at in-network cost-sharing.

Member notification at scale is a significant operational undertaking. Plans need to identify which members have had recent claims with the terminating provider, segment those members by treatment status, produce individualized notification letters, and track responses. Plans that do not have automated member impact analysis capabilities tied to their provider termination tracking often struggle to meet the 30-day member notice requirement when a large provider or system termination occurs on short notice.

When a Mid-Year Change Triggers an Adequacy Review

Not every material change notification automatically triggers a formal adequacy review by CMS. Whether CMS initiates a review depends on the scale of the change, the affected market's adequacy profile, and CMS's current audit priorities. However, plans should operate on the assumption that any notification of a significant provider termination may prompt CMS to request an updated adequacy analysis for the affected service area.

The most reliable triggers for a CMS-initiated adequacy review following a mid-year change are: a system termination affecting multiple counties in a service area, a change that eliminates the only contracted provider in a required specialty in a county, and any change occurring in a service area that CMS has previously identified as having adequacy concerns. Plans with prior adequacy deficiencies are more likely to receive heightened scrutiny on mid-year changes.

When a mid-year change triggers an adequacy review, CMS will typically request that the plan submit an updated adequacy attestation for the affected counties and specialties, along with documentation of the remediation steps underway. Plans that have a ready-made adequacy model that can be re-run quickly for specific county-specialty combinations are able to respond to these requests far more efficiently than plans that build their adequacy analysis from scratch each time.

How to Assess Whether a Provider Departure Creates a Material Adequacy Gap

The practical starting point for materiality assessment is straightforward: run your adequacy model with the departing provider removed and compare the results against the threshold for each affected county-specialty combination. If any county-specialty combination drops below threshold — or falls within your buffer margin — the departure is a candidate for material change classification.

This analysis requires an adequacy model that is granular enough to assess individual provider contributions by county and specialty, not just aggregate network counts. Models that operate at the plan-wide level or that cannot isolate the adequacy contribution of individual providers or provider groups are not adequate for this purpose. Blueprint's adequacy tracking engine is built to run this kind of counterfactual analysis on demand, generating a gap report that identifies every county-specialty combination affected by a specific provider removal.

Beyond the raw threshold analysis, materiality assessment should also consider concentration risk: even if a departure does not drop a county below threshold, if it leaves only one or two providers above threshold in a high-demand specialty, the network is highly vulnerable to the next departure. Plans that manage to a buffer above threshold — rather than to the threshold itself — have a more defensible adequacy position when CMS scrutinizes mid-year changes.

Proactive vs. Reactive Mid-Year Network Management Strategy

The plans that navigate mid-year network changes most successfully are the ones that identify potential gaps before they materialize, not after. Proactive network management means monitoring indicators of provider instability — practice sales, physician retirements, hospital system financial stress, group restructuring — and initiating replacement contracting before a departure creates an adequacy gap.

A proactive strategy requires intelligence gathering that goes beyond claims data and credentialing records. Network intelligence sources that flag provider market activity — system acquisitions, practice closures, physician employment changes — give network operations teams lead time to respond. Plans that learn about a major group dissolution from a CMS notification request are already behind; plans that identified the group's instability six months earlier and began alternative contracting have likely already resolved the potential gap.

Reactive management, by contrast, treats mid-year network changes as events to be responded to rather than anticipated. This approach consistently produces more exception filings, more member notification obligations, and more CMS scrutiny. The overhead of reactive management — legal review, CMS correspondence, member communications, expedited contracting — almost always exceeds the investment required for proactive monitoring. Blueprint's network management platform is built around the proactive model, surfacing risk signals in the provider network before they become compliance events.