Free Network Build Assessment
Score your buildBefore you submit to HPMS, your adequacy calculations need to survive CMS scrutiny. Here's how experienced network teams validate their adequacy scores before the filing window closes.
Network adequacy submissions to HPMS are not drafts. For an applicant, CMS "may deny an application" based on its network evaluation under 42 CFR 422.116(a)(2)(ii), and errors discovered late have to be fixed in a short response window.
So treat pre-submission validation as a structured discipline, not a last-minute sanity check. Run several validation passes at set milestones, give each pass a clear owner, and keep the results. If anyone asks how you verified your work, you want a paper trail, not a verbal explanation.
This guide walks through a pre-submission validation workflow, from the first internal QA pass through the final spot-checks on filing day.
CMS's Automated Criteria Check (ACC) in the Network Management Module scores your HSD tables for every provider and facility type in every county. Any organization with a contract ID can upload tables and run it at any time. Understanding what it does, and what it can't tell you, shows you where to focus internally.
The ACC places members using CMS's MA Medicare Sample Census, reads your provider addresses as typed on the HSD tables, and applies counting rules many internal tools skip, such as specialty limits and telehealth exclusions. The Address Information Report shows how your addresses were processed, so read it each cycle.
What it can't tell you is equally important. A passing score does not prove that a provider is really at that address, seeing patients, or accepting new ones. Those checks are yours.
The practical implication: passing the automated check is necessary but not sufficient.
A reliable validation cadence uses three passes before your filing date, spaced to leave time to act on what you find. Each pass has a defined scope and escalation path.
The first pass focuses on roster completeness. At this stage, the goal is to confirm that your provider roster extract contains all your contracted providers and that the data fields required for the HSD tables are populated. Pull your full roster from the provider data system, match it against your executed contract records, and flag any providers who lack an active contract or a mutually signed LOI. This pass often reveals "ghost providers," carried in the system from prior contract terms and no longer active, who need to be removed before the adequacy calculation runs.
The second pass focuses on adequacy accuracy. Run your adequacy model using the cleaned roster and compare the output against CMS's standards for each county-specialty combination in your service area, then test the tables in the Network Management Module. Document every combination below the standard and classify each gap as: closeable through recruitment in progress, a possible exception request, or needing escalation because recruitment has stalled. This pass should produce a gap action plan with assigned owners and deadlines.
The third pass focuses on final reconciliation and exception requests. Confirm that every provider added since the last pass has a fully executed contract or mutually signed LOI. Review all exception requests: each needs a complete provider census, a checkable reason for each provider not in network, and pattern-of-care evidence. Run the adequacy calculation one final time using the final roster and confirm that all closeable gaps are closed. Document the final adequacy percentages for every county-specialty combination and compare them to the prior benefit year's submission to identify any regression.
Roster reconciliation is the single most error-prone step in the pre-submission process, and it is the step where most adequacy calculation failures originate. The reconciliation process has three components: contract reconciliation, credentialing reconciliation, and NPPES reconciliation.
Contract reconciliation means verifying that every provider in your adequacy model has an executed participating provider agreement that is currently active. Pull your contract management records, whether in a dedicated contracting system or in a spreadsheet, and match them against your roster. Providers whose contracts have expired, been terminated, or are awaiting counter-signature should be flagged and excluded from the adequacy model until their contract status is resolved. Pay particular attention to providers whose contract term end dates fall within the benefit year you are submitting for; a provider contracted through June of the benefit year cannot be counted for the full year.
Credentialing reconciliation means verifying that every provider in your adequacy model has a current, complete credentialing file. Coordinate with your credentialing team to obtain a file-status extract that shows credentialing expiration dates and file-completeness status for every provider in the roster. Exclude any provider whose credentialing is in expired, suspended, or pending status. This is a more dynamic process than contract reconciliation because credentialing files come due on rolling dates, and a provider who was current at your last pass may not be by submission day.
NPPES reconciliation means comparing the NPIs in your roster against the National Plan and Provider Enumeration System to verify that each NPI is active, that the specialty you are using fits the provider's NPPES record, and that the practice location addresses you have on file match it. If your model starts from a stale address, the output is wrong even if the arithmetic is correct.
Certain data errors appear repeatedly across network adequacy submissions and are predictable enough that your validation workflow should check for them explicitly.
Wrong provider addresses are a common error. Provider groups relocate, multi-site practices open and close satellite offices, and hospital systems reorganize. CMS's December 2024 guidance says providers should be listed at the addresses where they see patients in an office-based setting, not where they solely perform procedures, and billing addresses cause trouble too. A specialist who isn't where your model thinks can flip a marginal county from passing to failing.
Incorrect specialty codes cause providers to count toward the wrong type or not count at all. For 2026, CMS scores 29 provider types and 14 facility types, and the notes in the HSD Reference File add limits. Primary care, for example, is scored as a group of codes under S03, with PAs and NPs limited to a narrow case. Review those notes each year and reconcile them against your provider data.
Duplicate entries, where the same provider appears more than once, can inflate your counts if your model treats each entry as a separate provider. CMS's 2017 criteria guidance described a "Duplicate Record" as the same county code, specialty code and NPI: a second address still helps time and distance, but the provider counts once toward the minimum. Check the current Network Management Module user guide for today's wording.
Accepting-new-patients errors leave you relying on providers who are effectively unavailable. Exception requests in particular have to show contracted providers are currently available and accessible, and a contract with a closed panel gives members little. Refresh this field close enough to submission that it still means something.
Time-distance calculations are the mechanical core of adequacy determinations, and they are worth spot-checking manually on a sample basis even if you are running them through a validated calculation tool. The goal of spot-checking is not to recalculate every county-specialty combination, that would defeat the purpose of using a calculation tool, but to verify that the tool's outputs are reasonable for a representative sample of counties.
Select a sample of counties for spot-checking, weighted toward marginal counties where your adequacy percentage is close to the threshold. For each selected county, pick several populated locations, including some at the edges of the county, identify the nearest contracted provider in each specialty, and use a mapping tool to check travel time and distance. Compare your result against the calculation tool's output. A real discrepancy is worth investigating: is the tool using the correct provider location, the correct member locations, and travel measures rather than straight-line distance?
Pay particular attention to counties whose CMS designation changed from one HSD Reference File to the next. When a county moves from Micro to Metro, or Metro to Large Metro, the applicable time-distance threshold tightens, and if your calculation tool's county designation table hasn't been updated, it may be applying the wrong standard. Designation changes can flip counties from passing to failing without any change in your actual network.
Document your adequacy validation process. It shows that the plan exercised reasonable diligence in verifying its submission, and it gives you a record to produce if anyone asks.
At minimum, your validation documentation should include: a description of each validation pass (date, scope, responsible staff, tools used), the roster reconciliation outputs (number of providers reviewed, number flagged, number removed and rationale), the adequacy calculation output at each validation milestone, the gap remediation log showing gaps identified and how each was resolved, and the final pre-submission sign-off with signature from the network operations leader responsible for the filing.
Store this documentation where your team can reach it, not in a personal drive or email thread.
The hardest situation in pre-submission validation is discovering a material adequacy gap right before the deadline. By then, the options for closing the gap through contracting are limited. But late-breaking gaps are manageable if you have a defined protocol.
First, classify the gap by severity. A county just short of the required share is a different problem from a county far below it. The severity determines how quickly to escalate to plan leadership and whether to raise it with your CMS Account Manager.
Second, exhaust your contracting options. Hospital-employed specialists sometimes can be added under an existing facility contract, and applicants may use letters of intent signed by both parties. Check whether a telehealth credit applies in that specialty. Document every option pursued and every response received.
Third, file an exception request only where the rule fits: the needed providers are not available, and your contracted providers are available and accessible to most enrollees, consistent with the local pattern of care. CMS's guidance says inability to contract is not a valid reason, so a gap you simply ran out of time to close won't qualify.
Finally, notify your compliance officer. Any gap that requires an exception filing in a material specialty category should be disclosed to your compliance function before submission. The compliance officer may need to assess whether the gap creates regulatory exposure beyond the standard exception-filing process and whether any additional stakeholder communications are warranted.
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.