The Care Stack

Medicaid work requirements: what your data team should build now

Victor Wilson · · 3 min read

On June 1, CMS issued the interim final rule for Medicaid work requirements. Starting January 1, 2027, adults 19 to 64 in the expansion group will have to show 80 hours a month of work or other qualifying activity.

Some states aren’t waiting. Nebraska began enforcing its requirements in May.

The details may still shift. On June 29, 25 states and DC sued CMS, mainly over the rule’s narrower medical-frailty exemption. The suit is about how CMS wrote the rule, not about the law that requires work requirements. I’d plan for a January start.

There’s a second change on almost the same timeline. Expansion adults will have their eligibility rechecked every six months, starting with renewals on or after December 31, 2026.

For a health system, both changes point the same way. Some patients who have Medicaid today will lose it. Some will get it back a few months later. Others won’t.

Why this is a data problem

This comes on top of a hard year for coverage. The enhanced ACA premium tax credits expired at the end of 2025. KFF found that paid Marketplace enrollment fell to 19.2 million in February, after enrollees faced an average 114% increase in what they paid to keep the same plan.

Hospitals were already feeling it. Kaufman Hall reported that bad debt, uninsured patients and charity care all rose in 2025.

The trouble is that coverage loss is hard to see when it happens. A patient who had Medicaid in March may be uninsured by September. Your systems may still show the old coverage until a claim comes back denied. By then the visit is over, and the bill may turn into bad debt.

You can’t stop the policy. You can see its effect early, and give your financial counseling and revenue cycle teams time to act.

What to build

Start with a coverage history for each patient. Most systems store the payer on file today. You want what it was over time, month by month. That’s how you see who moved from Medicaid to self-pay, and when.

Next, build a watch list. Which of your Medicaid patients are adults in the expansion group? When is each one due for renewal? You won’t know everything, because the state holds much of this data. Age, coverage type and visit history are a reasonable start. Refine it as your state shares more.

Then build a self-pay shift report. Track self-pay and charity care volume by service line, site and month. Set the baseline now, before January, so you can show the change when your CFO asks. They will ask.

Last, move eligibility checks earlier. Check coverage before scheduled visits, not after the claim comes back. When coverage has lapsed, you want to know while the patient is still reachable.

None of this needs new technology. It needs a few months of steady work, and the sooner it starts, the longer your baseline will be.

Where agents help, and where people decide

This work suits AI agents well, as long as a person stays in charge of the calls that matter.

An agent can run eligibility checks every night and flag patients whose coverage changed. It can sort the watch list by upcoming visits and renewal dates. It can draft reminder messages about renewals and the documents a patient may need. And it can pre-fill a charity care application from data you already have.

People decide the rest. A financial counselor decides who qualifies for charity care. A person talks with the patient who just lost coverage and is worried about a bill. Your team decides who gets a phone call instead of a letter. And the state, not your agent, decides who is eligible for Medicaid.

Be careful with outreach, too. Messages about coverage and work status touch sensitive ground. Have your compliance and patient experience teams review any template before an agent sends it.

This month, ask your data team one question: how many of our patients had Medicaid at some point in the last year, and how many have it today? If that takes more than a day to answer, start with the coverage history.

Discussion

    Join the discussion