Does a data lake copy need its own row?
Yes. The risk analysis (§ 164.308(a)(1)(ii)(A)) covers all ePHI you create, receive, maintain or transmit (§ 164.306(a)(1)), so analytics, test and support copies count.
HIPAA. ePHI inventory.
A risk analysis is only as complete as its list of ePHI locations; the copies outside the EHR, in analytics, test and backups, are where it falls short.
By Dipal Panchal, co-founder and CEO · Last reviewed: November 8, 2026
HIPAA’s Privacy, Security and Breach Notification Rules (45 CFR Parts 160 and 164) apply to covered entities: health plans, clearinghouses and providers that send standard transactions, such as claims, electronically (§ 160.103). Business associates that handle protected health information for them are covered too.
The HHS Office for Civil Rights handles enforcement. The Security Rule has applied since April 20, 2005, and since April 20, 2006 for small health plans (§ 164.318).
Protected health information is individually identifiable health information in any form; ePHI is the electronic part the Security Rule governs. This page is general information, not legal advice.
Where ePHI turned up in one clinic group’s systems outside the EHR. The risk analysis in § 164.308(a)(1)(ii)(A) covers all ePHI you create, receive, maintain or transmit (§ 164.306(a)(1)).
| Value | Detected type | Label | Reason | Kept or rejected |
|---|---|---|---|---|
| MRN 00482915 in analytics.patients | Medical record number | PHI: safe-harbor identifier, § 164.514(b)(2)(i)(H) | Copied from the EHR into an analytics schema | Kept |
| 1EG4-TE5-MK73 in billing.members | Medicare Beneficiary Identifier | PHI: beneficiary number, (b)(2)(i)(I) | CMS’s published example value, in a billing table | Kept |
| E11.9 beside patient_id in support.tickets | Diagnosis code (ICD-10) | PHI | A support ticket copied a diagnosis next to the patient ID | Kept |
| Admitted March 14 in lake.encounters | Admission date | PHI: a date other than the year, (b)(2)(i)(C) | Dates tied to a patient must go for safe-harbor de-identification | Kept |
| 203.0.113.24 in portal.access_log | IP address | PHI: safe-harbor identifier, (b)(2)(i)(O) | The portal log ties each address to a patient session | Kept |
| jdoe@example.com in test_db.patients | Email address | PHI in a test copy | A restored backup in a test database still holds real records | Kept |
| 1234567893 in directory.npi | National Provider Identifier | Not PHI here | It names a clinician in a provider directory, not a patient | Rejected |
Columns one to three are the regulation, pinpointed. The record column recommends what an OCR investigator or assessor can test: date, owner, source system.
| Section | What it requires | Time limit or amount | Record that shows it |
|---|---|---|---|
| § 164.308(a)(1)(ii)(A) risk analysis | A thorough assessment of the risks to all ePHI you create, receive, maintain or transmit. | Documentation kept six years (§ 164.316(b)(2)(i)) | An ePHI inventory by system, with the date each system was checked |
| § 164.308(a)(1)(ii)(D) activity review | Regularly review records of system activity, such as audit logs and access reports. | No fixed interval in the rule | Review records with dates and the reviewer’s name |
| § 164.308(a)(4) and § 164.312(a)(1) access | Authorize access to ePHI, and limit it to the people and software that need it. | No time limit in the rule | A dated map of who can reach each ePHI store, and the approval behind each grant |
| § 164.312(a)(2)(iv) and (e)(2)(ii) | Addressable: encrypt ePHI where reasonable and appropriate, or record why not and what you use instead. | A documented decision per system | A dated check of each store’s protection state, beside the signed decision record |
| § 164.404(b), § 164.406 and § 164.408 breach notice | Notify individuals, HHS and the media (over 500 in a state); business associates tell you within sixty days (§ 164.410). | Without unreasonable delay, within sixty days of discovery; HHS too if 500 or more, else sixty days after year end | The breach risk assessment, discovery and notice dates, and a dated list of the PHI the system held |
| § 164.524 right of access | Give individuals access to their PHI in a designated record set. | Thirty days from the request, with one thirty-day extension (§ 164.524(b)(2)) | A search record of the record sets searched, with request, extension and reply dates |
| § 164.514(b)(2) safe harbor | Safe harbor: all listed identifiers gone and no actual knowledge the rest identifies anyone; or expert determination. | Before data is released as de-identified | A dated identifier check per dataset, and the sign-off that no actual knowledge of identity remains |
| § 160.404(b) and § 102.3 penalties | Under 45 CFR 102.3: $145 to $73,011 per violation in lower tiers; $73,011 to $2,190,294 for uncorrected willful neglect. | Adjusted at 91 FR 3665, January 28, 2026 | Not a record: identical violations are capped at $2,190,294 a calendar year (45 CFR 102.3) |
Yes. The risk analysis (§ 164.308(a)(1)(ii)(A)) covers all ePHI you create, receive, maintain or transmit (§ 164.306(a)(1)), so analytics, test and support copies count.
Not a reportable one if the ePHI was encrypted to HHS’s guidance and the key wasn’t with it. Secured PHI falls outside the notice rules (§ 164.402).
Not by default. As I’ve written, a logged read supports access and a recorded transfer may support disclosure. Without logs, § 164.402 presumes a breach unless you show otherwise.
Lower per-tier caps for the three lower tiers. HHS has applied them as enforcement discretion since 2019 (84 FR 18151), below the $2,190,294 cap in 45 CFR 102.3.
Checked on the Federal Register, eCFR and hhs.gov on November 8, 2026. Next review by February 6, 2027, or when HHS finalizes a rule.
| Item | Status | Instrument |
|---|---|---|
| Security Rule | In force as amended through 2013; unchanged by the 2025 proposal | 45 CFR Part 164, Subpart C |
| Security Rule proposal | Proposed January 6, 2025; not final | 90 FR 898, RIN 0945-AA22 |
| Penalty amounts | Last adjusted January 28, 2026, with the 2025 multiplier; no later adjustment published | 91 FR 3665 |
| Per-tier annual caps | Still applied as enforcement discretion; not withdrawn | 84 FR 18151, April 30, 2019 |
| Reproductive health care rule (2024) | Vacated June 18, 2025, except most of its notice of privacy practices changes | Purl v. HHS, No. 2:24-cv-00228-Z (N.D. Tex.) |
| Privacy Rule proposal (2021) | Not final; a final rule listed for August 2026 isn’t out. It would cut the § 164.524 deadline to fifteen days | 86 FR 6446, RIN 0945-AA00 |
| 42 CFR Part 2 alignment rule | Compliance required since February 16, 2026 | 89 FR 12472, February 16, 2024 |
| Review | Editorial review by Sylox; not reviewed by a lawyer | Last reviewed November 8, 2026 |
HIPAA is one of the frameworks IRIS scores, and IRIS certifies nothing. Mapping shows relevance; your auditors judge whether a control is met. Capabilities vary by edition.
§ 164.308(a)(1)(ii)(A): where ePHI sits, copies included: IRIS produces part of this, for the sources you connect and the data types IRIS detects, such as NPI and Medicare numbers.
§ 164.308(a)(4): who can reach each ePHI store: IRIS produces part of this, where the source exposes permission data.
§ 164.312(a)(2)(iv): the protection state behind each decision: IRIS produces part of this, checks sampled values for encryption, masking or hashing, once activated on your install.
§ 164.524: the search of designated record sets: IRIS produces part of this, connected databases only, not files or mailboxes; the change happens in the source system.
§ 164.316: what each scan covered and couldn’t read: IRIS produces this.
HIPAA controls: where evidence is present, missing or deferred: IRIS produces this.
Explore evidenceOur recommended order of work; the rule sets the scope and leaves the method to you. The checklist for PHI outside the EHR covers the copies teams miss.
Where PHI hides in analytics, test and support systems, and how to find each copy.
Protected health information, the safe-harbor identifiers and where HIPAA stops.
Evidence on sensitive data that traces to a source, table and scan date.
Yes. IRIS maps findings to HIPAA controls and shows where evidence for each is present, missing or deferred. The assessment of whether a control is met stays with your auditor.
NPIs, checked with the Luhn method on the 80840 prefix, Medicare Beneficiary Identifiers and medical record numbers, among others. MRN formats differ by organization, so a custom pattern for yours sharpens detection.
IRIS reads the audit log of each supported source and shows who accessed PHI and when, where the source keeps one. The source remains the system of record. IRIS supports the activity review in § 164.308(a)(1)(ii)(D) and doesn’t replace the source’s logging.
No, not today. If your HIPAA program requires one from every vendor, raise it during scoping, before any scan.
Start the ePHI inventory with one system: a free assessment scans one database with a read-only login you create.