VA SB 672
Status unknownEmergency Response Exposure Grant Fund and Program; created.
Virginia · 2026 Regular Session · upper
Quick answers
Did VA SB 672 pass?
The current status of VA SB 672 is not known from the official record. Latest recorded action (2026-02-03): Continued to next session in Finance and Appropriations (15-Y 0-N)
What is VA SB 672 about?
Emergency Response Exposure Grant Fund and Program. Creates the Emergency Response Exposure Grant Fund and Program, to be administered by the Department of Fire Programs, to award grants to localities to support certain emergency responders who were exposed to a qualifying emergency, defined in the bill. The bill requires funding to be used for annual cancer screenings and health care expenses incurred by eligible emergency responders, defined in the bill, in the event such emergency responders are diagnosed with cancer from toxic material exposure. The bill permits funding to be used for out-of-pocket medical expenses not otherwise covered by insurance, workers' compensation, or other available funding.
Who sponsors VA SB 672?
Aaron R. Rouse is the primary sponsor of VA SB 672.
Description
Emergency Response Exposure Grant Fund and Program. Creates the Emergency Response Exposure Grant Fund and Program, to be administered by the Department of Fire Programs, to award grants to localities to support certain emergency responders who were exposed to a qualifying emergency, defined in the bill. The bill requires funding to be used for annual cancer screenings and health care expenses incurred by eligible emergency responders, defined in the bill, in the event such emergency responders are diagnosed with cancer from toxic material exposure. The bill permits funding to be used for out-of-pocket medical expenses not otherwise covered by insurance, workers' compensation, or other available funding.
- Introduced
- 2026-01-14
- Latest action
- 2026-02-03 — Continued to next session in Finance and Appropriations (15-Y 0-N)
- Bill type
- bill
- Last updated
- —
Sponsors
- Aaron R. Rouseprimary
Committees
Not provided by source.
Action timeline
2026-01-14
Prefiled and ordered printed; Offered 01-14-2026 26103752D
filing,introduction
2026-01-14
Referred to Committee on General Laws and Technology
referral-committee
2026-01-22
Fiscal Impact Statement from Department of Planning and Budget (SB672)
2026-01-28
Rereferred from General Laws and Technology to Finance and Appropriations (11-Y 0-N)
referral-committee
2026-02-03
Continued to next session in Finance and Appropriations (15-Y 0-N)
Versions
Documents
Votes
Rereferred from General Laws and Technology
2026-01-28 · pass · 11-0
Member-level votes (15)
- Adam P. Ebbin: yes
- Mamie E. Locke: yes
- Bryce E. Reeves: yes
- Jeremy S. McPike: yes
- Todd E. Pillion: yes
- Aaron R. Rouse: yes
- Christopher T. Head: not voting
- Emily M. Jordan: not voting
- Lashrecse D. Aird: yes
- Schuyler T. VanValkenburg: yes
- Danica A. Roem: not voting
- Jennifer D. Carroll Foy: yes
- Timmy French: not voting
- Christie New Craig: yes
- Angelia Williams Graves: yes
Continued to next session in Finance and Appropriations
2026-02-03 · pass · 15-0
Member-level votes (15)
- L. Louise Lucas: yes
- R. Creigh Deeds: yes
- Mamie E. Locke: yes
- David W. Marsden: yes
- Adam P. Ebbin: yes
- Ryan T. McDougle: yes
- Mark D. Obenshain: yes
- Richard H. Stuart: yes
- Bryce E. Reeves: yes
- Barbara A. Favola: yes
- Scott A. Surovell: yes
- Jeremy S. McPike: yes
- Jennifer B. Boysko: yes
- Todd E. Pillion: yes
- Aaron R. Rouse: yes
Related bills
No related bills recorded for this bill.
Official source
Attribution
Data from openstates_bulk_csv, retrieved 2026-07-24T05:35:59.552682Z
Inspect retained evidence for changes recorded after evidence tracking began:
Use this data
Every field on this page is available from the free public API — no key or licence required. Fetch this bill as JSON: GET /api/v1/bills?jurisdiction=VA&identifier=SB 672. See the API docs or the MCP server for AI assistants.
Known limitations
- Sponsor party and chamber affiliation are not yet captured by this API.
- Committee referrals are not yet captured.
See the methodology page for data sources and limitations.