Free Network Build Assessment
Score your buildMedicaid managed care network adequacy is governed at the state level within a federal floor set by 42 CFR 438.68. What that means in practice: every state has different standards, different filing processes, and different audit triggers. Here's how to navigate state variation.
Medicaid managed care network adequacy requirements exist within a layered regulatory structure. The federal floor is established by 42 CFR 438.68, which was substantially updated by the Medicaid managed care final rule in 2016 and has been modified through subsequent rulemaking. The federal regulation sets minimum requirements that every state Medicaid managed care program must meet, but it explicitly preserves state authority to impose requirements that go further than the federal floor.
The core federal requirements under 42 CFR 438.68 mandate that states establish network adequacy standards for their managed care programs that ensure enrollees have access to covered services with reasonable promptness. The regulation lists the provider types that need quantitative standards, so check the current text. It gives states significant discretion in how to define and measure adequacy. The 2024 Access Rule added federal wait-time standards at 42 CFR 438.68(e), applying to rating periods beginning on or after July 9, 2027, and secret shopper surveys at 438.68(f), applying from rating periods beginning on or after July 9, 2028 (a CMS chart lists July 10).
The federal floor also requires states to ensure that their managed care contracts address network adequacy, that MCOs demonstrate compliance with state standards, and that states conduct ongoing monitoring and enforcement. The mechanism through which states exercise all of these responsibilities, the managed care contract, is the primary compliance document for MCOs operating in Medicaid managed care, and understanding its contents is essential for any plan operating in or entering a Medicaid managed care market.
The variation in state Medicaid network adequacy standards is extensive. States differ in which specialty categories they require, what limits they apply, whether they use provider-to-enrollee ratios as an alternative or supplement to time and distance, how they treat sparsely populated areas, what exception processes they allow, and how they audit and enforce compliance. A plan operating in five states operates under five different sets of rules.
Some states use time and distance standards built differently from CMS's Medicare Advantage designations, so a plan coming from an MA background can't simply reuse its MA adequacy framework. Take each state's numbers from the state's own contract and published standards, never from memory or from another state.
Other states rely mainly on provider-to-enrollee ratios. There, the compliance question becomes a capacity analysis rather than a geographic coverage analysis, and the team's model needs to handle that.
States also vary in how they handle behavioral health adequacy, with some states carving behavioral health out of managed care contracts entirely and managing it through separate behavioral health organizations. Plans entering a state with a behavioral health carve-out do not need to demonstrate behavioral health network adequacy, but they need to know the carve-out structure before they begin building, since building a behavioral health network in a carve-out state wastes contracting resources and may not count toward compliance regardless.
For MCOs operating in Medicaid managed care, the state managed care contract is more operationally important than the state's Medicaid managed care regulations. State regulations establish the general framework; the contract specifies the exact standards the plan is required to meet, the filing timelines for network adequacy demonstrations, the audit methodologies the state will use, and the consequences of non-compliance. Two MCOs operating in the same state under the same regulatory framework but with different contract vintages may be subject to materially different requirements.
States update their managed care contracts through an amendment process that typically operates on an annual or biennial cycle. Plans should review their managed care contract amendments carefully each cycle: network adequacy standard updates are frequently embedded in technical amendment packages that cover dozens of contract sections simultaneously, and a network adequacy standard change can be easy to miss if the team's contract review process focuses on reimbursement rate amendments.
Procurement and re-procurement processes, when states competitively bid their Medicaid managed care contracts, typically result in new contracts with updated adequacy standards that reflect the state's current policy priorities. Plans that win competitive procurements in new states should treat the new contract as a fresh adequacy requirement document and build their network from scratch against contract requirements rather than assuming prior state practices continue unchanged.
State MCO certification and network adequacy filing timelines vary widely and are frequently not publicly obvious. States have different processes for initial MCO certification, different timelines for initial network adequacy demonstrations, and different annual or periodic reporting requirements for ongoing compliance. A plan entering a new Medicaid managed care market must map the full certification and filing calendar before beginning network build activities to ensure that contracting timelines align with filing deadlines.
Initial MCO certification in most states requires submission of a complete network adequacy demonstration: a roster of contracted providers organized by county and specialty, with calculations supporting compliance. Review times vary with the state's capacity and the completeness of the submission, so ask the state early.
Periodic network adequacy filings follow the schedule in the managed care contract, and the calendar differs from state to state. Missing a filing deadline is a contract compliance problem even if the plan's network is actually adequate.
Mid-year network change notifications are required in many states when a plan's contracted network falls below adequacy standards: for example, when a key provider terminates a contract and the affected county falls out of compliance. The notification requirement typically includes both a disclosure of the deficiency and a corrective action plan with a timeline for returning to compliance. Plans need a way to catch adequacy deficiencies as they happen, not at annual filing time.
Plans operating in multiple Medicaid managed care states need a state-specific adequacy tracking framework that captures the full requirements matrix for each state, applicable standards, required specialty categories, filing deadlines, exception processes, and audit methodologies, rather than attempting to apply a single cross-state model. A single-state Medicaid managed care build can get away with a contract-focused tracking approach; a multi-state build without a formal state variation tracker is a compliance risk.
The core elements of a state-specific adequacy tracker include the applicable standard type (time-distance, ratio, or hybrid), the threshold values for each required specialty category in each geographic tier, the managed care contract citation for each standard (including amendment history), the annual filing deadline, the deficiency notification timeline, and the contact information for the state's MCO oversight unit. This information should be maintained as a living document that is updated with each contract amendment cycle.
Beyond the structural variation in adequacy standards, several categories of state-specific requirements recur frequently enough to warrant explicit attention in multi-state Medicaid adequacy planning.
Long-term services and supports (LTSS), home and community-based services, nursing facility care, and related services, are increasingly included in Medicaid managed care contracts, and LTSS network adequacy requirements can be substantially different from traditional medical service requirements. LTSS providers are not licensed in the same credentialing framework as physicians and hospitals, and LTSS adequacy standards often focus on service capacity (hours of home care available, number of waiver slots) rather than geographic proximity. Plans that expand into LTSS-inclusive managed care contracts need adequacy modeling tools that can handle LTSS service categories.
Behavioral health carve-outs, as noted earlier, remove behavioral health adequacy from the MCO's responsibility in some states, but partial carve-outs are also common, where the MCO is responsible for some behavioral health services (outpatient counseling, for example) but not others (inpatient psychiatric, substance use disorder residential treatment). Plans must carefully map the carve-out boundary in each state to know exactly which behavioral health services are in-scope for their adequacy demonstration.
Blueprint comes with CMS's Medicare Advantage HSD standards, not state Medicaid rules. A customer can load another standards file, such as a state's Medicaid standards, and the engine scores against that file and cites it, on straight-line distance.
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.