A hospital employee in Texas once emailed a spreadsheet of patient names, dates of birth, and diagnosis codes to her personal Gmail account so she could "finish some work at home." That single email triggered a breach investigation, a six-figure settlement with OCR, and the end of her career. The kicker? She had no idea the spreadsheet contained protected health information. She thought PHI only meant medical records.
If you're searching for what information is included in PHI, you're asking the right question — and you're already ahead of that employee. PHI is broader than most people think. It's not just charts and lab results. It's any information that connects a person's identity to their health care, and the list of qualifying identifiers is specific, enumerated, and enforced with real penalties.
Let me walk you through every element.
What Information Is Included in PHI? The 18 Identifiers That Matter
The HIPAA Privacy Rule, codified at 45 CFR Part 164 Subpart E, defines protected health information as individually identifiable health information held or transmitted by a covered entity or its business associates. HHS breaks this down into 18 specific identifiers.
Here's the full list. If any of these data elements are linked to a person's health condition, health care services, or payment for health care, it's PHI:
- Names — first, last, maiden, or any other.
- Geographic data smaller than a state — street addresses, cities, counties, ZIP codes (the first three digits are allowed only if the ZIP covers more than 20,000 people).
- Dates directly related to the individual — birth date, admission date, discharge date, date of death, and all ages over 89.
- Phone numbers
- Fax numbers
- Email addresses
- Social Security numbers
- Medical record numbers
- Health plan beneficiary numbers
- Account numbers
- Certificate/license numbers
- Vehicle identifiers and serial numbers (including license plates)
- Device identifiers and serial numbers
- Web URLs
- IP addresses
- Biometric identifiers (fingerprints, voiceprints, retinal scans)
- Full-face photographs and comparable images
- Any other unique identifying number, characteristic, or code
That last catch-all is intentional. HHS designed it so you can't create a workaround identifier and claim it's not PHI.
The Part Most People Get Wrong: It's the Link That Creates PHI
A diagnosis code sitting alone in a database isn't PHI. A name in a phone book isn't PHI. But the moment you combine a name — or any of those 18 identifiers — with health information, it becomes PHI.
Here's a practical example. "Patient has Type 2 diabetes" is clinical information but not PHI by itself. "John Martinez, DOB 03/15/1978, has Type 2 diabetes" is absolutely PHI. The linkage between identity and health data is what triggers HIPAA's protections.
This distinction matters because your workforce handles linked data constantly — in scheduling systems, billing platforms, EHRs, even voicemail messages. If your staff doesn't understand what information is included in PHI, they can't protect it. That's why foundational courses like our HIPAA Introduction Training 2026 spend significant time on identifier recognition before moving to safeguards.
Electronic PHI: The Same Rules, Higher Stakes
When any of these identifiers exist in electronic form — in an EHR, a text message, a cloud backup, an email attachment — it becomes ePHI. The HIPAA Security Rule at 45 CFR Parts 160 and 164 adds an entire layer of technical, administrative, and physical safeguards specifically for ePHI.
In my experience, ePHI is where most breaches happen. Lost laptops, unencrypted USB drives, misconfigured cloud storage, and yes — personal email accounts. OCR's enforcement history is packed with cases where organizations knew the Privacy Rule but failed on the Security Rule side.
The Anthem Breach: 78.8 Million Records
In 2018, Anthem Inc. paid $16 million to settle HIPAA violations after hackers accessed ePHI for nearly 78.8 million individuals. The compromised data included names, dates of birth, Social Security numbers, and health plan ID numbers — four of the 18 identifiers linked to health plan enrollment. That's PHI. That's what triggered the largest HIPAA settlement in history at the time.
Anthem's failure wasn't a mystery. OCR found insufficient access controls and a lack of enterprise-wide risk analysis. The identifiers were there. The protections weren't.
What Doesn't Count as PHI? Drawing the Line
Not everything a covered entity touches is PHI. Understanding the boundaries is just as important as knowing the identifiers.
Employment Records
If your organization is both a covered entity and an employer, the health information in employment records — workers' comp claims, drug test results for hiring purposes, sick leave documentation — is generally not PHI under HIPAA. These records are governed by other laws like the ADA and FMLA, not the Privacy Rule.
De-Identified Data
Data that has been stripped of all 18 identifiers — with no reasonable basis to re-identify individuals — is no longer PHI. The Privacy Rule outlines two methods for de-identification: expert determination and safe harbor. Under the safe harbor method, you must remove every single one of those 18 identifiers and have no actual knowledge the remaining information could identify someone.
Education Records
Student health records covered by FERPA are excluded from HIPAA's definition of PHI, even if they contain health information. This catches some university health centers off guard.
The $1.5 Million Question Your Billing Department Should Answer
In 2018, OCR settled with Filefax, Inc. for $100,000 after PHI — including names, Social Security numbers, and medical information — was found abandoned at a shredding facility. The records were never properly destroyed.
Your billing team, your front desk staff, your IT contractors — they all handle PHI daily. The question isn't whether they touch it. The question is whether they can identify it. If someone in your organization thinks a patient's name on a scheduling whiteboard isn't PHI because it's not "in a chart," you have a training gap.
Closing that gap is exactly what structured workforce training is designed to do. Our HIPAA Fundamentals course walks staff through identifier recognition, real-world scenarios, and the kind of edge cases that lead to breaches.
How PHI Applies to Business Associates
If your organization shares any of those 18 identifiers linked to health information with a third party — an IT vendor, a billing company, a cloud storage provider — that third party is likely a business associate under HIPAA. The same PHI protections apply. The same penalties apply.
OCR has made this crystal clear through enforcement. In 2020, CHSPSC LLC, a business associate providing IT services to Community Health Systems, paid $2.3 million after a breach exposed the ePHI of over 6 million individuals. Business associates don't get a pass.
Quick-Reference: Is It PHI?
Ask yourself three questions:
- Does the information include one or more of the 18 identifiers?
- Is it linked to a person's health condition, health care provision, or payment for health care?
- Is it held or transmitted by a covered entity or business associate?
If the answer to all three is yes, it's PHI. Full stop. Protect it accordingly.
What You Should Do Right Now
Audit your workflows. Walk through your front desk, your billing cycle, your IT systems, and your HR files. Map where each of the 18 identifiers shows up. Then ask: does everyone who touches this data know it's PHI?
If the answer is "probably" or "I think so," that's not good enough. OCR doesn't accept "probably" as a defense. They look for documented training, written policies, and evidence that your workforce understands exactly what information is included in PHI.
Start with structured training. Browse the full HIPAA training catalog and get your team aligned before your next risk assessment — or your next OCR audit — forces the issue.
The 18 identifiers aren't suggestions. They're the legal boundary between compliant operations and a breach notification to HHS. Know them. Teach them. Enforce them.