Public Law 119-21 verification — FAQ

Public Law 119-21 (P.L. 119-21) — originally introduced as H.R. 1, the Working Families Tax Cut Act — is the 2026 federal law that expands Medicaid, CHIP, and SNAP verification obligations on state agencies. Title XI specifically strengthens requirements for lawful enrollment verification, community-engagement / work-requirement compliance, Death Master File cross-checks, and National Change of Address reconciliation.

Every state Medicaid agency, every state CHIP administrator, and every state SNAP agency. Compliance also flows down to county human-services departments processing eligibility on behalf of the state, Tribal Nation processing organizations, and the system integrators / prime contractors holding state IT contracts.

A new federal requirement under P.L. 119-21 §3201 that state Medicaid agencies verify enrollees are either participating in qualifying community-engagement activities (paid work, training, volunteer service, caregiving, etc.) at minimum-hours thresholds, or eligible for documented exemptions (medical frailty, pregnancy/postpartum, caregiving for a young or disabled household member, certain disability categories).

The redetermination cadence varies by program and category. The federal floor under §3204 establishes minimum recurring verification frequencies for Medicaid and CHIP that are higher than historical cadences. States may exceed the federal floor but cannot fall below it. Operational implication: most states need significantly more verification capacity than they had in 2024.

Federal guidance is still being clarified, but the operational consensus emerging from CMS guidance is: a verification attempt requires a documented contact-attempt across at least the channel of record (typically mail), with the option to disenroll only after a documented good-faith multi-channel attempt. Veridian Public uses a five-channel default (mail, SMS, voice, portal, in-person community partner) before treating a case as non-responsive.

National Change of Address (NCOA) reconciliation under §3204 requires states to periodically match enrollee addresses against USPS NCOA records. When a match indicates an enrollee moved out of state, the state must initiate a verification workflow rather than immediately disenrolling. False-positive review (the same person at a different address) is a documented prerequisite for any disenrollment action.

Recurring matching against the Social Security Administration's Death Master File (DMF). When a DMF match is flagged, the state cannot simply disenroll — it must document a human-in-the-loop review of the match (since DMF false-positives exist), then take action. Veridian operates this end-to-end.

AI assists with three specific operational tasks: (1) classifying inbound documents at scale (OCR + classifier so a 30-document case can be triaged in seconds); (2) generating multichannel outreach in the beneficiary's language of record; (3) flagging cases where an automated determination is unsafe and a human reviewer is needed. AI does NOT make the eligibility determination itself — that remains a human decision, documented for audit.

No. Veridian Public is explicitly designed to operate alongside state-designated systems of record. The state's eligibility system makes determinations; Veridian operates the verification workflow that feeds evidence into those determinations. We integrate via standard APIs or batch file exchange — whichever the state prefers.

Yes. Three engagement models: (1) direct managed service where Veridian operates verification; (2) software-only platform access where state staff operate the workflow but get the audit trail and outreach engine; (3) subcontract under an existing prime contractor's state IT contract. Most states choose option 1 for community-engagement verification specifically because the volume is new and they don't have the staffing.

We deliver outreach in the beneficiary's language of record. Standard coverage includes English, Spanish, Mandarin, Vietnamese, Tagalog, Korean, Russian, Arabic, Haitian Creole, and French. State-specific language coverage (e.g. Hmong in Minnesota, Somali in Ohio, Navajo across the Four Corners states) is added per-engagement.

All beneficiary data is handled under the state's existing data-use agreement; Veridian acts as the state's business associate / subcontractor under HIPAA. We do not retain data beyond the engagement; we do not sell or share data; we do not train AI models on beneficiary information. Audit logs are produced for the state on request.

Three pathways: (1) direct contract via existing state Medicaid IT vehicles (often as a competitive small-purchase or task order on an existing master contract); (2) subcontract under a current prime contractor; (3) sole-source where the state determines that a managed verification operations layer is uniquely available and time-critical under P.L. 119-21 compliance deadlines. Reach out and we'll work through your preferred procurement pathway.