Filing Mid-Year Network Adequacy Amendments: When You Must File and How

The Distinction Between Required and Optional Amendments

Medicare Advantage compliance teams often treat mid-year network adequacy amendments as an administrative option — something to file if things get particularly bad, or if CMS asks. That framing is incorrect and creates meaningful regulatory risk. Under 42 CFR 422.116 and the companion policy guidance in the MA Application Instructions and supporting HPMS memos, certain changes to a plan's network trigger a mandatory amendment obligation regardless of whether CMS has identified the issue independently.

The distinction between required and optional amendments matters because CMS evaluates a plan's amendment history as part of its overall compliance posture. Plans that proactively file amendments when required — even when the change reflects a network weakness — are treated more favorably than plans that allow gaps to persist unacknowledged until CMS identifies them through its own monitoring activity. The former demonstrates a functioning compliance program; the latter may indicate a more systemic problem.

Mandatory Amendment Triggers: What the Regulations Require

Under 42 CFR 422.116 and the CMS MA Enrollment and Appeals guidance, the following events trigger a mandatory mid-year network adequacy amendment obligation:

• Provider terminations that create a threshold deficiency: When a provider termination — whether voluntary or involuntary — causes a county-specialty combination to fall below the CMS adequacy threshold for that benefit year, the plan must file an amendment within a defined window. CMS policy guidance has historically indicated this window is 30 days from the date the plan knew or should have known of the deficiency, though plans should verify the current benefit year's specific guidance in their contract.
• Service area reductions: Any reduction in the plan's approved service area during the contract year requires an amendment filing. Service area reductions affect which county standards apply and which members may be subject to involuntary disenrollment, making them among the most consequential mid-year changes.
• Specialty gaps falling below threshold due to practice closure or change of specialty: A provider who changes their primary specialty designation in NPPES or closes their practice to MA patients — even if they remain nominally in the network — can trigger a threshold deficiency in the relevant specialty category. Plans are expected to monitor for these changes through ongoing credentialing re-verification rather than relying on the provider to self-report.
• Material changes to contracted providers' practice locations: If a significant share of a specialty's adequacy coverage depended on a provider at a particular location, and that provider relocates outside the time-and-distance radius for a material portion of the service area, an amendment may be required.

Optional amendments — those the plan may file but is not required to — typically involve network enhancements: adding providers, improving coverage in non-deficient counties, or updating provider directory information for providers already counted in the adequacy filing. These are encouraged but not mandated.

The Most Common Real-World Triggers

In practice, the triggering events that generate the most mid-year amendment activity across Medicare Advantage plans fall into three categories. Understanding these patterns helps network operations teams build monitoring systems that catch triggers before they become compliance gaps.

Hospital system exits and large group practice departures are the highest-impact triggers. When a hospital system terminates its contract mid-year — often following a fee schedule dispute — the plan can lose dozens of providers across multiple specialty categories simultaneously. Plans that have not built redundancy into their network for these specialties may find themselves below threshold in multiple counties at once, requiring a complex multi-specialty amendment filing on a compressed timeline.

Behavioral health provider attrition has become the most common specialty-level trigger over the past two benefit years. The behavioral health workforce shortage has led to high turnover rates among contracted providers. Plans in markets with thin behavioral health networks may see individual provider departures tip counties below the psychiatric and clinical social work thresholds even when the loss involves a single provider.

Primary care physician retirements and panel closures are a persistent trigger in rural and suburban markets. A PCP who closes their Medicare panel — even without formally terminating their contract — effectively removes themselves from adequacy calculations if they are no longer accepting MA plan members. Plans whose monitoring processes rely solely on contract status rather than active panel status will miss these triggers until they show up in claims data or member complaints.

How the Amendment Process Differs from the Initial Filing

The initial network adequacy filing is submitted as part of the annual MA bid and contract process, with a defined submission window and a structured HPMS workflow. Mid-year amendments operate through the same HPMS module but follow a different procedural track that compliance teams need to understand before they need to use it.

The amendment process requires the plan to submit a revised network adequacy data file that reflects the current state of the network, including the change that triggered the amendment obligation. Unlike the initial filing, which is submitted against a future contract year's standards, amendments are reviewed against the current benefit year's applicable standards — which in some cases may differ from the standards the plan originally filed against if CMS issued any mid-year guidance changes (rare but not unprecedented).

The amendment package also requires a narrative explanation of the change, the date the triggering event occurred, the steps the plan has taken or is taking to remediate any resulting deficiency, and a projected timeline for reaching compliance if the plan is not currently compliant. This narrative is reviewed by a CMS analyst and is part of the official record if the situation escalates to enforcement.

The HPMS Amendment Workflow: Step by Step

Plans file mid-year amendments through the Network Management module in HPMS. The specific menu path changes periodically with HPMS updates, but the core workflow has remained consistent. The plan accesses its current contract year's network adequacy submission, selects the amendment function, and uploads a revised network data file in the required format.

The revised file must be a complete replacement of the applicable network data — not a delta or change log. HPMS will run the same automated validation checks against the amended filing that it ran against the initial submission, including NPI validation against NPPES and PECOS, duplicate detection, and threshold calculation. Plans should expect the same automated validation turnaround time (one to three business days) before the amendment enters analyst review.

After uploading the data file, the plan must complete the amendment narrative fields in HPMS. These are free-text fields that prompt for the triggering event, the affected counties and specialties, and the remediation plan. Plans should treat these fields as official regulatory submissions — not internal notes — and ensure the narrative is accurate, complete, and reviewed by legal or compliance counsel before submission.

CMS's standard timeline for amendment review is four to six weeks, though this can extend for complex amendments involving multiple counties and specialties. During the review period, the plan's current network adequacy status is in a pending state; CMS does not automatically grant the plan compliance credit for the amended network until the amendment is approved.

Timing Considerations Relative to the Contract Year

The timing of a mid-year amendment matters for several reasons beyond the obvious compliance imperative. Amendments filed in the early months of the contract year (January through April) give the plan more runway to remediate deficiencies before CMS's mid-year monitoring pulls data from the plan's network. Amendments filed in the latter half of the contract year (August through November) are more likely to overlap with the next benefit year's initial submission preparation, creating resource conflicts for the network operations team.

Plans should also consider the enrollment implications of amendment timing. If a mid-year amendment reflects a service area reduction or a significant network contraction, CMS may determine that some members need to be notified of material changes to their plan. Under 42 CFR 422.111, plans are required to notify members of significant changes to the provider network with at least 30 days' advance notice — a timeline that must be coordinated with the amendment filing, not treated as a separate downstream task.

For plans approaching the annual election period (AEP) in the fall, amendments filed after August 1 may also affect CMS's assessment of the plan's network for the upcoming benefit year's filing cycle, particularly if the amendment reflects ongoing structural weaknesses rather than a resolved one-time event.

What CMS Expects in the Amendment Package

Beyond the data file and the narrative fields, CMS may request additional documentation during amendment review. Plans should be prepared to provide the following without significant delay:

• The executed termination notice or letter from the departing provider or provider group, establishing the date of the triggering event
• Documentation of outreach to replacement providers, including contact logs, letters of intent, and any executed contracts or letters of agreement for providers in the contracting pipeline
• Updated provider directory documentation confirming that the terminated provider has been removed from the plan's online and print directories, consistent with the 72-hour update requirements under the CMS directory accuracy standards
• A member communication plan if the network change affects a materially defined population's access to a specific provider or specialty

CMS reviewers assess whether the plan's amendment response is consistent with a functioning network monitoring and remediation program. A plan that can produce complete documentation quickly signals that it has the operational infrastructure to manage network changes responsibly. A plan that cannot locate basic documentation — or whose documentation is inconsistent with the dates and events described in the narrative — signals the opposite.

Managing Amendments Without Disrupting Current Member Care

The compliance obligation to file a mid-year amendment runs parallel to — and does not supersede — the plan's obligation under 42 CFR 422.112 to ensure continuity of care for members affected by provider terminations. These two obligations must be managed simultaneously, and the network operations team needs a workflow that addresses both.

For members who were in active treatment with a terminated provider at the time of the termination, the plan is required to offer continuity of care for up to 90 days or until the end of the course of treatment, whichever is shorter, under conditions that allow care to continue without interruption. This means the plan cannot simply remove the provider from the system and move on — it must identify affected members, notify them of the change, and coordinate the transition of care to an in-network provider or authorize the continuity period with the terminated provider.

The most effective approach to managing this dual obligation is to treat network monitoring, amendment filing, and member care continuity as a single integrated process rather than three separate workflows. When a monitoring alert identifies a triggering event, the plan's response protocol should simultaneously initiate the amendment preparation process, the member impact analysis, and the continuity of care notification workflow. Plans that silo these functions typically find that the compliance timeline and the member care timeline collide at the worst possible moment.