H.R. 9502 (119th)Bill Overview

Protect Seniors and Veterans from Health Care Fraud Act of 2026

domestic policy
Cosponsors
Support
Republican
Introduced
Jun 29, 2026
Discussions
Bill Text
Current stageCommittee

Referred to the Committee on Veterans' Affairs, and in addition to the Committees on Ways and Means, and Energy and Commerce, for a period to be subsequently determined by the Spe…

Introduced
Committee
Floor
President
Law
Congressional Activities
01 · The brief
Plain-English summaryWhat this bill actually does

Requires the Secretary of Veterans Affairs to seek a memorandum of understanding (MOU) with the Secretary of Health and Human Services (CMS) within one year to provide reciprocal access to VA and CMS data for veterans concurrently enrolled in VA patient enrollment and Medicare, Medicaid, or Medicare Advantage. The MOU must allow VA to transmit enrollment and clinical/billing information and require HHS to identify dual-enrolled veterans and return lists and other appropriate data.

Why people may split

Progressives emphasize privacy and preventing benefit reductions

Watch point

Relative to its intended legislative type, this bill establishes a clear administrative directive (to negotiate an interagency MOU and report on its effectiveness) with adequate high-level milestones and reporting, but it leaves out several implementation-critical elements.

Requires the Secretary of Veterans Affairs to seek a memorandum of understanding (MOU) with the Secretary of Health and Human Services (CMS) within one year to provide reciprocal access to VA and CMS data for veterans concurrently enrolled in VA patient enrollment and Medicare, Medicaid, or Medicare Advantage.

The MOU must allow VA to transmit enrollment and clinical/billing information and require HHS to identify dual-enrolled veterans and return lists and other appropriate data.

The MOU would be effective for two years, and VA must report on activities and effectiveness one year after entry and biennially thereafter.

Passage75/100

Technocratic, limited-scope bill targeting fraud among veterans and seniors with minimal fiscal impact and built-in oversight—historically the type that moves through committees and floor consideration.

CredibilityPartially aligned

Relative to its intended legislative type, this bill establishes a clear administrative directive (to negotiate an interagency MOU and report on its effectiveness) with adequate high-level milestones and reporting, but it leaves out several implementation-critical elements.

Contention18/100

Progressives emphasize privacy and preventing benefit reductions

02 · What it does

Who stands to gain, and who may push back.

Likely benefits vs burdens50% / 50%
Federal agenciesVeterans · States

These are examples from the analysis, not a ranked list of the most-affected groups.

Likely helped
  • Federal agenciesMay reduce duplicative or improper Medicare, Medicaid, and VA payments through cross‑agency identification of dual enro…
  • Federal agenciesCould produce federal program savings from fewer overpayments and reduced billing errors.
  • Potential benefitMay improve billing accuracy and reduce reconciliation workload for VA and CMS operations.
Likely burdened
  • VeteransRaises privacy and confidentiality concerns from expanded sharing of veterans' health and enrollment data.
  • StatesCould impose substantial upfront IT and administrative costs on VA, CMS, and possibly state Medicaid agencies.
  • StatesMay encounter legal or procedural barriers because Medicaid is administered by states with varied data systems.
03 · Why people split

Why the argument around this bill splits.

Progressives emphasize privacy and preventing benefit reductions
Progressive85%

Likely broadly supportive because the bill aims to prevent waste and protect veterans and seniors from billing errors.

Would emphasize protecting veterans' access to care, civil liberties, and strong data-privacy and anti-discrimination safeguards.

May insist on explicit guardrails to prevent data misuse or benefit reductions.

Leans supportive
Centrist75%

Generally supportive as a pragmatic, targeted measure to reduce improper payments and improve program integrity.

Wants clear implementation plans, cost estimates, and legal compliance (HIPAA, Medicare/Medicaid rules).

Will seek balanced oversight and a pilot or phased rollout.

Leans supportive
Conservative70%

Likely supportive of anti-fraud and cost-saving goals but wary of added bureaucracy and expansive federal data sharing.

Prefers efficiency and accountability; may press for limited scope, minimal new mandates, and safeguards against mission creep.

Leans supportive
04 · Can it pass?

The path through Congress.

Introduced

Reached or meaningfully advanced

Committee

Reached or meaningfully advanced

Floor

Still ahead

President

Still ahead

Law

Still ahead

Passage likelihood75/100

Technocratic, limited-scope bill targeting fraud among veterans and seniors with minimal fiscal impact and built-in oversight—historically the type that moves through committees and floor consideration.

Scope and complexity
24%
Scopenarrow
24%
Complexitylow
Why this could stall
  • Privacy and HIPAA safeguards not specified
  • No cost estimate or funding for implementation included
05 · Recent votes

Recent votes on the bill.

No vote history yet

The bill has not accumulated any surfaced votes yet.

06 · Go deeper

Go deeper than the headline read.

Included on this page

Progressives emphasize privacy and preventing benefit reductions

Technocratic, limited-scope bill targeting fraud among veterans and seniors with minimal fiscal impact and built-in oversight—historically…

Unlocked analysis

Relative to its intended legislative type, this bill establishes a clear administrative directive (to negotiate an interagency MOU and report on its effectiveness) with adequate high-level milestones and reporting, but…

Go beyond the headline summary with full stakeholder mapping, legislative design analysis, passage barriers, and lens-by-lens tradeoff breakdowns.

Perspective breakdownsPassage barriersLegislative design reviewStakeholder impact map
Open full analysis