twimco.Let’s talk ↗︎
Menu
Field notes / Product & engineering

States can check Medicaid members' college enrollment by API. Design the screen for "no record" first

A student in her second semester renews her Medicaid in January. The state checks a national enrollment database, and the answer comes back empty because her college hasn't reported yet. What happens next is the part no API decides for you.

Editorial engraving of a bright county services office where a caseworker turns his screen toward a student holding out a letter, a folder open on the desk.

Under H.R. 1, some Medicaid members can meet the new community engagement requirement by enrolling at least half-time in an eligible program, and states face a January 1 implementation deadline. The National Student Clearinghouse can verify enrollment by API, directly or through aggregators. The data exists; what states still have to design is where the check sits in the eligibility workflow and what a caseworker does with "no record," a stale record or a part-time result.

One student, one renewal

Take a member we'll call Dana. She's 24, works a few hours a week and started at a community college in the fall. Her Medicaid renewal comes up in January, after the new rules take effect.

Under H.R. 1, the One Big Beautiful Bill Act, some adult Medicaid members have to meet new community engagement requirements, often called work requirements. One way to meet them is to be enrolled at least half-time in an eligible education program. Dana should qualify.

So the state's system checks. According to StateScoop's November 10 report, states can verify enrollment through the National Student Clearinghouse, a nonprofit that holds more than 130 million verified education records and receives data from nearly 3,700 colleges and universities. It offers access through an existing API, and most states plan to reach it through third-party aggregators that already provide Medicaid verification services.

The check comes back: no record for the current term.

Dana is enrolled. Her college just hasn't sent the new term's data yet. StateScoop reports that colleges typically submit enrollment to the Clearinghouse every 30 to 60 days. In January, a spring enrollment may not be there.

What happens next is a design decision, and in most states it hasn't been made yet.

Sequence of work

One renewal, five moments

  1. Renewal opens

    The member's record shows she may qualify through school enrollment.

  2. Automatic check

    The system asks the enrollment source, directly or through an aggregator.

  3. Result arrives

    Enrolled half-time, enrolled less than half-time, or no record.

  4. Caseworker sees it

    With the date of the record and what it can and can't prove.

  5. Member hears about it

    A notice that says what was found and what she can send instead.

Illustrative sequence for a single member; not a state's actual process or measured timings.

The data exists. The workflow doesn't

The Clearinghouse's chief strategy and operations officer told StateScoop that the obstacle isn't demand for the data. It's "friction around implementation": fitting education records into existing eligibility workflows, updating data-sharing agreements, and resolving who is allowed to see what. Enrollment, she said, has not traditionally been part of those workflows.

That's how integration projects usually go. Connecting to a data source is a few weeks of work. Deciding what each answer means, who sees it, and what happens when it's wrong is the project.

She also expects verification to happen about every six months, in line with academic calendars. That's a rhythm, not a real-time guarantee. Any system that treats one API response as the truth about a person's status on a given day will get some people wrong, mostly at term boundaries, which is exactly when renewals bunch up.

The state has a January 1 implementation deadline, per StateScoop. That's close enough that the temptation will be to wire the check in and sort out the edge cases later. The edge cases are where people lose coverage.

"No record found" is not the same answer as "not enrolled," and the screen has to say which one it is.

Three answers that need three screens

From the caseworker's side, an enrollment check can come back three ways, plus a fourth that's easy to miss.

Enrolled at least half-time. The easy case. The screen should still show which term the record covers and when it was reported, so the caseworker isn't relying on last spring's data for a January renewal.

Enrolled, but less than half-time. A real answer, and it means this route doesn't work for this member. The screen should say that plainly and show the other routes she might still use, like work hours, rather than reading as a denial.

No record. "No record found" is not the same answer as "not enrolled," and the screen has to say which one it is. A member can be missing because her college reports late, because her name or date of birth is recorded differently, because the school doesn't report to that source, or because she isn't enrolled. Only the last one should count against her, and the system can't tell which it is. The screen should say "unverified" and prompt for a document.

An old record. A match from a previous term. It proves she was enrolled, not that she is. Treat it as stale, with a re-check date.

None of this needs AI. It needs someone to write down what each answer means before the first renewal runs.

Decision guide

Three results, three different next steps

ConsiderationWhat came backWhat the caseworker should see
Enrolled at least half-timeA current record that meets the thresholdVerified, with the record's date and the term it covers
Enrolled, less than half-timeA current record below the thresholdDoesn't qualify on this route; other routes listed
No recordNothing matchedUnverified, not denied; ask for proof and say why it might be missing
Old recordA match from before the current termStale; re-check later or accept a document
Decision framework for eligibility teams; illustrative, not policy guidance.

Where the check goes

StateScoop's source advised agencies to map their existing workflows first, find where education verification fits, and coordinate with others already working on it. She also pointed to county agencies, which in many states do the actual eligibility work. That matters: if the check runs at the state level but the caseworker is in a county office using a different screen, the result has to arrive there with its meaning attached.

Questions we'd answer before building anything:

  • At which step does the check run: at application, at renewal, or both? And does it run before or after the member is asked to report?
  • Who sees the raw result, and who sees only the conclusion? Data-sharing agreements may limit this.
  • What does the notice to the member say when the result is "no record"? Does it explain the likely reason and what document would settle it?
  • When a member sends a document, does that close the question, or does the system keep re-checking and overrule it?
  • How often is the check repeated, and does that schedule line up with when colleges actually report?

StateScoop also cites Code for America's work on renewals, including Minnesota cutting the average time caseworkers spent on a renewal from 70 to 11 minutes after workflow improvements. The lesson there wasn't a new data source. It was the work around it.

Our notes on a screener that tells people they don't qualify and on Michigan's SNAP work rules reaching a county front desk come at the same problem from the member's and the counter's side.

Before January

If you run or supply an eligibility system, take one illustrative member like Dana and walk her through every step, from renewal notice to decision, with each of the four results. Write down what the caseworker sees, what the member is told, and who can fix a wrong answer. Do it with a county caseworker in the room, not just the integration team.

That walkthrough will show you whether the work is a connection, a screen, a notice, or all three. It's the kind of work our government and public sector team does: intake, case handling and the systems behind them, designed so that a person waiting for an answer gets the right one. Talk to us.

Related work: Sutton|Place

FAQ

How can states verify Medicaid members' college enrollment under H.R. 1?

Under H.R. 1, some adult Medicaid members can meet the new community engagement requirement by enrolling at least half-time in an eligible education program. According to StateScoop's November 10 report, states can verify enrollment through the National Student Clearinghouse, which holds more than 130 million records from nearly 3,700 colleges, via an existing API, often through third-party aggregators.

When do states have to implement this?

StateScoop reports a January 1 implementation deadline. That's close enough that the temptation will be to wire the check in and sort out the edge cases later, but the edge cases are where people lose coverage.

Why might a student who's enrolled come back as "no record"?

Colleges typically submit enrollment to the Clearinghouse every 30 to 60 days, so in January a spring enrollment may not be there yet. A member can also be missing because her name or date of birth is recorded differently, or because the school doesn't report to that source. "No record found" is not the same as "not enrolled," and only an actual non-enrollment should count against the member.

What should a caseworker screen do with each result?

An enrolled-at-least-half-time result should show which term the record covers and when it was reported. Less-than-half-time should say so plainly and show other routes, such as work hours. No record should be labeled unverified and prompt for a document. An old match from a previous term should be treated as stale, with a re-check date.

twimco.

We build alongside the people doing the work.
Bring us the problem you’re thinking about.

Related work

Sutton Place ↗︎