Medicare Advantage Network Adequacy Appeals: When and How to File

Understanding the Deficiency and Appeal Process

When CMS reviews a Medicare Advantage network adequacy submission and identifies county-specialty combinations where the submitted network does not meet CMS's standards, it issues a deficiency notice through HPMS. The deficiency notice specifies the county, the specialty type, the required adequacy threshold, and the plan's submitted adequacy level. Plans have 10 business days to respond to a deficiency notice — either by closing the gap, submitting a corrected data file, or requesting a waiver.

The term "appeal" is used loosely in the industry, but the formal process is better described as a deficiency response and waiver request. CMS does not have a formal administrative appeals process for network adequacy deficiencies in the same way it does for coverage determinations. What plans can do is respond to deficiencies with evidence that the deficiency is data-based (an error in the submission that should be corrected) or market-based (a structural provider shortage that supports a waiver approval).

Type 1: Data-Based Deficiency Responses

Some deficiency notices stem not from genuine network gaps but from data errors in the submission — providers geocoded to incorrect counties, providers submitted under incorrect specialty codes, or providers whose Medicare enrollment was not reflected correctly in the data. When a deficiency is data-based, the appropriate response is a corrected data submission with documentation explaining the error and the correction.

Data-based deficiency responses require the plan to:

• Identify the specific providers whose data was incorrect
• Verify the correct data through primary sources (PECOS enrollment, confirmed practice location, correct specialty code)
• Prepare and submit a corrected provider data file within the 10-business-day window
• Provide a written explanation of the data error and how it was identified and corrected

Plans with robust pre-submission validation processes rarely encounter data-based deficiencies, because these errors should be caught before submission. Plans that discover data errors for the first time in a deficiency notice need to also examine their submission preparation process to prevent recurrence.

Type 2: Market-Based Deficiency Responses and Waivers

When a deficiency reflects a genuine network gap — there are genuinely not enough contracted in-person providers to meet the adequacy standard in the identified county-specialty combination — the plan's options are to contract additional providers within the 10-business-day window (which is generally not feasible given contracting and credentialing timelines) or to submit a waiver request.

A successful waiver request must demonstrate:

• Provider supply constraint: That the available supply of in-person, Medicare-enrolled providers in the specialty type within the required geographic radius is genuinely insufficient to meet the adequacy standard through contracting alone. This is demonstrated with NPPES/PECOS data showing the total available provider population and the plan's contracting penetration rate.
• Good faith effort: That the plan made genuine, documented efforts to contract with every available in-person provider in the specialty type and county. Good faith effort documentation requires contemporaneous outreach logs with dates, methods, provider contacts, and responses — not a summary prepared after the fact.
• Alternative access arrangements: That despite the network gap, members in the affected county have access to care through alternative mechanisms — telehealth, transportation benefits, care coordination programs, or arrangements with nearby in-network providers.

Building the Waiver Case: Documentation Best Practices

The strength of a waiver request is determined by the quality and specificity of its documentation. CMS reviewers evaluate thousands of waiver requests and can distinguish between plans that have genuinely addressed the access problem and those submitting form-letter waivers that do not engage with the specific county's circumstances.

High-quality waiver documentation includes:

• A county-specific narrative that explains why this particular county's provider supply is constrained — citing physician-to-population ratios, geographic barriers, or documented provider retirement patterns
• A complete outreach log showing every provider contacted, the date and method of contact, and the outcome — not just a count of attempts
• Specific description of each alternative access mechanism, including how members access it, what services it covers, and how it is communicated to members in the affected county
• Evidence of member access through the alternative mechanisms — utilization data, member testimonials, or care coordination case examples where available

When CMS Denies a Waiver

If CMS denies a waiver request, the plan faces a service area decision: accept the service area reduction for the affected county or counties, or explore further options. In practice, options after a waiver denial are limited — the plan can resubmit with additional documentation if new information is available, pursue additional provider contracting and resubmit in a subsequent filing cycle, or accept the service area reduction and exit the county.

Plans that receive waiver denials and are considering a service area exit should be aware of the member notification and transition-of-care obligations that accompany a mid-year service area reduction — members in affected counties must be notified and provided a special enrollment period, and care coordination support must be provided for members with ongoing care relationships.

Prevention: The Best Adequacy Appeals Strategy

The most effective approach to the deficiency and appeals process is avoiding it. Plans with strong pre-submission adequacy analysis, robust good faith effort documentation built into their outreach workflow, and proactively submitted waiver requests for known gaps before filing receive significantly fewer deficiency notices than plans that submit without pre-analysis and respond reactively. Building the deficiency prevention infrastructure requires investment but consistently produces cleaner submissions, faster certification timelines, and fewer regulatory crises.