HIPAA (45 CFR §164.502) governs how you handle Protected Health Information (PHI) — and yes, your website can create PHI obligations even if you don't intend it to.
What triggers HIPAA on your website:
- Appointment request forms that collect health information (chief complaint, insurance details, medical history)
- Patient portals or secure messaging features
- Online intake forms
- Any form that asks about current dental conditions or treatment history
What doesn't trigger HIPAA:
- General contact forms asking only for name, phone, and "I'm interested in braces"
- Newsletter signups
- General information pages with no data collection
Minimum technical requirements when PHI is involved:
- SSL/TLS encryption (HTTPS) for all pages with forms
- Business Associate Agreement (BAA) with your web host and any form processing services
- Access controls for any stored form submissions
- Audit logging if you store submissions on your server
A common mistake: using standard contact form plugins that email PHI in plain text. If your form collects health information and sends it via unencrypted email, you have a HIPAA gap. services include HIPAA-compliant form services or patient portal integrations that maintain encryption throughout.
This is educational guidance, not legal advice. Consult a healthcare compliance attorney for your specific situation.