Resources

Do Website Forms Need to Be HIPAA Compliant? A Decision Guide for Small Practices

A decision guide for small practices: which form fields create PHI, where submissions travel after Submit, and when you need a form vendor that signs a BAA.

By ClinicSite Editorial Team, Healthcare Practice Web Architecture · Published July 13, 2026

The short answer
Only when the form collects protected health information for a HIPAA covered entity or its business associate. HHS's own examples treat an email address or a reason for seeking care, entered while booking with a provider, as identifiable health information. Once PHI flows, every service that receives, stores or forwards the submission needs a signed BAA.

General information, not legal advice. Your compliance officer or attorney should make the final call for your practice. Sources were verified in 2026.

Start with the form you already have

Most practice owners searching this question are not shopping for a form builder. They have a contact box that came with their website template, and someone has asked whether it is a problem. So the useful order is: look at what the form asks, follow where the answers go, then decide whether the form needs to change, stay, or go.

Two definitions do most of the work. Under 45 CFR 160.103, individually identifiable health information is information created or received by a health care provider 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 reasonably could. Protected health information is that same information when held by a covered entity or business associate, in any form. A practice is a covered entity if it transmits health information electronically in a standard transaction, which in practice means billing insurance electronically.

Which fields turn a form into a PHI form

The test is the combination, not any single box. A name alone tells nobody anything about health. A name submitted through a dental practice's "request an appointment" form tells the reader that this person is seeking care from that practice.

HHS made this concrete in its online tracking bulletin. It describes a visitor who enters an email address, or a reason for seeking care, while making an appointment on a provider's unauthenticated web page, and says that information "meets the definition of IIHI." The 2024 court ruling against the bulletin vacated a different, narrower passage about IP addresses and public pages; our analytics and tracking guide explains what it did and did not change.

Field on the formOn its ownPaired with a request for care from your practice
Name, email, phoneContact detailsGenerally identifies a prospective patient seeking care
Preferred appointment day or timeScheduling detailPart of an appointment request
Reason for visit, symptoms, "How can we help?"Health informationClearly within the definition
Insurance carrier, member IDPayment informationRelates to payment for care
Date of birthIdentifierStrengthens identification
File upload (referral, X-ray, prior records)Usually clinicalClearly within the definition
Newsletter signup (email only)Contact detailLower risk, but list names and segments can reveal more
Job applicationNot health informationHIPAA generally not the governing law here

The free-text box deserves its own warning. You can label it "Please do not include medical details," and some visitors will still describe their symptoms in three sentences. Plan for what they actually type, not for what the label asks.

Follow the submission after someone clicks Submit

This is where most of the exposure sits, and it is easy to miss because it happens after the page. A single submission on a typical small-practice site can land in five or six places:

  1. The builder's own database. Squarespace, for example, can save form block submissions in its Contacts panel under "Form Submitters."

  2. A notification email. Squarespace's help page says the email body lists every form field and "can't be customized." That email then sits in an inbox, a phone, and possibly a shared front-desk login.

  3. A spreadsheet. Builders commonly offer a Google Drive or similar connection, which copies each submission into a sheet.

  4. A marketing or CRM tool. Mailchimp and Zapier connections push the same data into another company's system.

  5. Backups and exports. Inbox archives, downloaded CSV files, and laptop sync folders hold copies long after anyone reads them.

Each hop is a separate vendor. If the submission is PHI, each needs a BAA that covers that specific service. A BAA with your email provider covers only what that provider names. Google's Workspace BAA covers the services on its "HIPAA Included Functionality" list and, by Google's own statement, not third-party add-ons. GoDaddy sells a HIPAA email add-on for its Microsoft 365 plans and says plainly that signing the BAA "doesn't achieve compliance on its own."

A quick way to see your own chain: submit a test entry with a made-up name, then search every connected tool for that name a day later.

Three ways to handle it

OptionWhat it looks likeWho signs a BAATrade-off
A. No formTap-to-call and email links, plus a booking tool or patient portal that already has a BAAOnly the booking or portal vendorSome visitors prefer typing to calling
B. Minimal non-clinical formName, phone, best time to call; no free text; warning labelIdeally the form and email vendors anyway, because people still overshareLower risk, not zero
C. Form vendor that signs a BAAA dedicated secure form service, embedded or linkedThe form vendor, plus every tool the submissions are routed toMonthly cost and setup; worth it if you need web intake

Option A rarely appears in form-builder roundups, which exist to sell forms. A visitor who wants to book can call or use your scheduling tool. A visitor with a question can email, and that email arrives in an inbox you already have to manage carefully anyway.

Option B suits practices that want a lightweight "call me back" path. It is a risk-reduction choice, not a compliance shortcut.

Option C is right when intake, consent forms or document uploads genuinely have to happen online. Then the form is a clinical system and deserves the same care as your EHR.

What to check in a form vendor's BAA and settings

The BAA is signed between your practice (the covered entity) and the form vendor (the business associate). HHS lists ten elements the contract must contain. For a small practice choosing a form tool, these questions translate them into plain checks:

  • Which services does the BAA name? Look for the exact product and plan you will use. Some vendors offer a BAA only on higher tiers.

  • What do notifications contain? A secure form that emails the full submission to an ordinary inbox moves the problem rather than solving it. Look for "notification without content" settings, where the email only says a new submission is waiting.

  • Where is data stored, and for how long? You should be able to delete entries and set a retention period.

  • Which subcontractors touch the data? HHS requires business associates to bind their subcontractors to the same terms.

  • How will you be told about a breach? The BAA must require the vendor to report it.

  • What happens when you cancel? The contract should provide for return or destruction of PHI.

  • Which integrations fall outside? Connecting a secure form to a non-BAA spreadsheet or email-marketing tool reopens the gap.

Vendors change plans and terms often. Read the BAA itself on the day you sign, not a summary on a comparison page.

The operational cost nobody budgets for

Forms create work that is easy to overlook when choosing a template. Spam submissions arrive and must be screened by a person who can recognize a real patient among them. Someone has to check the inbox daily, reply, and move anything clinical into the record. Old submissions need deleting on a schedule. When the staff member who set up the form leaves, someone has to know which tools it feeds.

None of that is a reason to avoid forms. It is a reason to count them as a process with an owner, not as a page element.

How ClinicSite handles this

ClinicSite took a narrow position on forms. Published ClinicSite sites run under a content security policy that blocks form submission entirely, so a generated site has no contact or intake form that can post data anywhere. Visitors reach the practice by tapping its phone number or email link.

There is one exception, and it matters for this topic. Paid plans include online booking, which is off until a practice turns it on. When it is on, a patient choosing a slot gives a name, contact details and an optional note, which ClinicSite stores and emails to the practice. ClinicSite lists a business associate agreement as "Partial" and not self-serve on its hosting page, so raise it before enabling booking. If your practice depends on web intake forms, ClinicSite's own FAQ says it is not a fit today.

If a site with no forms sounds like the right starting point, you can preview a rebuilt version of your current site for free, with no account or card, and decide from there. The HIPAA website requirements guide covers the other safeguards a practice site needs.

Sources

Frequently asked questions

Does a simple contact form on a medical practice website need to be HIPAA compliant?
It depends on what it asks and what people type. A form that collects contact details as part of a request for care from your practice will generally capture identifiable health information, by HHS's own examples. Then the form, the inbox it emails, and any storage it feeds need BAAs. A form you strip to non-clinical fields lowers the risk, though visitors can still overshare.
Is a name and phone number alone PHI?
On their own, no. Context changes that. The same name and phone number submitted through a "book a consultation" form on a therapist's site indicate that the person is seeking care from that provider, which relates to the provision of health care. Your compliance reviewer should decide how to treat each of your forms; assuming yes is the cautious default.
Who signs the BAA for a website form: me or my web designer?
Your practice signs it with the vendor that receives, stores or transmits the data, such as the form service or email provider. A web designer who never touches submissions usually does not need one. A designer or agency that can log in and read form entries, or that manages the inbox, may be a business associate too, so ask your compliance reviewer.
Is an encrypted form enough?
No. Encryption in transit protects the data while it moves from the browser to the server. It says nothing about who stores the submission afterward, whether the notification email carries the full text, or which other tools receive a copy. Ask about storage, notifications and integrations, then get a BAA that names the service.
Can I use Google Forms for patient intake?
Only if Google Forms is covered by your Google Workspace BAA, and only on a Workspace account where an administrator has accepted that BAA. Google limits coverage to the services on its "HIPAA Included Functionality" list. Check that list for Forms on the day you decide, since it can change, and remember that add-ons are excluded.
What should I do with old form submissions sitting in my inbox?
Decide on a retention rule, copy anything that belongs in the clinical record into the patient's chart, then delete the rest from the inbox, trash, and any connected spreadsheets or exports. If those emails were in an account without a BAA, ask your compliance reviewer whether the exposure needs further assessment.
Do HIPAA rules apply if I am a cash-only practice?
HHS defines a provider as a covered entity only if it transmits health information electronically in connection with a standard transaction, such as electronic insurance claims. A practice that never does may fall outside HIPAA. State privacy laws and professional ethics rules can still apply, so handling form data with the same care is a sensible default.

See what your clinic site could look like

Paste your current website address. You get a full generated replacement to look at, free, with no account and no card.

Free preview with no card. Previews are deleted after 7 days.