Free Network Build Assessment
Score your buildWhen the providers you need aren't available within CMS time-and-distance standards for a given specialty and county, plans can file an exception request. Here's what 42 CFR 422.116(f) requires, how to document it, and why so many get denied.
A CMS network adequacy exception is a formal request that a Medicare Advantage plan files in HPMS, for one county and one specialty, using CMS's current exception request template. It is not a waiver of the adequacy requirement. Under 42 CFR 422.116(f), the plan must prove two things. First, the providers needed to meet the time and distance standard are not available. Second, the providers it did contract with are currently available and accessible to most enrollees, consistent with the local pattern of care.
Inability to contract is not a valid reason, and neither are the plan's own internal standards. CMS's December 2024 guidance is blunt on this. CMS is not asking whether you tried hard. It is asking whether its own picture of supply is wrong.
The guidance lists valid rationales and says the list is not limited to them. Each one is something a reviewer can check:
Two more are accepted only with substantial and credible evidence: the provider may cause beneficiary harm, or the provider is inappropriately credentialed under 42 CFR 422.204. Retain all your supporting documentation, not just what you upload.
MedPAC's June 2024 report says that in 2021 CMS denied 259 of the 448 exception requests it reviewed, or 58%, and that the most common reason was finding providers within the criteria that the plan failed to include on the request or HSD tables. So a good request is mostly a good census with an argument on top.
Start with CMS's Provider Supply file, but CMS warns it may not be a complete depiction of supply, so don't rely on it alone. The criteria aren't restricted by county or state boundaries. Keep an outreach record for each provider (NPI, name, practice address, date, method, outcome). That record won't win the request by itself, but it is how you learn who retired, moved or opted out.
The guidance says pattern-of-care evidence can be internal claims data showing the current pattern of care in that county and specialty, or a detailed explanation. Either way, compare the closer non-contracted providers against the farther contracted ones. Show where members actually go, and show that the contracted providers are taking new patients and can be reached.
Telehealth has a separate role. In the 15 specialty types listed in 42 CFR 422.116(d)(5), telehealth earns a 10 percentage point credit toward the required share of beneficiaries, though it does not by itself cure a deficiency.
The template lives in HPMS, and plans must use the current one. The exception forms and supporting documents (maps, screenshots, letters) go up as separate PDFs inside a single zip file. Non-contracted providers that don't fit on the form go on CMS's overflow template. Confirm the current conventions in the template instructions.
Keep each request specific to its county and specialty. It should name the actual providers in the census and the actual evidence for each one, not language copied across every exception in the filing.
Plans must resubmit all previously approved exceptions whenever CMS requests an HSD upload. An approval is a finding about supply at a point in time, and supply moves. Before each upload, re-verify every approved exception as if it were new.
The stakes differ by situation. MedPAC reports CMS has never imposed intermediate sanctions or civil money penalties for network adequacy noncompliance, but that new applications have been denied on this basis. For an applicant, a denied exception can mean losing the county.
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.