Free Network Build Assessment
Score your buildMost health plan compliance teams spend months preparing their network adequacy filing, and relatively little time understanding what CMS does with it. This breakdown walks through what CMS has published about the review, from the automated check to the deficiency notice.
CMS reviews Medicare Advantage networks through HSD tables uploaded to the Network Management Module in the Health Plan Management System (HPMS). Under its December 2024 guidance, contract networks are reviewed on a triennial basis, and contracts due for review are prompted to upload full tables in mid-June. Applicants upload as part of the application. An application, a termination CMS considers significant, a network access complaint, or a gap the plan discloses itself can pull a review forward.
Plans that treat an upload as the finish line can be caught flat-footed by a deficiency notice. Plans that understand the review can anticipate where it will fail and fix that first. CMS doesn't publish everything about how it works internally, so this article sticks to what the rules, guidance, and MedPAC have said.
CMS's Automated Criteria Check (ACC) scores the uploaded tables for every provider and facility type in every county. It runs two tests under 42 CFR 422.116, and a few details decide whether your internal numbers match its answer:
Any organization with a contract ID can upload HSD tables at any time to test compliance, and CMS offers an informal Consultation upload before the formal triennial review, so you don't have to wait for a review to see this result.
Read the "actual time" and "actual distance" fields as CMS's 2017 guidance defines them: the percentage of beneficiaries with access. The ZIP Code Report for Failed Counties shows where the misses cluster, which tells you where a new provider would actually help.
The two tests fail for different reasons. A network can pass the count and fail time and distance when its providers are clustered in one town. Sort your failures by which test failed before you decide what to do, since one calls for more providers and the other for providers in a different place.
CMS doesn't rely solely on what plans report. Its Provider Supply file matters most in exception requests, where a plan has to show that the providers it would need are not available. The guidance warns that the file "may not be a complete depiction" of supply and that plans "should not rely solely on the supply file," so build your own census as well. Two points deserve attention:
CMS doesn't publish how its reviewers divide up their work, so be wary of anyone describing exact internal queues or review tracks. For applicants, what is published is the sequence: three HSD upload rounds, made up of the initial submission with the application, the response to CMS's deficiency notice, and the response to the Notice of Intent to Deny (NOID). Each upload goes back through the ACC.
For operating contracts, CMS's guidance says networks that fail may face compliance or enforcement actions, and a triggered full review may reset the triennial clock. Applicants that used letters of intent go through the triennial review in their first operational year.
Compliance teams should look for these patterns in their own tables before CMS scores them:
CMS does not publish a guaranteed review timeline we can cite, so take the dates from the CMS notices and application materials for your cycle rather than from anyone's rule of thumb.
One response window is set in regulation: an applicant must respond to a NOID within 10 days under 42 CFR 422.502(c)(2)(ii). That is enough time to fix a mistyped address or add a provider whose contract was already signed, not enough to recruit a specialist. So don't wait for a notice to begin remediation. Keep providers in your pipeline for the counties most likely to fail.
Compliance teams need to interpret a deficiency notice carefully to respond effectively. For each failure, pin down the county, the provider or facility type, and which test failed. For the time and distance test, the required share under 42 CFR 422.116 is 90% of beneficiaries in Large Metro and Metro counties and 85% in Micro, Rural, and CEAC counties, before any credit.
Plans should also classify each gap by severity themselves. A county a point or two below the required share is a different problem from a county far below it. CMS does not publish fixed severity bands, so read the notice itself for what CMS is asking for.
A well-structured response addresses three things: the immediate fix (providers contracted to fill the gap, or a corrected table), the root cause (why the gap existed in the first place), and the process change (what the plan is doing to prevent recurrence). Check first whether the failure is a data problem, because a corrected address costs far less than a recruiting campaign.
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.