HIPAA compliant website checklist for small clinics
By Umair, founder of DragonPro. Updated . 5 min read.
The short answer
Check every form, tool and agreement on your site. Ordinary contact forms should ask no health questions, anything that collects health details should run on a service that signs a business associate agreement, and no analytics, pixel or log should receive what patients type. The checklist below covers each point.
This HIPAA compliant website checklist is for practice owners and managers at small clinics, whoever built the site. Work through it with the site open in another tab and tick each item as you check it. If you want to see how we set these things up on the sites we build, read how we set up HIPAA compliant websites.
This checklist is not legal advice. Review it with your compliance adviser. Where a point depends on what HIPAA requires, it links to the HHS page that explains it.
Forms
Most health details reach a clinic website through a form, so start there.
- List every form on the site. Contact, appointment, newsletter and consultation forms, any pop-up, and the forms inside booking or chat tools.
- Mark the ones that ask about health. Symptoms, conditions, medications, reason for visit and history all count, and so does a free-text box where people tend to describe them.
- Take health questions out of ordinary forms. Ask for a name, a way to reach the person and a good time, and add a line under any free-text box: “Please don't include patient or health details.”
- Move health questions to a covered service. Use an intake form on a service that signs a business associate agreement with your clinic.
- Send a test submission from each form. Then check exactly where it arrives and what it contains.
Where the answers go
A form can be set up well and still copy what patients type into places nobody checks.
- Read the notification email. If it copies the patient's answers into an ordinary inbox, change it to a short “you have a new submission” alert.
- Check the website's own database or admin area. It should hold enquiries only: names, contact details and messages, and no health details.
- Check spam filters and backups. A copy of a form submission is still a copy.
- Check exports and integrations. CRMs, spreadsheets and automation tools that receive form data all count as places the answers go.
Business associate agreements
HIPAA requires a written agreement with each outside company that handles health information for your practice. HHS explains who counts in its business associates FAQs.
- List every company that receives health details for you. The form service, the patient portal, the booking tool if it asks for a reason for visit, and email if your team sends health information.
- Have a signed BAA with each one. Check that it covers the plan you are actually on, because some services offer HIPAA features only on higher plans.
- Keep copies where you can find them, with the date each was signed.
- Repeat the check when you add a tool. A new form or widget can add a new company to the list.
For examples of which plans include HIPAA features and what they cost, see our medical website cost guide.
Analytics, pixels and widgets
Scripts added for marketing can see more than they need to, especially on pages with forms.
- List every tag and script on the site. Analytics, advertising pixels, heatmaps, session recording and chat widgets.
- Keep tags off pages behind a patient login. Portal and account pages should load no analytics or advertising scripts.
- Make sure no tag reads form fields. Analytics should count that a form was sent, not record what was typed.
- Check chat widgets. If a chat asks visitors what is wrong, it is collecting health details, and the vendor needs a BAA.
- Review the HHS guidance with your compliance adviser. Part of it was set aside by a federal court in June 2024, and the page explains which part.
HHS guidance: use of online tracking technologies.
Logins, updates and backups
These are the basics that keep anyone else from reaching the site or the data behind it.
- Serve every page over HTTPS. Including the forms and any page they redirect to.
- Turn on two-step login for the website, domain, hosting and form service accounts.
- Remove access for people who have left, and for agencies or freelancers you no longer work with.
- Keep the site's software and plugins updated, or know exactly who does it and how often.
- Know where backups are kept and who can open them.
Your practice’s side
The website is one part of HIPAA. HHS explains which organizations the rules apply to on its covered entities page, and the rest of the work sits with the practice.
- Include the website in your risk assessment. HHS lists a free Security Risk Assessment Tool for small and medium practices.
- Decide who reads enquiries and how long you keep them. Write it down so the answer does not depend on one person.
- Train staff not to ask for health details by email or in website chat. Point patients to the intake form or portal instead.
- Have a plan for what to do if a form sends something it should not. Who checks, who decides and who tells the patient.
HHS guidance: guidance on risk analysis.
HIPAA compliant website checklist questions
Does HIPAA apply to my clinic's website?
HIPAA applies to covered entities and their business associates, and HHS explains who those are. If your practice is one, the parts of your website that collect, store or send patients' health information are part of what you protect. A page with no forms and no patient data carries much less risk.
Is a contact form a HIPAA risk?
A form that asks only for a name, contact details and a good time keeps health information out. The risk comes from fields that ask about symptoms or conditions, and from free-text boxes where people describe them, which is why every box should carry a note asking people to leave health details out.
How often should I go through this checklist?
Whenever you add a form, a tool or a tracking tag, and once a year as part of your risk assessment. The list stays short if you check each change as it happens.
Can a web developer make my practice HIPAA compliant?
No. A developer can set up the website so it does not add risk and tell you which agreements to sign. The policies, training, risk assessment and agreements belong to your practice.
Written by Umair, founder of DragonPro. The DragonPro team builds websites for clinics in the United States.