Privacy policies and cookie banners for practice websites
Most practice websites need two documents, not one: the HIPAA Notice of Privacy Practices, which a covered entity must post prominently on its site, and a website privacy policy that describes what the site itself collects. A cookie banner can help with some state privacy laws, but a click on Accept is not a HIPAA authorization and does not make a pixel on a booking page acceptable.
Two documents with two different jobs
The Notice of Privacy Practices is a HIPAA document. It explains how your practice uses and discloses protected health information and what rights patients have. If you are a covered entity and your website gives information about your services, the Privacy Rule requires you to post the notice prominently on the site and make it available electronically. It is the same notice you give patients at the first visit.
The website privacy policy describes the website: what it collects from visitors, through forms, chat, booking tools, cookies and analytics, which outside companies receive that information, and how a visitor can contact you about it.
The common mistakes are mirror images of each other. Some sites paste the Notice of Privacy Practices in as the privacy policy, which says nothing about cookies, analytics or the chat vendor. Others use a template policy written for an online store, which says nothing about health information and may promise things the site does not do. Neither is enough on its own.
What your website privacy policy should say
A good policy is specific and true. Draft it from a list of what the site really does, not from a template.
- What the site collects: form fields, chat transcripts, booking details, uploads, and technical data such as IP address and device information
- Which outside services receive it: analytics, the booking or chat vendor, embedded maps and videos, email delivery, and any advertising platforms
- Whether you use cookies or pixels for advertising or retargeting, and how a visitor can opt out
- How long you keep what the site collects, and how to ask for it to be deleted where the law gives that right
- How to contact the practice about privacy, with a real email address or phone number
- An effective date, and a link to your Notice of Privacy Practices for anything that becomes part of the medical record
Then run the self check that matters most: compare the list of third parties in the policy with the tag audit from tracking technology and patient privacy. If the policy says you never share data and the site runs ad pixels, fix the site or fix the policy, ideally the site.
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.
State laws that can apply to a practice website
State privacy laws differ, and your attorney should tell you which ones reach your practice based on where you operate and where your patients live. Two examples show the range.
Washington's My Health My Data Act applies to consumer health data that falls outside HIPAA, including health information inferred from purchases or other data that is not about health on its face. Regulated entities and small businesses must maintain a separate consumer health data privacy policy and prominently link it on their homepage, a term the law defines to include any web page where personal information is collected. Collection generally requires consent unless it is necessary to provide a service the person asked for, and sharing requires a separate consent. The law covers Washington residents and people whose health data is collected in Washington.
California's Consumer Privacy Act applies to for profit businesses doing business in California that meet any of three thresholds, which the state Attorney General lists as annual gross revenue over $25 million, buying, selling or sharing the personal information of 100,000 or more California residents or households, or earning half or more of revenue from selling personal information. It exempts certain medical information. Most small practices will not meet those thresholds, but large groups and practices owned by bigger organizations should ask.
When a cookie banner helps, and when it does not
Cookie banners exist because some privacy laws give visitors choices, such as opting out of the sale or sharing of their personal information. California's Attorney General, for example, describes the Global Privacy Control browser signal as one way consumers can submit those opt out requests. If a state law that applies to you requires choices like these, a well built consent tool can record and honor them.
A banner cannot do two things. First, it cannot stand in for a HIPAA authorization. A valid authorization must describe the information specifically, name who will disclose and receive it, state the purpose, give an expiration and carry the patient's signature and date. Accept all cookies does none of that, so a banner cannot make it acceptable to send booking or portal activity to an ad platform.
Second, a banner only works if it controls the tags. Test it: choose Reject, then have your developer confirm that the analytics and ad tags really did not load. A banner that records a choice while the pixels fire anyway is worse than no banner, because it promises something the site does not deliver.
Where to link them, and how to keep them true
Put two clearly labeled links in the footer of every page: Notice of Privacy Practices and Website Privacy Policy. Link both again near your forms and in the booking flow, where a patient is deciding whether to share information. If the Washington law applies to you, add its separate consumer health data policy link as that law requires.
Publish both as ordinary web pages rather than scanned PDFs, so patients using screen readers can read them, as ADA website lawsuits and accessibility rules explains. Keep the online notice identical to the version in your office.
A privacy policy goes stale the day someone adds a new tool. Give one person ownership, and make updating the policy part of adding any form, chat, booking or tracking tool. A footer that still shows an old year is often the first sign nobody owns it, as a footer that still says 2019 points out.
This guide is general information, not legal advice. Have your healthcare attorney review both documents, and the banner setup, before you publish them.
Checklist
- Your Notice of Privacy Practices is posted as a web page and linked from every footer
- A separate website privacy policy describes forms, chat, cookies, analytics and every third party
- The third parties named in the policy match what your tag audit actually found
- Both documents are linked near forms and in the booking flow
- If a consent banner is used, choosing Reject actually stops the tags from loading
- Your attorney has confirmed which state privacy laws apply to your practice
- One named person updates the policy whenever a new tool is added
Frequently asked
Can we use our Notice of Privacy Practices as our website privacy policy?
Not by itself. The notice explains how you use and disclose protected health information in your practice. It does not describe the cookies, analytics, chat and booking vendors on your website. Post both, label them clearly, and link each from the footer.
Does a small practice need a cookie banner?
It depends on which state privacy laws apply to you and what your site does with visitor data. If you run advertising tags or share visitor data, ask your attorney whether any state law requires opt out choices. A banner never replaces a HIPAA authorization.
Do we need to honor the Global Privacy Control signal?
If your practice is subject to California's privacy law, the Attorney General describes the Global Privacy Control as one way consumers can submit opt out requests. Whether that or a similar rule applies to you depends on thresholds and state law, so confirm with your attorney.
Who should write our privacy policy?
Your team should supply the facts, meaning every tool and vendor the site uses, and your healthcare attorney should review the language. A generic template or a policy written by your agency without that list is likely to be wrong about what your site really collects and shares.
Sources
- 45 CFR 164.520, Notice of privacy practices for protected health information, Electronic Code of Federal Regulations
- 45 CFR 164.508, Uses and disclosures for which an authorization is required, Electronic Code of Federal Regulations
- RCW 19.373, Washington My Health My Data Act, Washington State Legislature
- Protecting Washingtonians' Personal Health Data and Privacy, Washington State Office of the Attorney General
- California Consumer Privacy Act (CCPA), State of California, Department of Justice, Office of the Attorney General
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.