Public Access to HHS Health Data Act of 2026
- Sponsor
- Rep. Bentz, Cliff [R-OR-2]
- Committees
- Natural Resources Committee (primary)
- Last action
- Sep 28, 2026
Bottom line
The bill aims to enhance public access and usability of HHS health data by centralizing it in a machine-readable, freely accessible online repository with API capabilities and regular reporting.
What it actually does
This bill mandates the Secretary of Health and Human Services (HHS) to establish an online repository for all publicly available data sets generated or maintained by the department. These data sets must be machine-readable, accessible, free, and include metadata. The website must allow searching, sorting, downloading, and API access, and be regularly updated.
Proponents argue
Supporters argue that this bill will significantly improve transparency and data utility, enabling researchers, innovators, and the public to more easily access and utilize vast amounts of health data. This increased access can foster scientific discovery, public health improvements, and the development of new health technologies and services, ultimately leading to better health outcomes and economic benefits.
Opponents contend
Opponents might contend that while the goal is laudable, the implementation could be costly and complex, potentially diverting resources from other critical HHS functions. Concerns could also be raised about the practical challenges of ensuring data quality, maintaining security, and addressing privacy issues across a vast array of diverse datasets, despite the bill specifying "publicly available" data.
The bill is very short and clearly written, making it easy for any interested reader to understand its provisions quickly.
Section 2(a)
Mandate for HHS Public Data Repository
This section requires the Secretary of Health and Human Services to create an online repository on opendata.hhs.gov (or a successor site) within one year of the bill's enactment. This repository must contain all publicly available data sets generated or maintained by the Department of Health and Human Services.
Supporters argue
Supporters argue this provision is foundational to improving data transparency and accessibility, centralizing disparate data sources into a single, easy-to-find location, thereby reducing barriers to data utilization.
Critics contend
Critics might argue that while the intent is good, the operational burden and potential costs of consolidating and standardizing "all publicly available data sets" from a vast department like HHS within a year could be substantial and challenging to meet.
Tradeoffs
Balances the public's right to access government data with the administrative and technical challenges of aggregating and maintaining such a comprehensive repository.
Section 2(b) and 2(c)
Standards for Data Accessibility and Usability
These subsections specify that all data sets in the repository must be machine-readable, published in an accessible format, available for unrestricted, free use (including automated processing and bulk access), and include associated metadata. The website itself must allow searching, sorting, downloading, and provide standardized application programming interfaces (APIs) for machine-to-machine retrieval, and be regularly updated.
Section 2(d)
Oversight and Accountability Report
This section requires the Secretary of Health and Human Services to submit an annual report to Congress, starting two years after enactment. The report must detail the number and types of data sets available, their update frequency, and any constraints (legal, technical, operational, financial, administrative) limiting or delaying the publication of additional data sets, including those related to privacy, security, data quality, and resources.
Requires data sets to be "machine-readable (as defined in section 3502 of title 44, United States Code)".
Section 2(b)(1)
Why it matters:This is standard legislative drafting practice to avoid re-defining terms already established in law, ensuring consistency.
Case for: Supporters argue this ensures a consistent and legally established standard for machine-readability, preventing ambiguity and promoting interoperability across government data initiatives.
Case against: Critics might argue that relying on external definitions can make the bill less self-contained and harder for the public to fully understand without additional research.
Estimated impact: Ensures technical consistency in data format, impacting the utility and ease of automated processing for all data sets.