The bill amends title 38 to force the Veterans Health Administration (VHA) and Veterans Benefits Administration (VBA) to produce much more detailed annual reports to Congress for a five-year period beginning at enactment. The VHA report expands service- and condition-level counts, utilization and quality metrics, facility capital spending, staffing and workload measures, prescription and inpatient detail, copayment collections, and subgroup breakdowns (for example, Post‑9/11 veterans, homeless veterans, and priority groups).
The VBA additions require disaggregated counts and historic series for compensation, pension, dependency and indemnity compensation, claims timeliness, reevaluations, and staffing metrics.
Beyond reporting, the bill creates two data-sharing systems: an aggregated, anonymized VHA data system modeled on CMS’s Qualified Entity program to serve researchers, and an individual-level but anonymized VBA dataset for approved researchers. Both systems must meet VA security standards and prohibit release of personally identifiable information.
For compliance officers and VA managers, the bill imposes new data collection, processing, and IT obligations; for policy analysts and researchers, it opens substantially richer VA datasets — temporarily (the reporting mandates sunset after five years).
At a Glance
What It Does
The bill revises 38 U.S.C. §7330B to require expanded annual VHA reports and adds new 38 U.S.C. §7735 to expand VBA reporting. It also directs the Secretary to build two researcher data-sharing systems (aggregated VHA data and anonymized individual‑level VBA data) with eligibility criteria and privacy protections.
Who It Affects
Directly affects VA program offices (VHA and VBA) and their IT, analytics, and compliance teams; independent researchers and academic groups that meet VA data‑security criteria; Congress and oversight staff who will receive the new reports; and VA contractors who support data collection and reporting.
Why It Matters
The bill moves VA reporting from summary-level disclosures to operationally actionable datasets and formal researcher access pathways, enabling deeper oversight, independent research, and service‑level performance analysis — while creating material implementation, privacy, and resource questions for VA.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill has two parallel tracks: richer public reporting and researcher access. For VHA it replaces the current §7330B with an enlarged reporting template covering the preceding calendar year and requiring counts of veterans served, detailed health-status incidence for specified chronic conditions, demographic splits, utilization by care setting, prescription dispensing channels, inpatient metrics (length and cost), diagnostic categories by body system, and quality measures such as hospital‑acquired infection rates and patient satisfaction split by Department and non‑Department care.
It also requires facility‑level inventory (square footage, construction/renovation dates, maintenance costs, occupancy rates), a description of capital projects and equipment purchases above $20,000, and summaries tied to statutory programs (e.g., MISSION Act, PACT Act), plus copayment and Medical Care Collections Fund detail.
For VBA the bill adds a new reporting section that compiles counts and demographic breakdowns of benefit recipients (compensation, pension, dependency and indemnity compensation), historical series for reevaluations and pension levels, averages for compensation by category (including special monthly compensation and unemployability), counts and timeliness for new and supplemental claims, and staffing levels for claims processing. The first VBA report must include the newly required elements for the submission year and for the multi‑year baseline specified in the text (prior years back to the dates the bill lists for particular series), creating an initial historical series for analysts.Both tracks include data‑sharing systems for approved researchers.
The VHA system is explicitly to provide aggregated, anonymized datasets and should be developed with an eye toward the Centers for Medicare & Medicaid Services Qualified Entity model; it must include visit-level indicators (dates for outpatient visits, admission/discharge for inpatient care), diagnostic codes, enrollment and priority‑group counts, and insurance coverage indicators. The VBA system is designed to provide anonymized individual‑level records that include demographic fields, service-connected disability diagnostic codes and claim outcomes, and the various benefit categories received.
In both systems the Secretary must promulgate data‑security criteria and ensure no personally identifiable information is accessible, assigning unique identifiers for linkage without revealing identities.Operationally, the bill imposes discrete deadlines and content requirements that will require VA to standardize coding, reconcile data from Department and non‑Department providers, and stand up secure researcher access processes. The reporting mandate carries a five‑year sunset for both enhanced reporting and the data‑sharing buildout; after that period the new requirements lapse unless reenacted.
That sunset creates an initial window for oversight and research but raises questions about long‑term data continuity.
The Five Things You Need to Know
The bill requires expanded VHA and VBA annual reports to Congress for a five-year period starting at enactment (reports cover the calendar year preceding submission).
VHA reports must disaggregate health‑status incidence for specific chronic conditions including traumatic brain injury, diabetes, cardiovascular disease, and cancer, and include subgroup breakdowns (Post‑9/11 veterans, homeless veterans, mental health, polytrauma, spinal cord injury, service‑connected disability status).
The Secretary must build a VHA data‑sharing system providing aggregated, anonymized datasets to qualified researchers and explicitly consider CMS’s Qualified Entity (Medicare) model for performance measurement.
The VBA additions establish a data‑sharing system that provides anonymized individual‑level records (demographics, claim dates, diagnostic codes, approvals/denials, and benefit receipts) to approved researchers, with required safeguards against release of PII and mandatory use of unique identifiers.
The VHA report demands facility management detail including construction/renovation dates, square footage, maintenance costs, occupancy rates, and disclosure of capital purchases over $20,000 — creating new asset reporting obligations for VA facilities.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
Designates the measure as the 'VA Data Transparency and Trust Act.' This is a formal heading and has no substantive effect, but it signals the bill’s framing around transparency and researcher confidence — language that matters for communications and potential appropriation riders in implementation.
Expanded annual VHA reporting requirements
Rewrites §7330B to prescribe an itemized list of metrics the VHA must include annually: service counts, condition incidence measures for enumerated diseases, demographic splits (age, sex, period of service), utilization and visit counts, prescription dispensing by channel, inpatient length/cost, diagnostic breakdowns, quality indicators (e.g., hospital‑acquired infections, patient satisfaction), copayment and collection fund detail, physician and clinician staffing/workload measures, facility asset data, and capital spending plans. Practically this provision standardizes what Congress receives and forces VHA to collect or aggregate data that previously lived across operational systems. VA will need to map existing data sources to these specific elements and close any gaps (for example, linking community care claim payments into a single dataset).
Aggregated, anonymized VHA researcher access modeled on CMS program
Directs the Secretary to create a data‑sharing system that grants eligible researchers access to aggregated, anonymized VHA data and requires the Secretary to adopt data‑security criteria for applicants. The bill calls out the CMS Qualified Entity program as a model, and lists types of data to include (visit indicators, diagnostic codes, enrollment/priority groups, insurance claims data for non‑Department care). The provision balances availability with control: datasets must be anonymized and eligibility limited, but the specification of visit‑level timing and diagnostic detail makes the resulting product analytically rich and useful for outcomes and utilization research.
Expanded VBA reporting and historical series
Adds a new statute directing the VBA to include counts and disaggregations for benefit recipients (compensation, pension, DIC), disability‑rating distributions, reevaluations and reassignment outcomes, claims flows (new and supplemental) and processing timelines, staffing levels, and multi‑year averages for compensation and pension (for specified past years). The first report must backfill the required fields for the baseline period the statute specifies, creating an immediate historical dataset for oversight. This section places explicit analytical demands on VBA’s claims and payments data and will require coordinated pulls across legacy claims systems.
Anonymized individual‑level VBA researcher access
Requires an access program for approved researchers that grants individual‑level but anonymized VBA records: demographics, service history, claim filing and decision dates, diagnostic codes, and benefit types/amounts. The statute mandates safeguards — no PII exposed and assignment of unique identifiers to permit longitudinal analysis without revealing identity. That design enables microdata analysis for claim outcomes, compensation equity, and program evaluation while attempting to protect privacy.
This bill is one of many.
Codify tracks hundreds of bills on Veterans across all five countries.
Explore Veterans in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Independent researchers and academic centers — gain access to richer, standardized VHA aggregated datasets and anonymized VBA microdata for longitudinal and comparative studies that were previously difficult or impossible using VA public reports.
- Congressional oversight offices and GAO/CBO analysts — receive a consistent, itemized reporting package that enables more precise program evaluation, cost estimates, and legislative oversight across health, benefits, and facility management domains.
- Veterans with complex or service‑connected conditions (as a group) — stand to benefit indirectly because the new visibility into condition incidence, utilization, and outcomes can highlight unmet needs and justify targeted programmatic or funding responses.
- State homes and community providers — benefit from clearer reporting on community care, payments, and partnerships, which can inform capacity planning and reimbursement negotiations.
- Veterans service organizations — obtain evidence they can use in advocacy (e.g., trends in claims timeliness, compensation averages, or homelessness duration) to press for policy or funding changes.
Who Bears the Cost
- Veterans Health Administration and Veterans Benefits Administration — must absorb the administrative and IT costs to standardize, extract, and validate the expanded datasets, stand up secure researcher portals, and maintain annual reporting workflows.
- VA IT and data governance teams — will face significant implementation workloads to harmonize disparate legacy systems, ensure coding consistency (diagnostic, procedure, facility), and develop de‑identification/ linkage processes that meet legal and security requirements.
- VA contractors and vendors — likely need to perform new development, analytics, and maintenance work under existing or new contracts, increasing program management overhead and procurement activity.
- Privacy and compliance officers — must implement and monitor researcher vetting, data use agreements, de‑identification standards, and audit trails to prevent reidentification or improper disclosures.
- Congressional staff and program offices — will need internal resources to analyze the influx of detailed data and to maintain continuity if the five‑year window ends without reauthorization.
Key Issues
The Core Tension
The central dilemma is transparency versus practicability and privacy: the bill demands rich, near‑microdata visibility into veterans’ health and benefits to enable oversight and research, but delivering that visibility without exposing individuals or imposing unsustainable IT and staffing burdens on VA requires difficult technical trade‑offs (de‑identification thresholds, data harmonization, and funding choices) that the statute leaves to implementation.
The bill substantially increases the volume and granularity of VA data that must be assembled and disclosed, but it provides only a conceptual framework for implementation. First, VA’s operational data live in multiple legacy systems (electronic health records, community care claims, benefits claims systems) with differing coding standards and data quality.
Converting that heterogeneous information into the precise, disaggregated fields the statute lists will require data‑mapping, re‑coding, and validation work that the bill does not fund or schedule; implementation timelines and costs could be material.
Second, the bill walks a narrow line on privacy. It requires anonymization and forbids PII, and it prescribes unique identifiers for linkage — but it also requires visit‑level timing and individual‑level VBA records that, when combined with demographic slices and small subgroup reporting (e.g., homeless veterans in small geographic areas), raise reidentification risk.
The statute leaves substantive decisions about de‑identification thresholds, minimum cell sizes, and researcher vetting to VA regulation; those regulatory choices will determine whether the research outputs are safe and analytically useful. Finally, the five‑year sunset gives an initial window for transparency but risks fragmentation of longitudinal series unless VA codifies the underlying data processes; researchers relying on the datasets will need clarity on which elements will persist after the statutory window closes.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.