Free Network Build Assessment
Score your buildMany network teams still wait for an annual Call Letter to learn this year's adequacy standards. CMS doesn't publish them that way. Here's where the standards actually live, how they change, and what network ops teams should do before the filing window opens.
A common assumption in network operations is that CMS updates Medicare Advantage network adequacy standards each spring in an annual Call Letter, and that teams should wait for it before planning their builds. That is not how the standards work. There is no annual Call Letter that sets time-and-distance standards. The standards live in regulation at 42 CFR 422.116, and the county-level numbers live in CMS's HSD Reference File.
Teams that wait for a document that isn't coming lose planning time they can't get back. The numbers they need are already published, and they can start modeling as soon as the current HSD Reference File is available.
42 CFR 422.116 sets the framework: the five county designations (Large Metro, Metro, Micro, Rural, and CEAC, for counties with extreme access considerations), the 29 provider types and 14 facility types, the base time-and-distance maximums, the required share of beneficiaries within both the time and the distance limit (90% in Large Metro and Metro counties, 85% in Micro, Rural, and CEAC counties), and the credits that can reduce that share by 10 percentage points each.
The HSD Reference File applies that framework county by county. It lists each county's designation, the maximum time and distance for every provider and facility type in that county, including any customized standards CMS has set for that county, and the minimum provider counts, which CMS sets county by county from the number of beneficiaries.
Because the framework is in regulation, changes to it come through CMS rulemaking: proposed and final rules for the MA program, with a comment period in between. Changes at the county level come through the HSD Reference File, which CMS publishes for each contract year. Between files, counties can change designation, customized standards can be added or changed, and minimum provider counts can move as beneficiary counts change.
That gives network ops teams two things to watch: MA proposed and final rules, for any change to the framework itself, and each new HSD Reference File, for the county-level numbers.
A useful practice is to create a side-by-side comparison: take the prior year's HSD Reference File and the current one, and diff them county by county. Any row where the minimum provider count, the time or distance maximum, or the county designation has changed represents a direct operational action item.
The critical changes to track are: counties that change designation (every standard for the county changes with it); customized standards (which can only be higher than the base, never lower); and changes in minimum provider counts (which can turn a compliant county deficient without any provider attrition). Teams that maintain a county-level adequacy model in a structured platform can re-run gap analysis as soon as the new file is loaded. Teams that track adequacy in spreadsheets face a more manual process, and are more likely to miss a subtle change.
The operational response follows a predictable sequence. First, update the adequacy model with the new file. Second, re-run gap analysis across all operating counties. Third, produce a gap report that identifies counties newly deficient under the updated numbers and counties where an exception request is likely to be needed. Fourth, prioritize recruitment resources against the gap report, with urgency assigned based on time to filing deadline and geography of the gap.
Network development leads should also brief plan leadership on any material changes. A designation change that tightens standards across a large county, or a new minimum count in a shortage specialty, has direct budget implications: new recruitment, contracting, and potentially credentialing resources may be required. Leadership should understand the scope of the change before the filing window opens, not after.
CMS sets network adequacy review dates in its application materials and HPMS memos, and those dates can change from year to year, so confirm them each cycle. The MA bid deadline is the first Monday in June. CMS can deny an application for failure to demonstrate an adequate network, and it has done so for new applications.
The runway between the current HSD Reference File and your filing date is the time you have to close gaps. For straightforward contracting gaps in counties with available providers, it may be enough. For specialty gaps in Rural and CEAC counties, it is very tight. Plans that start modeling against the published file early are in a fundamentally better position than plans waiting for a Call Letter that will not arrive.
Plans that have historically treated hard specialties as a secondary concern, filing exceptions and moving on, should recalibrate. In 2021, CMS denied 259 of 448 exception requests, about 58%, according to MedPAC's June 2024 report. CMS also has authority to sanction plans for network adequacy failures. The safest plan is a network that meets the published standard, built early against the current HSD Reference File.
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.