Free Network Build Assessment
Score your buildNetworks change throughout the year: providers leave, practices close, groups restructure. CMS's rules and guidance set specific notices for significant network changes. Here's what triggers a notice to CMS, what members must be told, and when.
A network doesn't stop mattering once it has passed. Medicare Advantage networks have to meet the standards throughout the contract year, and applicants attest to exactly that. Two sources set the mid-year notices: Chapter 4 of the Medicare Managed Care Manual and CMS's December 2024 network adequacy guidance, plus 42 CFR 422.111(e) for what members must be told.
Under the December 2024 guidance, four events can pull a network review forward: an application, a termination CMS considers significant, a network access complaint, and a gap the plan discloses itself, which plans must report to their CMS Account Manager. A triggered full review may reset the triennial review clock. Read these sources directly, and check them for updates each year.
Medicaid managed care plans answer to their state contracts for mid-year changes, and those terms vary. Plans operating in both markets should track each program's triggers separately.
Every large network has routine provider turnover, and only some of it is worth a notice to CMS. For terminations, the question in Chapter 4 is which ones a plan considers significant. A useful working test is whether the change creates or risks a gap in a required standard: a county and specialty combination that met the standard before the change and may not after it.
Changes that usually belong in this 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 generally aren't significant 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 touches the standards.
For terminations a plan considers significant, Chapter 4 of the Medicare Managed Care Manual asks for notice to the CMS Account Manager at least 90 days before the effective date. Some terminations come with less warning than that, so tell your Account Manager as soon as you learn of them, and check the manual for how it treats those cases.
This notice is not an administrative technicality. A significant termination can trigger a network review, so include what you are doing to fill the gap when you send it.
Meeting a 90-day clock means your network team needs a systematic way to spot when an expected termination is significant. If a hospital system's contract is heading toward termination, assess the impact right away, so the notice can go out on time and replacement contracting can start immediately.
That clock may also interact with the notice terms in your provider agreements. A provider may give less notice than the contract requires, leaving the plan with contractual remedies and a CMS notice to manage at the same moment. Run these two timelines in parallel, not one after the other.
Notice to CMS is only half of it. The other half, and often the more work, is notice to members. Under 42 CFR 422.111(e), MA plans must give enrollee notice of a provider termination 45 calendar days ahead for primary care and behavioral health providers and 30 days for other specialties.
Members in active treatment need particular care, such as those receiving chemotherapy, recovering from surgery, or managing a chronic condition with a specific specialist. Check 42 CFR 422.112 and your own policies for the continuity of care obligations that apply.
Member notification at scale is a significant undertaking. Plans need to identify which members have seen the terminating provider, work out who is in active treatment, produce the notices, and track responses. Plans without a way to link provider terminations to affected members can struggle to meet the notice dates when a large provider or system leaves on short notice.
Not every notice leads to a review. But a termination CMS considers significant is one of the listed triggers in the December 2024 guidance, so plans should assume that notice of one may prompt CMS to look at the affected service area.
Be ready for that. A triggered full review means uploading HSD tables and being scored by CMS's Automated Criteria Check, and it may reset the triennial clock. Any organization with a contract ID can also upload HSD tables to the Network Management Module at any time to test compliance, which is a useful way to see CMS's answer early.
Plans with an adequacy model that can be re-run quickly for specific county and specialty combinations will respond faster than plans that build the analysis from scratch each time.
The practical starting point is simple: run your adequacy model with the departing provider removed and compare the results against the standard for each affected county and specialty. If any combination drops below the standard, or gets close to it, treat the departure as potentially significant.
This analysis requires a model that works at the level of individual providers, by county and specialty, not just aggregate network counts. Blueprint's adequacy scoring shows which providers a county depends on, on straight-line distance, so a team can see which departures would matter most.
Also look past the raw result. Even if a departure doesn't drop a county below the standard, leaving one or two providers holding up a high-demand specialty makes the network vulnerable to the next departure. Managing to a buffer above the standard, rather than to the standard itself, gives you room when things change.
It is far better to find potential gaps before they happen. 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 when the termination letter arrives are already behind; plans that saw the group's instability early and began alternative contracting have time to close the potential gap.
Reactive management, by contrast, treats mid-year network changes as events to respond to rather than anticipate. It leaves less time for replacement contracting and puts legal review, CMS correspondence, member communications, and expedited contracting all on the same short clock.
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.