Free Network Build Assessment
Score your buildThe MA application asks a plan to attest that its network meets 42 CFR 422.116 in every county. Here's what stands behind that statement, what to settle about who signs, which data errors to check first, and how to test your tables before you attest.
A network adequacy attestation is not an administrative checkbox. The MA application's attestation 3.6.8 asks for a network meeting 42 CFR 422.116 "for each county in the requested service area during the entire contract year," ready for operations on January 1, and the HSD tables you upload in HPMS are the proof. Application language can move, so reread the network sections of the current application every cycle.
The stakes depend on where you stand. MedPAC's June 2024 report says CMS has never imposed intermediate sanctions or civil money penalties for network adequacy noncompliance, and adds that new applications have been denied on this basis. So an applicant with a gap can lose the county, and an operating contract with a gap faces possible compliance or enforcement action. An attestation is also a statement to a federal regulator. Ask your counsel what exposure an inaccurate one creates.
The practical implication is that whoever signs needs genuine confidence in the data underneath, based on a documented review by qualified network operations staff and checked against contract and credentialing records rather than taken from a status report.
In practice, the attestation rests on three things. First, the provider data on the HSD tables: that the providers listed are contracted, that their specialties and locations are correct, and that names and addresses are typed the same way each time, since CMS guidance warns that differences can cause processing problems and network deficiencies. Second, the result: that the network meets the minimum count and the time and distance standards in each county, or has an approved exception. Third, contract status: applicants attest to letter of intent use in the application and mark "Y" in the LOI column of the HSD table, removing it once the contract is fully executed.
The provider data is the most operationally demanding part, because errors change the calculation itself. CMS's Automated Criteria Check (ACC) reads provider addresses exactly as typed and applies specialty limits, telehealth exclusions, and credit conditions. A wrong address can put a provider on the wrong side of a time and distance line. Reconcile the tables against your own contract records before every upload.
Keep this attestation separate in your mind from the directory attestation. Under 42 CFR 422.111(m), for plan years beginning on or after January 1, 2026, MA organizations must attest at least annually that the directory data they submit is accurate. CMS proposed making plans attest that directory data matches what they submit for network adequacy, then declined to finalize it. We'd still keep one roster, because anyone comparing the two lists will see the differences.
We can't point to a public CMS list of which job titles may sign. Read the current application and HPMS instructions, and settle the question with your compliance lead and counsel at the start of the cycle rather than at the deadline.
Plans should keep a clear delegation of authority that says who signs CMS attestations, how that authority is documented, and who steps in if that person is unavailable near a deadline. The signer should be accountable for accuracy, not simply the person who processed the upload.
Several gaps between internal reports and CMS's check are worth looking at before anyone signs. Addresses first, since the ACC reads them as typed. Specialty next: a provider listed under a specialty that doesn't match how they practice can overstate a county. Then the census itself. MedPAC reports that the most common reason CMS denied exception requests was that it found providers within the criteria that the plan "failed to include" on the request or HSD tables.
Contract status is the second category. CMS expects fully executed contracts on the HSD tables. A mutually signed letter of intent can stand in during an initial or service area expansion application, but once the plan is operational, LOIs are no longer permitted. A tracker that shows "LOI signed" as in network is overstating the network.
County coverage is a third category. Reconcile the counties on your HSD upload against your approved or requested service area before loading provider data, so no county is missing and none is included by mistake.
You don't have to find out what CMS's check says at the last moment. Any organization with a contract ID can upload HSD tables to the Network Management Module in HPMS at any time to test compliance, and the ACC then scores every provider and facility type in every county. CMS also offers an informal Consultation upload with technical assistance before the formal triennial review.
Plan for at least two rounds. The first loads the complete provider dataset and generates the ACC output. The team reviews the output and the ZIP Code Report for Failed Counties, corrects what it finds, and loads a revised dataset. Only after that, with a documented response to each remaining failure, should anyone sign.
For applicants, the network review runs in three HSD upload rounds: the initial submission with the application, the response to CMS's deficiency notice, and the response to the Notice of Intent to Deny, which must come within 10 days under 42 CFR 422.502(c)(2)(ii). Each upload goes back through the ACC. Ten days is enough to fix a mistyped address. It is not enough to recruit a specialist.
For operating contracts, a gap the plan discloses itself must be reported to its CMS Account Manager, and that disclosure can pull a network review forward. For terminations a plan considers significant, Chapter 4 of the Medicare Managed Care Manual asks for notice to the Account Manager at least 90 days before the effective date. Plans that find a material error in what they gave CMS should bring in compliance and counsel right away rather than hoping the next upload fixes it quietly.
Blueprint keeps a history of work on each provider, showing who did what and when, and produces HSD-format provider tables for your team to review and file. It doesn't attest, sign, or submit anything to CMS.
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.