Cookie settings

Necessary, always on: they keep the site working and remember your cookie choice.

Skip to content
Skip to content

Glossary. PHI.

What is PHI (protected health information)?

PHI is identifiable health information HIPAA protects; whether a value is PHI depends on who holds it. One diagnosis can be PHI in one table and not the next.

By Dipal Panchal, co-founder and CEO · Updated November 8, 2026

Health information, a person and a holder

Protected health information (PHI) is individually identifiable health information, in any form, that the HIPAA rules protect when a covered entity or business associate creates, receives, keeps or sends it. Unlike health data under GDPR, which is protected whichever sector holds it, PHI depends on the holder.

The information relates to health, care or payment for care. It identifies the person, or could reasonably be used to, and a covered entity or its business associate holds it. The definitions are in 45 CFR 160.103.

Covered entities and business associates

Covered entities are health plans, health care clearinghouses and health care providers that send health information electronically in connection with HIPAA standard transactions, such as claims. A business associate is a person or company that handles PHI on a covered entity’s behalf, such as a billing service or a cloud host.

A fitness app, an employer’s wellness tracker run outside its group health plan, or a UK clinic that is not a covered entity is outside that list, so the health data it holds isn’t PHI. Other laws can still reach that data, as row 7 in the table below shows for the UK clinic.

Seven values: PHI or not

Records from seven systems, judged against 45 CFR 160.103 and, for row 5, 164.514(b). The Sensitivity column applies a four-level policy scheme, whatever HIPAA says.

Records
SourceLocationDetected typeWhySensitivityDecision
Clinic EHR, US (covered provider)appointments.diagnosis_codeDiagnosis code E11.9 beside a patient IDA health condition, identifiable, held by a covered providerRestrictedPHI
Billing service, US (business associate)claims.claim_lineMember ID, procedure code 99213, amount paidPayment for care, identifiable, handled for a health planRestrictedPHI
Hospital HR system, UShr.employee_sick_leaveA nurse’s sick-note diagnosisExcluded: an employment record the hospital holds as employerConfidentialNot PHI; HR privacy rules still apply
Fitness app, USapp.heart_rate_dailyDaily heart rate linked to an email addressThe app is neither a covered entity nor a business associateRestrictedNot PHI; the FTC Health Breach Notification Rule may apply
Research extract, USresearch.visits_2025Age bands, first three ZIP digits, admission yearAll 18 safe-harbor identifiers removed under 164.514(b)(2), with no actual knowledge leftInternalExcluded as de-identified, if the ZIP areas each hold over 20,000 people
Hospital archive, USarchive.inpatients_1960sTreatment notes, with a recorded date of death in 1968Excluded per person: the death was more than 50 years ago; records with no date of death stay PHIInternalNot PHI
Private clinic, UKclinic.consultationsConsultation notes with an NHS numberNot a covered entity or a business associate of one; UK GDPR Article 9 treats it as health dataRestrictedNot PHI; special category data in the UK

Rows 3 to 7: same data, different holder

In row 3 the same hospital holds PHI in its EHR and non-PHI in its HR system, because the sick note is an employment record held as employer. In row 4, identical heart-rate data would be PHI if a health plan’s business associate held it.

Row 5 holds only if every condition in the safe-harbor list is met. Ages over 89 have to be removed or grouped as 90 or older, and the three-digit ZIP stays only where that area has more than 20,000 people; otherwise it becomes 000.

The rules that attach to PHI

Each provision below applies to covered entities, and most to business associates too. Links go to the eCFR text.

The rules that attach to PHI
RuleProvisionWhat it asks
Privacy Rule45 CFR 164.502Use or disclose PHI only as permitted, with reasonable efforts to limit it to the minimum necessary; some are exempt
Security Rule (technical safeguards)45 CFR 164.312Technical safeguards for electronic PHI: access and audit controls, integrity, authentication, transmission security
Breach Notification Rule45 CFR 164.400–414Notify people of an unsecured PHI breach without unreasonable delay, within 60 calendar days of discovery; others differ
De-identification45 CFR 164.514(b)Expert determination, or removal of the 18 listed identifiers, with no actual knowledge the rest could identify anyone

What the label doesn’t settle

Calling a column PHI doesn’t say who can reach it, whether it is encrypted or whether anyone uses it. It sets which rules apply, and those rules then ask for access controls, audit controls and a breach process.

HIPAA follows status, not geography: a covered entity’s PHI stays PHI when a business associate stores it offshore. A hospital group with clinics in the UK or the Gulf also holds health data under those countries’ laws, and the UK clinic in row 7 is outside HIPAA because it isn’t a covered entity.

Classify by holder first, then by value

Our rule for a mixed estate: decide first which systems belong to a covered entity or business associate, then classify the values inside them. A value-first scan finds diagnosis codes everywhere, while the holder decides which of them are PHI.

Outside those systems, label the same values by the law that does apply, such as UK GDPR Article 9 or the FTC rule. Keep that label in the same field, so one table never carries two schemes.

With IRIS

IRIS finds health and identity values in the sources you connect, among 103 built-in data types for Indian, US and global formats. Capabilities vary by edition.

Where health and identity values sit, by source, table and column, or file: IRIS produces part of this, in the sources you connect.

Evidence mapped to HIPAA: IRIS produces part of this, HIPAA is one of six frameworks IRIS maps; your auditors judge whether a control is met.

Whether you are a covered entity or business associate: Not produced by IRIS.

A de-identification determination under 164.514: Not produced by IRIS.

Explore discovery and classification

Mark every system covered or not

List the systems that hold health values and mark each one: covered entity, business associate, employer record, or outside HIPAA. Any system you can’t mark is the first question for your privacy officer, because nothing inside it can be labeled until it is answered.

For the law-by-law view of personal data, see what is PII. For where PHI collects beyond the EHR, work through the checklist for PHI outside the EHR.

FAQ

What health data teams ask

Protect your brand. Start with your data.

Bring the systems where patient data lands outside your EHR. We’ll show where IRIS finds health and identity values.