· Agency action
Use of Online Tracking Technologies by HIPAA Covered Entities and Business Associates (revised bulletin)
U.S. Department of Health and Human Services, Office for Civil Rights
Primary source: HHS guidance page. Checked on November 10, 2026.
HHS's revised bulletin says HIPAA-regulated entities may not let tracking technologies impermissibly disclose protected health information to vendors; a court later vacated only its part on IP addresses and public pages about conditions or providers.
What happened
The HHS Office for Civil Rights, which administers and enforces the HIPAA Privacy, Security and Breach Notification Rules, issued this bulletin in December 2022 and revised it on March 18, 2024. It addresses HIPAA covered entities and business associates that use tracking technologies, such as cookies, web beacons or pixels, session replay tools and fingerprinting, on websites and mobile apps.
The bulletin separates user-authenticated pages, such as patient portals and telehealth platforms, where it says tracking technologies generally have access to protected health information, from unauthenticated public pages, where it says many tracking technologies do not. It names exceptions on public pages: appointment booking and symptom-checker pages, and portal login and registration pages when credentials or registration details are collected.
The revised bulletin also said that connecting an IP address or other identifying information with a visit to a page about specific health conditions or providers is not enough, by itself, to be individually identifiable health information. In the bulletin's view, the combination qualifies only if the visit relates to that individual's past, present or future health, health care or payment for care. It illustrated the point with a student researching oncology services and a patient seeking a second opinion.
On June 20, 2024, in American Hospital Association v. Becerra, the Northern District of Texas declared unlawful and vacated part of the revised bulletin. The vacated part made HIPAA obligations arise when an online technology connects an IP address with a visit to an unauthenticated public page addressing specific health conditions or health care providers. The court said the vacatur should not be read to limit the rest of the bulletin, and HHS's page now opens with a note describing the order and otherwise keeps the March 2024 text.
What the agency did
The bulletin says regulated entities may not use tracking technologies in a way that results in impermissible disclosures of protected health information to tracking technology vendors, and that disclosures to those vendors for marketing without HIPAA-compliant authorizations are impermissible. (Bulletin, introduction)
Regulated entities are not permitted to use tracking technologies in a manner that would result in impermissible disclosures of PHI to tracking technology vendors or any other violations of the HIPAA Rules.
Bulletin, introduction (footnote omitted) On pages that require a login, such as patient portals and telehealth platforms, tracking technologies generally have access to protected health information, and the entity must have a business associate agreement with a vendor that receives it on the entity's behalf. (Bulletin, section on tracking on user-authenticated webpages)
Tracking technologies on a regulated entity’s user-authenticated webpages generally have access to PHI.
Bulletin, section on tracking on user-authenticated webpages Many public pages give tracking technologies no access to protected health information. But tracking on pages where people book appointments or use a symptom checker without logging in may collect it, such as an email address or the reason for seeking care. Tracking that collects login or registration details on patient portal pages is a disclosure of protected health information. (Bulletin, section on tracking on unauthenticated webpages)
Tracking technologies on a regulated entity’s unauthenticated webpage that permits individuals to schedule appointments or use a symptom-checker tool without entering credentials may have access to PHI in certain circumstances.
Bulletin, section on tracking on unauthenticated webpages A website banner asking users to accept or reject tracking is not a valid HIPAA authorization. The Privacy Rule also does not permit disclosures to a tracking vendor based solely on a privacy policy, notice or terms of use saying they will occur. (Bulletin, section on HIPAA compliance obligations)
Website banners that ask users to accept or reject a website’s use of tracking technologies, such as cookies, do not constitute a valid HIPAA authorization.
Bulletin, section on HIPAA compliance obligations A vendor's agreement to remove or de-identify protected health information after receiving it is not enough; without individuals' authorizations, the vendor needs a signed business associate agreement and the disclosure needs a Privacy Rule permission. (Bulletin, section on HIPAA compliance obligations)
it is insufficient for a tracking technology vendor to agree to remove PHI from the information it receives or de-identify the PHI before the vendor saves the information.
Bulletin, section on HIPAA compliance obligations An impermissible disclosure to a tracking vendor, made without a Privacy Rule permission and without a business associate agreement, is presumed to be a breach of unsecured protected health information that requires notice. The presumption holds unless the entity shows a low probability that the information was compromised. (Bulletin, section on HIPAA compliance obligations)
there is a presumption that there has been a breach of unsecured PHI unless the regulated entity can demonstrate that there is a low probability that the PHI has been compromised.
Bulletin, section on HIPAA compliance obligations In American Hospital Association v. Becerra, the court declared unlawful and vacated the bulletin's treatment of an IP address combined with a visit to an unauthenticated public page addressing specific health conditions or health care providers. It held that this part was issued in clear excess of HHS's authority under HIPAA, and it limited the vacatur to that part. (No. 4:23-cv-01110-P, ECF No. 67 at 31 (N.D. Tex. June 20, 2024))
Such vacatur is not intended to, and should not be construed as, limiting the legal operability of other guidance in the germane HHS document.
ECF No. 67 at 31 n.8 The bulletin states that it does not have the force and effect of law. (Bulletin, disclaimer)
The contents of this document do not have the force and effect of law and are not meant to bind the public in any way.
Bulletin, disclaimer
What it did not decide
- The bulletin decides no case and imposes no penalty; OCR describes its investigations as fact-specific.
- It does not address the federal Wiretap Act, state wiretap or privacy statutes, or state consumer-protection law, though it notes that the FTC Act and the FTC's Health Breach Notification Rule may apply to health apps outside HIPAA.
- The Becerra court reviewed only the vacated combination and did not reach the challengers' notice-and-comment or arbitrary-and-capricious arguments (ECF No. 67 at 20, 26).
- HHS's note at the top of the page says it is evaluating its next steps in light of the order.
The tracking involved
Tools
- Cookies
- Web beacons and tracking pixels
- Session replay tools
- Fingerprinting
- Tracking code in mobile apps
Data
- IP addresses and geographic location
- Device IDs and advertising IDs
- Medical record numbers, email and home addresses and appointment dates
- Reasons for seeking care typed or selected on booking or symptom-checker pages
- Patient portal login and registration details
How it bears on website tracking claims
Supports: strengthens a website tracking claim on this issue. Limits: narrows or defeats a website tracking claim on this issue. Context: bears on the issue without deciding it either way.
Supports: HIPAA
How HIPAA, its criminal provision at 42 U.S.C. § 1320d-6 and HHS guidance bear on tracking.
For HIPAA covered entities and business associates, the bulletin's core statement is that tracking may not produce impermissible disclosures of protected health information to vendors, and that marketing disclosures need HIPAA-compliant authorizations (Bulletin, introduction). It points to where HHS sees that risk: portals and telehealth platforms, booking and symptom-checker pages, and portal login and registration pages. The bulletin says it lacks the force of law, so its weight comes from the HIPAA rules it describes.
Limits: Health information
What counts as individually identifiable health information when it is sent through tracking tools.
The part of the bulletin that tied HIPAA obligations to an IP address combined with a visit to a public page about specific conditions or providers was declared unlawful and vacated in American Hospital Association v. Becerra (ECF No. 67 at 31). The court reasoned that a person's identity plus a query does not show that the person has the condition (ECF No. 67 at 25). A theory that rests only on HHS's view of public page visits cannot draw support from that vacated part of the bulletin.
Supports: Health information
What counts as individually identifiable health information when it is sent through tracking tools.
The rest of the bulletin still says tracking may collect protected health information on booking and symptom-checker pages, on portal login and registration pages, and on authenticated pages (Bulletin, sections on authenticated and unauthenticated webpages). The Becerra court called much of the revised bulletin legally and pragmatically sound and said its vacatur should not be read to limit the other guidance (ECF No. 67 at 7 n.3, 31 n.8).
Supports: Consent
Whether visitors agreed to the tracking through banners, privacy policies or terms.
The bulletin says cookie banners asking users to accept or reject tracking are not HIPAA authorizations, and that a privacy policy or terms announcing disclosures do not by themselves permit them (Bulletin, section on HIPAA compliance obligations). For HIPAA-regulated sites, that answers the argument that a banner click or a policy notice made sharing protected health information with a tracking vendor lawful under HIPAA. It says nothing about consent under wiretap or consumer-protection laws.
Context: HIPAA
How HIPAA, its criminal provision at 42 U.S.C. § 1320d-6 and HHS guidance bear on tracking.
The bulletin presumes that an impermissible disclosure to a tracking vendor without a business associate agreement is a breach of unsecured protected health information requiring notice, unless the entity shows a low probability of compromise. It also says vendor promises to remove or de-identify data after receipt are not enough (Bulletin, section on HIPAA compliance obligations). Those statements describe compliance duties under the HIPAA rules that OCR enforces.
Arguments it addresses
- AHA v. Becerra struck down HHS's tracking guidance
- The court vacated only the treatment of an IP address combined with a visit to a public page about specific conditions or providers, and said the vacatur should not be read to limit the rest of the bulletin.
- A page visit is not health information
- After Becerra the bulletin's treatment of an IP address combined with a visit to a public page about specific conditions or providers is vacated, but the bulletin still says booking and symptom-checker pages may collect protected health information such as an email address or the reason for seeking care.
- Visitors accepted the cookie banner
- The bulletin says banners that ask users to accept or reject tracking technologies do not constitute a valid HIPAA authorization.
- The privacy policy disclosed the tracking
- The bulletin says the Privacy Rule does not permit disclosures of protected health information to a tracking vendor based solely on a privacy policy, notice or terms of use.
- The vendor removes or de-identifies health data after receipt
- The bulletin says it is insufficient for a tracking vendor to agree to remove or de-identify protected health information before saving it.
- Guidance is not binding
- The bulletin agrees that it lacks the force and effect of law; its statements rest on the HIPAA rules it cites.
For a company that received a letter
- The bulletin speaks to HIPAA covered entities and business associates; for health apps outside HIPAA, it notes that the FTC Act and the FTC's Health Breach Notification Rule may apply.
- After Becerra, the vacated part concerns an IP address combined with a visit to a public page about specific conditions or providers; the bulletin's statements on portals, booking and symptom tools, login pages, banners and business associate agreements remain on HHS's page.
- The bulletin is guidance without the force of law, so it describes HHS's reading of the HIPAA rules rather than deciding any company's obligations.
What to check on your own site
- List every third-party tag on patient portal, telehealth, appointment booking, symptom-checker, login and registration pages, and check what each one sends.
- Check whether any tracking vendor that receives data from those pages has signed a business associate agreement.
- Check what reaches vendors when a visitor types or selects a reason for care on a booking form or symptom tool.
Later history
On June 20, 2024, American Hospital Association v. Becerra declared unlawful and vacated the part of the bulletin covering an IP address combined with a visit to an unauthenticated public page about specific health conditions or providers. HHS's page, as archived on October 28, 2026, still notes that order at its top. HHS appealed on August 19, 2024, and the Fifth Circuit dismissed the appeal on HHS's motion on September 4, 2024 (No. 24-10775).
Related rulings
Published by Privacy Resolve from public records. It does not cover our own matters.
General information only, not legal advice, and not a substitute for the advice of an attorney. Laws, deadlines, defenses and outcomes vary by jurisdiction and facts.