HIPAA on your website: what applies and what does not
HIPAA does not cover your website as a whole. It protects patient health information, so it applies wherever your site collects, stores or sends identifiable information about someone's health, care or payment, such as forms, booking, chat and the portal, and to every vendor that handles that information for you.
HIPAA follows the information, not the web page
HIPAA applies to covered entities: health plans, health care clearinghouses, and health care providers who transmit health information electronically in connection with a standard transaction, such as submitting a claim or checking a patient's eligibility with a plan. A practice that submits claims to insurers electronically is a covered entity.
What HIPAA protects is protected health information: information that relates to a person's past, present or future health, the care they receive, or payment for that care, and that identifies them or could reasonably be used to identify them. A page explaining what a rotator cuff tear is contains none. A form where a visitor types their name, phone number and "shoulder pain for three months" does.
So the useful question is not whether your website is HIPAA compliant. It is which parts of your website create, receive, store or send patient information, and who else touches it along the way.
A note for cash pay practices: if you never conduct those standard electronic transactions, you may fall outside the covered entity definition. That is a fact specific question for your attorney, and it does not take you outside every other law. Washington's My Health My Data Act, for example, was written for health data that falls outside HIPAA.
Map where patient information enters your site
This is the most valuable fifteen minutes you can spend on website compliance. Open your site on your phone and list every place a patient can type, upload or say something:
- Contact and appointment request forms
- Online booking widgets, including ones embedded from your EHR or a scheduling vendor
- New patient intake forms and insurance card uploads
- Chat widgets and AI assistants
- The patient portal login and everything behind it
- Payment pages
- Newsletter or event signups placed on condition pages
For each one, write down what it collects, which company receives it, where it is stored, and who gets the notification. A common weak point is a form that emails every submission, symptoms included, to a shared inbox or a staff member's personal account. Another is a booking confirmation page that runs the same analytics and ad tags as the rest of the site. Tracking is its own topic, covered in tracking technology and patient privacy.
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.
Vendors that touch patient information need a business associate agreement
Under HIPAA, a business associate is a person or company that creates, receives, maintains or transmits protected health information on your behalf. Before you let a vendor do that, the Privacy Rule requires satisfactory assurance that it will safeguard the information, which in practice means a signed business associate agreement.
On a website, that usually includes your form builder, booking tool, chat or AI assistant, any host that stores form submissions, the email service that delivers them, and call tracking that records calls. A host serving brochure pages that never receive patient information is a different case, which is why the map in the previous step matters.
Ask each vendor one question in writing: will you sign a business associate agreement for this service? If the answer is no, do not send patient information through it. Google, for example, states that it does not offer business associate agreements for Google Analytics and that HIPAA regulated entities must not expose protected health information to it. For chat tools specifically, see HIPAA and AI chat widgets.
The Security Rule covers what your site collects electronically
The HIPAA Security Rule applies to electronic protected health information, which is exactly what a web form or booking tool produces. Among its technical safeguards is transmission security: measures that guard against unauthorized access to that information while it travels over a network.
You do not need to be technical to ask the right questions:
- Does every page, and especially every form, load over HTTPS?
- Are submissions stored inside a system covered by a business associate agreement, or passed around by ordinary email?
- Who has logins to the website, the form tool and the booking tool, and have former staff and old agencies been removed?
- How long are submissions kept, and who deletes them?
- Is the website, with its vendors, part of your practice's security risk analysis?
The answers usually point to one or two easy fixes, such as turning off email delivery of full form contents and having staff read submissions inside the secure tool instead.
What your website must do, and what it must not
One requirement is specific to websites. A covered entity that maintains a website with information about its services must prominently post its Notice of Privacy Practices on that site and make it available electronically. A clearly labeled footer link on every page is the usual way to meet it. It is a different document from your website privacy policy, as privacy policies and cookie banners explains.
The most common thing a practice website must not do is publish something that identifies a person as your patient without their written authorization. That covers testimonials, patient stories, photos and videos. HIPAA lists full face photographs among the identifiers, and using patient information for marketing generally requires an authorization with specific required elements. The details are in testimonials and before and after photos. The same caution applies to replies to online reviews, where confirming that someone was seen at your practice is itself a disclosure.
What HIPAA does not cover, and when to call your attorney
HIPAA is not the law for every website question. Accessibility comes from the ADA and Section 504. Advertising claims and testimonials also fall under FTC rules and your state medical board. Job applications are a separate matter, since the definition of protected health information excludes employment records a covered entity holds in its role as an employer. State privacy laws can reach health data that HIPAA does not.
This guide is general information, not legal advice, and it cannot account for your state, your payers or your vendor contracts. Bring your map of forms, tools and vendors to your healthcare attorney and ask three things: which of these handle protected health information, which vendors need a business associate agreement we do not have yet, and what we should change first.
Checklist
- Every form, booking tool, chat widget and upload on the site is listed with the vendor that receives it
- Each vendor that receives patient information has a signed business associate agreement
- No patient information reaches analytics or ad platforms that will not sign one
- Form submissions are read inside the secure tool, not forwarded in full to ordinary inboxes
- Your Notice of Privacy Practices is linked prominently, ideally from the footer of every page
- A written authorization is on file for every patient story, photo or video you publish
- The website and its vendors are part of your annual security risk analysis
Frequently asked
Is a contact form on my website a HIPAA problem?
Not by itself. Once patients can type details about their health into it, the submissions are protected health information, and the vendor that receives and stores them needs a business associate agreement. One option is to keep the general contact form short, without a free text symptoms box, and collect clinical details through secure intake instead.
Do I need a business associate agreement with my web host?
Only if the host creates, receives, maintains or transmits protected health information for you, for example by storing form submissions or running your intake forms. A host serving pages that never receive patient information is a different situation. Map your forms first, then ask your attorney.
We are a cash pay practice. Does HIPAA apply to our website?
Possibly not, if you never conduct the standard electronic transactions that make a provider a covered entity, such as electronic claims or eligibility checks. That is a fact specific question for your attorney, and state privacy laws and FTC rules can still apply to the health data your site collects.
Do we have to post our Notice of Privacy Practices on the website?
If you are a covered entity and your website gives information about your services, yes. The Privacy Rule requires you to post the notice prominently on the site and make it available electronically. A clearly labeled footer link on every page is the usual approach.
Sources
- 45 CFR 160.103, Definitions (covered entity, business associate, protected health information, transaction), Electronic Code of Federal Regulations
- 45 CFR 164.302, Security Rule applicability, Electronic Code of Federal Regulations
- 45 CFR 164.312, Technical safeguards (transmission security), Electronic Code of Federal Regulations
- 45 CFR 164.502(e), Disclosures to business associates, Electronic Code of Federal Regulations
- 45 CFR 164.508, Uses and disclosures for which an authorization is required, Electronic Code of Federal Regulations
- 45 CFR 164.514, De-identification standard and list of identifiers, Electronic Code of Federal Regulations
- 45 CFR 164.520, Notice of privacy practices for protected health information, Electronic Code of Federal Regulations
- HIPAA and Google Analytics, Google Analytics Help
- Protecting Washingtonians' Personal Health Data and Privacy (My Health My Data Act), Washington State 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.