14 min read
Can You Build a HIPAA-Compliant Website with WordPress?
Yes, you can run a HIPAA-compliant healthcare website on WordPress, but WordPress itself does not make you compliant and no plugin does either. Compliance comes from the architecture around it: where protected health information (PHI) lives, who has signed a Business Associate Agreement (BAA), how data is encrypted, and what you can prove in an audit. The pattern that holds up is simple: keep PHI out of WordPress wherever possible, and lock down everything that remains.
This guide covers what HIPAA actually asks of a website, which parts of a WordPress stack are affected, the hosting and form decisions that matter most, and the mistakes practices commonly make. It is general information with pointers to official guidance, not legal advice: confirm your obligations with your compliance officer or counsel, and start from the HHS HIPAA pages.
Last updated: 15 November 2026
Quick answer: Yes, but WordPress cannot make a site HIPAA compliant by itself, and no plugin does either. HHS treats any vendor that maintains electronic PHI for you, including a web host, as a business associate that must sign a BAA. So keep PHI out of WordPress where you can, and where you cannot, use a host and form service that sign a BAA.
What HIPAA actually requires of a website
HIPAA applies to covered entities (providers, health plans, clearinghouses) and to their business associates (any vendor that creates, receives, maintains or transmits PHI on their behalf). A brochure site that lists your clinic hours, doctors and a phone number does not handle PHI and is not in scope. The moment a visitor types “I need an appointment for my diabetes follow-up” into a contact form, you are collecting PHI and the Security Rule applies to every system that touches it.
The Security Rule breaks down into three groups of safeguards:
- Administrative: a documented risk analysis, workforce training, access policies, an incident response plan and signed BAAs with every vendor in the PHI path.
- Physical: control over the servers and devices that store PHI. For a website this is mostly your hosting provider’s responsibility, which is exactly why the hosting BAA matters.
- Technical: unique user IDs, access controls, audit logs, integrity controls, and encryption of PHI in transit and at rest.
One regulatory note worth knowing. HHS proposed an update to the Security Rule that was published in the Federal Register on 6 January 2025. According to the HHS Security Rule proposal pages, it would require encryption of ePHI at rest and in transit with limited exceptions, multi-factor authentication, vulnerability scanning at least every six months, penetration testing at least once every 12 months, and written procedures to restore critical systems and data within 72 hours. It remains a proposal: law firm reporting on the Fall 2026 Unified Agenda says HHS moved it to its long-term actions list with final action projected for July 2027 (see the McDermott Will & Schulte summary). The current Security Rule stays in force meanwhile. Building toward the proposed controls now is a sensible direction, but they are not yet law.
The first decision: where does PHI actually live?

Every HIPAA WordPress project should start by drawing a simple data-flow map. List every place a patient can submit information and trace where that information ends up: the WordPress database, an email inbox, a third-party SaaS, a CRM, a backup file, a log. Each stop on that map needs a BAA and needs to meet the technical safeguards.
In practice you have two architectures to pick from.
Option A: PHI never touches WordPress
WordPress serves the public site (services, providers, locations, blog, insurance information). Anything that collects PHI is handled by a dedicated, HIPAA-ready service that signs a BAA: an embedded Jotform HIPAA form, a patient portal or scheduling tool from your EHR vendor if it offers one, or a telehealth platform. The embed is an iframe or script; the data posts directly to the vendor and never enters your database or email.
This is the simplest architecture for most small and mid-sized practices. Your WordPress install stays out of scope for PHI, your hosting requirements relax to “good security hygiene”, and your compliance burden collapses to a handful of vendor BAAs.
Option B: WordPress stores or processes PHI
If you need custom intake workflows, a member area with patient records, or forms whose submissions stay in WordPress, you are now running a PHI system. That means HIPAA-grade hosting with a BAA, encrypted database fields, audit logging at the application level, strict role management, and a plugin inventory you can defend in an audit. It is doable, but expect considerably more effort than option A and plan for annual reviews.
Pick A unless you have a concrete reason to pick B.
Hosting: the BAA is non-negotiable
HHS’s cloud computing guidance says a cloud service provider that maintains ePHI on your behalf is a business associate, even if it stores only encrypted ePHI and holds no decryption key, and that a covered entity using one without a BAA is in violation of the HIPAA Rules. So if your site stores or transmits PHI, your host must sign a BAA. Not every host does, and the published positions differ:
- Atlantic.Net says a BAA is a standard part of its HIPAA hosting. As of 15 November 2026 its lowest listed price is $516.34 a month for the Linux HIPAA Developer plan on a 36-month term ($607.11 a month on a 12-month term).
- Liquid Web says it provides signed BAAs for all HIPAA-ready environments on its HIPAA hosting page, with dedicated servers listed from $229 a month (Linux) and $271 a month (Windows).
- HIPAA Vault says it provides a BAA for every service it offers, including HIPAA WordPress hosting, on its website. It lists no prices, only quotes.
- Kinsta states in its technical FAQ that it does not offer HIPAA-compliant hosting, does not enter into BAAs, and that you should not store or transmit PHI there. That is fine for a marketing-only site under Option A, and not fine for Option B.
The WordPress VIP capabilities page says to contact its team about HIPAA, so get any such commitment in writing before you put PHI on a managed WordPress platform. Prices above come from the vendors’ own pages and change, so confirm before you budget.
Things to look for in a HIPAA hosting plan beyond the signature:
- Encrypted disks (AES-256 at rest) and TLS 1.2+ enforced for every connection.
- Isolated environments rather than shared tenancy.
- Centralised audit logging with a retention period you have agreed in writing.
- Managed OS patching, intrusion detection and a documented backup and restore procedure.
- Staff who have completed HIPAA training and are bound by confidentiality terms.
Ask two questions before signing: “Will you provide your most recent risk assessment or SOC 2 report?” and “What exactly is excluded from the BAA?” Liquid Web’s own pages, for example, say customers remain responsible for making sure their applications and operational processes follow HIPAA, which means WordPress, its plugins and your users stay your problem.
Forms: the most common compliance failure

Contact and appointment forms are where most healthcare WordPress sites break HIPAA without anyone noticing. Most form plugins can store each entry in the WordPress database and email a copy to the front desk. That email is PHI sitting in an inbox, and an inbox is only an acceptable home for it if your email provider has signed a BAA with you and you have configured the service as the provider requires (Google, for example, publishes HIPAA guidance for Google Workspace).
Here is how the mainstream options compare on the public record as of 15 November 2026. Vendor positions change, so verify before you rely on them.
| Tool | BAA position (from vendor pages) | Where entries live | What to know |
|---|---|---|---|
| Jotform | The Jotform HIPAA page says eligible customers with HIPAA features enabled can sign a BAA, and names the Gold and Enterprise plans | Jotform’s HIPAA environment | A simple path for Option A sites: embed the form and keep PHI out of WordPress. Confirm plan eligibility with Jotform. |
| Gravity Forms | Says in its HIPAA documentation that it will not sign a BAA because it does not host your form data | Your WordPress database | Compliance falls on you and your host. Its docs list a third-party HIPAA add-on and say it does not test or support third-party solutions. |
| WPForms | No BAA found on its public pages, which list GDPR, PCI and CCPA badges but no HIPAA claim | Your WordPress database | Ask the vendor in writing before using it for PHI. |
| Formidable Forms, Contact Form 7 | No BAA position verified; check with the vendor | Database (Formidable) or email only (Contact Form 7 by default) | An email-only flow puts PHI into mail systems, which is the worst case unless that mail provider has signed a BAA. |
| EHR-provided scheduling widget | Covered by your EHR vendor’s BAA if the vendor signs one | Your EHR | Often the cleanest option because data lands where staff already work. |
If you must use a self-hosted form plugin, do all of the following:
- Change every notification email so it says only “A new appointment request has arrived. Log in to view it.” No field values in the email body.
- Restrict entry viewing to a dedicated role (not Editor or Administrator shared by the whole office) and enforce two-factor authentication for that role.
- Encrypt sensitive fields at rest, using a vetted add-on or custom code built on PHP’s sodium extension, and have a developer review it.
- Set an automatic purge so entries are deleted once they have been transferred into the EHR, with the retention window agreed with your compliance officer.
- Confirm your backups are encrypted too, because every backup now contains PHI.
Hardening the WordPress layer

Whichever architecture you choose, the WordPress install itself needs to be defensible. Security plugins do not confer compliance, but the controls below map directly to Security Rule requirements and an auditor will look for them.
Access control and authentication
Give every staff member their own account (HIPAA requires unique user identification; shared logins fail immediately). Enforce two-factor authentication for all users with a plugin such as WP 2FA or Kadence Security. Require strong, unique passwords, limit login attempts, and remove accounts the day someone leaves. Use the least privileged role that does the job; a receptionist who only reads form entries does not need Administrator.
Audit logging
WordPress does not log user activity by default. Install WP Activity Log (or Stream) and ship the logs off-site to your host’s logging service or a SIEM. You should be able to answer “who viewed this patient’s entry and when”. The Security Rule’s documentation requirement (45 CFR 164.316) calls for keeping required policies and records for six years, so agree a log retention period with your compliance officer.
Encryption in transit
Force HTTPS everywhere, redirect HTTP, enable HSTS, and disable TLS 1.0 and 1.1 at the server. Test with Qualys SSL Labs and aim for an A rating. Set FORCE_SSL_ADMIN to true in the wp-config file.
Plugin and theme discipline
Outdated plugins are an everyday risk on any WordPress site. Keep a written inventory of every plugin with its purpose, vendor and update cadence. Remove anything unused. Subscribe to Patchstack or Wordfence vulnerability feeds so you hear about a CVE before an attacker exploits it. Test updates on staging, then apply to production within a defined window (for example a few days for routine updates and 24 hours for critical security releases). Major core releases such as WordPress 7.1, scheduled for 19 August 2026, can break older plugins, so staging is not optional.
Backups and recovery
The proposed rule’s 72-hour restoration requirement is a sensible target anyway. Take daily encrypted backups to a location covered by a BAA (your HIPAA host’s backup service, or Amazon S3 with server-side encryption, once you have accepted the BAA in AWS Artifact and use only HIPAA-eligible services). Run a restore drill twice a year and document it. If you want a shortlist of tools, our backup plugin comparison covers the options, but on a PHI site the host-level backup is the one you rely on.
Analytics, chat widgets and tracking pixels
In December 2022 HHS’s Office for Civil Rights published a bulletin on online tracking technologies used by covered entities and business associates. HHS’s page now says a federal court in the Northern District of Texas vacated part of that guidance on 20 June 2024, the part treating an IP address linked to a visit to an unauthenticated public webpage about health conditions or providers as triggering HIPAA obligations, and that HHS is evaluating next steps. That narrows the rules for public pages but does not make analytics risk-free: tags on pages behind a login, or on pages that handle PHI, remain a concern. Google’s own HIPAA and Google Analytics page says Google does not offer a BAA for Google Analytics and that HIPAA-regulated customers must not expose PHI to it.
Practical rules:
- No third-party scripts on any page behind a login or on any page that handles PHI (forms, portals, symptom checkers).
- On public pages, prefer an analytics tool that runs on your own infrastructure (for example self-hosted Matomo on your HIPAA server) or comes from a vendor that signs a BAA. If you keep Google Analytics, follow Google’s advice to keep tags off authenticated pages and off pages tied to providing care, and take legal advice on which pages are safe.
- Live chat only from vendors with a BAA. A generic chat widget that lets a visitor type “I think I have an STI” has just created PHI in an uncovered system.
A realistic build plan for a small practice
Here is a sensible plan for a three-provider clinic that needs a public site, online appointment requests and a newsletter, with no patient portal in WordPress.
- Scope and map. Confirm the only PHI entry point is the appointment request form. Everything else is marketing content.
- Hosting. Because PHI does not enter WordPress, use a reputable managed WordPress host with strong security practices. Skip the HIPAA tier unless the scope changes, and revisit if it does.
- Form. Embed a Jotform HIPAA form for appointment requests. Route submissions to the practice manager’s Jotform inbox and to the EHR through an integration your EHR vendor supports. No email notifications containing field data.
- Newsletter. Use a mailing tool for general health tips only. Never segment by condition. Collect email and first name, nothing else.
- WordPress hardening. Unique accounts, 2FA, activity logging, HTTPS with HSTS, limited plugin set, automatic minor updates, weekly review of major updates on staging.
- Analytics. Privacy-first analytics on public pages only; no pixels on the appointment page.
- Paperwork. Collect BAAs from Jotform and any other vendor in the PHI path. Write the risk analysis, the access policy and the incident response plan. Train staff annually and keep the records.
- Review. Re-run the data-flow map every twelve months or whenever a new tool is added. Most compliance drift happens when someone installs “just one more plugin”.
If your needs go beyond this (patient education gated by login, provider-only communities, intake that must live in WordPress), the same principles apply but the implementation needs a developer who has done it before. Our security hardening service covers the technical controls above, and custom intake and portal workflows can be built through custom plugin development when off-the-shelf tools will not do.
Frequently asked questions
Is there a plugin that makes WordPress HIPAA compliant?
No. Plugins can supply individual controls (2FA, logging, encryption) but compliance is the combination of hosting, vendors, configuration, policies and training. Any product that advertises “one-click HIPAA compliance” is overselling.
Do I need a BAA if my site only has a contact form?
If the form can reasonably receive health information (and “describe your concern” fields always do), yes. Either move the form to a vendor that signs a BAA or make sure your host, form storage and email provider are all covered. The HHS cloud guidance applies to any provider that maintains the ePHI for you.
Can I use WordPress.com for a healthcare site?
For a pure marketing site with no PHI collection, yes. For anything that collects PHI, do not do it unless you hold a signed BAA that covers the service. We found no published BAA terms for WordPress.com, and the WordPress VIP page tells HIPAA customers to contact its team, so ask in writing first.
Does an SSL certificate make my forms compliant?
It covers encryption in transit only. Data at rest in your database, in email and in backups still needs protection, and you still need access controls, logs and BAAs.
What happens if we get it wrong?
HHS’s Office for Civil Rights enforces HIPAA, and penalties depend on the level of negligence found. Beyond fines, a breach notification to every affected patient does lasting damage to a practice’s reputation. The cost of doing it right is small by comparison.
Is the HIPAA Security Rule changing?
HHS has proposed changes, including mandatory encryption, multi-factor authentication, six-monthly vulnerability scanning, annual penetration testing and a 72-hour restoration requirement. As of the Fall 2026 agenda reporting, final action is projected for July 2027, so the current rule still applies.
Does my web host need to sign a BAA?
If the host stores or transmits ePHI for you, yes. HHS says a cloud service provider that maintains ePHI is a business associate even when it holds only encrypted data and has no key. If PHI never reaches your WordPress server, the host is out of the PHI path.
Can I use Google Analytics on a healthcare website?
Google says it does not offer a BAA for Google Analytics and that HIPAA-regulated customers must not send it PHI. Keep it off authenticated pages and pages tied to providing care, or use a different tool, and take legal advice on your pages.
Where to start
Draw the data-flow map today. If PHI only enters through one or two forms, move those forms to a BAA-backed service this week and you have removed most of your risk in an afternoon. Then harden the WordPress install, write the policies, and schedule the annual review. WordPress is a perfectly good foundation for a healthcare site; it just needs to be treated as one component of a compliant system rather than the whole answer.
Related reading
- How to Secure Wordpress Media Files Images Pdfs Videos
- Why Wordpress Locks You Out And How to Fix it Faster
- Why Managed Wordpress Teams Offer a Smarter Alternative
- Most Bulletproof Wordpress Hosts That Never go Down
- Wordpress Theme For Your Business
- How to Secure Your Wordpress Site For Handling Sensitive Client Data