Written and maintained by CASRAI Editorial Board
Published · Last updated
On this page
Short answer: there is no such thing as a website that is “HIPAA compliant” on its own. HIPAA applies to people and organizations, namely covered entities and their business associates, and to the electronic protected health information (ePHI) they handle. A website is in scope only when it creates, receives, maintains or transmits ePHI for such an organization; if it does, the Security Rule’s technical safeguards at 45 CFR 164.312 apply to it.
This guide is general regulatory information, not legal advice. It is written for lab, clinic and supply-business staff deciding whether their site needs a HIPAA review.
Does HIPAA apply to your website at all?
Start with who you are, not with what the site does. Under 45 CFR 160.103 a covered entity is a health plan, a health care clearinghouse, or a health care provider that transmits health information in electronic form in connection with a covered transaction. A business associate is, with respect to a covered entity, a person who creates, receives, maintains or transmits protected health information (PHI) for that covered entity. PHI, in turn, rests on the definition of “individually identifiable health information.”
That order matters for a medical-supply or laboratory-equipment store. A business that sells products to customers and does not act for a covered entity may have no PHI flowing through its site, and the Security Rule would not attach to it simply because the products are medical. A business that handles patient information on behalf of a clinic or health plan may be a business associate. The decision turns on the facts, so read the covered entity test and the PII versus PHI comparison before buying anything labelled “HIPAA compliant.”
Map each site function to whether PHI flows
Once you know you are a covered entity or business associate, the practical question is which parts of the site touch ePHI. Walk the site function by function.
| Site function | Question to ask | Where to read more |
|---|---|---|
| Brochure and information pages | Does any page collect or display information about an identifiable individual’s health or care? | 45 CFR 160.103 (definition of individually identifiable health information) |
| Contact, intake and order forms | Do submitted fields identify a person and relate to their health, care or payment for care, for a covered entity? | HIPAA-compliant form builders |
| Hosting, form and email vendors | Does the vendor create, receive, maintain or transmit ePHI for you? If so, a business associate arrangement is involved. | Business associate agreements |
| Payment processing | Is the payment activity one of those listed in 42 U.S.C. 1320d-8? | See the payment section below |
| Analytics and tracking tools | Does the tool send ePHI to a vendor? If so, the disclosure needs a lawful basis, and a vendor receiving ePHI on your behalf is a business associate question. | 45 CFR 164.502(e), 164.308(b) |
Every row above is a question to answer from your own data flows, not a verdict. The same page can be out of scope for one organization and in scope for another.
What the Security Rule’s technical safeguards ask of a site
When ePHI is involved, 45 CFR 164.312 sets five technical-safeguard standards. They are a usable checklist for a technical review:
- Access control (164.312(a)(1)): restrict access to ePHI to those who should have it.
- Audit controls (164.312(b)): “Implement hardware, software, and/or procedural mechanisms that record and examine activity in information systems” that contain or use ePHI.
- Integrity (164.312(c)(1)): protect ePHI from improper alteration or destruction.
- Person or entity authentication (164.312(d)): verify that the person or entity seeking access is the one claimed.
- Transmission security (164.312(e)(1)): guard against unauthorized access to ePHI being transmitted over an electronic network.
Encryption is addressable, not unconditional
Many guides state that encryption is mandatory. The text is more specific. Encryption appears as an addressable implementation specification: 164.312(a)(2)(iv) says “Implement a mechanism to encrypt and decrypt electronic protected health information,” and 164.312(e)(2)(ii) says “Implement a mechanism to encrypt electronic protected health information whenever deemed appropriate.” Addressable means you assess it for your environment and document the decision; it does not mean optional. Do not describe it to colleagues as “required in every case” or as “not needed.”
Forms, hosting and vendors: the business associate question
A vendor that creates, receives, maintains or transmits ePHI for you is functioning as a business associate, and the Privacy and Security Rules require written assurances with that vendor (45 CFR 164.502(e) and 164.308(b)). “HIPAA compliant” on a vendor’s marketing page is not a property the software has by itself; the contract and your configuration are what count. For procurement, ask each vendor that touches ePHI for its business associate agreement and its security documentation, and compare them using your own vendor selection criteria. The HIPAA compliance checklist covers the wider program beyond the website.
HIPAA compliant payment processing
Payments are a frequent source of confusion. Section 1179 of HIPAA, codified at 42 U.S.C. 1320d-8, says that HIPAA “shall not apply to the entity with respect to such activities” when an entity engaged in the activities of a financial institution, or in authorizing, processing, clearing, settling, billing, transferring, reconciling or collecting payments for a financial institution, uses or discloses information to handle a payment for health plan premiums or for health care, whether by card, account, check or electronic funds transfer. The statute also covers related activities such as audits, customer disputes and inquiries, and communications to customers about their transactions.
Two limits follow from the statute’s wording. The exemption is activity-specific, not blanket: it covers the activities listed, not everything else an entity does. And it describes the payment handling itself, so it does not turn the rest of a site that holds ePHI into an out-of-scope system. Treat the payment step and the rest of the order flow as separate questions.
HIPAA compliant ecommerce and online medical-supply stores
For an online store, the applicability test above comes first. A retail order for supplies placed by a customer, with a delivery address and payment details, does not by that fact alone make the seller a covered entity. If the store also operates as a health care provider that transmits covered transactions electronically, or processes patient information for a covered entity as a vendor, the analysis changes and the order, account and customer-record systems need the safeguard review described earlier. The Shopify HIPAA question is a worked example of how a platform’s role is assessed in this setting.
Common misunderstandings
- “An SSL certificate makes the site HIPAA compliant.” Transmission security is one standard among five, and encryption itself is addressable.
- “A hosting company that says it is HIPAA compliant covers us.” The covered entity or business associate remains responsible for its own obligations; the vendor relationship needs a business associate agreement where ePHI is involved.
- “Any site that sells medical products is covered.” Status depends on the 160.103 definitions, not on the product category.
- “Payment data is always exempt.” The statute exempts listed payment activities, not every payment-adjacent system.
Frequently asked questions
What makes a website HIPAA compliant?
No certification attaches to a site. The organization behind it must be a covered entity or business associate, and where the site handles ePHI it must meet the Security Rule, including the technical safeguards in 45 CFR 164.312 and the business associate requirements for vendors.
Does my medical supply store need to be HIPAA compliant?
Only if it is a covered entity or acts as a business associate under 45 CFR 160.103. Selling medical products does not by itself decide that; check how your organization and its data flows fit those definitions.
Is HIPAA compliant payment processing a separate requirement?
Section 1179 (42 U.S.C. 1320d-8) lifts HIPAA from certain listed payment activities performed by financial institutions. It is limited to those activities, so confirm that your specific payment flow falls within the list.
Is encryption required on a HIPAA website?
It is an addressable specification in 164.312(a)(2)(iv) and (e)(2)(ii): you implement it where reasonable and appropriate, and document the reasoning.
Sources
- 45 CFR 164.312, technical safeguards: https://www.law.cornell.edu/cfr/text/45/164.312 (checked 2026-11-03).
- 45 CFR 160.103, definitions: https://www.law.cornell.edu/cfr/text/45/160.103 (checked 2026-11-03).
- 42 U.S.C. 1320d-8 (HIPAA section 1179): https://www.law.cornell.edu/uscode/text/42/1320d-8 (checked 2026-11-03).
- 45 CFR 164.502(e), business associate disclosures: https://www.ecfr.gov/current/title-45/part-164/section-164.502 and 45 CFR 164.308(b), business associate contracts: https://www.ecfr.gov/current/title-45/part-164/section-164.308, as summarised in the site’s HIPAA and HIPAA Privacy Rule entries.







