Free Network Build Assessment
Score your buildThe most common errors network teams make in their annual adequacy filings, and exactly how to avoid each one.
Most adequacy filing failures aren't caused by genuine network gaps: they're caused by process errors that produce inaccurate submissions. A plan can have a contractually complete network that fails adequacy review because of how the data was prepared, classified, or submitted. These are fixable problems, but only if you know to look for them before submission, not after a deficiency notice arrives.
The following seven mistakes are common and correctable. Each one is preventable with the right process checkpoints.
For 2026, CMS evaluates adequacy across 29 provider types and 14 facility types, and each code carries its own rules. The mistake is mapping providers to the wrong code. For example, primary care is scored as a group: CMS sums codes 001 through 006 under S03, and the 2026 HSD Reference File notes limit PAs and NPs to a narrow case in designated physician shortage areas.
Why it gets caught: CMS's Automated Criteria Check applies counting rules that many internal tools skip, so a roster that looks fine internally can come up short.
How to prevent it: Read the notes in the current HSD Reference File, check each provider's specialty and credential against the code you assign, and apply the mapping consistently.
Provider records change: providers move, change practice affiliations, retire, or opt out of Medicare. An adequacy model built on old data will count providers who have since left the county or stopped seeing patients.
Why it gets caught: CMS reads the addresses you type on the HSD tables, and CMS's guidance warns that names and addresses must be submitted exactly the same way each time. A provider who has really moved no longer gives members access, whatever the file says.
How to prevent it: Refresh provider data from NPPES and your own contract records shortly before each adequacy check. Do it more often in any county where you are close to the threshold, so a departure doesn't create a surprise gap.
Adequacy is measured at the county level. Some teams submit provider rosters without clearly mapping each provider to the specific counties toward which they count for adequacy purposes. A provider whose office sits near a county line may be within reach of beneficiaries in two counties, or in only one, and if the submission doesn't make the mapping explicit, reviewers may misassign the provider.
Why it gets caught: HSD tables are keyed by five-digit SSA state and county codes, which are not FIPS codes. Join on the wrong code, or on county name, and providers land in the wrong county or in none.
How to prevent it: Carry both SSA and FIPS codes on every county record. For each county, list every provider counted toward adequacy for each specialty, with the provider's service address and NPI, and remember that CMS's criteria are not restricted by county or state boundaries.
CMS does not measure from a county centroid. Its standard is that a required share of beneficiaries, 90% in Large Metro and Metro counties and 85% in Micro, Rural, and CEAC counties, live within both the maximum travel time and the maximum travel distance of a contracted provider. Plans that measure from a centroid, or that treat time and distance as either-or, produce systematically incorrect adequacy assessments.
Why it gets caught: CMS's own adequacy calculation will produce different results than your model if you've used the wrong method, and the discrepancy can flip a passing county to a failing one.
How to prevent it: Model against where beneficiaries actually live, require both the time and the distance limit to be met, and use the limits for each county's designation from the current HSD Reference File. Treat any internal estimate that CMS did not produce as unconfirmed until it matches CMS's results.
A contracted provider who has closed their panel to new patients cannot fulfill their adequacy function for members who need to see them. Plans that count all contracted providers without verifying panel status are building an adequacy model that overstates actual member access.
Why it gets caught: A network access complaint is one of the triggers CMS's December 2024 guidance names for a full network review, and appointment wait standards under 42 CFR 422.112(a)(6)(i) now apply to primary care and behavioral health.
How to prevent it: Conduct a panel status audit: call the providers you depend on in critical specialties and confirm they are accepting new patients and accepting your plan. Do this early enough that there is time to replace providers with closed panels.
Plans operating in multiple lines of business, MA, Medicaid managed care, QHP, sometimes build a single provider roster and use it for all LOB adequacy filings without accounting for the fact that a provider may be contracted for MA but not for Medicaid, or vice versa. The same provider cannot count toward Medicaid adequacy if they don't have a Medicaid contract with the plan.
Why it gets caught: A provider who appears in a Medicaid adequacy filing without a Medicaid contract is a false entry, and state reviewers and secret shoppers can find it.
How to prevent it: Maintain separate provider rosters by line of business and validate that each provider's contract explicitly covers the LOB for which they are being counted. LOB crossover tables in your provider management system should be a standard data field, not an afterthought.
This sounds obvious, but the real problem is usually missed internal milestones that make an on-time submission impossible. The final submission takes sign-offs and system uploads, and people need HPMS access before they can do any of it. Teams that finish their adequacy analysis on the day of the deadline cannot complete the process in time.
Why it gets caught: CMS's dates are firm. For contract year 2027, its application said CMS "will not accept applications from organizations that fail to submit a timely NOIA." After filing, the last chance to fix the network is the response to the Notice of Intent to Deny, and the regulation allows 10 days.
How to prevent it: Set your internal deadline well ahead of CMS's. Use that time for quality review, legal sign-off, and system upload. If the buffer is consumed by fixes, you still meet the real deadline. If it isn't, you've built in a quality check.
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.