Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Security · Info

Is WordPress HIPAA Compliant? What Healthcare Websites Need to Know

Is WordPress HIPAA Compliant? What Healthcare Websites Need to Know

Short answer

WordPress software on its own is neither HIPAA compliant nor non-compliant, because HIPAA applies to organisations and how they handle protected health information, not to a CMS. A WordPress site can be part of a HIPAA-compliant setup if patient data is collected, stored and sent only through services that sign a Business Associate Agreement and meet HIPAA security requirements.

Key takeaways

  • HIPAA applies to covered entities and their business associates, not to software by itself.
  • A website only falls under HIPAA when it collects or stores protected health information.
  • Any vendor handling that data, such as a host or form service, needs a signed BAA.
  • Many healthcare sites keep patient data out of WordPress entirely and use compliant tools instead.
  • This is general information, not legal advice; check your setup with a compliance professional.

What is HIPAA?

HIPAA is a US law that sets rules for protecting health information held by healthcare providers, health plans, clearing houses and the businesses that work for them.

The US Department of Health and Human Services explains the rules in its HIPAA for professionals section, including the Privacy Rule and the Security Rule.

HIPAA focuses on protected health information, or PHI, which is health information that can be linked to a specific person, such as a patient's name together with their condition or appointment details.

This article gives general information only. It is not legal advice, so confirm your own situation with a qualified compliance or legal professional.

Can software like WordPress be HIPAA compliant?

No software is HIPAA compliant on its own, because compliance depends on how an organisation uses tools, controls access, signs agreements and protects data, not just on the tool's features.

WordPress can be part of a compliant setup, or part of a setup that breaks the rules, depending on what data it handles and how.

This is why claims that a theme or plugin is HIPAA compliant should be read carefully. At best, a product can support compliance when used correctly.

When does HIPAA apply to a website?

HIPAA matters for a website when a covered entity or business associate uses the site to collect, store, send or display protected health information, such as appointment requests with symptoms or patient portal data.

A simple clinic brochure site with opening hours, services and a phone number usually does not handle PHI. Adding a form that asks about symptoms or medical history changes that.

Online tracking can also matter. HHS has issued guidance on online tracking technologies for regulated entities, which affects analytics and advertising tools on health websites.

That guidance has been the subject of legal challenges, so check the current status with your compliance adviser.

What is a Business Associate Agreement?

A Business Associate Agreement, or BAA, is a contract in which a vendor that handles PHI for a covered entity agrees to protect it according to HIPAA rules.

HHS publishes sample BAA provisions that show what these agreements usually cover.

For a WordPress site that handles PHI, every service that touches the data may need a BAA. That can include the web host, backup service, form or email provider, and any third-party integration.

If a vendor will not sign a BAA, it should not receive PHI from your site, however convenient its features are.

What are the risks of using WordPress for patient data?

The main risks are PHI landing in ordinary form entries or emails, unpatched plugins, weak admin access, backups stored with services lacking a BAA, and tracking scripts sending data to third parties.

Standard contact form plugins often save entries in the WordPress database and send them by plain email. Both can expose PHI if the host and email provider are not covered by a BAA.

WordPress sites are frequent targets for automated attacks, mostly through outdated plugins and weak passwords. Our overview of the most common WordPress vulnerabilities explains the typical weak points.

How do healthcare sites use WordPress safely?

Many healthcare organisations use WordPress only for public information and send anything involving PHI to dedicated, BAA-covered systems such as patient portals, scheduling tools or secure form services.

This split keeps the website simple. WordPress handles content, while specialised tools built for healthcare handle sensitive data.

Links or embedded tools from compliant providers let patients book or message securely without the data passing through WordPress itself.

If you must collect PHI on the site, work with a host and form provider that sign BAAs and support encryption, access controls and audit logs.

What security basics should every health website have?

Every health website should use HTTPS, strong unique passwords with two-factor authentication, prompt updates, least-privilege user roles, reliable backups and careful control of third-party scripts.

HTTPS encrypts data between visitors and your site. Our guide on installing an SSL certificate on WordPress shows how to set it up.

Security headers add another layer of protection in the browser. Our guide on adding security headers to WordPress explains the most useful ones.

The HHS Security Rule guidance describes the administrative, physical and technical safeguards regulated entities must consider.

Do analytics and marketing tools cause HIPAA problems?

They can. Tracking pixels and analytics tags on pages where patients book or describe conditions may send identifiable information to third parties without a BAA.

Review every script on pages that relate to health services or appointments. Remove tools that do not need to be there, or switch to options that support healthcare requirements.

Keep tracking off patient portals and forms entirely unless your compliance team has approved the setup.

Does enterprise WordPress hosting help?

Some enterprise and specialist hosts offer stronger compliance support, including BAAs and audited security controls, which can make a WordPress setup easier to align with HIPAA.

Ask any host directly whether it signs BAAs and which services the agreement covers. Do not assume a host is suitable because it markets itself for healthcare.

Our explainer on what WordPress VIP is shows the kind of compliance features enterprise platforms offer.

Which security guides can help a health website team?

Useful starting points are NIST's guide to implementing the HIPAA Security Rule, the WordPress hardening documentation and the OWASP Top Ten list of common web application risks.

NIST's Special Publication 800-66 explains how organisations can put the HIPAA Security Rule into practice, from risk analysis to safeguards.

The WordPress hardening guide covers practical steps specific to WordPress, such as file permissions, updates and limiting admin access.

The OWASP Top Ten summarises the most common weaknesses in web applications. Reviewing your site against it is a sensible part of any risk analysis.

Pair these resources with a written risk assessment for your site. It shows what you checked, what you changed and why, which helps when questions come up later.

What should you do next?

Map what data your site collects, decide whether any of it is PHI, list every vendor that touches that data, confirm which ones sign BAAs, and involve a compliance professional before launching.

If your site does not need to handle PHI, the simplest path is to keep it that way. Ask patients to call or use a secure portal for anything medical.

Document your decisions carefully. Clear records of what the site does and does not collect make audits and future changes much easier.

Frequently asked questions

Is WordPress HIPAA compliant?

WordPress itself is neither compliant nor non-compliant. HIPAA applies to organisations and how they handle health data. A WordPress site can be part of a compliant setup if patient data is handled only by BAA-covered services.

Does my clinic website need to follow HIPAA?

It depends on whether the site collects, stores or sends protected health information. A simple information site usually does not, but forms asking about symptoms or appointments with health details may.

Can I use a normal contact form on a healthcare website?

For general enquiries, yes. Avoid using ordinary contact forms to collect health details, because entries and emails may be stored or sent by services without a Business Associate Agreement.

Do I need a BAA with my WordPress host?

If your site stores or processes protected health information, the host and other vendors handling that data generally need to sign a Business Associate Agreement.

Is this article legal advice?

No. It provides general information about how HIPAA relates to WordPress websites. Confirm your specific situation with a qualified compliance or legal professional.

Sources

  1. HIPAA for Professionals U.S. Department of Health and Human Services
  2. Business Associate Contracts U.S. Department of Health and Human Services
  3. Use of Online Tracking Technologies U.S. Department of Health and Human Services
  4. The Security Rule U.S. Department of Health and Human Services
  5. SP 800-66 Rev. 2 NIST
  6. OWASP Top Ten OWASP
  7. Hardening WordPress WordPress Developer Resources

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.