Why Myths Persist in a Regulatory Environment
Network adequacy compliance is dense enough that misconceptions take root easily. A plan's compliance team learns a rule in year one, codifies it into internal policy, and repeats it for five years without revisiting whether CMS guidance has shifted. A consultant passes along an interpretation that was accurate in 2019 but is no longer operative. A network VP remembers how the standards worked at their prior employer and applies the same assumptions to a different market, a different product type, and a different regulatory year.
The result is a set of persistent myths that cost plans real money: failed filings, deficiency remediation, delayed market entry. Below are the five most consequential ones, with the accurate picture for each.
Myth 1: Telehealth Always Counts Toward Adequacy
This myth is dangerous because it contains a grain of truth that makes it sound authoritative. Telehealth can help with network adequacy determinations: CMS gives a telehealth credit in listed specialties, including behavioral health. But "can count" is doing a lot of work in that sentence, and many plans have treated it as "always counts."
The accurate picture: under 42 CFR 422.116(d)(5), contracted telehealth providers in 15 listed specialties earn a 10 percentage point credit toward the share of beneficiaries who must be within the time-distance standard in a county. That is all. Telehealth-only providers do not count toward the minimum provider count, and they are not physical locations. In a Metro county, the credit means 80% of beneficiaries within the cardiology standard is enough to reach the 90% requirement, but it does not satisfy the standard for a county where few beneficiaries are near a contracted cardiologist. CMS's recognition of telehealth is not a blanket offset for physical access gaps.
The credit has conditions. It applies where the network includes providers furnishing additional telehealth benefits under 42 CFR 422.135 in that specialty, and it does nothing for the minimum count. Plans that add a telehealth vendor and assume it resolves specialty shortages across the board are going to learn the limits of that assumption from a deficiency notice.
Myth 2: HSD Categories Are Fixed
Health Service Delivery (HSD) table categories, the provider and facility types CMS requires plans to demonstrate access to, are not immovable. Clinical Psychology and Clinical Social Work became provider types for coverage beginning in 2024, and Outpatient Behavioral Health was added as a facility type for 2025. The regulation now lists 29 provider types and 14 facility types.
Plans that build their network strategy around a static category list from a prior year are building toward the wrong target. A plan that has not reviewed current requirements against its prior-year strategy may discover gaps in types it didn't know it needed to cover.
Treat HSD categories as annually verified, not assumed. Pull the current HSD Reference File, including its Notes tab, at the start of each build cycle and compare it against last year.
Myth 3: A Single Provider Satisfies Any County
Many network build leaders operate under the impression that if they have one in-network provider for a required specialty within a county's time-distance threshold, that county is covered. This is incorrect in two distinct ways.
First, CMS sets a minimum provider count for every provider and facility type in every county, based on the number of beneficiaries. Larger counties often require more than one in-network provider for primary care and several key specialties. A single provider in a populous county will not satisfy adequacy requirements regardless of geographic proximity.
Second, and more practically: a single provider in any county is an adequacy risk even when CMS does not require multiples. If that provider retires, terminates their contract, stops accepting new patients, or changes their practice scope between submission and the CMS review period, the county falls out of compliance. Plans that have single-provider coverage in any specialty-county combination are sitting on contingent deficiencies that one practice-level event can activate.
The operational standard should be redundancy, not minimalism. A county covered by two providers in a required specialty is not gold-plating: it is the minimum defensible position.
Myth 4: Deficiency Notices Are Negotiable
There is a persistent belief in plan operations circles that a deficiency notice is the beginning of a conversation, not a finding, that a well-written response can negotiate the underlying adequacy standard down to a level the plan can meet, rather than simply demonstrating compliance with the standard that exists.
This is wrong, and acting on it is expensive. A response is a chance to upload corrected tables and to file exceptions where they apply. What the process does not provide is flexibility on the standard itself. A county that fails the time-distance test requires either a contracted provider in range or an approved exception under 42 CFR 422.116(f), which needs proof that the providers aren't available and that your contracted network fits the local pattern of care. CMS's guidance says inability to contract is not valid, because of the non-interference clause. A well-written letter explaining why the standard is unreasonable for that county is not a path to approval.
Deficiency notices are correctable, not negotiable. The correction is provider access, a valid exception, or both, not persuasive writing about market conditions.
Approach a deficiency response as a negotiation and you spend your response window drafting arguments instead of building the provider access or evidence you actually need. For an applicant, the final response window is 10 days.
Myth 5: Passing Once Means Passing Again
A plan that filed a compliant network in the prior cycle has no guarantee of compliance in the current cycle. Provider rosters are not static. Providers retire, relocate, and terminate contracts. Specialties shift between scarcity and availability. County designations can change from one HSD Reference File to the next, which changes the applicable time-distance standards for individual counties. The 2026 file lists 6,862 county and specialty criteria changes from 2025, including 807 county designation changes. A county that was a comfortable pass last year may be a borderline failure this year.
Treat a prior approval as a baseline you can coast from, and you may discover mid-build that a "stable" network has drifted out of compliance. The prior year's submission is a starting point for the current year's analysis, not a proxy for it. Every build cycle requires a full county-by-specialty assessment against current standards and current provider status, not a diff of what changed since last year. The diff approach misses the cumulative drift that occurs when multiple small changes compound.
Persistent compliance is an active posture, not a status that persists once achieved.
The Blueprint team
Provider network build practice
Written by the people behind Blueprint, who between them have spent 30 years building provider networks for health plans: recruiting and contracting providers, chasing credentialing, and filing adequacy. Blueprint is new. The experience behind it isn't.