Free Network Build Assessment
Score your buildWhen CMS issues a network adequacy deficiency notice, plans have limited time and a specific process for appealing or responding. Understanding the appeals pathway, and how to build a compelling response, is essential for protecting your service area.
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. Take the response deadline from the notice. For applicants, the final chance is the response to the Notice of Intent to Deny, and 42 CFR 422.502(c)(2)(ii) allows 10 days. Plans can respond by closing the gap, submitting corrected HSD tables, or requesting an exception.
The term "appeal" is used loosely in the industry, and the day-to-day process is better described as a deficiency response and an exception request. If CMS denies an application, the applicant can request a hearing: the CY2027 application says the request must be received within 15 calendar days of the denial notice. Before that point, plans respond to deficiencies with evidence that the problem is data-based (an error in the submission that should be corrected) or supply-based (the needed providers truly aren't available).
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:
Testing your tables in CMS's Network Management Module before the formal review can catch these errors early. If you discover data errors for the first time in a deficiency notice, also examine your submission preparation process to prevent recurrence.
When a deficiency reflects a genuine network gap, the plan's options are to contract additional providers within the response window (usually not feasible for a hard specialty) or to submit an exception request under 42 CFR 422.116(f).
A successful exception request must demonstrate:
The strength of an exception request comes from the quality and specificity of its evidence. In 2021, CMS denied 259 of 448 requests, about 58%, according to MedPAC's June 2024 report.
Strong documentation includes:
If CMS denies an exception request, the plan faces a service area decision. For an applicant, that can mean losing the county. The plan can resubmit if it has new evidence, pursue additional provider contracting, or remove the county from the service area.
If an operating plan is considering leaving a county, it should check the member notification and transition obligations that come with a service area reduction before it decides.
The most effective approach to the deficiency process is avoiding it. Run your analysis early, test against CMS's Automated Criteria Check before the formal review, keep an outreach record as you go, and prepare exception requests only for gaps that truly meet the rule.
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.