The essential answer
The relevant question is not whether a page looks medical. It is what information flows through it, who receives that information, and what obligations apply to each party.
Key takeaways
- 01Map data flows before choosing tools or collecting appointment details.
- 02A cloud provider that creates, receives, maintains, or transmits ePHI on behalf of a covered entity typically needs a compliant BAA.
- 03Review website trackers by page and data flow; do not assume every public page view is automatically PHI.
- 04Avoid labeling a site “HIPAA certified”—use documented safeguards and legal review.
SECTION 01
A brochure, an appointment system and a patient portal are not the same product
A static page describing services and publishing office hours usually has a different risk profile from a portal displaying clinical records. Appointment forms create another category: even a seemingly simple request can link identity, contact details and a care context. A vendor might receive that information through a form, email notification, database, log, API, analytics script or support tool.
Start with a data inventory listing every input, every downstream destination and every third-party processor. Draw separate boundaries for anonymous browsing, public inquiries, clinical scheduling and authenticated patient functions. Then ask qualified privacy and security professionals to determine HIPAA applicability for the actual organization and workflow.
- Name and contact details
- Requested appointment/service and comments
- Referrer URL, query string, IP address and analytics identifiers
- Uploaded forms, referrals and documents
- Information exported to CRM, email, spreadsheets or notifications
SECTION 02
Business associate agreements are contractual safeguards, not magic switches
HHS explains that a covered entity or business associate may use a cloud service provider to create, receive, maintain or transmit ePHI on its behalf if an appropriate business associate agreement is in place and the parties otherwise satisfy applicable HIPAA rules. A BAA alone does not guarantee secure operations; access control, data handling, staff training, incident response and risk analysis are also required.
Ask each vendor precisely what products and configurations are in scope of its BAA, which subprocessors it uses, where backups and logs reside, how deletion is handled, and what happens at contract termination. Do not treat generic “secure hosting” language as sufficient evidence.
Field checklist
- Vendor product and BAA scope verified
- Administrative, technical and physical safeguards evaluated
- Encryption and key responsibilities documented
- Access logs and retention rules defined
- Breach notification responsibilities documented
SECTION 03
Tracking pixels deserve a page-level review
Healthcare websites sometimes install analytics, conversion pixels, session replay or advertising scripts everywhere by default. Those scripts may receive URLs, page titles, device identifiers and form interaction signals, even when the clinic never intended to share medical context. Test the actual network requests and review each third party’s purpose and contractual role.
HHS has issued guidance addressing tracking technologies. Its public bulletin also notes a June 2024 federal court ruling vacating a portion of the guidance concerning the combination of an IP address and visits to unauthenticated public pages about conditions or providers. Do not repeat a blanket claim that every such page view automatically triggers HIPAA; assess current authority and case-specific facts with counsel.
Practical example: A general “Contact us” page and an authenticated patient portal should not automatically receive identical tags. A query string containing a requested treatment should never be treated as harmless analytics metadata.
SECTION 04
Prefer clear handoffs to purpose-built, approved systems
For the common small-practice website, the simplest reliable architecture is often a public website that explains care and links directly to the practice’s established scheduling, portal, refill or forms provider. This avoids building a second patient database without a business reason.
If custom intake is truly needed, design the data lifecycle first: minimization, authenticated administrative access, least privilege, audit logging, encryption, retention/deletion, backups, incident response, vendor agreements and secure transmission. Do not promise this capability as part of a low-cost marketing website build by default.
SECTION 05
Patient-facing copy needs a privacy safety review
Use plain language to tell patients not to send emergency concerns or sensitive details through ordinary marketing contact channels. Route clinical questions to an approved care team. Explain where an appointment request goes, whether it is a confirmed booking, and when the practice will respond. Avoid misleading “100% secure” or “fully HIPAA compliant” badges where no independent evidence supports the assertion.
Written privacy notices, HIPAA notices and consent mechanisms are not interchangeable. Determine which notices the practice is required to provide and where they belong; do not generate legal text and assume it is sufficient simply because it resembles a standard template.
SECTION 06
A practical privacy design review
Test every visible form, embedded scheduling widget, chat interface and file download. Record the vendor, data categories, hosting region, analytics calls, notifications, database storage, access rights and deletion method. Re-test whenever the site changes providers or adds tracking. Preserve a lightweight change log so a future agency can understand the architecture without reverse engineering it.
Field checklist
- Public/clinical flows separated
- Sensitive values absent from URLs and analytics events
- Third-party tags inventoried
- Appropriate BAA/legal review completed
- Deletion and export procedures tested
- No fake certification or unreviewed compliance claims
Sources & further reading
External sources support the attributed statements above. Links may change; always check their current wording and effective date.


