The Minnesota Department of Human Services webinar in August 2025 walked navigators and community partners through the Medicaid provisions in H.R. 1. At least 320,000 Minnesotans would likely be subject to work reporting requirement rules, approximately 23 percent of the state’s Medicaid population. The federal government must issue interim final rules by June 1, 2026. States must implement work requirements by December 31, 2026, though the HHS Secretary can exempt a state from compliance if the state demonstrates good faith effort. This exemption cannot be extended beyond December 31, 2028.
The careful presentation reflected Minnesota’s position. The state has never implemented Medicaid work requirements and has consistently rejected work requirement approaches, viewing them as inconsistent with Minnesota’s tradition of generous public assistance and philosophical commitment to healthcare as a fundamental need rather than an earned benefit. Now federal law compels compliance, forcing the Walz administration to reconcile DFL values with federal mandates.
Governor Tim Walz marked the 60th anniversary of Medicaid and Medicare in July 2025 by highlighting the impacts of federal cuts on health care for Minnesotans. State officials projected that federal Medicaid changes would cost Minnesota $1.4 billion in federal funding over four years, with losses deepening over time to potentially $2.5 billion per biennium when fully implemented. Work requirement implementation costs would compound these fiscal pressures.
H.R. 1, signed July 4, 2025, transformed Medicaid work requirements from a state-option policy experiment into a federal mandate affecting approximately 18.5 million expansion adults nationwide. The law requires 80 hours monthly of work, education, training, or qualifying community engagement activities, with semi-annual redetermination cycles replacing annual reviews. States face a January 1, 2027 implementation deadline, though good-faith extensions are available through December 31, 2028 for states demonstrating genuine progress toward compliance infrastructure.
CMS issued its first substantive implementation guidance on December 8, 2025, establishing several parameters that shape state planning. States must use reliable data sources to verify compliance before requesting documentation from enrollees, a data-first approach that privileges automated verification over member-initiated reporting. A 30-day cure period is required between initial non-compliance determination and coverage termination, during which members can demonstrate they were meeting requirements or qualify for exemptions. Congress allocated $200 million in implementation funding, half distributed equally across states and half proportional to affected population.
Two provisions create particular downstream pressure. Individuals who lose Medicaid coverage for work requirement non-compliance are barred from receiving premium tax credits on the ACA marketplace, meaning non-compliance creates a coverage void rather than a coverage transition. And the Trump administration rescinded Biden-era guidance on health-related social needs services in March 2025, while CMS has signaled it will not approve new or extend existing continuous eligibility waivers, narrowing the flexibility states had been using to stabilize enrollment.
Minnesota’s 320,000 affected expansion adults face implementation across the state’s county-administered eligibility system. Whether the state achieves low coverage losses through coverage-protective design or experiences significant enrollment declines depends on implementation execution, county capacity, technology functionality, and member navigation support in a compressed timeline.
The County Administration Challenge#
Minnesota operates a county-administered eligibility system across 87 counties ranging from Hennepin County’s sophisticated human services infrastructure to rural northern counties with minimal administrative resources. Implementation quality will vary geographically, potentially creating coverage disparities based on county of residence.
County workers process Medicaid applications, conduct redeterminations, and verify eligibility through state systems. This front-line role means counties will bear substantial implementation burden for work requirements. County staff will need training on new requirements, exemption criteria, verification processes, and system updates. The state’s fiscal impact analysis projects additional annual costs to Minnesota taxpayers of $4.9 million through increased administrative costs to complete data verifications against the federal hub. Costs to counties are still being determined.
The state must decide whether to provide additional county funding specifically for work requirement implementation or expect counties to absorb costs within existing allocations. This decision will significantly affect implementation quality across counties. Well-resourced counties may invest in navigation support while under-resourced counties may implement minimalist compliance monitoring.
Linnea Mirsch, director of community and human services in St. Louis County, manages dozens of civil servants who parse through applications for Medical Assistance. She told MinnPost in July 2025 that her job just got more difficult under work requirement rules. The administrative burden falls disproportionately on county systems not designed for monthly work verification.
The Diverse Population Challenge#
Minnesota’s diverse immigrant and refugee populations present unique outreach challenges. Somali, Hmong, Latino, Karen, and other communities require culturally competent, multilingual communications and trusted community intermediaries. The state’s robust community-based organization infrastructure provides potential capacity, but mobilizing these networks for work requirement compliance represents new territory.
Somali communities in Minneapolis and St. Paul have substantial Medical Assistance enrollment. Many work in service sector jobs that may not generate consistent wage records or in culturally specific employment arrangements not captured by state wage reporting systems. Hmong communities, particularly in the Twin Cities and Rochester, include substantial populations working in agriculture, food processing, and small business ownership that may face verification challenges.
Refugee populations arriving through federal resettlement programs face particular challenges. Many are learning English, navigating unfamiliar systems, and seeking employment in tight labor markets. Work requirements add another layer of complexity to already difficult transitions. Whether the state will build specialized navigation for refugee populations or expect mainstream systems to accommodate diverse needs remains unclear.
The state’s rural populations present different challenges. Northern Minnesota’s remote communities have limited formal employment opportunities outside healthcare, education, government, and tourism. Iron Range communities transitioning from mining economies face structural employment barriers. Whether federal exemptions for areas lacking sufficient employment will apply to these regions depends on qualification criteria that remain undefined.
Cross-Program Coordination Potential#
Minnesota maintains SNAP and TANF programs with existing work requirements. H.R. 1 allows states to deem Medicaid requirements satisfied if individuals meet SNAP or TANF work requirements. This cross-program coordination could reduce verification burden for the subset of expansion adults active in both programs.
Minnesota’s TANF program, called Minnesota Family Investment Program, includes work requirements for cash assistance recipients. TANF work requirement participants are explicitly exempt from Medicaid work requirements under federal law, eliminating duplication for families receiving both benefits. However, TANF serves primarily parents with dependent children, while Medicaid expansion includes many childless adults not eligible for TANF.
The extent of overlap between Medicaid expansion and SNAP varies by economic conditions and region. Minnesota’s integrated eligibility systems handle both programs, providing technical foundation for data sharing. However, SNAP work requirements differ from Medicaid requirements in hours, qualifying activities, and exemption criteria. Perfect alignment is impossible without federal regulatory changes.
Employment wage records provide another verification data source. Minnesota’s unemployment insurance system captures most formal employment. Automated wage record verification will identify members working sufficient hours without requiring individual documentation. This data-first approach aligns with federal guidance but misses gig economy workers, cash earners, informal caregivers, and culturally specific employment arrangements.
Tribal Coordination Requirements#
Minnesota’s relationships with eleven sovereign nations create specific coordination requirements. Federal law exempts tribal members from Medicaid work requirements. Implementing these exemptions requires careful coordination to respect tribal sovereignty while ensuring proper verification.
The state has worked to improve Medicaid coverage for Native American populations through partnerships with tribal health systems. Red Lake Reservation operates as the only closed reservation in Minnesota, with land held in common. White Earth and Leech Lake have substantial enrolled populations. Urban Indian populations in Minneapolis and St. Paul may not be enrolled in federally recognized tribes but still identify as Native American.
Tribal enrollment verification through federal databases should allow automated exemption determination for most tribal members. However, urban Indians not enrolled in federally recognized tribes may face documentation requirements. The state’s approach to these edge cases will test Minnesota’s commitment to tribal sovereignty principles.
MinnesotaCare Coverage Bridge#
Uniquely among states, Minnesota operates MinnesotaCare, a state-subsidized health coverage program for individuals earning between 138 percent and 200 percent of the federal poverty level who do not have access to employer-sponsored insurance. This Basic Health Program under the ACA creates a coverage bridge that other states lack. As of August 2025, approximately 101,000 Minnesotans were enrolled in MinnesotaCare.
Expansion adults losing Medicaid coverage may qualify for MinnesotaCare if their income remains below 200 percent FPL. This transition provides alternative coverage unavailable in most states. However, MinnesotaCare requires premiums up to $80 monthly in 2026 and may not qualify for federal Basic Health Program funding depending on other legislative changes. The program demonstrates Minnesota’s commitment to comprehensive coverage infrastructure beyond federal minimums, but it doesn’t eliminate coverage gaps from work requirement non-compliance.
Expected Implementation Approach#
Minnesota will implement federal work requirements reluctantly, viewing them as an unwanted federal mandate rather than sound policy. The Walz administration will maximize exemptions, pursue cross-program deemed compliance, and invest in navigation support to minimize coverage losses.
Verification systems will emphasize automated data sources. Wage record matching through the Department of Employment and Economic Development will capture most full-time workers. Cross-program coordination with SNAP and TANF will provide deemed compliance for overlapping populations. Educational enrollment verification will accommodate students. These automated processes will reduce individual documentation requirements.
Exemption determination processes will balance accessibility with verification requirements. Tribal exemptions will be automated through enrollment verification. Disability exemptions may initially accept self-attestation followed by medical documentation for ongoing compliance. Hardship exemptions for individual circumstances or geographic areas lacking employment will be broadly available, though qualification criteria await federal guidance.
County implementation quality will vary based on capacity and resources. Hennepin and Ramsey counties will likely invest in navigation support. Smaller rural counties may implement minimalist compliance monitoring. This variation creates potential coverage disparities based on residence, though state oversight may mitigate the most extreme differences.
Managed care organizations serving Medical Assistance enrollees will receive implementation guidance from DHS and will be expected to support member navigation through care coordination infrastructure. Minnesota’s strong MCO infrastructure provides foundation for member outreach, though whether MCOs receive additional payment for work requirement navigation or absorb costs within existing rates remains undetermined.
Member communications will emphasize that most Medical Assistance members already meet requirements through existing work, education, or qualifying activities. DHS will frame work requirements as documentation challenges rather than behavior change initiatives. This messaging aligns with research showing coverage losses in Arkansas 2018 occurred primarily among people who were working or qualified for exemptions but couldn’t navigate verification systems.
The state’s timeline depends on federal guidance arriving by June 1, 2026. System development, county training, navigator partnerships, and member communications must occur in the compressed June 2026 to December 2026 period. Whether Minnesota will request an extension to December 2028 depends on implementation progress and political calculations. An extension delays coverage losses but also delays federal compliance, potentially creating political vulnerability.
Minnesota’s fiscal constraints limit investment in navigation infrastructure that might reduce coverage losses. DHS projects that federal Medicaid changes will cost Minnesota $1.4 billion in federal funding over four years. Governor Walz has proposed budget measures to address structural deficits, including slowing growth in disability services spending. Work requirement implementation costs compound existing fiscal pressures while TABOR-like constraints limit revenue options.
Minnesota’s implementation will test whether a state with strong infrastructure, diverse populations, and political resistance to work requirements can minimize coverage losses through coverage-protective system design. The state has county capacity, community organization networks, and MCO infrastructure that many states lack. Whether these advantages translate to substantially different outcomes than compliance-focused states remains an empirical question Minnesota’s implementation will help answer.
The healthcare systems serving Minnesota’s diverse communities watch implementation with uncertainty. Coverage losses will affect provider revenue and patient care regardless of system design quality. Rural northern communities already struggling with provider shortages may see further healthcare infrastructure erosion as work requirements compound existing pressures. Immigrant and refugee populations may face particular vulnerability if verification systems cannot accommodate culturally specific employment patterns and language barriers.