D.C. delays Medicaid work requirements, but thousands may still lose their health insurance next year

Trump’s One Big Beautiful Bill has left the District scrambling to protect D.C. residents' federal food aid and medical coverage.

A photo collage of a hospital waiting room, Medicaid insurance paperwork, and a bottle of medication.
(Maddie Poore)

As of a week ago, it looked like the District was hurtling towards a perfect-storm scenario for some of the city’s most vulnerable.

The city was staring down a January deadline to enforce federal work requirements for some Medicaid beneficiaries without children, likely impacting over 74,000 people in the District. The new rules are expected to disenroll a large number of D.C. residents, causing potentially thousands of low-income people to lose their health insurance. 

The city was already struggling with another impact of President Trump’s One Big Beautiful Bill Act — the requirement that some SNAP recipients without children prove they’re working 80 hours a month, or that they’re participating in an approved training or volunteer program. According to data from the Department of Human Services, roughly 1,000 D.C. residents lost their food assistance between September and October as a result. Another 1,000 are at risk of losing their benefits this month. 

So when the Center for Medicare and Medicaid Services announced an optional six-month enforcement delay last week, city leaders, healthcare advocates, and providers shared a collective sigh of relief. They hope this period, meant for states to “modernize systems, improve processes, and streamline the applicant and beneficiary experience,” will give the District more time to prepare. 

While DHCF will still have to monitor Medicaid recipients’ work activity, the agency confirmed to The 51st that it won’t disenroll noncompliant residents until after June 30, 2027. (Some states, like Kentucky and Iowa, have chosen not to opt into the grace period and plan to move ahead with enforcement.) But the very recent SNAP experience means city agencies are already overburdened, and even a delay may not be enough to stave off the worst potential outcomes.

The rollout of the SNAP requirements this past summer was not exactly smooth. Caflora Lunakuntz, a Southwest D.C. resident and SNAP recipient, has a disability that should’ve exempted them from the work requirements. But even after submitting the necessary documentation, Lunakuntz lost their benefits in September. 

“The very thing that I feared was the very thing that was manifested,” they told The 51st. After working with an attorney at Bread for the City, they were able to get their SNAP benefits back, but only after 20 days of going without them, a period they called “very traumatizing.” 

“It put me back into a space of just surviving in the gutter,” they said.

Advocates are raising the alarm that this type of error could be replicated when it comes to the Medicaid work requirements rollout. Experts have reported numerous examples of glitches and other errors in the D.C. Access System, the eligibility and enrollment platform for public benefits like SNAP and Medicaid. 

“Sometimes [it] works exactly as it's supposed to, and DCAS will automatically exempt someone based on information that it has,” said Jessica Berger, a supervising attorney with Legal Aid DC. “But yet, for some of our clients, it didn't work the way that it was supposed to, and folks received information from DHS saying that, ‘We don't think you're exempt from SNAP work requirements, and you need to provide this additional information.’”

“It raises serious concerns about how many people might fall through the cracks with Medicaid work requirements,” she added. With this extra time before enforcement, Berger wants to see the city improve DCAS so that automatic exemptions work as they should.

When asked about errors with DCAS, DHCF spokesperson Dorinda White said last week that the agency was developing and testing “additional functionality to support Medicaid work requirements” for the system. Following the extension, she said DHCF is still moving forward “with planned eligibility system updates, caseworker training, and resident outreach campaigns.” 

Another concern relates to information sharing about the new requirements. Prior to the delay announcement, At-Large Councilmember Christina Henderson told The 51st that the District wasn’t ready to implement Medicaid work requirements. Part of the issue, she said, was communicating the changes to residents. The new rollout schedule provides the District some additional space for outreach, she said on Monday, but there’s still no time to lose.

“It still means that we have to be very clear in terms of our communication with residents,” said Henderson. That need for clarity is particularly true for the 21,000 Medicaid recipients in D.C. who are also on SNAP and are still subject to those work requirements — which are similar to, but not exactly the same as, the Medicaid requirements, only adding to the confusion. 

Councilmember-elect Oye Owolewa, a pharmacist, felt that the city government was “missing a huge opportunity" when it came to effectively reaching out to healthcare facilities and workers about the requirements.

“As a pharmacist, I'm gonna let you know, I'm not being let up to date,” said Owolewa, who represents Ward 8, where residents have worse health outcomes than the residents west of the Anacostia River. “If I wasn't the incoming councilmember, I wouldn't know about any of these things.”

According to DHCF testimony for an Oct. 29 D.C. council roundtable about the SNAP and Medicaid work requirements, DHCF sent out a notice to the over 70,000 households who may be subject to the new policy on Sept. 4. It has not sent out additional outreach to them since.

“Residents impacted by [Medicaid work requirements] will receive more targeted notices from DHCF, their managed care organizations, and potentially providers they receive services from as their renewal dates approach in 2027,” said White in an email to The 51st. They've launched a website with information about work requirements for both SNAP and Medicaid, and DHCF will also be launching an ad campaign on public transit, newspapers, and on local TV in the coming weeks, she added.

The hope is that the six-month delay will help the District and local healthcare organizations get everyone prepared in time for the change. “It's fair for our participants, and also it's fair for healthcare centers,” said Veronica Hernandez, an entitlement manager at Mary’s Center, a community health center that serves primarily uninsured and underinsured patients. “We can prepare better and ensure that the participants that come to us are being assisted and guided in this process.” 

The delay also gives D.C.’s next mayor, Janeese Lewis George, more time to address this issue as she enters office, Hernandez said. 

“This should be a priority for this new administration,” she added. “I would hope that they work together with DHCF and DHS … to align goals.”

The work requirements come at a time when the D.C. government is already under financial pressure, and the local job market still hasn’t recovered from the federal slashing of the government workforce. One group of local nonprofits established an initiative called the Workforce & Wellness Collaborative to help residents meet the work requirements. Recognizing the state of D.C.’s labor market, the group is focusing on getting residents connected to high-demand jobs that won’t be made obsolete by AI.

“Those are jobs in construction. Those are jobs in healthcare. Those are jobs in automotive repair,” said Scott Kratz, CEO and president of Building Bridges Across The River, one of the nonprofits leading the initiative. “There are a lot of jobs that are out there. It’s not all doom and gloom, we just need to make sure that they have the skills to apply for those jobs.”

At the October council roundtable, city agency leaders were aware of the challenges ahead. Wayne Turnage, director of DHCF, called the Medicaid change “a day of reckoning” and said that even if agencies did all they could to prepare, there could still be “a critical mass of people in the city who either won’t respond to what we’re doing, or who are not attached to the labor force in any meaningful way that would allow them to meet … the new, and very punitive in my judgment, Medicaid work requirements.”

For those who wind up in that critical mass, the loss of benefits could be devastating, regardless of when it happens.

Joseph Pearson, a 31-year-old D.C. resident on Medicaid, didn’t know about the new work requirements until last week, when The 51st spoke with him. He relies heavily on a range of medications, including ones for mental health disorders, and was disturbed to hear about the work requirements. While his conditions should allow him to keep his Medicaid coverage without working, even a brief break in care — as Lunakuntz experienced with their SNAP benefits —  could be very dangerous. In the past, Pearson has lost his healthcare services, causing him to go around three months without medication, and he was scared over the thought of entering that space again.

“I couldn't get up out of bed. I couldn't breathe. My mental health was horrible,” said Pearson. “I had gotten so bad to a point where I just basically said, ‘Well, I guess this is where I die, because I'm not going to be able to get any help.’”

Great! You’ve successfully signed up.

Welcome back! You've successfully signed in.

You've successfully subscribed to The 51st.

Success! Check your email for magic link to sign-in.

Success! Your billing info has been updated.

Your billing was not updated.

Join