A front-desk employee at a dermatology clinic emailed a spreadsheet of patient appointment times to her personal Gmail account so she could "work from home." No diagnoses. No Social Security numbers. Just names, dates, and times. Her employer reported the incident, and OCR opened an investigation that consumed eight months of staff time and legal fees. The kicker? Most of the staff didn't even realize that appointment schedule qualified as protected health information.
So what can PHI consist of? The answer is broader than almost every healthcare worker assumes — and that gap between assumption and reality is where breaches happen.
What Can PHI Consist Of? A Straight Answer
Protected health information is any individually identifiable health information that a covered entity or business associate creates, receives, maintains, or transmits. It covers past, present, and future physical or mental health conditions, the provision of healthcare, and payment for healthcare — as long as it can be tied back to a specific person.
The key phrase is "individually identifiable." A blood pressure reading of 140/90 sitting in a database with no way to connect it to a human being is not PHI. Attach a name, a medical record number, or even a ZIP code to that reading, and it transforms into PHI instantly.
PHI exists in every format: paper charts, electronic health records (ePHI), verbal conversations, faxes, photographs, even voicemail messages. If it identifies a person and relates to their health or healthcare, it's PHI.
The 18 Identifiers That Turn Health Data Into PHI
HHS defines 18 specific identifiers under the HIPAA Privacy Rule's Safe Harbor de-identification method. If any one of these identifiers accompanies health information, you're handling PHI. Here they are:
- Names — full or partial
- Geographic data smaller than a state — street address, city, ZIP code (first three digits are sometimes permitted)
- Dates — 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 or 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 the one that trips organizations up most. I've seen covered entities assume they were safe because they stripped names and dates — but left a unique patient ID code in a research dataset. That code still links back to a person, so the data is still PHI.
The Formats Most People Forget
Verbal PHI
Two nurses discussing a patient's lab results in a hospital elevator are transmitting PHI. No paper. No screen. Still covered. OCR has investigated complaints rooted in overheard conversations, and the Privacy Rule explicitly includes oral communications.
Images and Video
A before-and-after photo taken on a clinician's personal phone is PHI if the patient is identifiable — even if no name is attached. Full-face photos are one of the 18 identifiers. I've consulted with plastic surgery practices that had thousands of patient images stored on unencrypted personal devices. Each photo was a potential breach.
Billing and Payment Records
An explanation of benefits, a billing statement, even a record of a copayment — all PHI. The Privacy Rule covers information related to the payment for healthcare. Your billing department handles just as much PHI as your clinical staff, sometimes more.
Appointment Schedules and Sign-In Sheets
That clipboard at the front desk with patient names and arrival times? PHI. HHS has issued specific guidance on sign-in sheets, permitting them under certain conditions — but the data on those sheets is still protected health information, and organizations must apply reasonable safeguards.
ePHI: The Digital Version With Extra Rules
When PHI exists in electronic form — stored on a server, transmitted via email, saved on a USB drive — it becomes electronic protected health information, or ePHI. The HIPAA Security Rule applies specifically to ePHI and demands administrative, physical, and technical safeguards.
In my experience, ePHI catches organizations off guard because it lives in places they don't expect. Text messages between providers. Cloud-based scheduling tools. Even metadata in a PDF exported from an EHR system. If your workforce doesn't understand what can PHI consist of in electronic form, they can't protect it.
The $1.5 Million Mistake That Started With a Spreadsheet
In 2018, OCR settled with Anthem Inc. for $16 million following a breach affecting nearly 79 million individuals — the largest HIPAA settlement in history. But you don't need a mega-breach to face consequences. In 2013, Idaho State University paid $400,000 to settle with OCR after disabling firewall protections on a server containing ePHI for roughly 10 months, exposing the records of approximately 17,500 patients.
The common thread in every enforcement action I've studied? Someone in the organization didn't fully grasp the scope of what qualifies as PHI. They thought they were handling "just" names. Or "just" appointment data. Or "just" billing codes. Every one of those is PHI when linked to an individual.
PHI vs. De-Identified Data: Where the Line Falls
Data stops being PHI when it's been properly de-identified under one of two methods defined in the Privacy Rule. The Safe Harbor method requires removing all 18 identifiers and having no actual knowledge that the remaining data could identify someone. The Expert Determination method requires a qualified statistical expert to certify that re-identification risk is very small.
Anything short of full de-identification means you're still handling PHI. A "limited data set" — which removes direct identifiers but may retain dates, ZIP codes, and city — is still considered PHI and requires a data use agreement.
Why Your Workforce Training Probably Isn't Covering This
Here's what I see repeatedly: organizations run annual HIPAA training that covers breach notification timelines and password policies but never walks staff through the 18 identifiers. Employees leave those sessions thinking PHI means "medical records" and nothing more.
Your front-desk staff, billing team, IT administrators, and even marketing department all handle PHI in some form. If they can't identify it, they can't safeguard it. That's not a training gap — it's a compliance failure waiting for an OCR complaint to expose it.
If your current workforce training doesn't drill into the specifics of what PHI can consist of, it's time to fix that. Our HIPAA training catalog includes role-based courses that walk every member of your team through these identifiers with real-world scenarios — not abstract definitions.
Three Steps to Close the Gap Today
1. Audit Where PHI Actually Lives
Conduct a data inventory. Map every system, device, and workflow that touches health information. You'll almost certainly find PHI in places your risk assessment didn't account for — shared drives, personal devices, third-party apps.
2. Train by Role, Not by Checkbox
A receptionist and a systems administrator face different PHI risks. Generic training doesn't prepare either of them. Role-specific HIPAA workforce training closes the gap between policy and practice.
3. Test Understanding, Not Attendance
A signature on an attendance sheet proves nothing. Use scenario-based assessments that ask staff to identify PHI in realistic situations. If someone can't spot that an IP address paired with a diagnosis code is PHI, they need more training — not a certificate.
The Bottom Line on What PHI Can Consist Of
PHI is not limited to medical charts and diagnosis codes. It encompasses any information — in any format — that identifies an individual and relates to their health condition, healthcare services, or payment for those services. The 18 identifiers cast a wide net, and the catch-all category makes that net even wider.
Every covered entity and business associate is responsible for ensuring their entire workforce understands this scope. OCR doesn't accept "we didn't know that was PHI" as a defense. The enforcement record proves it.
Your next step is straightforward: make sure every person in your organization who touches patient data — clinical or not — can answer the question "what can PHI consist of" without hesitating. That single competency prevents more breaches than any firewall or encryption tool you'll ever deploy.