Free Network Build Assessment
Take it freeStep-by-step walkthrough of the CMS HPMS network adequacy filing process — from obtaining system access to the final attestation. Includes HSD table field requirements, common upload errors, and submission calendar.
7-Step Process
The HPMS network adequacy filing process has seven distinct stages. Each must be completed correctly before moving to the next — errors discovered late compress your timeline significantly.
HPMS access requires a CMS-issued user account. Designated staff must complete the CMS security training modules and submit a User ID request through the HPMS Help Desk. Each user has role-based permissions — not all staff need write access to the network adequacy module.
Key Points
CMS updates the HSD (Health Service Delivery) reference file annually. The reference file defines the exact specialty codes, county FIPS codes, and county type classifications that must be used in your submission. Using an outdated reference file will cause validation errors.
Key Points
The network submission consists of the HSD table — a structured data file listing your contracted providers by NPI, specialty code, county FIPS code, and service location. Each row represents one provider-county-specialty combination. The file must be formatted to CMS specifications with exact column headers and data types.
Key Points
Before uploading to HPMS, run your own adequacy calculation against the HSD table. Identify county-specialty combinations that are below threshold. Resolve what you can; prepare exception documentation for what you cannot. Discovering gaps after upload forces a corrective resubmission under deadline pressure.
Key Points
In HPMS, navigate to the Network Adequacy module for your contract. Upload the HSD table as a CSV or Excel file per CMS format requirements. HPMS runs automated validation on upload — you will receive an immediate error report if column headers, FIPS codes, or NPI formats are incorrect.
Key Points
For counties that remain deficient after uploading your HSD table, file exception requests in HPMS before finalizing the submission. Exception requests require a written narrative and supporting documentation (outreach logs for Access Exceptions; HRSA shortage data for Geographic Exceptions).
Key Points
The final step is the network adequacy attestation — a legally binding certification by an authorized plan officer that the submitted network data is accurate and the plan will maintain adequate networks throughout the contract year. The attestation must be completed before the submission deadline.
Key Points
HSD Table Reference
The HSD table is the core data file for the HPMS network adequacy submission. Every field must be populated correctly for each provider row.
| Field | Format | Required | Notes |
|---|---|---|---|
| NPI | Numeric (10-digit) | Required | Type 1 (individual) NPIs only |
| Provider Last Name | Text | Required | Must match NPI registry |
| Provider First Name | Text | Required | Must match NPI registry |
| Specialty Code | CMS Code | Required | From current HSD reference file |
| Practice Location Address | Text | Required | Physical location; no PO boxes |
| Practice Location Zip | 5-digit | Required | Must match NPI registry location |
| County FIPS Code | 5-digit | Required | From current HSD reference file |
| Accepting New Patients | Y / N | Required | Y = open panel; N = closed panel |
| Hospital Affiliation | Text | Conditional | Required for hospital-based specialists |
| Telehealth Indicator | Y / N | Conditional | Required if counting as telehealth provider |
Error Prevention
HPMS validation catches many errors automatically — but others slip through to CMS review and trigger deficiency notices weeks later. Fix these before you submit.
Error
Invalid NPI format
Common Cause
Using a 9-digit NPI, an organizational (Type 2) NPI, or a deactivated NPI
Fix
Verify all NPIs in NPPES before upload; filter out Type 2 NPIs; check for deactivated status
Error
FIPS code mismatch
Common Cause
Using an outdated FIPS code list or manually entered FIPS codes that don't match the current HSD reference file
Fix
Always derive county FIPS codes from the current contract-year HSD reference file downloaded from HPMS
Error
Specialty code not recognized
Common Cause
Using a specialty code from a prior year's reference file, or mapping a specialty incorrectly
Fix
Use only specialty codes from the current year's HSD reference file; confirm mappings against the CMS specialty taxonomy
Error
Practice location zip doesn't match NPI registry
Common Cause
Provider changed office location but NPI registry wasn't updated, or the zip in your system differs from NPPES
Fix
Cross-reference practice location zip with NPPES before building the HSD table; request providers update their NPPES records
Error
Duplicate rows
Common Cause
Same NPI listed twice for the same county-specialty combination
Fix
Deduplicate your HSD table before upload; each NPI-county-specialty combination should appear exactly once
Error
Missing panel status
Common Cause
Accepting New Patients field left blank or filled with values other than Y or N
Fix
All rows must have Y or N in the panel status field — blank values are treated as errors, not as Y
Error
File format error
Common Cause
Uploading an Excel file with formulas, merged cells, or non-standard character encoding
Fix
Save as plain CSV (UTF-8) before upload; no formulas, no merged cells, standard ASCII characters only
Key Deadlines
CMS releases HSD reference file
HPMS network adequacy module opens
Initial HSD table upload deadline
MA bid submission deadline
CMS initial adequacy review period
Deficiency notices issued
30-day deficiency response window
Final adequacy approval
Blueprint Platform
Blueprint maintains your provider roster in HPMS-ready format year-round. When the submission window opens, export a validated HSD table with every required field pre-populated — no manual formatting, no column header errors, no NPI lookups.
FAQ