What Are Patient Identifiers? Definition, Examples, and HIPAA’s 18 Identifiers

Check out the new compliance progress tracker


Product Pricing Demo Video Free HIPAA Training
LATEST
video thumbnail
Admin Dashboard Walkthrough Jake guides you step-by-step through the process of achieving HIPAA compliance
Ready to get started? Book a demo with our team
Talk to an expert

What Are Patient Identifiers? Definition, Examples, and HIPAA’s 18 Identifiers

Kevin Henry

HIPAA

August 14, 2025

6 minutes read
Share this article
What Are Patient Identifiers? Definition, Examples, and HIPAA’s 18 Identifiers

Definition of Patient Identifiers

Patient identifiers are data elements that single out, trace, or can reasonably be used to identify an individual who receives care. When such elements relate to health status, treatment, or payment, they form Protected Health Information (PHI) under the Health Insurance Portability and Accountability Act.

Identifiers include obvious items like names and Social Security numbers, as well as indirect or quasi-identifiers such as dates and small-area locations. They also cover Unique Identifying Codes—think medical record numbers, device serials, and study subject IDs—that consistently link records back to the same person.

In practice, you use patient identifiers to match records across systems, avoid mix-ups, and coordinate care. The same elements, however, heighten privacy risk and therefore trigger stringent HIPAA requirements.

Overview of HIPAA’s 18 Identifiers

HIPAA’s de-identification Safe Harbor lists 18 specific identifiers that must be removed for data to be considered de-identified. These are:

  1. Names.
  2. Geographic subdivisions smaller than a state (street address, city, county, precinct, ZIP code, and similar geocodes).
  3. All elements of dates (except year) directly related to an individual (e.g., birth, admission, discharge, death), and all ages over 89 and related date elements.
  4. Telephone numbers.
  5. Fax numbers.
  6. Email addresses.
  7. Social Security numbers.
  8. Medical record numbers.
  9. Health plan beneficiary numbers.
  10. Account numbers.
  11. Certificate/license numbers.
  12. Vehicle identifiers and serial numbers, including license plates.
  13. Device identifiers and serial numbers.
  14. Web URLs.
  15. IP addresses.
  16. Biometric identifiers (e.g., finger and voice prints).
  17. Full-face photographs and comparable images.
  18. Any other unique identifying number, characteristic, or code.

Safe Harbor nuances

  • ZIP codes: You may retain only the first three digits if the population of the combined 3‑digit area exceeds 20,000; otherwise, use 000.
  • Dates: You must remove all elements except the year. For individuals aged 90 and older, aggregate to a single “90 or older” category and omit related years.

Purpose of Patient Identifiers

Patient identifiers enable accurate patient matching, reduce clinical errors, and support continuity of care across hospitals, clinics, labs, and pharmacies. They help you reconcile medications, retrieve prior results, and ensure that critical alerts reach the right person.

Operationally, identifiers support billing, eligibility checks, referrals, and public health reporting. In analytics, consistent identifiers allow longitudinal outcomes tracking—provided De-Identification Standards or appropriate safeguards keep privacy risks low.

Ready to simplify HIPAA compliance?

Join thousands of organizations that trust Accountable to manage their compliance needs.

De-Identification Process

HIPAA recognizes two routes to render data no longer PHI. Under Safe Harbor, you remove all 18 identifiers and avoid any actual knowledge that remaining data could identify a person. This method is prescriptive and straightforward to implement.

Under Expert Determination, a qualified expert applies accepted statistical methods to show a very small risk of re-identification. This path may preserve more utility (for example, certain dates or locations) while meeting De-Identification Standards through risk controls and documentation.

Practical steps

  • Map data elements to the 18 identifiers and purge or generalize them (e.g., month/day to year; exact address to state).
  • Aggregate outliers (e.g., advanced ages) and coarsen small-area geography.
  • Use pseudonyms or tokens not derived from PHI for record linkage; store the key separately per HIPAA re-identification rules.
  • When a Limited Data Set is appropriate, remove direct identifiers and execute a data use agreement to define permitted uses and safeguards.
  • Continuously monitor re-identification risk as datasets evolve or are combined.

Importance of HIPAA Compliance

Compliance with the Health Insurance Portability and Accountability Act protects patients, reduces breach risk, and avoids civil and criminal penalties. It also supports trust with partners and payers who expect strong governance around PHI and ePHI.

Embedding “minimum necessary” access, robust auditing, and prompt incident response aligns clinical operations with privacy-by-design. Clear policies and training keep your workforce aligned with evolving requirements and organizational Privacy Safeguards.

Examples of Patient Identifiers

  • Medical Record Numbers on lab labels that tie specimens to a specific individual.
  • Health plan beneficiary numbers and account numbers on insurance claims.
  • Biometric Identifiers used for check-in, such as voice prints or fingerprint scans.
  • Device serial numbers from home monitoring equipment linked to a patient profile.
  • IP addresses and web URLs captured by a patient portal session tied to PHI.
  • Full-face photos within telehealth recordings or clinical photography.
  • Dates of service coupled with small-area location that could single out a patient in a rare-procedure context.

Safeguards for Patient Information

Administrative safeguards

  • Perform risk analyses; maintain policies for PHI handling, retention, and disposal.
  • Apply role-based, minimum-necessary access; vet vendors and execute BAAs.
  • Train workforce routinely; test incident response and breach notification plans.

Technical safeguards

  • Encrypt ePHI in transit and at rest; enforce MFA and strong authentication.
  • Implement least-privilege, network segmentation, and timely patching.
  • Monitor with audit logs, anomaly detection, and DLP; secure APIs and integrations.

Physical safeguards

  • Control facility access; secure servers, workstations, and removable media.
  • Use privacy screens, locked storage, and documented device sanitation and destruction.

Summary

Patient identifiers power safe, connected care—but they also elevate privacy risk. By understanding HIPAA’s 18 identifiers, applying rigorous de-identification, and enforcing layered Privacy Safeguards, you protect individuals while preserving data utility.

FAQs

What constitutes a patient identifier?

A patient identifier is any data element that directly identifies an individual (like a name, SSN, or Medical Record Number) or can reasonably be used to identify them when combined with other data (such as full dates, small-area locations, IP addresses, or Unique Identifying Codes).

How does HIPAA define protected health information?

HIPAA defines Protected Health Information as individually identifiable health information—relating to a person’s past, present, or future health, care, or payment—that is created, received, maintained, or transmitted by a covered entity or business associate. It includes the 18 identifiers when linked to health-related content.

What is the significance of de-identifying patient data?

Proper de-identification removes or minimizes identifiers so the data no longer qualifies as PHI under HIPAA. This reduces privacy risk, enables broader research and quality improvement, and allows data sharing without patient authorization, provided de-identification is done and governed correctly.

How can healthcare providers ensure compliance with HIPAA regulations?

Conduct risk assessments, adopt written policies, and train staff. Enforce minimum-necessary access, MFA, and encryption; log and review access; manage vendors with BAAs; apply De-Identification Standards where appropriate; and test incident response and breach notification processes regularly.

Share this article

Ready to simplify HIPAA compliance?

Join thousands of organizations that trust Accountable to manage their compliance needs.

Related Articles