Updated:
Patient data protection checklist
The rules for protecting patient data sit in several places: the Privacy Rule, the Security Rule, the Breach Notification Rule, and information blocking and nondiscrimination provisions. This page puts them into one list you can go through item by item.
In short: patients must be notified of a breach within 60 calendar days of discovery, and HHS at the same time when 500 or more people are affected (45 CFR 164.404, 164.408); a written business associate agreement is needed before PHI goes to a vendor that is a business associate (§ 164.502(e)); the Security Rule requires a risk analysis (§ 164.308(a)(1)(ii)(A)).
- This is not an official checklist. It is the author’s list built from sections that were read; each item gives its basis, so check the text.
- Whether your organization is a covered entity, and what state law adds to HIPAA, are not decided here. Ask your privacy officer or counsel.
- Items marked “author’s recommendation” are not legal requirements.
A. Permitted uses and disclosures
The Privacy Rule lets a covered entity use protected health information (PHI) for treatment, payment and health care operations, and requires authorization for some uses, such as marketing and sale of PHI.
| No. | What to check | Basis |
|---|---|---|
| 1 | For each flow of patient data (including any flow to an AI tool), you can name the basis: treatment, payment or health care operations, a required authorization, or another permitted path. | 45 CFR 164.506(a), (c) |
| 2 | You checked whether any use is marketing, or a disclosure that amounts to a sale of PHI, because those need an authorization (with the exceptions in the text). | 45 CFR 164.508(a)(3), (a)(4) |
| 3 | Minimum necessary is applied: reasonable efforts to limit PHI to what is needed for the purpose, noting the exceptions in § 164.502(b)(2). | 45 CFR 164.502(b) |
| 4 | If data is de-identified before it goes to a tool, the method is documented: expert determination (with the methods and results written down) or removal of the listed identifiers with no actual knowledge that the data could identify a person. | 45 CFR 164.514(b) |
| 5 | All workforce members are trained on PHI policies as needed for their work, and the training is documented. This includes staff who use AI tools. | 45 CFR 164.530(b) |
B. Vendors and business associates
| No. | What to check | Basis |
|---|---|---|
| 6 | For each AI or software vendor, someone has decided whether it is a business associate, by reading the definition against what the vendor actually does with PHI. | 45 CFR 160.103 |
| 7 | Before PHI is disclosed to a business associate, you have satisfactory assurance documented in a written contract that meets § 164.504(e). | 45 CFR 164.502(e)(1)–(2) |
| 8 | The agreement covers: no use or disclosure beyond the contract or the law, safeguards, reporting of unauthorized uses and breaches, subcontractors bound to the same terms, support for access, amendment and accounting, return or destruction at termination if feasible, and your right to terminate for a material violation. | 45 CFR 164.504(e)(2)(i)–(iii) |
| 9 | You asked whether the vendor’s planned use of your data, such as improving its own product, fits within what the contract may permit, and had counsel read the answer. | 45 CFR 164.504(e)(2)(i) |
| 10 | The contract sets a vendor breach-notice period shorter than the 60-day outer limit, lists subcontractors, and says where data is processed and how it is deleted. | Author’s recommendation (not a legal requirement) |
C. Security Rule safeguards
| No. | What to check | Basis |
|---|---|---|
| 11 | A risk analysis covers the electronic PHI the hospital holds, including systems added with an AI tool, and is accurate and thorough. | 45 CFR 164.308(a)(1)(ii)(A) |
| 12 | Security measures reduce the identified risks to a reasonable and appropriate level. | 45 CFR 164.308(a)(1)(ii)(B) |
| 13 | Systems that contain or use ePHI record and examine activity (audit controls), and someone regularly reviews audit logs and access reports. | 45 CFR 164.312(b); 164.308(a)(1)(ii)(D) |
| 14 | The decision on encryption of ePHI is assessed and documented. The current text lists it as an addressable specification. | 45 CFR 164.312(a)(2)(iv) |
| 15 | Policies and required documentation are in writing, kept 6 years from creation or last effective date, and reviewed when operations change. | 45 CFR 164.316(b) |
D. Incidents and breaches
| No. | What to check | Basis |
|---|---|---|
| 16 | There is a procedure to assess an impermissible use or disclosure against the four risk factors, since it is presumed to be a breach unless you can show a low probability of compromise. | 45 CFR 164.402 |
| 17 | The notice clock is known: individuals within 60 calendar days of discovery; HHS at the same time for 500 or more; media for more than 500 residents of a state; an annual log for fewer than 500. | 45 CFR 164.404–164.408 |
| 18 | Discovery is understood as the first day the breach is known, or would have been known with reasonable diligence, to any workforce member or agent. A one-page incident card shows who decides and who files. | 45 CFR 164.404(a)(2); author’s recommendation for the card |
E. Oversight of decision support tools
| No. | What to check | Basis |
|---|---|---|
| 19 | You keep a list of patient care decision support tools that use input variables measuring race, color, national origin, sex, age or disability, and made reasonable efforts to mitigate discrimination risk for each. | 45 CFR 92.210(b)–(c) |
| 20 | Staff know the information blocking standard for providers and the exceptions before refusing to share electronic health information, including with a vendor. | 45 CFR 171.103 |
| 21 | For each clinical decision support product, the vendor has said in writing whether it treats the product as a device or as non-device clinical decision support, and why. | FDA CDS guidance (January 2026) |
How to use it (author’s advice)
- Sort the items into “done,” “not done” and “not sure.” Send the unsure ones to IT, compliance or the vendor.
- Start with section B. It needs the vendor’s input and usually takes the longest.
- Make a one-page incident card. Who decides, who files, where, and the 60-day outer limit, placed where people will find it at night and on weekends.
Questions for vendors are in the templates; records and AI vendors are in the separate checklist.
Frequently asked questions
- How fast must we report a breach?
- Notify affected individuals without unreasonable delay and no later than 60 calendar days after discovery (45 CFR 164.404(b)). For 500 or more individuals, notify HHS at the same time (§ 164.408(b)); for fewer than 500, keep a log and report within 60 days after the end of the calendar year (§ 164.408(c)).
- Can an AI vendor use our patient data to improve its own product?
- It depends on the business associate agreement. The contract may not authorize the business associate to use or further disclose PHI in a way that would violate the Privacy Rule if the hospital did it, with narrow exceptions for the business associate’s own management and administration and for data aggregation (45 CFR 164.504(e)(2)(i)). Ask counsel to read the vendor’s clause against that text.
- Is a business associate agreement needed for every software vendor?
- Only if the vendor is a business associate, which depends on whether it creates, receives, maintains or transmits PHI on your behalf, or provides listed services involving disclosure of PHI (45 CFR 160.103). If it is, § 164.502(e) requires satisfactory assurance documented in a written contract.
Sources and date checked
- eCFR — 45 CFR 164.506 (treatment, payment and health care operations) (opens in a new tab)
- eCFR — 45 CFR 164.508 (uses and disclosures requiring authorization) (opens in a new tab)
- eCFR — 45 CFR 164.502(e) (disclosures to business associates) (opens in a new tab)
- eCFR — 45 CFR 164.504(e) (business associate contracts) (opens in a new tab)
- eCFR — 45 CFR 160.103 (definitions: business associate, covered entity) (opens in a new tab)
- eCFR — 45 CFR 164.514(b) (de-identification) (opens in a new tab)
- eCFR — 45 CFR 164.530 (administrative requirements, including training) (opens in a new tab)
- eCFR — 45 CFR 164.308 (Security Rule: administrative safeguards) (opens in a new tab)
- eCFR — 45 CFR 164.312 (Security Rule: technical safeguards) (opens in a new tab)
- eCFR — 45 CFR 164.316 (Security Rule: policies, procedures and documentation) (opens in a new tab)
- eCFR — 45 CFR 164.402 (breach definition and risk assessment) (opens in a new tab)
- eCFR — 45 CFR 164.404 (notification to individuals) (opens in a new tab)
- eCFR — 45 CFR 164.406 (notification to the media) (opens in a new tab)
- eCFR — 45 CFR 164.408 (notification to the Secretary) (opens in a new tab)
- eCFR — 45 CFR 92.210 (patient care decision support tools) (opens in a new tab)
- eCFR — 45 CFR 171.103 (information blocking) (opens in a new tab)
- FDA — Clinical Decision Support Software, guidance for industry and FDA staff (January 2026) (opens in a new tab)
Sources checked November 6, 2026. Rules and procedures change, so rely on the current text on the official source page.
The material on this site is general information for education. It does not replace diagnosis or medical advice for a specific patient, and it is not legal advice or a purchasing recommendation. For rules and policy, rely on the primary official sources.