The Capitol LedgerEvery move in Congress, on the record
HomeBillsRecordsLedger AI

The Capitol Ledger

Built from the Congressional Record and Congress.gov. Every summary links to its source.

AboutFAQFeedbackTerms of ServicePrivacy Policy
Follow us onlineInstagram

Summaries are AI-generated from primary sources. Verify anything important against the original record.

The Capitol Ledger

Built from the Congressional Record and Congress.gov. Every summary links to its source.

The projectAboutFAQFeedback
LegalTerms of ServicePrivacy Policy
Follow us onlineInstagram

Summaries are AI-generated from primary sources. Verify anything important against the original record.

All bills
H.R. 6117·119th Congress·Introduced Nov 18, 2025

Patient Device Data Access Act of 2025

IntroducedHealthSubstantive
View bill text
Sponsor
Rep. Sherrill, Mikie [D-NJ-11]
Committees
Energy and Commerce Committee (primary)
Last action
Nov 18, 2025

Bottom line

This bill aims to empower patients with greater access to their medical device data by enabling the FDA to mandate disclosure from manufacturers, enhancing transparency and patient autonomy in personal health management.

What it actually does

This bill authorizes the Secretary of Health and Human Services (via the FDA) to issue regulations requiring manufacturers of certain electronic medical devices (specifically implanted or remotely monitored devices) to disclose patient-specific data to patients upon request. It also allows the FDA to mandate that manufacturers publish information about their data collection and access methods on their websites, and proactively notify patients about device recalls, software updates, or error messages.

Proponents argue

Proponents argue this bill significantly increases patient autonomy and transparency regarding personal health data collected by medical devices. They contend that patients have a fundamental right to access their own data, which can help them better understand their health conditions, make more informed treatment decisions, and potentially identify issues with their devices. This initiative aligns with broader movements advocating for greater patient control over health information.

Opponents contend

Opponents might raise concerns about the potential administrative burden and compliance costs for medical device manufacturers, particularly for smaller companies, to develop and implement new data disclosure systems. They may also argue about the risk of patients misinterpreting raw, complex medical data without proper clinical guidance, or highlight potential cybersecurity risks associated with new data transfer protocols.

The bill is very short and clearly written, making it accessible for a quick read and easy to understand its core intent.

Section 2, adding new Section 524C(a) to the Federal Food, Drug, and Cosmetic Act.

Authorization for Patient-Specific Data Disclosure

prominently featuredstraightforward

This provision grants the Secretary of Health and Human Services (acting through the FDA) the authority to create regulations. These regulations would require manufacturers of "covered devices" to provide patients with all patient-specific data recorded or transmitted by their device, provided that data is accessible to the manufacturer, upon the patient's request.

GroupImpactMechanismScale
GroupPatients using covered medical devicesImpactIncreased access to their personal health data, potentially leading to better health management and informed decision-making.MechanismDirect request to manufacturers, facilitated by new FDA regulations.ScalePotentially affects millions of patients with implanted or remotely monitored electronic medical devices.
GroupMedical device manufacturersImpactNew regulatory compliance requirements and potential operational costs associated with data extraction and disclosure.MechanismMandated data disclosure and system development to comply with FDA regulations.ScaleImpacts all manufacturers of covered devices, requiring adjustments to data handling practices.

Supporters argue

Supporters argue this provision is crucial for patient empowerment, allowing individuals to have full control and understanding of their own health information generated by devices. It promotes transparency in an area where data is often proprietary and inaccessible to the user, aligning with modern healthcare data rights.

Critics contend

Critics might contend that this broad authorization could lead to overly burdensome regulations for manufacturers, potentially stifling innovation or increasing device costs. They may also express concerns about the security implications of widespread data sharing if not carefully managed.

Tradeoffs

This provision balances the desire for enhanced patient autonomy and data access against potential industry burden, compliance costs, and data security considerations.

Section 2, adding new Section 524C(b) to the Federal Food, Drug, and Cosmetic Act.

Regulatory Framework and Manufacturer Obligations

prominently featuredmoderately complex

This section details how the FDA would implement the data disclosure requirement through regulations. It specifies that these regulations must apply to all covered device manufacturers and should consider existing FDA guidance. It also allows the FDA to include requirements for manufacturers to disclose data in understandable formats, publish information about data collection and access on their websites, and notify patients about recalls, software updates, or error messages.

Section 2, adding new Section 524C(c) to the Federal Food, Drug, and Cosmetic Act.

Limitations on Disclosure Authority

mentioned in summarystraightforward

This provision outlines specific situations where the Secretary is *not* authorized to require data disclosure. These exceptions include data that is recorded, transmitted, and retained in a closed system and is inaccessible to the manufacturer, or data that is generally inaccessible to the manufacturer. It also explicitly states that the Secretary cannot require manufacturers to redesign their devices solely to enable data disclosure.

FOUND

Defines "covered device" as an electronic device intended for diagnosis, cure, mitigation, treatment, or prevention of disease, that is *either* implanted into a patient's body *or* used for remote monitoring, and is capable of recording or transmitting patient data.

Section 2, adding new Section 524C(d)(1) to the Federal Food, Drug, and Cosmetic Act.

Why it matters:This is standard legislative practice to define terms at the end of a section, but its specific wording is critical to understanding the bill's scope.

Case for: Supporters argue this precise definition ensures the bill targets specific types of devices where patient data access is most critical and technically feasible, avoiding overreach into simpler medical devices where the benefits might not outweigh the regulatory burden.

Case against: Critics might argue that limiting the scope to "implanted" or "remote monitoring" devices could exclude other significant data-generating medical devices that patients might also want access to, potentially creating an arbitrary distinction in data rights.

Estimated impact: This definition determines the exact scope of devices, and thus the number of patients and manufacturers, directly affected by the bill's data access requirements.

FOUND

Defines "patient-specific data" broadly to include data unique to an individual patient or their treatment/diagnosis, recorded or transmitted by a covered device, and accessible to the manufacturer. It explicitly includes usage, alarms, outputs, pulse oximetry, heart electrical activity, and pacemaker rhythm data, regardless of whether it would otherwise be required by law to be disclosed.

Section 2, adding new Section 524C(d)(2) to the Federal Food, Drug, and Cosmetic Act.

Why it matters:Standard legislative practice for definitions, but the breadth and specific inclusions are critical for the bill's impact and could be missed by a cursory reading.

Case for: Proponents would highlight that this comprehensive definition ensures patients get access to a wide range of relevant data, closing potential loopholes where manufacturers might claim certain data types are not "patient-specific" or are already covered by other, potentially less accessible, laws.

Case against: Manufacturers might argue that such a broad definition could encompass proprietary operational data or data that is not clinically meaningful to patients without expert interpretation, thereby increasing the disclosure burden and potential for misinterpretation.

Estimated impact: This definition significantly expands the types of data patients can request, potentially increasing the utility and value of the bill for patients by providing a more complete picture of their device's performance and their health metrics.

About this analysis. AI-Generated from the official bill text and available committee reports. Gaps in available data are noted explicitly. Verify important details with the official Congress.gov record.

On this page

  • Executive summary
  • Key provisions
  • Buried treasure
  • Follow the money
  • Critical analysis
  • Questions to ask
Ask Ledger AI about this