H.R. 8679 (119th)Bill Overview

To amend title 38, United States Code, to require the Secretary of Veterans Affairs to transmit a veteran's history of opioid prescriptions to a Community Care health care provider.

domestic policy
Cosponsors
Support
Republican
Introduced
May 7, 2026
Discussions
Bill Text
Current stageCommittee

Referred to the House Committee on Veterans' Affairs.

Introduced
Committee
Floor
President
Law
Congressional Activities
01 · The brief

This bill amends 38 U.S.C. §1703C to require the Secretary of Veterans Affairs to transmit a covered veteran’s history of opioid prescriptions, as contained in VA records, to non‑Department Community Care health care providers who furnish care under section 1703.

The transmission must also occur through a Third Party Administrator (with that term referenced to the meaning in section 1703B).

The text adds the transmission requirement and a cross-reference definition for the Third Party Administrator.

Passage50/100

Technocratic, limited‑scope veterans' data sharing bill has plausible bipartisan support though privacy/implementation questions create uncertainty.

CredibilityPartially aligned

Relative to its intended legislative type, this bill is a narrowly focused statutory change that establishes a clear, single obligation but provides limited operational detail, no fiscal/resource acknowledgment, and no safeguards or accountability mechanisms.

Contention30/100

Privacy and consent: liberals demand strong safeguards; conservatives want limited scope/opt‑in

02 · What it does

Who stands to gain, and who may push back.

Who this appears to help vs burden50% / 50%
CommunitiesTargeted stakeholders
Likely helped
  • CommunitiesImproves clinical continuity between VA and non‑VA Community Care providers treating veterans.
  • Targeted stakeholdersHelps reduce duplicate opioid prescriptions and potential overprescribing by sharing prescription histories.
  • CommunitiesEnables community clinicians to make more informed opioid prescribing decisions at point of care.
Likely burdened
  • Targeted stakeholdersExpands data sharing in ways that may raise patient privacy and confidentiality concerns.
  • Targeted stakeholdersRouting records through Third Party Administrators increases cybersecurity and unauthorized‑access exposure risks.
  • Targeted stakeholdersCreates additional administrative and IT implementation costs for the VA and contracted TPAs.
03 · Why people split

Why the argument around this bill splits.

Privacy and consent: liberals demand strong safeguards; conservatives want limited scope/opt‑in
Progressive80%

Likely supportive because improved data sharing can reduce opioid harm and improve care continuity for veterans.

They will want strong privacy, consent, and non‑punitive safeguards for substance use information.

Leans supportive
Centrist70%

Generally favorable to better interoperability and safety, but concerned about implementation details, costs, legal compliance, and safeguarding patient privacy.

Would seek clarifying amendments and funding language.

Leans supportive
Conservative60%

Mixed to cautiously supportive: improving veteran access to coordinated care aligns with priorities, but wary of new federal mandates, data sharing with third parties, and administrative costs.

Would push for patient choice and limited scope.

Split reaction
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 likelihood50/100

Technocratic, limited‑scope veterans' data sharing bill has plausible bipartisan support though privacy/implementation questions create uncertainty.

Scope and complexity
24%
Scopenarrow
24%
Complexitylow
Why this could stall
  • No cost estimate or funding source provided
  • Patient consent and HIPAA/PDMP interactions not specified
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

Privacy and consent: liberals demand strong safeguards; conservatives want limited scope/opt‑in

Technocratic, limited‑scope veterans' data sharing bill has plausible bipartisan support though privacy/implementation questions create unc…

Unlocked analysis

Relative to its intended legislative type, this bill is a narrowly focused statutory change that establishes a clear, single obligation but provides limited operational detail, no fiscal/resource acknowledgment, and no…

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