Veridian Public
Statutory text · Title XI

What Public Law 119-21 Says About Verification

A section-by-section reading of the verification and eligibility provisions — the exact statutory language, what it means in plain English, what each provision requires operationally, and the page reference in the enrolled text at congress.gov.

Operations reading → Read the law (PDF)
By Veridian Public Policy & Operations Team · Operations specialists for Public Law 119-21 implementation
Last updated 2026-05-20

This page is the legal-reading companion to the Citizens operations reading of Public Law 119-21. Where that page describes how state agencies operationalize the law, this one walks through what the statute itself says — section by section, with the exact quotes and citations a procurement reviewer or program counsel will want to see.

Sections covered

  1. § 71102 — Moratorium on the CMS streamlining rule
  2. § 71103 — Duplicate Medicaid / CHIP enrollment
  3. § 71104 — Deceased beneficiaries
  4. § 71105 — Deceased providers
  5. § 71106 — Erroneous excess Medicaid payments
  6. § 71107 — Eligibility redeterminations
  7. § 71109 — Alien Medicaid eligibility
  8. § 71119 — Community engagement requirements
  9. § 71303 — Premium tax credit eligibility
  10. § 71401 — Rural Health Transformation (context)
  11. § 73001 — Unemployment wage verification (context)
  12. Cross-cutting verification themes

All quoted text below is reproduced from the enrolled official text of Public Law 119-21 as published by congress.gov. Page references point to the corresponding pages of the official PDF. Read the full text: congress.gov/119/plaws/publ21/PLAW-119publ21.pdf ↗

§ 71102

Moratorium on Medicaid / CHIP Eligibility & Enrollment Streamlining Rule

Plain-English: The law pauses enforcement of parts of the 2024 CMS eligibility/enrollment streamlining rule through September 30, 2034. States cannot rely on those simplification rules during that window and may need stricter, more manual verification workflows in the meantime.

What the statute requires

The Secretary of Health and Human Services is prohibited from implementing, administering, or enforcing certain provisions of the streamlining rule during the moratorium period.

Operational impact

State systems, call centers, eligibility workers, and vendor partners must operate in a more verification-heavy environment through Sept. 30, 2034. Plan verification workloads at full scale, not at the streamlined-rule baseline.

Veridian Public capability

Right-sized operational capacity that handles the full verification workload — with the workflow flexibility to adapt as the streamlining rule eventually returns.

"The Secretary of Health and Human Services shall not, during the period beginning on the date of the enactment of this section and ending September 30, 2034, implement, administer, or enforce…"

Public Law 119-21, § 71102, pp. 220–221. congress.gov PDF ↗

§ 71103

Duplicate Medicaid / CHIP Enrollment

Plain-English: States must check whether enrollees are simultaneously enrolled in another state's Medicaid or CHIP program. The law creates a federal system for this check, sets a data-submission cadence of at least monthly, and requires action when duplicates are detected.

Cross-state duplicate-enrollment checks

Operational impact

Automated cross-state identity matching, SSN validation, monthly submissions, and exception handling become standing program functions — not one-time projects.

Veridian Public capability

Workflow coordination for monthly submission cycles, exception queues, false-positive resolution, and audit-ready logs.

States must submit information "not less frequently than once each month and during each determination or redetermination of the eligibility of such individual…"

§ 71103, pp. 221–222.

Required identifying data for duplicate checks

Operational impact

Secure SSN exchange, identity-data privacy controls, structured audit logs, and a process for resolving false-positive matches before any coverage action.

Veridian Public capability

Privacy-controlled data exchange, role-based access, and human-in-the-loop review for sensitive matches.

Required information includes "the social security number of such individual" and "such other information…necessary…for purposes of preventing individuals from simultaneously being enrolled…"

§ 71103, p. 222.

Residency action when a duplicate is detected

Operational impact

When the federal system flags simultaneous enrollment, the state must determine residency and may disenroll if the individual does not reside in the state — meaning notices, outreach, document collection, appeals, and audit trail.

Veridian Public capability

Address-verification operations, multichannel outreach, document collection assistance, exception resolution.

If the system indicates another-state enrollment, the state must take "appropriate action…to identify whether such an individual resides in the State and disenroll…" if the person does not reside there.

§ 71103, p. 222.

Federal duplicate-enrollment system — established by Oct. 1, 2029

Operational impact

States and vendors should plan now for integration with the forthcoming federal system: monthly batch checks, API workflows, exception queues, and reporting.

Veridian Public capability

Integration-ready outputs and workflow coordination designed to plug into emerging federal data systems as they come online.

"Not later than October 1, 2029, the Secretary shall establish a system…to prevent an individual from being simultaneously enrolled…"

§ 71103, p. 222.

Address verification — reliable data sources

Operational impact

States must regularly obtain addresses from defined reliable sources — including USPS returned mail, NCOA, managed care organizations, and other state-approved sources.

Veridian Public capability

Automated NCOA matching, returned-mail handling, MCO data ingestion, and beneficiary contact workflows with documented outreach attempts.

Reliable sources include "Mail returned to the State by the United States Postal Service," "The National Change of Address Database," managed care entities, and "Other data sources…"

§ 71103, p. 223.

§ 71104

Deceased Beneficiaries

Plain-English: States must use the SSA Death Master File to identify potentially deceased enrollees — and must correct mistakes by retroactively reinstating coverage if someone was wrongly disenrolled.

Death Master File matching with mistake-correction

Operational impact

Death-data matching, human review, notification workflow, false-positive handling, rapid retroactive reinstatement, and a complete audit trail of each decision.

Veridian Public capability

DMF match-review operations including escalation handling, beneficiary outreach for false-positive cases, and documented case closure with retroactive-reinstatement support.

If a person was "misidentified as deceased… and was erroneously disenrolled," the state must "immediately re-enroll such individual…retroactive to the date of such disenrollment."

§ 71104, p. 225.

§ 71105

Deceased Providers

Plain-English: Beginning January 1, 2028, states must check the SSA Death Master File during provider enrollment, reenrollment, revalidation, and at least quarterly while a provider remains enrolled.

Recurring provider DMF checks

Operational impact

Provider enrollment systems need automated DMF checks at intake plus quarterly recurring monitoring, with provider-status flagging and payment-prevention controls when matches occur.

Veridian Public capability

Configurable workflow coordination for recurring screening cadences and exception routing, delivered in coordination with the state's provider enrollment system.

"Beginning January 1, 2028… the State conducts a check of the Death Master File… to determine whether such provider or supplier is deceased."

§ 71105, p. 225.

§ 71106

Erroneous Excess Medicaid Payments

Plain-English: The definition of erroneous payments expands to include payments made where eligibility cannot be confirmed due to insufficient information — not just payments for ineligible individuals.

Insufficient-information payments now count as erroneous

Operational impact

This raises the value of documentation, verification-status tracking, evidence capture, and audit-trail completeness. "We didn't have the information" is no longer a defense.

Veridian Public capability

Built-in audit trail and exportable case-evidence records produced as a side-effect of doing the verification work, not assembled retroactively for audit.

Erroneous payments include payments "where insufficient information is available to confirm eligibility" and payments for services to someone "who is not eligible…"

§ 71106, p. 225.

§ 71107

Eligibility Redeterminations

Plain-English: For specified Medicaid populations, states must redetermine eligibility every six months — double the prior cadence — beginning after December 31, 2026.

Semi-annual redetermination for applicable populations

Operational impact

Effectively doubles renewal workload for affected populations. Each cycle creates outbound notices, digital intake, document handling, AI-assisted triage, worker review, call-center support, and compliance tracking.

Veridian Public capability

Redetermination outreach operations with reminder cadences, multilingual content, response tracking, and human-assisted resolution for incomplete responses.

A state "shall make such a redetermination once every 6 months" for specified individuals.

§ 71107, p. 225.

§ 71109

Alien Medicaid Eligibility

Plain-English: Beginning October 1, 2026, federal Medicaid payment is limited unless the individual is a U.S. citizen / national or falls into a listed eligible-alien category, with statutory exceptions (such as emergency Medicaid) defined within the section.

Citizenship and immigration-status verification

Operational impact

Citizenship and immigration-status verification, document capture, eligibility rules-engine updates, and careful handling of emergency Medicaid exceptions — paired with strong language access so eligible individuals are not deterred from coverage they remain entitled to receive.

Veridian Public capability

Multilingual citizen assistance, document collection support, and human-in-the-loop review for complex case resolution.

"Beginning on October 1, 2026… in no event shall payment be made… unless such individual is" a resident and citizen/national or listed eligible alien category.

§ 71109, p. 228.

§ 71119

Medicaid Community Engagement Requirements

Plain-English: States must verify community engagement compliance during regular redetermination (and may verify more frequently). The law requires ex parte verification using available data wherever possible, and a 30-day cure period when an individual cannot be verified automatically.

Verification at redetermination

Operational impact

One of the law's biggest operational additions: work / activity attestation, payroll-data checks, exemption screening, hardship handling, notices, cure-period management, and human review for sensitive cases.

Veridian Public capability

Community engagement verification operations — outreach, attestation handling, exemption review, exception resolution.

The state "shall verify…that each such individual has met the requirement to demonstrate community engagement…during each such individual's regularly scheduled redetermination…"

§ 71119, p. 239.

Ex parte verification — check data before asking the beneficiary

Operational impact

States must use reliable data already available (payroll data, Medicaid payment / encounter data, etc.) before requiring documents from the individual. Excellent fit for automated data matching, payroll integration, and "no-touch" verification.

Veridian Public capability

Automated data-source workflow coordination with exception-only human review — reducing beneficiary burden while preserving accuracy.

The state shall "establish processes and use reliable information available to the State…without requiring, where possible, the applicable individual to submit additional information."

§ 71119, p. 239.

Noncompliance notice and 30-day cure period

Operational impact

When the state cannot verify community engagement automatically, it must send a notice and provide 30 calendar days for the individual to prove compliance or prove the requirement does not apply. Requires multilingual / accessible notices, appeal/cure workflow, document upload, live-agent support, and deadline tracking.

Veridian Public capability

Multichannel cure-period workflow with reminders, document collection assistance, and human-assisted resolution — the single most impactful operation for protecting coverage continuity.

The state must "provide such individual with the notice of noncompliance" and "provide such individual with a period of 30 calendar days…"

§ 71119, pp. 239–240.

§ 71303

Premium Tax Credit Eligibility Verification (Marketplace)

Plain-English: For Affordable Care Act exchanges, a coverage month does not count before the Exchange verifies eligibility to enroll and eligibility for advance premium tax credit. Exchanges may use available and reliable third-party data sources; pre-enrollment verification must be available by August 1 for the following plan year.

Verification before coverage counts

Operational impact

State-based marketplaces need pre-enrollment verification, income / family-size verification, immigration-status checks, residence and coverage-status checks, and third-party data matching — before a coverage month is counted.

Veridian Public capability

Where engaged, the same verification operations layer used for Medicaid extends to Exchange premium-tax-credit verification with documented outcomes.

A coverage month does not include any month before the Exchange verifies the individual's eligibility "to enroll in the plan" and "for any advance payment…"

§ 71303, p. 253.

Categories that must be verified

Operational impact

Income, family size, alien status, health coverage status, and place of residence each need their own verification rule and audit trail.

Veridian Public capability

Structured verification checklist and rules-engine coordination, exception escalation, and audit-ready case histories.

Applicable enrollment information includes "Household income and family size," "Whether the individual is an eligible alien," "health coverage status," and "Place of residence."

§ 71303, pp. 253–254.

Use of third-party data and pre-enrollment verification

Operational impact

Exchanges are permitted to use any data available and reliable third-party sources for applicant verification. A pre-enrollment verification process must be in place by August 1 for the next plan year.

Veridian Public capability

Integration-ready outputs and document-intake workflow that plug into existing Exchange tooling.

"An Exchange shall be permitted to use any data available to the Exchange and any reliable third-party sources…"
Exchange must provide "a process for pre-enrollment verification" where an applicant may verify "household income and eligibility for enrollment…"

§ 71303, pp. 254–255.

§ 71401

Rural Health Transformation Program (context, not a verification rule)

Plain-English: Not a beneficiary-verification rule, but a major rural-health funding program created by the law. Small and rural hospitals may benefit indirectly through state programs that draw on this funding for digital front door, telehealth, care coordination, workforce support, and operational modernization.

Funding for rural health transformation

The law establishes "CHAPTER 4—PROTECTING RURAL HOSPITALS AND PROVIDERS" and "SEC. 71401. Rural Health Transformation Program."

§ 71401, p. 257.

§ 73001

Unemployment Wage Eligibility (context)

Plain-English: Not a Medicaid rule, but it reflects the same legislative direction toward system-based verification: states must use available systems to verify wage eligibility as much as possible, paired with overpayment recovery.

System-based wage verification

State agencies "shall utilize available systems to verify wage eligibility by assessing claimant income to the degree possible."

§ 73001, p. 263.

Cross-Cutting Themes

The Verification Themes Running Through the Statute

Read in aggregate, the law has one dominant theme: data-driven eligibility control. The statute repeatedly pushes states toward using available systems and reliable data sources rather than relying only on applicant statements. The same pattern appears in duplicate-enrollment checks, Death Master File checks, address verification, community-engagement ex parte verification, premium-tax-credit verification, and unemployment wage verification.

Verification theme Why it matters Technology opportunity
Cross-state duplicate enrollment Prevents simultaneous enrollment across states Identity matching, SSN matching, interstate data exchange, case exceptions
Address / residency verification Determines whether the person belongs in the state's program USPS / NCOA checks, MCO address feeds, returned-mail automation
Death checks (beneficiaries & providers) Prevents payments for deceased individuals DMF matching, false-positive review, retroactive reinstatement
More frequent redeterminations Doubles eligibility workload for affected populations Digital renewal workflows, AI triage, worker dashboards, call-center support
Community engagement verification New compliance obligation for applicable Medicaid individuals Payroll data, exemption detection, hardship review, cure-period tracking
Ex parte verification Reduces unnecessary beneficiary burden Automated data matching before asking for documents
Payment-error control Missing eligibility evidence now creates financial exposure Audit trails, evidence management, QA sampling, compliance reporting
Exchange / marketplace verification Premium tax credit depends on verified eligibility Marketplace verification, third-party data, pre-enrollment verification
Bottom line: Public Law 119-21 makes verification a central operational requirement of the Medicaid program. The most procurement-relevant sections are § 71103, § 71104, § 71105, § 71106, § 71107, § 71109, § 71119, and § 71303. Together they support a verification-operations approach that combines secure, auditable, human-assisted automation across redetermination, address / residency checks, death checks, community-engagement compliance, notices, and exception handling.
This page summarizes statutory text and operational implications for state Medicaid programs and partner organizations. It is for informational and operational planning purposes only and does not constitute legal advice. Agencies, counsel, and partners should rely on the official enrolled text of Public Law 119-21, CMS implementing guidance, and Federal Register notices for binding interpretation. All page references point to the official PDF published by the U.S. Government Publishing Office at congress.gov ↗.

Operationalize Each Section — with a Specialist Who Knows the Statute Cold.

Talk with our team about how Veridian Public operationalizes each provision above — one section at a time, or as a coordinated capability across the full statute.

Request a Briefing Citizens Operations reading →