It is any use or disclosure of individually identifiable health information by a covered entity or business associate in connection with health care, payment, or health-care operations. Opening a record, discussing care, billing an account, or transmitting data through a service can qualify.
This overview explains how you can identify PHI, evaluate linked data, distinguish ePHI from de-identified information, and apply HIPAA requirements in clinical, administrative, research, and vendor settings.
PHI Within the HIPAA Framework
A patient’s name beside a diagnosis is the clearest example of protected data, but HIPAA coverage does not depend on seeing the word “medical” on a screen. The information’s content, context, holder, and connection to a covered function determine whether protections apply.
Protected Health Information, or PHI, is individually identifiable health information that a covered entity or business associate holds or transmits in connection with specified functions. Those functions include providing health care, conducting financial activities, and handling health-care operations.
A covered entity is generally a health plan, health-care clearinghouse, or provider that transmits health information in a covered electronic format. A business associate performs services involving PHI for a covered entity and must operate within the contractual and regulatory safeguards that govern that relationship.
Two rules with different jobs
| HIPAA rule | What it governs | Practical focus |
|---|---|---|
| HIPAA Privacy Rule | Uses and disclosures of PHI | Whether a purpose is permitted |
| HIPAA Security Rule | Electronic Protected Health Information safeguards | How systems and electronic information are protected |
Permission to handle a record does not prevent a Security Rule violation when the record travels through an insecure channel. The Privacy Rule governs what may happen to information, while the Security Rule protects its availability, privacy, and integrity from improper access.
Federal privacy, security, and breach-notification duties apply across health plans, providers, clearinghouses, and the systems they use. Oversight comes from the U.S. Department of Health and Human Services through its Office for Civil Rights. The HITECH Act strengthened protections for electronic health records and related systems.
Information That Can Qualify as PHI
An appointment without a visible patient name can still contain identifying details. Your organization may recognize the date, clinic, reason for the visit, and referring physician. That practical recognition can be enough for the appointment to remain protected information.
Clinical and administrative records can both qualify. A medical record number may reveal little on its own, yet it can connect a lab result to one person inside a hospital system. An insurance identifier can link services, coverage, and payments across a payer’s records.
| Information category | Concrete example | Why it matters |
|---|---|---|
| Medical records | Diagnosis with a patient name | Connects clinical details to a person |
| Appointment details | Clinic, date, and visit reason | May identify a patient through context |
| Billing information | Invoice tied to an account number | Links services and payments to a person |
| Insurance identifiers | Member number on a claim | Connects coverage to an individual |
| Oral communications | Care discussion at a pharmacy counter | Reveals PHI without an electronic record |
Names, street addresses, telephone numbers, email addresses, medical record numbers, account numbers, and identifying dates fall within the 18 identifier categories recognized by the Privacy Rule. A year may still identify someone when it combines with a rare condition and a small clinic population.
Classify a record by its practical identifiability rather than by counting visible direct identifiers. A device serial number tied to a glucose-monitoring account can reveal a user’s health information without displaying that user’s name anywhere on the screen.
Identifiability and Data Linkage
Removing a name does not automatically make a record anonymous. A research table containing ZIP code, age, a rare diagnosis, and an employer could identify a worker through a small set of distinguishing characteristics.
The 18 identifiers include names, geographic details smaller than a state, dates tied to a person, telephone numbers, email addresses, social media accounts, URLs, IP addresses, device identifiers, and biographical identifiers. They also cover other unique numbers, characteristics, or codes.
Data linkage occurs when separate information makes a record identifiable. A clinic schedule combined with a family member’s account can reveal who attended a visit. A manufacturer name and serial number can link device readings to a customer, while a workplace incident report can connect an injury to an employee.
| De-identification route | Core requirement | Key caution |
|---|---|---|
| Safe Harbor | Remove the specified identifiers and meet related conditions | No actual knowledge that the remaining information could identify a person |
| Expert Determination | A qualified expert evaluates and documents re-identification risk | Removing a name alone is not enough |
Hiding a patient’s name satisfies neither route by itself. Safe Harbor follows a defined removal method. Expert Determination relies on a qualified expert’s analysis of the likelihood that someone could identify an individual from the remaining information.
Both routes affect whether de-identified information remains PHI under the Privacy Rule. Safe Harbor requires removal of specified identifiers and satisfaction of related conditions, including no actual knowledge of a re-identification route. Expert Determination requires a statistical and scientific analysis of the remaining information’s risk.
Once removal is attempted, the resulting records must still be classified correctly under HIPAA.
Before releasing a data set, check whether it can be matched with payroll records, public notices, clinic schedules, or other outside facts. Context can restore a name after the original file has lost it.
PHI, ePHI, and De-Identified Information
A device serial number can reveal who owns a glucose-monitoring account. That link connects a unique identifier to health information even when the record contains no visible name, which means the information may not satisfy a de-identification standard.
A voice conversation at a nursing station may contain PHI even when no computer is involved. Format does not control coverage. Individual identifiability and involvement of a covered organization or its business associate remain central.
Electronic Protected Health Information, or ePHI, is PHI created, received, maintained, or transmitted electronically. An electronic health record, patient portal message, emailed appointment, scanned document, or connected glucose monitor can each contain ePHI. A paper chart remains PHI, but it falls outside the Security Rule’s specific electronic safeguards.
Proper de-identification can move information outside the Privacy Rule’s de-identification requirements. That status depends on meeting Safe Harbor or Expert Determination. It does not guarantee that nobody can reconnect the data, especially when another dataset contains matching details.
- Paper records remain PHI. A signed intake form stays protected when you store it in a locked file cabinet.
- Oral disclosures can involve PHI. A nurse’s hallway conversation can contain protected details without creating an electronic record.
- Digital images can be ePHI. A scan linked to a patient account may be protected even without a diagnosis typed into the file.
- De-identified datasets lack protected status. Properly processed information falls outside HIPAA protection, although linkage can still create a privacy risk.
- Re-identification restores protection. Linking anonymous data to a person establishes that person’s identity and requires strict control.
Source and linkage controls should remain in place after de-identification. A key stored beside a file labeled “de-identified” can recreate the link the transformation was meant to remove. Governance matters because you must govern the file, lookup key, and recipients together.
HIPAA-Permitted Uses and Disclosures
A connected glucose-monitoring account shows why context matters after direct identifiers disappear. Once a record identifies an individual, you need a permitted basis for handling it and controls proportionate to the activity.
Checking a chart before a patient arrives is a common treatment activity, but employment in the same building does not justify access. Each access needs a permitted purpose, suitable role-based access, and a reason connected to the worker’s assigned duties.
HIPAA permits specified activities without separate patient authorization. These permissions occupy narrow categories rather than creating blanket access. A close connection to treatment, payment, or healthcare operations makes an activity more likely to fall within one of them.
| Category | Example activity | Typical boundary |
|---|---|---|
| Treatment | A clinician reviews records for care | Used by a provider for care delivery |
| Payment | A billing team validates a claim | Used to obtain or provide payment |
| Healthcare operations | A quality reviewer examines workflows | Supports operations connected to health care |
| Public health | Required information is reported to public authorities | Scope and legal authority control |
| Research | A study uses a de-identified data set | An agreement, waiver, or another legal basis may apply |
Treatment, payment, and healthcare operations are not interchangeable labels. A clinician reviews a chart to provide care, a billing worker accesses payment data, and an operations employee examines workflow records for a legitimate organizational purpose rather than curiosity, marketing, or an unrelated business need.
A business associate may handle PHI only while performing services for the covered entity and under safeguards established by a written contract. A cloud host, transcription company, or electronic health record software vendor can perform that role. Each party’s actual functions determine its obligations.
Activities outside a permitted category may require patient permission, a specific legal exception, or a documented analysis under another applicable law. Public-health reporting, certain law-enforcement requests, and legally required disclosures can involve different standards. You should not apply one broad exception across all of them.
When you assess HIPAA-permitted uses and disclosures, document the purpose, recipient, information involved, and legal basis. Those four details help distinguish authorized care activity from curiosity, marketing, or another unrelated use.
Even an authorized disclosure must be limited to the information reasonably needed for its documented purpose.
Applying the Minimum Necessary Standard
Access to a full chart is rarely necessary for every task involving it. A scheduling worker may need an appointment time, while a billing specialist may need service and payment details without the full clinical note. The minimum necessary standard turns that distinction into a workflow.
The standard limits how much PHI a workforce member or business associate may use, access, or disclose for the stated purpose. It applies broadly, although its details vary by context. Treatment receives a specific Privacy Rule approach for evaluating need; other permitted uses require consideration of whether information could reasonably be limited.
The minimum necessary standard for PHI use does not require you to discard useful context automatically. You still need enough information to perform the task. Unrelated notes, dates, identifiers, attachments, and conversation details can expose more than the job requires.
A repeatable review workflow
- State the purpose. Identify whether the task concerns care, payment, operations, research, reporting, or another documented activity.
- Identify the data owner. Determine which person or role needs access and what relationship that person has to the task.
- Limit the fields. Remove unrelated notes, dates, identifiers, attachments, and conversation details from the view or request.
- Record the exception. Document why broader access is needed, along with the person approving the exception and its duration.
- Review the pattern. Examine access logs for unusual volume, unrelated records, repeated searches, or repeated exceptions.
Safeguards must cover the full life of the information, not only the electronic health record. Paper documents need controlled storage and disposal. Verbal disclosures need privacy-conscious settings. Shared systems need role-based access, reliable user accounts, and prompt removal of access when a job changes.
Secure transmission matters too. Verify the destination, use a permitted channel, limit attachments, and avoid sending more information than the recipient needs. Keep records only as long as your organization’s approved retention schedule allows, then dispose of paper and electronic copies through appropriate processes.
Audit the reason behind unusual access, not only the user’s credentials. A person with proper login rights can still create a privacy problem by opening records that have no connection to the assigned task.
Suspected loss or improper access needs a prompt response. Preserve logs, contain the affected system, notify the responsible privacy and security teams, and follow the organization’s incident-response process. Office for Civil Rights guidance addresses breach notification, while the HITECH Act adds notice obligations for qualifying electronic records.
Final Check Before You Use Health Data
HIPAA applies when a covered entity or business associate handles individually identifiable health information through paper, speech, or software. Before acting, determine who handles the data, why they handle it, which information is involved, what legal basis applies, and how access should be limited.
Correct classification depends on practical identifiability rather than the label applied to a file. Properly de-identification changes HIPAA status, but linkage risks remain. Secure handling then depends on permitted purpose, minimum necessary access, appropriate safeguards, and accountability for unusual activity.
FAQ
What constitutes the use of PHI under HIPAA?
It is the use or disclosure of individually identifiable health information by a covered entity or business associate in connection with health care, payment, or health-care operations. Opening, creating, maintaining, disclosing, or transmitting the information can qualify.
What types of information qualify as protected health information?
Diagnoses, lab results, appointments, billing records, insurance identifiers, account numbers, and oral care discussions qualify as protected health information when they identify a person. Identifying dates, device identifiers, and contextual details can also connect health information to an individual.
Does PHI include information that does not directly identify a person?
Yes. Information without a visible name can remain PHI when a covered entity or business associate can recognize the individual through a medical record number, account number, device identifier, dates, clinic, or other context. Practical identifiability matters more than the number of direct identifiers shown.
When can health information be combined with other data to become PHI?
Health information can become identifiable when another dataset supplies a missing name, account, date, location, employer, device number, or distinguishing fact. A clinic schedule combined with a family member’s account, for example, can reveal who attended an appointment.
How do the HIPAA 18 identifiers affect whether information is PHI?
The 18 identifiers are central to the Safe Harbor de-identification standard. They include names, contact details, geographic subdivisions, identifying dates, account and device numbers, URLs, IP addresses, biographical identifiers, and other unique codes. Safe Harbor also requires related conditions and no actual knowledge of a re-identification route.
What is the difference between PHI, ePHI, and de-identified health information?
PHI is individually identifiable health information held or transmitted by a covered entity or business associate in connection with specified functions. Electronic Protected Health Information is the electronic subset of PHI. Properly de-identified information falls outside the Privacy Rule’s de-identification requirements after Safe Harbor or Expert Determination.
