Free Network Build Assessment
Score your buildCMS HPMS · Network Adequacy Submission
What CMS has published about getting a Medicare Advantage network through HPMS: access, HSD tables, the Automated Criteria Check, exceptions and the review rounds, with common data problems and the CY2027 dates. CMS's current templates and NMM Plan User Guide in HPMS control.
Seven Steps
The steps are our way of organizing what CMS has published, not CMS's own list. The sooner a problem surfaces, the more options you have.
HSD tables go in through the Network Management Module (NMM) in HPMS, so whoever uploads them needs CMS access. For the CY2027 cycle, CMS's Part C application recommended submitting the Notice of Intent to Apply by November 18, 2025 to ensure HPMS access, and the CMS User ID form was due December 1, 2025.
Key Points
CMS publishes an HSD Reference File for each contract year, on cms.gov. It carries each county's designation, the time and distance maximums, the minimum counts and the specialty codes. The 2026 file carries an update date of December 17, 2025.
Key Points
There are two tables, one for providers and one for facilities. A provider is listed against every county it serves, not only the county its office is in. Counties are keyed by the five-digit SSA state and county code, not FIPS. Primary care goes in under its individual codes (001 to 006), and CMS sums them into S03.
Key Points
Before you upload, compare your tables against each county's minimum count and time and distance standard. CMS places members using its MA Medicare Sample Census, which only CMS can see, so your own result is an estimate. A county that passes internally is a hypothesis until CMS's check agrees.
Key Points
The Automated Criteria Check (ACC) scores every provider and facility type in every county against 42 CFR 422.116: the minimum count, and the share of beneficiaries within both the maximum time and the maximum distance. Each new upload goes back through it.
Key Points
An exception goes in on CMS's current template in HPMS, for one county and one specialty, under 42 CFR 422.116(f). It has to show that the providers you would need aren't available and that the providers you did contract with fit the local pattern of care. Inability to contract is not a valid reason.
Key Points
The CY2027 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. Applicants then work through three HSD upload rounds: the initial submission, the response to CMS's deficiency notice, and the response to the Notice of Intent to Deny (NOID).
Key Points
HSD Table Reference
The columns in the Provider and Facility HSD tables, following CMS's published layouts. Check the current template in HPMS before you upload.
| Column | Table | Notes |
|---|---|---|
| SSA State/County Code | Both | Five-digit SSA code, not FIPS. Arizona is state 03 in SSA codes and 04 in FIPS |
| Name of Physician or Mid-Level Practitioner | Provider | Spelled the same way each time |
| Facility or Service Type, Facility Name | Facility | Type from the HSD Reference File |
| National Provider Identifier (NPI) Number | Both | Check it against the NPI Registry |
| Specialty, Specialty Code | Both | From the HSD Reference File. Primary care uses the individual codes 001 to 006 |
| Contract Type (DC or DS) | Provider | Direct or downstream contract |
| Street Address, City, State, Zip Code | Both | The office where the provider sees patients, not a PO box or billing address |
| If PCP, Accepts New Patients (Y/N) | Provider | Primary care rows only |
| Medical Group Affiliation | Provider | DC for a direct contract, otherwise the group or IPA name |
| Number of Staffed, Medicare-Certified Beds | Facility | Acute inpatient minimums are counted in beds |
| Uses CMS MA Contract Amendment (Y/N) | Both | From the contract |
| Letter of Intent (Y/N) | Both | Applicants only. Remove the Y once the contract is fully executed |
Data Problems
Small differences between your data and what CMS's check reads can turn a green internal map into a deficiency notice. Fix these before you upload.
Problem
FIPS codes where SSA codes belong
Why It Happens
Census files, GIS layers and most vendor data use FIPS. HSD tables use SSA codes, a different numbering
Fix
Carry both codes on every county record, and never join on county name
Problem
The wrong address
Why It Happens
Rosters pulled from credentialing or claims systems often carry a billing address, a corporate address or a hospital
Fix
List the office where the provider sees patients for consultations
Problem
Names and addresses that change
Why It Happens
"Ste 200" one cycle and "Suite 200" the next. CMS says differences can cause processing problems and network deficiencies
Fix
Submit each name and address exactly the same way every time
Problem
Addresses the software can't place
Why It Happens
CMS's 2017 guidance said an unlocated address with a valid ZIP gets a generated point inside the ZIP, and an invalid address and ZIP is left out of automated processing
Fix
Read the Address Information Report every cycle, and correct what it flags
Problem
Providers who don't count, counted
Why It Happens
Telehealth-only providers filling a minimum, or PAs and NPs under 005 and 006 who don't meet the Reference File's conditions
Fix
Flag telehealth-only providers, and check 005 and 006 against the Notes tab
Problem
One behavioral health provider, two codes
Why It Happens
A provider submitted as Psychiatry, Clinical Social Work or Clinical Psychology can't also be submitted under Outpatient Behavioral Health (068)
Fix
Give each behavioral health clinician one assignment, made on purpose
Problem
A roster that has gone stale
Why It Happens
Terminated providers left on, contracted providers left off, or an LOI flag still set on an operating contract
Fix
Before each upload, take off terminations since the last one, add new contracts, and clear LOI flags
Published Dates
From CMS's CY2027 Part C application, which says all its dates are subject to change. The 10-day NOID response is in 42 CFR 422.502(c)(2)(ii), and mid-June is from CMS's December 2024 guidance. When we last checked, on September 30, 2026, CMS had not posted CY2028 dates. The Integrated Care Resource Center lists November 11, 2026 as the CY2028 Notice of Intent date to ensure HPMS access, so confirm it with CMS.
Recommended Notice of Intent to Apply date, to ensure HPMS access
CMS User ID form due
Final applications posted
Notice of Intent to Apply deadline
Completed applications due, with HSD tables for the service area
Deficiency response, then Notice of Intent to Deny response
Bids due (the first Monday in June)
CMS executes contracts
Operating contracts due for triennial review are prompted to upload
Blueprint Platform
Blueprint builds HSD-format provider tables from your network, listing each provider in every county it serves, under SSA codes. Fields it can't know are left blank and listed. Your team reviews and files them: Blueprint doesn't connect to HPMS or file anything.
FAQ