HIPAA recognizes health information as de-identified when it meets one of two standards in 45 CFR 164.514(b): Expert Determination, in which a qualified expert finds the risk of identifying an individual very small, or Safe Harbor, in which the covered entity removes 18 categories of identifiers and has no actual knowledge that what remains could identify the person [1]. Safe Harbor is the more concrete of the two because the list is fixed, but the list has details that are easy to miss, such as ZIP code limits, dates tied to test results, and a catch-all category at the end.

This post lists all 18 identifiers in the order HHS uses, compares the two methods, covers the rules that trip teams up, explains how Expert Determination works in practice, and shows why de-identification belongs in third-party risk work. Every figure is tied to a numbered source.

The two de-identification methods

Expert Determination requires a person with appropriate knowledge of and experience with generally accepted statistical and scientific methods to determine that the risk of identifying an individual is very small, and to document the methods and results [1]. Safe Harbor requires removal of the 18 listed identifiers for the individual and for the individual's relatives, employers, and household members, plus no actual knowledge that the remaining information could identify the individual [1].

Safe Harbor and Expert Determination compared
FeatureSafe HarborExpert Determination
What it requiresRemove the 18 identifiers for the individual and for relatives, employers, and household membersAn expert finds the risk of identification very small
Who decidesThe covered entity applies the listA person with statistical and scientific expertise
Risk thresholdNone; the list defines the standardNo numeric threshold defines very small
DocumentationKeep a record of the review (recommended)Methods and results documented and available to OCR on request
CredentialNoneNo specific credential; OCR reviews training and experience
Data use agreementNot requiredNot required

‍

The 18 identifiers

HHS labels the Safe Harbor identifiers (A) through (R). The table keeps that order, so each row maps to the regulation [1].

The 18 Safe Harbor identifiers in HHS order
#IdentifierWhat to remove or change
1NamesAll names
2Geographic subdivisions smaller than a stateStreet address, city, county, precinct, ZIP code, and equivalent geocodes; the first three ZIP digits can stay only under the 20,000-person rule
3Dates and agesAll date elements except year that relate directly to the individual, and ages over 89, which can be grouped as 90 or older
4Telephone numbersAll telephone numbers
5Fax numbersAll fax numbers
6Email addressesAll email addresses
7Social Security numbersAll Social Security numbers
8Medical record numbersAll medical record numbers
9Health plan beneficiary numbersAll health plan beneficiary numbers
10Account numbersAll account numbers
11Certificate and license numbersAll certificate and license numbers
12Vehicle identifiers and serial numbersIncluding license plate numbers
13Device identifiers and serial numbersAll device identifiers and serial numbers
14Web URLsAll Web Universal Resource Locators
15IP addressesAll Internet Protocol address numbers
16Biometric identifiersIncluding finger prints and voice prints
17Full-face photographsAnd comparable images
18Any other unique identifying number, characteristic, or codeThe catch-all; the only exception is a permitted re-identification code

‍

The regulation folds ages into the dates item and ends with the catch-all, which is the structure above. A list that counts ages separately has to drop the catch-all to reach 18, and so misses the one category that covers identifiers nobody listed.

Rules that trip teams up

Five rules cause most of the errors in Safe Harbor reviews [1].

Safe Harbor rules that trip teams up
RuleWhat HHS saysCheck before release
ZIP codesThe first three digits can remain only if the combined area has more than 20,000 people, based on current public Census data; otherwise they become 000Check each three-digit prefix against current Census data. HHS lists 17 restricted prefixes from 2000 Census data and warns against relying on that list when newer data exists
DatesOnly the year can remain for dates directly related to the individual; dates tied to test results are PHI and cannot be reported, even partiallySearch lab, prescription, claim, and note fields for full and partial dates
AgesAges over 89 must be removed, though they can be grouped into one category of 90 or olderReplace every age above 89 with the single 90 or older value
Actual knowledgeThe covered entity must not have clear and direct knowledge that the remaining information could identify an individual; knowing that re-identification studies exist does not by itself countRecord who reviewed the data set and what they knew
Re-identification codesA code can be assigned only if it is not derived from or related to information about the individual and is not used or disclosed for other purposesUse random codes, keep the mapping separate, and never use a hash of a real identifier

‍

A code built from a secure hash without a secret key counts as an identifier under Safe Harbor. Under Expert Determination, hashed codes are permitted if the keys are not disclosed [1].

How Expert Determination works in practice

HHS describes Expert Determination as an iterative process: assess the risk, apply mitigation, and re-evaluate [1]. No single method is required, and no universal threshold applies. Assessment principles include replicability, data source availability, and distinguishability. Mitigation methods include suppression, generalization, perturbation, and k-anonymity, and OCR sets no universal value of k. An expert can produce more than one data solution, as long as the solutions cannot be combined to re-identify someone. No expiration date is required, though time-limited certifications are common.

This route takes more specialized work than applying a list, but it can keep details that Safe Harbor removes, such as full dates or fine geography, when the expert finds the risk very small. Teams that need those details for research or analytics can weigh that trade first.

Why de-identification belongs in third-party risk work

Data sets move to vendors, researchers, and analytics partners, and the identifiers in them travel too. The benchmark data show how thin the control coverage can be around data protection. In the 2025 Healthcare Cybersecurity Benchmarking Study, the optional HICP section (n=32) scored Data Protection and Loss Prevention at 58%, the second-lowest of the ten practices after Network Connected Medical Device Security at 48%, against a 70% average across practices [2]. In the same study, Strong Encryption, an Essential Goal in the HHS performance goals, scored 77% across the full sample of 69 organizations [2].

The 2024 study found that organizations whose information security leaders owned more of the cybersecurity program reported higher Data Protection and Loss Prevention coverage: 66% for the high-ownership group (n=18), 60% for the medium group (n=14), and 57% for the low group (n=24) [3]. This is an association in survey data and does not show that ownership causes coverage.

Vendors also sit behind many PHI incidents. HIPAA Journal counted 118 of the 741 breaches of 500 or more records reported to the Office for Civil Rights (OCR) in 2024 as filed by business associates [4].

A review checklist for de-identification

  1. Choose the method. Use Safe Harbor when the list can be applied cleanly, and Expert Determination when the work needs dates, geography, or detail that Safe Harbor removes.
  2. Map where identifiers live. Check structured fields, free-text notes, images, file names, and file metadata, not only the obvious columns.
  3. Apply the rules in the table above. Cover the ZIP code limit, dates and test-result dates, ages over 89, and re-identification codes.
  4. Test for actual knowledge. Ask whether anyone involved knows that the remaining fields could identify a person, and record the answer.
  5. Document the work. Keep the method, the reviewer, and the date, since OCR can ask for the methods and results of an Expert Determination.
  6. Check the receiving vendor. Confirm what the vendor does with the data set and whether its contract bars attempts to re-identify.

How Censinet supports third-party PHI risk

Censinet's third-party risk capability keeps a centralized vendor and product inventory, adds automated rapid inherent risk scoring, sends breach and ransomware notifications focused on the vendors in your inventory, and routes events through an incident review workflow into a Risk Register and a remediation workflow, with people making every final risk decision [5]. For de-identification work, that inventory answers a basic question: which vendors receive data sets from us, and how much risk does each carry?

Conclusion

Key points

HIPAA defines de-identification through two methods, Safe Harbor and Expert Determination. Safe Harbor depends on 18 identifiers, with specific limits on ZIP codes, dates, ages, and codes. Benchmark coverage of data protection controls is lower than for most other practices, and business associates file a share of the large breaches reported to OCR.

Next steps

Run your next de-identification request through the checklist above, and add a data-set review to your next vendor assessment.

References

  1. U.S. Department of Health and Human Services, Office for Civil Rights. Guidance Regarding Methods for De-identification of Protected Health Information in Accordance with the HIPAA Privacy Rule (45 CFR 164.514(b); page modified March 20, 2026). https://www.hhs.gov/hipaa/for-professionals/special-topics/de-identification/index.html
  2. KLAS Research and Censinet, with the American Hospital Association. Healthcare Cybersecurity Benchmarking Study 2025, Executive Summary (April 2025). https://censinet.com/2025-healthcare-cybersecurity-benchmarking-study-executive-summary
  3. Censinet, KLAS Research, the American Hospital Association, Health-ISAC, and the Healthcare and Public Health Sector Coordinating Council. Healthcare Cybersecurity Benchmarking Study 2024 (February 2024). https://censinet.com/2024-healthcare-cybersecurity-benchmarking-study-executive-summary
  4. HIPAA Journal. Healthcare Data Breach Statistics, updated for 2026 (statistics updated October 15, 2026, from OCR data obtained October 10, 2026). https://www.hipaajournal.com/healthcare-data-breach-statistics/
  5. Censinet. Third-Party Risk. https://censinet.com/capabilities/third-party-risk