What is PHI (Protected health information)?

Protected health information (PHI) is individually identifiable health information that a HIPAA covered entity or business associate holds or transmits, in electronic, paper, or any other form. It covers information about a person's health, care, or payment for care that identifies them or could reasonably be used to identify them.

HIPAA defines PHI in 45 CFR 160.103 by building on individually identifiable health information. That is health information, including demographic information, that meets three tests. It is created or received by a health care provider, health plan, employer, or health care clearinghouse. It relates to a person's past, present, or future physical or mental health, the care they receive, or payment for that care. And it identifies the person, or there is a reasonable basis to believe it could. When that information is maintained or transmitted in any form or medium, it is PHI. The electronic subset, ePHI, is what the Security Rule protects.

What is not PHI

  • Education records covered by FERPA.
  • Employment records a covered entity holds in its role as an employer.
  • Information about a person who has been dead for more than 50 years.
  • Information that has been de-identified under 45 CFR 164.514, either by an expert determination that the risk of re-identification is very small, or by the safe harbor method of removing 18 listed types of identifiers.

What it means in practice

In a software product, PHI turns up in more places than the patient table. Application logs that print request bodies, analytics events tagged with a user ID, crash reports, push notification text, support tickets with screenshots, and test databases copied from production can all contain it. The safe harbor list is a useful checklist because it is broader than most teams expect: it includes email addresses, phone numbers, medical record numbers, IP addresses, full-face photos, and any other unique identifying number. A dataset that drops names but keeps IP addresses and visit dates is not de-identified under safe harbor.

Whether data is PHI also depends on who holds it. The definition covers information created or received by providers, plans, employers, and clearinghouses, and HIPAA's rules bind covered entities and their business associates. A vendor that processes the data for a covered entity is handling PHI and needs a BAA.

Example

A clinic's reminder service sends a text that reads: "Maria, your cardiology follow-up is Tuesday at 9:00." That message combines a name with information about the care she receives, so it is PHI, and the SMS vendor that transmits it is a business associate. A safer design sends a generic message with a link that opens only after the patient signs in to the portal.