s90

HIPAA tracking technology on patient portals: where do the rules stand now?

A 2024 court ruling narrowed OCR's tracking technology guidance for public pages, but patient portals, logged-in pages and apps remain covered. Here is where the HIPAA and FTC rules stand and what to review this quarter.

A compliance professional reviews a complete audit binder and checklist at a desk, with translucent panels showing a shield, a padlock and a check mark representing verified data privacy compliance for a patient portal.

Key takeaways

  • OCR says tracking technology on patient portals and other logged-in pages generally has access to PHI.
  • Disclosing PHI to a tracking vendor needs a Privacy Rule permission and a BAA when the vendor is a business associate.
  • On June 20, 2024, a federal court vacated only OCR's position on unauthenticated public pages; the rest of the guidance stands.
  • OCR says cookie consent banners are not a valid HIPAA authorization.
  • The FTC enforces against health apps and sites outside HIPAA, including a 2026 lawsuit against Hims & Hers over tracking-based sharing.

Tracking pixels and analytics tags are a form of tracking technology: small pieces of code that report what visitors do on a website or app to a third party, usually an advertising or analytics platform. On a public marketing page that is ordinary. On a patient portal, a telehealth login or a page where someone books an appointment, the same tracking technology can send protected health information (PHI) to a company that has no right to receive it. The federal rules shifted in 2024 and enforcement has moved in 2026, so it is worth knowing exactly where the lines sit now.

What does HIPAA say about tracking technology on patient portals?

HHS treats tracking technology on a patient portal or other logged-in page as having access to PHI, so the HIPAA Privacy Rule applies to whatever that code collects and sends. The HHS Office for Civil Rights (OCR) says in its guidance on online tracking technologies that tracking on user-authenticated pages "generally" has access to PHI, and that regulated entities must configure those pages so the technology only uses and discloses PHI as the Privacy Rule allows.

In practice, that means a disclosure to a tracking vendor needs two things before it happens: a Privacy Rule permission for the disclosure, and a business associate agreement if the vendor meets the definition of a business associate under 45 CFR 160.103. The business associate agreement requirements in 45 CFR 164.502(e) and 164.504(e) apply to tracking vendors the same way they apply to any other vendor. OCR also notes that a vendor can be a business associate whether or not anyone signed a BAA, and that a vendor's promise to de-identify the data after receiving it does not remove the need for a BAA and a permission.

The same reasoning covers mobile apps. OCR says information collected through an app that a covered entity or business associate offers is generally PHI.

This matters beyond hospitals. Law firms, accounting firms and nonprofits with health programs can be HIPAA business associates, and any portal they run that handles a covered entity's PHI falls under the same rules.

What did the court in AHA v. Becerra change?

A federal court vacated one part of OCR's guidance: the position that an IP address combined with a visit to an unauthenticated public webpage about a health condition or provider is PHI. On June 20, 2024, the U.S. District Court for the Northern District of Texas ruled in American Hospital Association v. Becerra that this part of the guidance, which the court called the "Proscribed Combination," exceeded HHS's authority.

The rest of the guidance was left in place. As of November 2026, the OCR guidance page carries a notice of the order and says HHS is evaluating its next steps. The ruling did not touch OCR's positions on patient portals, telehealth logins or apps offered by regulated entities.

Which pages are still risky after the ruling?

Logged-in pages remain the clearest risk, and some public pages remain risky too. OCR's guidance says unauthenticated pages are generally outside HIPAA, with exceptions where the page collects information such as:

  • Appointment requests or scheduling details.
  • Symptom checker entries.
  • Patient portal login and registration details.

A useful way to sort a site is by what the visitor types or does on the page. A public page that describes services is in a different position from a public page with a form asking for a date of birth, an insurance plan or a reason for the visit. The court's ruling dealt with browsing public pages, and it did not create a safe harbor for forms that collect patient information.

Can a consent banner or privacy policy fix the problem?

No, OCR's guidance says website banners asking users to accept or reject tracking technologies do not count as a valid HIPAA authorization. It also says a disclosure to a tracking vendor is not permitted based solely on describing the practice in a privacy policy or notice.

A HIPAA authorization under the Privacy Rule has specific required elements, and a cookie banner does not meet them. If a firm's plan for portal analytics depends on a banner, that plan does not address the HIPAA question.

What happens if a pixel already sent PHI to a vendor?

OCR's guidance says that when PHI is disclosed to a tracking vendor without a permission and a BAA, there is a presumption of a breach of unsecured PHI. Under the breach definition in 45 CFR 164.402, the entity can rebut that presumption only by showing a low probability that the PHI was compromised, using the four-factor risk assessment. If it cannot, notice goes to affected individuals, to HHS and, where the breach is large enough, to the media.

OCR also says it is prioritizing Security Rule compliance in its investigations of online tracking technologies, and that entities should address tracking in their risk analysis and risk management under 45 CFR 164.308(a)(1). OCR's enforcement record on risk analysis is a useful guide to where investigations tend to focus; we covered that in why OCR keeps enforcing risk analysis. The four-factor process works the same way it does in our piece on a breach risk assessment after PHI goes into an AI tool.

Where does the FTC fit in when HIPAA does not apply?

Health apps and websites outside HIPAA still face the Federal Trade Commission. The FTC's amended Health Breach Notification Rule, 16 CFR Part 318 (89 FR 47028, effective July 29, 2024), clarifies that a breach of security includes an unauthorized disclosure, so sharing health data with third parties in ways a company did not authorize can trigger notice obligations. The rule covers vendors of personal health records and related entities. It does not apply to HIPAA covered entities and business associates, which follow HHS's breach notification rule instead.

The FTC also uses its general authority over deceptive practices. On July 29, 2026, the FTC, joined by Utah and by California through Los Angeles County Counsel, sued Hims & Hers in the Northern District of California. The complaint alleges the company shared consumers' health information with advertising platforms, including through third-party tracking technologies, despite privacy promises. On November 10, 2026, five more states joined an amended complaint. These are allegations, and the court will decide the case.

For a California organization, the takeaway is that tracking on health-related pages draws attention from federal, state and local enforcers under several laws at once, depending on whether HIPAA applies.

What should a firm review about portal tracking this quarter?

A quarterly review of portal tracking inventories every tag, maps where each one fires, confirms a BAA and a Privacy Rule permission for any vendor receiving data from a flagged page, and adds tracking to the Security Rule risk analysis. Where the answer depends on your own vendors, contracts or facts, the counsel review list that follows names the decisions and the documents to bring.

  • Inventory every tag, pixel, SDK and session-replay script on the website, patient or client portal, scheduling pages and mobile app, including ones added by marketing tools or website plugins.
  • Map each one to the pages where it fires, and flag any that run on logged-in pages or on public pages with forms that collect health or appointment information.
  • For each vendor receiving data from a flagged page, confirm whether there is a BAA and a Privacy Rule permission for the disclosure. Remove or reconfigure the tag where there is not.
  • Add tracking technologies to the Security Rule risk analysis and record the decisions made.
  • If PHI has already gone to a vendor without a BAA, document a breach risk assessment under 45 CFR 164.402 and add the notification decision to the counsel review list below.
  • Set a review step so new marketing or analytics tags cannot go onto portal pages without sign-off from whoever owns HIPAA compliance.

What should your counsel review about portal tracking?

A counsel review of portal tracking typically covers four decisions: business associate status for each vendor, the Privacy Rule permission for each disclosure, whether any past disclosure is a reportable breach, and whether the FTC rule applies outside HIPAA. Schedule this review as soon as the tag inventory is complete, and again before any new analytics or marketing tool goes onto a logged-in page or a page with a patient form.

  • Whether each tracking vendor is a business associate under the definition in 45 CFR 160.103. Bring the tag inventory, the vendor's terms of service and any BAA the vendor offers.
  • Which Privacy Rule permission, if any, covers each disclosure from a flagged page, under 45 CFR 164.502. Bring the page map and a list of the data fields each tag sends.
  • Whether a past disclosure to a vendor without a BAA is a reportable breach, using the four-factor assessment in 45 CFR 164.402. Bring the dates the tag ran, the data fields it sent and any deletion confirmation from the vendor.
  • For an app or site outside HIPAA, whether the FTC Health Breach Notification Rule (16 CFR Part 318) applies. Bring a description of the app or site, who offers it and what health data it collects.

How s90 helps

If you run a client or patient portal, the hard part is often not knowing what it sends, to whom, or whether it would hold up if OCR or a client asked. s90's HIPAA compliance service inventories the scripts and third-party connections on client portals and websites, documents them in the HIPAA risk analysis and tracks remediation in the evidence package regulators and clients ask for. Our agreements include 72-hour breach notification and 24-hour evidence production commitments. If you would like a second look at what your portal is sending, we are happy to talk it through.

Low-rise office buildings with tile roofs among oaks and palms in the south Orange County foothills, with Saddleback Mountain in the morning haze beyond.

New articles for your industry

Get new insights for your industry by email.