Skip to content
AnswerHealthcare systems
Home/Answers/What does HIPAA require from a WordPress healthcare website?
Technical answer · healthcare systems

What does HIPAA require from a WordPress healthcare website?

HIPAA does not certify WordPress or make a site compliant because it uses a particular host or form plugin. Start by identifying whether the site handles protected health information (PHI), which vendors create, receive, maintain or transmit it, and what agreements and safeguards apply. The covered practice and its advisers must determine the legal requirements for their actual workflow.

Last reviewed

01Diagnosis

The data path matters more than the platform label

A healthcare site may collect only a name and callback request, or it may collect detailed intake information. The hosting provider, form processor, email notifications, CRM, analytics and support access can all affect where data travels. A BAA is not a technical configuration and does not certify the rest of the stack.

Inventory systems before PHI is collected

  1. List every form field and decide whether it is necessary for the first contact.
  2. Trace where each field is stored, transmitted, logged, emailed and backed up.
  3. Identify vendor roles, access controls, retention and incident responsibilities with the practice.
  4. Confirm whether BAAs and other agreements are required before covered data flows.
  5. Test that analytics, marketing tags and error logs do not receive fields they should not see.

Do not infer compliance from a WordPress setup

Use the minimum data needed, restrict access, document retention and keep PHI out of unrelated analytics or notification systems by configuration. The practice and qualified advisers decide which laws and agreements apply; implementation follows that documented decision. Amagraphs does not claim HIPAA certification, and this engineering checklist is not legal advice.

Verify the configured data flow

Use synthetic records to inspect network requests, server logs, vendor destinations and access permissions. Record which systems receive data and repeat the test after plugin, form or analytics changes; do not use real patient details as test data.

02Questions

Common questions

Is WordPress HIPAA certified?

No. WordPress is software, not a certification. Compliance depends on the covered entity’s obligations and the complete configured workflow.

Does signing a BAA make a website compliant?

No. A BAA addresses a specific relationship. Forms, hosting, access, storage, retention and other vendors still need review.

Can a healthcare website use analytics?

Only after the practice determines what data is collected and whether it may include PHI. Configure tags to avoid sensitive fields and verify actual network traffic.

Where should patient form data be stored?

In systems selected and approved by the practice for the specific data and workflow, with vendor terms, access and retention documented before launch.

03Case study

Healthcare work is not a compliance badge

The GeneLean360 case study documents public and member commerce, subscriptions and fulfilment architecture. It makes no HIPAA certification or client compliance claim.

Read the GeneLean360 healthcare commerce study →

NextStart here

Get the handoff measured before changing it.

Send the URL. We will write up what we can verify and what remains unknown within two working days.