Free Network Build Assessment
Score your buildSection 1115 demonstrations create unique network obligations that differ substantially from standard Medicaid managed care requirements. Here's what network teams need to know when building or maintaining waiver program networks.
Section 1115 of the Social Security Act grants the Secretary of Health and Human Services broad authority to approve experimental, pilot, or demonstration projects that promote Medicaid's objectives. When a state receives an 1115 waiver approval, it can deviate from standard Medicaid requirements, including eligibility rules, benefit structures, cost-sharing provisions, and, critically, managed care contracting requirements, in ways that have direct consequences for the networks that managed care organizations must build to serve waiver populations.
For health plan network teams, an 1115 waiver is not simply an administrative background fact. It is a legally binding framework that modifies the network standards the plan must meet in order to maintain its contract to serve the waiver population. Waiver demonstrations frequently introduce population-specific provider requirements, access standards tailored to high-need beneficiaries, and monitoring obligations that exceed those applicable to the plan's standard Medicaid managed care lines of business. A plan that applies its standard network adequacy framework to a waiver population without reading the waiver Special Terms and Conditions (STCs) in detail can end up out of compliance with obligations it did not know it had accepted.
The starting point for any network team managing a plan participating in a Section 1115 demonstration is a thorough reading of the waiver's Special Terms and Conditions, which are the legally binding terms negotiated between the state and CMS. The STCs specify the populations covered under the demonstration, the benefits included, the managed care contracting requirements that apply, and any network-specific obligations the waiver imposes. STCs vary substantially across states and demonstrations, so generic knowledge of 1115 waivers is not a substitute for reading the specific STC package governing your plan's participation.
Section 1115 waivers are negotiated between the state Medicaid agency and CMS, and the terms of that negotiation establish the network standards that managed care plans participating in the demonstration must meet. CMS approval of a waiver does not mean CMS has pre-approved the specific network the plan will build: it means CMS has agreed to the general framework of standards within which the plan's network will be evaluated.
The practical implication is that plans participating in 1115 demonstrations face a two-layer regulatory oversight structure. At the federal level, CMS retains oversight authority over the demonstration and can impose conditions on the state's waiver renewal: conditions that may include enhanced network monitoring requirements or access standard modifications that flow down to managed care organizations through the state's contract amendment process. At the state level, the Medicaid agency serves as the plan's direct regulator and contract counterparty, and the state agency interprets and enforces the STC network requirements as part of its demonstration oversight responsibilities.
CMS conducts formal waiver evaluation activities, including independent evaluation requirements specified in the STCs, and those evaluations include assessments of beneficiary access to care. Network deficiencies identified in waiver evaluations are reported to CMS and can affect state waiver renewal prospects, which creates a state-level incentive to monitor plan network compliance more intensively than might occur in a standard managed care contracting relationship.
Plans should maintain regular communication with the state Medicaid agency's managed care contracting team throughout the demonstration period, not only during contract renewal cycles. Waiver STCs can be amended during the waiver term, so watch the federal-state correspondence rather than waiting to hear about changes through the contracting process.
One of the defining features of 1115 waivers is that they allow states to exercise flexibility that is not available under standard Medicaid managed care authorities. For network teams, this flexibility manifests in several ways that create plan-specific obligations not found in the standard regulatory framework.
States frequently use 1115 authority to extend Medicaid coverage to populations not otherwise eligible: expansion adults under the ACA, individuals in institutions for mental disease (IMDs) under waiver IMD exceptions, justice-involved individuals, or other populations with distinctive service profiles. Each newly eligible population group may have associated network requirements: substance use disorder treatment providers for justice-involved beneficiaries, IMD-based providers for seriously mentally ill individuals, or primary care providers with documented experience serving low-income uninsured populations for expansion adults. The plan's network cannot be a simple extension of its existing Medicaid network; it must be evaluated against the actual service needs of the waiver population.
States also use 1115 authority to implement managed long-term services and supports (MLTSS) programs, which bring LTSS benefits into managed care and impose network requirements for home- and community-based services (HCBS) providers, personal care agencies, adult day health programs, home health agencies, supported employment providers, and others, that standard managed care networks typically do not include. MLTSS network builds can be especially complex, because the provider universe is diffuse, often operates through individual provider arrangements, and may not appear in standard provider directories or enrollment databases.
Here are population-specific network requirements to look for when entering a waiver market. Check each one against the STCs of the demonstration you are in, because they differ.
Behavioral health. Demonstrations serving individuals with serious mental illness (SMI) or serious emotional disturbance (SED), or implementing behavioral health integration, may specify network requirements for psychiatrists, licensed clinical social workers, psychologists, community mental health centers (CMHCs), and certified community behavioral health clinics (CCBHCs). They may also set access standards that call for specific tracking and reporting by the plan.
Substance use disorder (SUD) treatment. SUD-focused demonstrations may require capacity across the ASAM Criteria continuum of care: outpatient, intensive outpatient, partial hospitalization, residential, and medically managed intensive inpatient treatment. Plans may need to contract across that continuum and verify that providers are licensed at the appropriate level and meet any state certification requirements.
Long-term services and supports (LTSS). These requirements apply under MLTSS demonstrations. LTSS provider types include personal care attendants, home health agencies, adult day health programs, assisted living facilities, skilled nursing facilities, and the full range of HCBS waiver service providers. Each provider type may have its own credentialing or enrollment requirements under the state's HCBS waiver program, and the plan must build contracting relationships that accommodate the state's existing HCBS program structures rather than importing standard managed care contracting models wholesale.
Section 1115 demonstrations come with monitoring and evaluation requirements on the state, and states may flow them down to managed care plans through the managed care contract.
Network-related reporting obligations can include: regular provider network reports to the state, including provider counts by type, geographic distribution, and panel availability; beneficiary access reports that track appointment availability and wait times for key provider types; member complaint and grievance data specifically related to access-to-care issues, reported with sufficient detail for the state to identify network adequacy correlates; and provider directory accuracy reports that confirm the currency of the plan's public provider directory against the active network.
Demonstrations may also include independent evaluation requirements that look at access. Plans may be required to provide data to independent evaluators on a separate timeline from their regular state reporting obligations. Understanding the full scope of monitoring and reporting obligations before the contract is executed allows network teams to build the data collection and reporting infrastructure they will need before they are in breach of a reporting deadline.
If CMS raises access concerns with the state, the state may pass new requirements on to its plans, possibly on a short timeline.
Documenting network compliance in an 1115 waiver program context requires a more structured and population-specific approach than standard managed care network documentation. The documentation framework must account for the population-specific provider requirements, the enhanced reporting obligations, and the dual federal-state oversight structure that characterizes 1115 demonstrations.
At the provider roster level, waiver program network documentation should maintain provider type classifications that map to the STC's network requirement categories, not just the plan's internal specialty taxonomy. If the STC specifies minimum network requirements for CCBHCs, the plan's roster must be able to identify CCBHC-certified providers specifically, not just behavioral health providers generally. If the STC specifies ASAM Criteria continuum levels for SUD treatment, the plan's provider database must maintain the ASAM credentialing level for each SUD treatment provider in the network.
At the access standard documentation level, plans should maintain appointment availability tracking that reflects the specific access standards in the STC rather than generic managed care access standards. If the STC sets a specific wait time for routine behavioral health appointments, track against that number, not a generic standard that may apply to other lines of business.
At the reporting documentation level, plans should maintain an indexed archive of all state-required network reports, including the methodology used to generate each report and the data sources used. When state or federal auditors review waiver program network compliance, the ability to trace each reported data point back to the underlying provider records and data systems is a critical element of a defensible compliance posture.
Blueprint doesn't include 1115 waiver rules or state Medicaid rules out of the box. A customer can load another standards file, for example a state's Medicaid standards, and the engine scores against that file and cites it.
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.