Does HIPAA apply to my app? What the Security Rule says about who it binds
The Security Rule does not decide this by what your software does. It decides it by what you are to the information: a covered entity, a business associate, or neither. Here is the sentence that says so, and the general requirements that follow from it.
The answer, in the publisher's own words
Applicability is one sentence. It binds two kinds of organisation, with respect to electronic protected health information, and it says nothing about industries, technologies or company size.
164.302 — HIPAA Security Rule (45 CFR part 164, subpart C) — Applicability.
A covered entity or business associate must comply with the applicable standards, implementation specifications, and requirements of this subpart with respect to electronic protected health information of a covered entity.
The same source names the document and the control this provision sits in, which is how the citation above is put together:
§ 164.302 Applicability.
Our record: /security-compliance-controls/164-302/. Quoted from <https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.302>, last checked 2026-11-15, due to be re-checked by 2026-12-15.
If it does bind you, these are the general requirements it binds you to. They are stated as outcomes, not as a checklist of features.
164.306(a) — HIPAA Security Rule (45 CFR part 164, subpart C) — Security standards: General rules.
(a) General requirements. Covered entities and business associates must do the following:
The same source names the document and the control this provision sits in, which is how the citation above is put together:
§ 164.306 Security standards: General rules.
Our record: /security-compliance-controls/164-306-a/. Quoted from <https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.306>, last checked 2026-11-15, due to be re-checked by 2026-12-15.
164.306(a)(1) — HIPAA Security Rule (45 CFR part 164, subpart C) — Security standards: General rules.
(1) Ensure the confidentiality, integrity, and availability of all electronic protected health information the covered entity or business associate creates, receives, maintains, or transmits.
Our record: /security-compliance-controls/164-306-a-1/. Quoted from <https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.306>, last checked 2026-11-15, due to be re-checked by 2026-12-15.
164.306(a)(2) — HIPAA Security Rule (45 CFR part 164, subpart C) — Security standards: General rules.
(2) Protect against any reasonably anticipated threats or hazards to the security or integrity of such information.
Our record: /security-compliance-controls/164-306-a-2/. Quoted from <https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.306>, last checked 2026-11-15, due to be re-checked by 2026-12-15.
164.306(a)(3) — HIPAA Security Rule (45 CFR part 164, subpart C) — Security standards: General rules.
(3) Protect against any reasonably anticipated uses or disclosures of such information that are not permitted or required under subpart E of this part.
Our record: /security-compliance-controls/164-306-a-3/. Quoted from <https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.306>, last checked 2026-11-15, due to be re-checked by 2026-12-15.
164.306(a)(4) — HIPAA Security Rule (45 CFR part 164, subpart C) — Security standards: General rules.
(4) Ensure compliance with this subpart by its workforce.
Our record: /security-compliance-controls/164-306-a-4/. Quoted from <https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.306>, last checked 2026-11-15, due to be re-checked by 2026-12-15.
A great deal of what is sold as HIPAA compliance is an interpretation of those four sentences. The sentences themselves are above, and they are the whole of the general requirements.
The rule also tells you how to read the rest of itself, which matters more than it sounds: every obligation in it is marked either Required or Addressable, and Addressable does not mean optional.
164.306(d) — HIPAA Security Rule (45 CFR part 164, subpart C) — Security standards: General rules.
(d) Implementation specifications. In this subpart:
Our record: /security-compliance-controls/164-306-d/. Quoted from <https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.306>, last checked 2026-11-15, due to be re-checked by 2026-12-15.
164.306(d)(1) — HIPAA Security Rule (45 CFR part 164, subpart C) — Security standards: General rules.
(1) Implementation specifications are required or addressable. If an implementation specification is required, the word “Required” appears in parentheses after the title of the implementation specification. If an implementation specification is addressable, the word “Addressable” appears in parentheses after the title of the implementation specification.
Our record: /security-compliance-controls/164-306-d-1/. Quoted from <https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.306>, last checked 2026-11-15, due to be re-checked by 2026-12-15.
164.306(d)(2) — HIPAA Security Rule (45 CFR part 164, subpart C) — Security standards: General rules.
(2) When a standard adopted in § 164.308, § 164.310, § 164.312, § 164.314, or § 164.316 includes required implementation specifications, a covered entity or business associate must implement the implementation specifications.
Our record: /security-compliance-controls/164-306-d-2/. Quoted from <https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.306>, last checked 2026-11-15, due to be re-checked by 2026-12-15.
164.306(d)(3) — HIPAA Security Rule (45 CFR part 164, subpart C) — Security standards: General rules.
(3) When a standard adopted in § 164.308, § 164.310, § 164.312, § 164.314, or § 164.316 includes addressable implementation specifications, a covered entity or business associate must—
Our record: /security-compliance-controls/164-306-d-3/. Quoted from <https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.306>, last checked 2026-11-15, due to be re-checked by 2026-12-15.
164.306(d)(3)(i) — HIPAA Security Rule (45 CFR part 164, subpart C) — Security standards: General rules.
(i) Assess whether each implementation specification is a reasonable and appropriate safeguard in its environment, when analyzed with reference to the likely contribution to protecting electronic protected health information; and
Our record: /security-compliance-controls/164-306-d-3-i/. Quoted from <https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.306>, last checked 2026-11-15, due to be re-checked by 2026-12-15.
164.306(d)(3)(ii) — HIPAA Security Rule (45 CFR part 164, subpart C) — Security standards: General rules.
(ii) As applicable to the covered entity or business associate—
Our record: /security-compliance-controls/164-306-d-3-ii/. Quoted from <https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.306>, last checked 2026-11-15, due to be re-checked by 2026-12-15.
164.306(d)(3)(ii)(A) — HIPAA Security Rule (45 CFR part 164, subpart C) — Security standards: General rules.
(A) Implement the implementation specification if reasonable and appropriate; or
Our record: /security-compliance-controls/164-306-d-3-ii-a/. Quoted from <https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.306>, last checked 2026-11-15, due to be re-checked by 2026-12-15.
164.306(d)(3)(ii)(B) — HIPAA Security Rule (45 CFR part 164, subpart C) — Security standards: General rules.
(B) If implementing the implementation specification is not reasonable and appropriate—
Our record: /security-compliance-controls/164-306-d-3-ii-b/. Quoted from <https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.306>, last checked 2026-11-15, due to be re-checked by 2026-12-15.
What the rule does not say
The subpart we hold does not define "covered entity" or "business associate", so it cannot tell you whether you are one.
Checked, not asserted: none of covered entity means, business associate means, definitions appears anywhere in the 105 provisions we hold of the HIPAA Security Rule. That is a search of the publisher's own words, and it is what the gate on this page tests; if one of those words turned up, this page would stop being built.
Those terms are defined in another part of the regulations, which we do not hold. The rule's own definitions section is deliberately absent from our records, because its paragraphs carry no citable labels and a definition is not a control. Read it at its source if the answer turns on whether you are a business associate.
It names no vendor, no cloud, no framework and no certificate. There is no such thing in the rule as a HIPAA-certified product.
Checked, not asserted: none of certified, certification, Amazon, Microsoft, Google, cloud appears anywhere in the 105 provisions we hold of the HIPAA Security Rule. That is a search of the publisher's own words, and it is what the gate on this page tests; if one of those words turned up, this page would stop being built.
A vendor may tell you their service can be used in a compliant way, and that can be true. The rule binds you, not them — except where they are themselves a business associate, which is the question the paragraph above cannot answer for you.
What we have not read
We hold the HIPAA Security Rule, which is subpart C of 45 CFR part 164. We do not hold the Privacy Rule, the Breach Notification Rule, or the definitions in part 160. A question whose answer is in one of those is not answered here, and no page here will pretend otherwise.
The same answer for a machine
- The provisions as data — every provision of the rule as its own record, with a machine-readable twin.
- Requirements by component — one address, no account: the provisions bearing on the part you are building.
The other questions answered here
What does HIPAA require software to do?, Does HIPAA require encryption at rest, and which algorithm?, What must I log for HIPAA, and how long must records be kept?, What session timeout do HIPAA and NIST require?, What password rules does NIST state?, Do I need multi-factor sign-in, and under which rule?, How fast must I report a breach, by law and by state?, Which state privacy laws apply to my app, by revenue and number of consumers?, Which NIST 800-53 controls bear on a database, on object storage, on logs and on backups?, What is SOC 2, and what in it can and cannot be quoted for free?, Which cryptographic algorithms and TLS certificate lifetimes stop being acceptable, and when?.
All of them are listed on the question list.
What this page is
This page is assembled automatically out of the records named on it. No sentence of a rule on it is ours: every one is quoted from the publisher that wrote it, with a link to the page it was quoted from and the date we last checked that page.
SOC 2, ISO/IEC 27001 and PCI DSS are not quoted anywhere on these pages. The bodies that write those documents sell the text, and our position, written down in our constitution, is that facts plus a short attributed quote with a link are fine but republishing licensed text is not. So nothing here quotes a trust services criterion or an ISO clause. What can be quoted is the rules the public bodies publish — the HIPAA Security Rule, NIST SP 800-53, federal retention regulations, state statutes and the CA/Browser Forum's requirements — and that is what every answer here is built out of.
This is not legal advice and it is not a statement that any system complies with anything. A provision quoted here is a sentence from a published document, not a finding about your software. Who decides: your own counsel, your auditor, and the regulator.