Tracking technology and patient privacy on your practice website
Analytics tags, ad pixels and session recording tools can send what patients do on your site to companies that will not sign a business associate agreement. A 2024 court decision struck down one part of HHS's guidance, about public pages, but left the rest standing, and FTC and state rules reach health data HIPAA does not. Keep advertising tags off pages where patients log in, book or describe symptoms.
What these tools actually send
A tracking tool is a piece of code from another company that runs on your pages and reports back to it. Common examples on practice sites are Google Analytics, the Meta pixel and other ad platform tags, tag managers that load them, session recording and heatmap tools, and some chat and booking widgets.
Depending on how they are set up, these tools can receive the address of the page, its title, the buttons a visitor clicks, the visitor's IP address and device identifiers, and sometimes text typed into forms. On a practice site, that says a lot. Picture a hypothetical urology practice whose booking confirmation page is titled "Your vasectomy consultation is booked" and fires an ad conversion event. The ad platform now holds a page title that names a procedure, tied to a device it can recognize.
Nobody at the practice decided to share that. It happened because a tag installed for the homepage was set to load on every page.
What HHS said, and what the court changed
HHS's Office for Civil Rights issued a bulletin on online tracking technologies in December 2022 and revised it on March 18, 2024. Hospital groups challenged one piece of it: the position that HIPAA obligations are triggered when a tracking technology connects a person's IP address with their visit to an unauthenticated public web page about specific health conditions or health care providers. The court called this the Proscribed Combination.
On June 20, 2024, the federal district court in Fort Worth, Texas, declared that piece unlawful and vacated it. The court said the vacatur was not meant to limit the rest of the guidance, and it described much of the revised bulletin as legally and pragmatically sound.
So the ruling narrowed the guidance for public pages that only discuss a condition. It did not bless tracking on pages where patients log in, book, pay or type information about themselves. Google's own help page says HIPAA regulated entities should not set Google Analytics tags on authenticated pages, and that unauthenticated pages related to providing health care services are more likely to be HIPAA covered too. Retargeting ads built from these tags carry the same risk.
Does ChatGPT recommend your practice?
The Surge Score measures five things about your practice website: how often ChatGPT, Gemini and Perplexity recommend you, your PageSpeed, your structured data, your indexing and your reviews, each with its evidence and date. Free.
HIPAA is not the only rule
On July 20, 2023, the FTC and HHS's Office for Civil Rights jointly warned approximately 130 hospital systems and telehealth providers about tracking technologies such as the Meta pixel and Google Analytics. The FTC's point was that organizations not covered by HIPAA still have to protect health information, under the FTC Act and, for some, the Health Breach Notification Rule. That rule does not apply to HIPAA covered entities such as doctors' offices, but it does reach health apps and similar services, and it treats sharing data without the person's authorization as a breach, not only hacking. The FTC's first action under it, against GoodRx in 2023, involved sharing users' prescription and health information with advertising companies.
States are adding their own rules. Washington's My Health My Data Act covers consumer health data outside HIPAA. It requires consent to collect that data unless the collection is necessary to provide a service the person asked for, requires a separate consent to share it, and bans geofences around places that provide in person health care when they are used to track visitors, collect their health data or send them ads. Its exemption is written around information that meets HIPAA's definition of protected health information, so browsing data that HIPAA may not reach can still fall under Washington law for Washington consumers. Ask your attorney which state laws apply where your patients live.
A tag audit you can run with your developer
You need someone who can read the code, but you should be in the room, because you know which pages are sensitive. Set aside thirty minutes.
- Ask for an export of everything in your tag manager and a list of any scripts written directly into the site template.
- Open four pages together: the booking confirmation page, the contact form thank you page, the portal login page and one condition page.
- On each page, have your developer show you every outside company the page sends data to, and what it sends: page address, title, events and any form values.
- Look at the event names and audiences in your ad accounts. Names like "IVF page visitors" or "booked consult" tell you what the platform knows.
- If you use session recording, confirm that every form field is masked.
Write down what you find, page by page. That record is what your attorney will want to see. For the short version of this problem, see tracking pixels on pages where patients enter health information.
Safer ways to measure your marketing
You do not have to stop measuring. You have to stop sending health details to companies that will not protect them.
- Remove ad pixels from booking, form, payment and portal pages, and from condition or procedure pages that collect information
- Count conversions with neutral names, such as "appointment request", on a generic thank you page that does not name a visit type
- Strip visit types, symptoms and patient details out of page titles and web addresses
- Use analytics and call tracking vendors that will sign a business associate agreement for the parts of the site that need it
- Keep any ad platform tags to general pages, and only after legal review
A cookie banner does not solve this. A HIPAA authorization must contain specific elements, including a description of the information, who will receive it, the purpose, an expiration and the patient's signature and date. A click on Accept supplies none of that. For a measurement setup built around these limits, see HIPAA safe analytics.
What to bring to your healthcare attorney
This guide is general information, not legal advice. Tracking law is unsettled, and the answer for your practice depends on your pages, your vendors and the states your patients live in.
Take your page by page tag record and ask four questions. Which of our pages should we treat as handling protected health information? Do any state laws require consent from our visitors before these tools load? Does anything our tags sent in the past need a closer look? Which vendors need an agreement, a configuration change or replacing?
Then make the changes in order of risk, starting with pages behind the login and pages where patients type, and put a rule in writing that no new tag goes on the site without someone checking which pages it loads on.
Checklist
- You have a written list of every tracking tag and script on the site, page by page
- No ad pixels load on booking, form, payment or portal pages
- Page titles and web addresses do not name a patient's condition or visit type
- Conversion events use neutral names that reveal nothing about health
- Session recording, if used, masks every form field
- Analytics on sensitive pages runs only through vendors that sign a business associate agreement
- Your attorney has reviewed which state privacy laws apply to your visitors
Frequently asked
Did the 2024 court ruling make tracking pixels legal on medical websites?
No. The court vacated only HHS's position on connecting an IP address with a visit to a public page about a condition or provider. The rest of the guidance stands, pages where patients log in or enter information remain sensitive, and FTC and state rules still apply.
Can we still use Google Analytics?
Google says it does not offer a business associate agreement for Google Analytics and that HIPAA regulated entities must not send it protected health information. Keep it off authenticated and sensitive pages, configure it so page titles and events reveal nothing about health, and review the setup with your attorney.
Is a cookie consent banner enough?
Not for HIPAA. An authorization requires specific elements, such as the purpose, the recipient, an expiration and a signature, that a banner click does not provide. A banner can help with state privacy choices, such as opt outs, but only if it actually stops the tags from loading.
Does this apply to our retargeting ads?
Retargeting depends on the same pixels, so the same limits apply. Audiences built from visits to condition or booking pages can reveal health information to the ad platform. Get legal review before running retargeting from a medical website.
Sources
- American Hospital Association v. Becerra, No. 4:23-cv-01110-P, Opinion and Order (N.D. Tex. June 20, 2024), U.S. District Court for the Northern District of Texas, copy published by the American Hospital Association
- HIPAA and Google Analytics, Google Analytics Help
- FTC and HHS Warn Hospital Systems and Telehealth Providers about Privacy and Security Risks from Online Tracking Technologies (July 20, 2023), Federal Trade Commission
- FTC Enforcement Action to Bar GoodRx from Sharing Consumers' Sensitive Health Info for Advertising (February 1, 2023), Federal Trade Commission
- Complying with FTC's Health Breach Notification Rule, Federal Trade Commission
- RCW 19.373, Washington My Health My Data Act, Washington State Legislature
- 45 CFR 164.508, Uses and disclosures for which an authorization is required, Electronic Code of Federal Regulations
Book a strategy call with the team.
Twenty minutes. We'll walk through the specific opportunities in your market and what a MedPracticeGrowth engagement would look like for your practice.