A Spreadsheet That Cost a Health System $4.3 Million

In 2019, the University of Rochester Medical Center agreed to a $3 million settlement with HHS after employees stored PHI data on unencrypted flash drives and laptops. Not a sophisticated hack. Not a ransomware gang. Flash drives. The kind your staff might have in a desk drawer right now.

That's the thing about PHI data — most organizations think they understand it, but the gaps in that understanding are exactly where OCR finds violations. If you can't define what PHI is with precision, you can't protect it. And if you can't protect it, you're one lost laptop away from a seven-figure settlement.

This post is your definitive guide to PHI data: what qualifies, what doesn't, the 18 identifiers that matter, and the specific steps your workforce needs to take every single day.

What Exactly Is PHI Data Under HIPAA?

PHI — Protected Health Information — is any individually identifiable health information that a covered entity or its business associates create, receive, maintain, or transmit. That definition comes straight from 45 CFR § 160.103.

Here's the part most people miss: it's not just diagnoses and lab results. PHI data is created the moment health information gets linked to an identifier that could reveal a person's identity. A blood pressure reading by itself? Not PHI. A blood pressure reading attached to a name, date of birth, or medical record number? That's PHI, and HIPAA's full weight applies.

PHI exists in every format — paper charts, verbal conversations, electronic records. When it's in digital form, we call it ePHI, and the HIPAA Security Rule adds an entire layer of administrative, technical, and physical safeguard requirements on top of the Privacy Rule.

The 18 Identifiers That Turn Health Data Into PHI

HHS defined exactly 18 types of identifiers. If health information is linked to any one of these, it qualifies as PHI data. I've seen compliance officers who can only name five or six off the top of their heads. That's a problem. Here's the complete list:

  • Names
  • Geographic data smaller than a state
  • All dates (except year) related to an individual — birth date, admission date, discharge date, date of death
  • 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)
  • Full-face photographs and comparable images
  • Any other unique identifying number, characteristic, or code

That last one is the catch-all, and it's intentionally broad. If your organization assigns a unique patient code, that code is an identifier. Period.

The Identifier Most Teams Overlook

In my experience, IP addresses and device identifiers trip up the most organizations. IT departments log these routinely. If those logs intersect with any health-related system — a patient portal, a telehealth platform, an EHR — you've created PHI data. Your IT team needs to understand this, not just your clinical staff.

What Doesn't Qualify as PHI Data

De-identified data is the key exception. Under the HIPAA Privacy Rule, data is de-identified when all 18 identifiers are removed and the covered entity has no reasonable basis to believe the remaining information could identify an individual. There are two methods to get there: expert determination (a qualified statistician certifies the risk is very small) or safe harbor (strip all 18 identifiers).

Aggregate data used in public health reporting — like "412 patients in County X were diagnosed with influenza in March" — generally doesn't qualify as PHI, as long as no individual could be identified from the data set. But be careful: small population sizes can make even aggregate data identifiable.

Employment records held by a covered entity in its role as an employer also fall outside PHI. Your HR files on a nurse's sick days aren't PHI, even though you're a healthcare organization. The line is subtle but critical.

Where PHI Data Lives (and Where It Hides)

Most compliance programs focus on the EHR. That's necessary but insufficient. In every risk assessment I've conducted, PHI data shows up in places that surprise leadership:

  • Email inboxes — clinicians forwarding lab results to personal accounts
  • Text messages — quick consults between nurses that include patient names
  • Shared drives — old spreadsheets from a research project three years ago
  • Voicemails — callback messages with patient details
  • Printer trays — discharge summaries sitting uncollected for hours
  • Vendor systems — billing platforms, scheduling tools, analytics dashboards

Every one of these locations requires safeguards. If your risk analysis doesn't map every place PHI data flows, it has gaps. And OCR looks for those gaps specifically.

The $5.55 Million Lesson from Advocate Medical Group

In 2016, Advocate Medical Group paid $5.55 million to settle HIPAA violations after multiple breaches exposed the ePHI of approximately 4 million patients. One breach involved stolen laptops from an administrative office. Another involved an unauthorized third party accessing electronic PHI at a business associate's data center.

The root cause wasn't a lack of technology. It was a failure to conduct a comprehensive risk analysis and implement the physical safeguards that analysis would have demanded. OCR's investigation found that Advocate hadn't assessed the risks to ePHI across all its locations and devices.

This is why understanding PHI data isn't an academic exercise. It's the foundation of every safeguard you implement.

How to Protect PHI Data: The Non-Negotiables

1. Conduct a Thorough Risk Analysis

Map every system, device, and workflow that touches PHI data. Not just the EHR — include mobile devices, cloud platforms, paper records, and verbal communications. Update this analysis annually and after any significant change to your environment.

2. Encrypt ePHI at Rest and in Transit

Encryption is an addressable specification under the Security Rule, which doesn't mean optional. It means you must implement it or document why an equivalent alternative is appropriate. In practice, there is almost never a defensible reason not to encrypt.

3. Train Your Entire Workforce

Workforce training under HIPAA isn't limited to clinicians. It covers every person who has access to PHI — front desk staff, IT administrators, billing specialists, volunteers. Everyone. Training must be role-specific and documented. A one-size-fits-all annual slideshow doesn't cut it anymore.

If you're building a training program for clinical staff, our HIPAA training for nurses and clinical workflows covers PHI handling in the specific scenarios your team faces daily — shift handoffs, bedside conversations, and electronic charting.

4. Implement Access Controls

The minimum necessary standard requires that workforce members access only the PHI they need to do their jobs. Role-based access controls in your EHR are a start, but you also need policies governing who can access paper records, shared drives, and communication platforms.

5. Manage Your Business Associates

Every vendor that creates, receives, maintains, or transmits PHI data on your behalf needs a Business Associate Agreement. But the BAA alone isn't enough — you need to verify that your business associates actually implement the safeguards they promise. The Advocate settlement proved what happens when you don't.

What Happens When PHI Data Is Breached?

The HIPAA Breach Notification Rule requires covered entities to notify affected individuals within 60 days of discovering a breach. If the breach affects 500 or more individuals, you must also notify HHS and prominent media outlets in the affected state. HHS publishes these breaches on its public breach portal — often called the "Wall of Shame."

Penalties range from $100 to $50,000 per violation, with annual maximums up to $1.5 million per violation category under the current penalty tiers. State attorneys general can pile on additional actions. And then there's the reputational damage that no dollar amount captures.

PHI Data and the Minimum Necessary Rule: A Quick-Reference Answer

Does HIPAA require you to limit PHI data access? Yes. The minimum necessary standard under the HIPAA Privacy Rule requires covered entities to make reasonable efforts to limit PHI access, use, and disclosure to the minimum amount needed to accomplish the intended purpose. This applies to internal access, routine disclosures to business associates, and requests from other covered entities. It does not apply to disclosures for treatment purposes or disclosures to the individual who is the subject of the PHI.

Build PHI Protection Into Daily Operations

Understanding PHI data isn't a one-time compliance checkbox. It's something your staff needs to apply in every patient interaction, every email, every system login. The organizations that avoid OCR scrutiny aren't the ones with the biggest IT budgets — they're the ones whose workforce members instinctively know what PHI is and how to handle it.

If your team needs structured, role-specific guidance, explore the full course catalog at HIPAACertify to find programs tailored to clinical, administrative, and technical roles.

PHI data protection isn't about perfection. It's about building systems and habits that make the right action the easy action — and making sure every person in your organization knows exactly what's at stake when they don't.