SAFER Health Act of 2026
- Sponsor
- Rep. Jacobs, Sara [D-CA-51]
- Committees
- Energy and Commerce Committee (primary)
- Last action
- Jun 25, 2026
Bottom line
The bill significantly strengthens privacy protections for sensitive reproductive health information by restricting its disclosure and updating federal health data regulations to prevent unauthorized access and sharing.
What it actually does
This bill prohibits the disclosure of an individual's pregnancy termination or loss information in federal, state, local, or tribal legal proceedings without their explicit authorization, with narrow exceptions for professional liability defense or investigating harm to the individual. It also mandates revisions to HIPAA and HITECH regulations to prevent 'information blocking' for such data and requires health IT developers to implement data segregation practices for this sensitive information.
Proponents argue
Supporters argue this bill is crucial for protecting individuals' privacy rights in the wake of evolving legal landscapes regarding reproductive healthcare. They contend it prevents sensitive medical information from being used in legal proceedings without explicit consent, thereby safeguarding patients and providers from potential legal repercussions.
Opponents contend
Opponents might argue that this bill could hinder legitimate law enforcement investigations or civil proceedings in certain circumstances, potentially creating loopholes that could be exploited. They might also raise concerns about the administrative burden on healthcare providers and IT developers to implement new data segregation requirements and the potential impact on health information exchange.
The bill is relatively short, making it accessible for a quick read, but its implications for existing federal regulations (HIPAA, HITECH) warrant a more detailed review to understand its full impact.
Section 2(a)(1)
General Prohibition on Disclosure of Pregnancy Information
This provision prohibits healthcare providers and their business associates from sharing an individual's pregnancy termination or loss information in any federal, state, local, or tribal legal proceedings (civil, criminal, administrative, legislative) unless the individual explicitly authorizes it. This overrides existing HIPAA privacy regulations to create a stronger, specific protection for this type of health data.
Supporters argue
Supporters argue this is a vital protection for patient autonomy and privacy, especially in states with restrictive reproductive health laws, ensuring that personal medical decisions are not weaponized in legal contexts.
Critics contend
Critics might argue this provision could impede justice by making it harder for law enforcement or other legal bodies to access potentially relevant information in certain cases, even if those cases are not directly related to the legality of the procedure itself.
Tradeoffs
This provision balances individual privacy rights against potential needs for information in legal proceedings, aiming to prioritize patient confidentiality for highly sensitive medical data.
Section 2(a)(2)
Limited Exceptions to Disclosure Prohibition
This section outlines two narrow exceptions where pregnancy termination or loss information can be disclosed without individual authorization. The first is for defense in professional liability actions against the covered entity or business associate. The second is to investigate physical harm to the individual directly related to the pregnancy loss or termination, but only if the individual is deceased or incapacitated.
Section 2(b)(1)
HITECH Information Blocking Clarification
This provision directs the Secretary of Health and Human Services to revise HITECH regulations to clarify that refusing a request to access, exchange, or use electronic health information (EHI) related to pregnancy termination or loss, in order to comply with the bill's new privacy prohibitions, will not be considered 'information blocking.' Information blocking is generally prohibited under HITECH to promote EHI interoperability.
Section 2(b)(2)
HITECH Data Segregation Requirement for Health IT
This provision mandates the Secretary to revise HITECH regulations to require that, as a condition for health IT developers to receive certification, they must implement practices allowing for the segregation of data related to pregnancy termination or loss information. This is to ensure compliance with the bill's new disclosure prohibitions.
Section 2(c)
Federal Preemption and State Law Modification
This section establishes that the Act preempts any state law that conflicts with or prevents its application. However, it explicitly states that it does not preempt state laws that provide greater privacy protections for pregnancy termination or loss information. It also directs the Secretary to revise HIPAA preemption rules to ensure no exceptions apply to this information, other than for greater state privacy protections.
Defines 'pregnancy termination or loss information' broadly to include not just the procedures themselves, but also any related requests, services, education, counseling, or referrals, encompassing abortion, miscarriage, stillbirth, and ectopic pregnancy.
Section 2(f)(2)
Why it matters:While it is standard legislative practice to define terms at the end of a bill, the broad scope of this definition is highly consequential for the practical application and reach of the bill's protections.
Case for: Proponents argue this broad definition is essential to provide comprehensive protection, as privacy breaches can occur at any stage of seeking or receiving care, not just during the procedure itself, ensuring robust safeguards.
Case against: Opponents might argue that such a broad definition could inadvertently sweep in routine medical consultations or information that is not directly related to a 'termination or loss' in a way that creates unnecessary administrative burdens or privacy restrictions.
Estimated impact: Significantly expands the scope of protected health information beyond just the medical event itself, covering a wider range of related activities and communications, thereby increasing the compliance burden on entities.
Mandates the Secretary of Health and Human Services to issue an interim final rule within 90 days of enactment and a final rule within 270 days to implement the required regulatory revisions.
Section 2(e)
Why it matters:This is standard legislative practice for implementation details, but the aggressive timeline is consequential for the Department of Health and Human Services and regulated entities, as it requires rapid action.
Case for: Proponents argue this expedited timeline is crucial to ensure rapid implementation of critical privacy protections, responding to an urgent need for safeguards in the current legal environment.
Case against: Critics might contend that such a tight deadline could strain agency resources, potentially leading to rushed or inadequately considered regulations, or creating significant compliance challenges for affected entities.
Estimated impact: Accelerates the implementation of the bill's provisions, potentially leading to faster privacy protections but also increased pressure on HHS and regulated entities to adapt quickly.