Study guide

5.2 De-Identification Methodologies: Safe Harbor 18 Identifiers vs. Formal Expert Determination

AHIMA Certified in Healthcare Privacy and Security CHPS

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Healthcare Privacy & Security Legal Framework

1.1 HIPAA Statutory Architecture, HITECH Act, and Enforcement Evolution 1.2 Specialized Federal Privacy Laws: 42 CFR Part 2, GINA, FERPA, and Cures Act Information Blocking 1.3 State Law Preemption Analysis, Stringency Standards, and Multi-State Compliance

2 Chapter 2: Governance, Officer Responsibilities & Compliance Documentation

2.1 Privacy Officer vs. Security Officer: Roles, Governance, and Dual Accountability 2.2 Healthcare Accreditation Standards: Joint Commission, NCQA, and CARF Privacy Requirements 2.3 Documentation, Production, and Record Retention Mandates (State vs. Federal 6-Year Rule)

3 Chapter 3: Notice of Privacy Practices & Patient Rights

3.1 Notice of Privacy Practices (NPP): Content Requirements, Distribution, and Acknowledgment 3.2 Individual Right of Access: Timelines, Digital Formats, and Fee Limitations 3.3 Patient Rights: Amendments, Accounting of Disclosures, and Restriction Requests 3.4 Operational Workflows for Managing Patient Rights and Dispute Resolution

4 Chapter 4: Designated Record Sets, Special Protections & Release Protocols

4.1 Defining the HIPAA Designated Record Set (DRS) Across Clinical and Billing Systems 4.2 Special Privacy Protections: Mental Health, Psychotherapy Notes, SUD Records, and Reproductive Healthcare 4.3 Legal Demands for PHI: Subpoenas, Court Orders, Warrants, and Law Enforcement Inquiries 4.4 Verification Protocols for Requestor Identity, Legal Authority, and Release of Information (ROI)

5 Chapter 5: Minimum Necessary, De-Identification & Research Disclosures

5.1 Minimum Necessary Standard: Protocols, Role-Based Access, and Mandatory Exceptions 5.2 De-Identification Methodologies: Safe Harbor 18 Identifiers vs. Formal Expert Determination 5.3 PHI in Clinical Research: IRB Waivers, Preparatory to Research, Decedents, and Limited Data Sets (DUA)

6 Chapter 6: Business Associates, Contracts & Workforce Training

6.1 Business Associate Agreements (BAA): Mandatory Provisions, Subcontractor Flow-Down, and Liability 6.2 Vendor Risk Management and Service Level Agreements (SLAs) for Health Data 6.3 Workforce Privacy and Security Training: Curriculum Design, Delivery, and Retraining Triggers 6.4 Policy Management Lifecycle: Policy Formulation, Regular Review, and Organizational Communication

7 Chapter 7: Information Security Plan & Asset Risk Analysis

7.1 Developing and Maintaining an Organizational Information Security Plan (ISP) 7.2 Hardware, Software, and Sensitive Data Asset Inventories and Criticality Categorization 7.3 HIPAA Security Rule Risk Analysis: Threat Identification, Vulnerabilities, and NIST SP 800-30 Alignment

8 Chapter 8: Access Control Systems, Authentication & Emergency Operations

8.1 Access Authorization and Privilege Management: Role-Based (RBAC) and Attribute-Based Controls 8.2 Authentication Architectures: Multi-Factor Authentication (MFA), Passwords, and Identity Proofing 8.3 Emergency Access Protocols: "Break-Glass" Workflows, Documentation, and Post-Event Review 8.4 Information System Activity Review: Audit Logs, Access Tracking, and Anomaly Monitoring

9 Chapter 9: Technical Safeguards, Cryptography & Network Security

9.1 Data Encryption Standards: In Transit (TLS) vs. At Rest (AES-256) and FIPS Validation 9.2 Network Architecture Security: Firewalls, DMZ, Segmentation, and Wireless Protections 9.3 Secure External Data Transmission: Direct Messaging, SFTP, APIs, and FHIR Security 9.4 Event Triggering, Intrusion Detection/Prevention (IDS/IPS), and Security Information Event Management (SIEM)

10 Chapter 10: Physical Safeguards, Media Controls & Facility Security

10.1 Facility Access Controls: Visitor Policies, Physical Access Tracking, and Building Security 10.2 Workstation Use and Security: Screen Privacy, Physical Placement, and Clean Desk Standards 10.3 Media Control Lifecycle: Receipt, Movement, Re-Use, and Sanitization/Destruction (NIST SP 800-88)

11 Chapter 11: Business Continuity, Disaster Recovery & Contingency Planning

11.1 Contingency Planning Frameworks: Business Impact Analysis (BIA) and Emergency Mode Operations 11.2 Data Backup Plans, Redundancy Architectures, and Off-Site Storage Strategies 11.3 Disaster Recovery and Testing: RTO, RPO, Downtime Procedures, and Restoration Validation

12 Chapter 12: Incident Response, Investigation Protocols & Mitigation

12.1 Security and Privacy Incident Intake, Triage, and Response Team (CSIRT/PIRT) Structure 12.2 Investigating Privacy and Security Complaints: Evidence Gathering and Root-Cause Analysis 12.3 Immediate Containment and Harm Mitigation Strategies for Breaches and Exposures 12.4 Disciplinary Guidelines and Sanctions Enforcement for Workforce Non-Compliance

13 Chapter 13: Federal Breach Notification Rule & Risk Assessment

13.1 Federal Breach Notification Rule Definition, Exceptions, and Safe Harbors 13.2 The Four-Factor Breach Risk Assessment Methodology and Documentation 13.3 Individual Notification Requirements: Content, Timelines (60-Day Clock), and Substitute Notice 13.4 Entity Notification Mandates: HHS OCR Reporting (<500 vs. ≥500) and Media Notifications

14 Chapter 14: Compliance Auditing, External Investigations & Enforcement Tiers

14.1 Ongoing Compliance Auditing, Risk Metrics, and Executive/Board Governance Reporting 14.2 Managing External Investigations: Responding to OCR Inquiries, Subpoenas, and State AGs 14.3 Enforcement Penalties: HIPAA Civil Monetary Penalty Tiers, Resolution Agreements, and Criminal Sanctions

5.2 De-Identification Methodologies: Safe Harbor 18 Identifiers vs. Formal Expert Determination

Key Takeaways Explain This Topic AI

Under 45 CFR § 164.514(a), health information that does not identify an individual and with respect to which there is no reasonable basis to believe the information can be used to identify an individual is not Protected Health Information (PHI) and falls completely outside HIPAA regulations.

The Safe Harbor method (45 CFR § 164.514(b)(2)) requires the removal of 18 enumerated direct and indirect identifiers of the individual, employers, relatives, and household members, combined with the covered entity having no actual knowledge that the remaining information could identify the individual.

Under the Safe Harbor geographic rule, all units smaller than a state must be removed, but the first 3 digits of a ZIP code may be retained if the geographic unit formed by combining all 3-digit ZIPs contains more than 20,000 people; if 20,000 or fewer, the digits must be replaced with '000'.

The Formal Expert Determination method (45 CFR § 164.514(b)(1)) relies on statistical and scientific principles applied by a qualified expert who determines and documents that the risk of re-identification is 'very small'; this documentation must be retained for 6 years.

Re-identification codes (45 CFR § 164.514(c)) allow a covered entity to assign a unique pseudonym to a de-identified record, provided the code is not derived from or related to the individual's PHI and the re-identification key is never disclosed or accessible to the recipient.

Last updated: September 2026

5.2 De-Identification Methodologies: Safe Harbor 18 Identifiers vs. Formal Expert Determination

CHPS Core Standard: Under the Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule ( 45 CFR § 164.514(a) ), health information that does not identify an individual and with respect to which there is no reasonable basis to believe that the information can be used to identify an individual is not Protected Health Information (PHI) . Once health data is properly de-identified according to federal standards, it ceases to be governed by HIPAA: it may be freely utilized, disclosed, licensed, aggregated, or commercialized without patient authorization, Business Associate Agreements (BAAs), or Data Use Agreements (DUAs).

1. The Legal and Economic Architecture of De-Identified Data

The statutory threshold for de-identification under 45 CFR § 164.514(a) creates a definitive legal boundary: Individually Identifiable Health Information (IIHI) held by Covered Entity / BA

  • │
  • ┌────────────────┴────────────────┐
  • ▼ ▼
  • Contains Identifiers / Properly De-Identified
  • Risk of Re-identification (Safe Harbor or Expert Method)
  • │ │
  • ▼ ▼
  • CLASSIFIED AS PHI NOT CLASSIFIED AS PHI
  • 45 CFR Parts 160 & 164 Completely Outside HIPAA
  • ┌──────────────────────────────┐ ┌──────────────────────────────┐
  • │ • Authorization required │ │ • No HIPAA restrictions │
  • │ • BAA required for vendors │ │ • No BAA or DUA required │
  • │ • Minimum necessary applies │ │ • Can be sold or shared │
  • │ • Accounting of disclosures │ │ • No accounting required │
  • │ • Breach notification rule │ │ • No breach reporting │
  • └──────────────────────────────┘ └──────────────────────────────┘

To achieve this legal status, covered entities and business associates must satisfy one of two rigorous statutory standards codified in 45 CFR § 164.514(b) :

The Safe Harbor Method (§ 164.514(b)(2)): The removal of 18 specified direct, indirect, and quasi-identifiers coupled with the absence of "actual knowledge" that the remaining data could identify an individual.

The Formal Expert Determination Method (§ 164.514(b)(1)): The application of statistical, mathematical, or scientific disclosure-limitation principles by a qualified expert who determines that the risk of re-identification is "very small."

2. Safe Harbor Method: The 18 Enumerated Identifiers (45 CFR § 164.514(b)(2))

The Safe Harbor methodology is an objective, rules-based de-identification standard. Under 45 CFR § 164.514(b)(2)(i) , a covered entity must remove all 18 enumerated categories of identifiers of the individual or of relatives, employers, or household members of the individual:

Identifier # Regulatory Category (45 CFR § 164.514(b)(2)(i)) Precise Statutory Specification Operational Guidance & Exam Considerations

1 Names All personal names Includes first, middle, last, maiden names, aliases, and patient initials.

2 Geographic Subdivisions All geographic subdivisions smaller than a state Must remove street address, city, county, precinct, neighborhood, geocodes, and full 5-digit ZIP codes. Special rule applies to 3-digit ZIP prefixes.

3 Dates Directly Related to Individual All elements of dates (except year) Must remove exact days and months for: birth dates, admission dates, discharge dates, service/visit dates, death dates. All ages > 89 must be aggregated into a single category of "90 or older."

4 Telephone Numbers All voice telephone numbers Landlines, cellular numbers, secondary contact numbers.

5 Fax Numbers All facsimile numbers Domestic and international fax numbers.

6 Electronic Mail Addresses All email addresses Personal, professional, and student email addresses.

7 Social Security Numbers SSN in any format Full 9-digit SSNs and partial SSNs (e.g., last 4 digits).

8 Medical Record Numbers Institutional MRNs Unique patient record identifiers across EHRs, master patient indexes (MPI), and paper charts.

9 Health Plan Beneficiary Numbers Insurer identification numbers Policy numbers, Medicaid IDs, Medicare Beneficiary Identifiers (MBIs), group numbers.

10 Account Numbers Financial billing account numbers Patient encounter billing numbers, guarantor accounts, credit card numbers on file.

11 Certificate / License Numbers Professional, state, or legal licenses Driver's license numbers, nursing/medical license numbers, marriage certificate IDs.

12 Vehicle Identifiers Vehicle IDs and serial numbers Vehicle Identification Numbers (VIN), license plate numbers, registration tags.

13 Device Identifiers & Serial Numbers Medical device serials Unique Device Identifiers (UDIs), pacemaker/defibrillator serials, insulin pump IDs.

14 Web URLs Universal Resource Locators Personal blogs, patient social profiles, or medical portal URLs.

15 IP Address Numbers Internet Protocol addresses IPv4 and IPv6 addresses associated with patient portal logins or telehealth sessions.

16 Biometric Identifiers Biometric recognition templates Fingerprints, voiceprints, retina and iris patterns, facial geometry scans.

17 Full-Face Photographic Images Full-face photos & comparable images Clinical dermatology photos of full faces, security badge photos, telehealth snapshots.

18 Any Other Unique Identifying Number, Characteristic, or Code Catch-all identifier provision Any unique code or characteristic not explicitly listed (excluding compliant re-identification codes under § 164.514(c)).

The Safe Harbor Geographic Rule: The 3-Digit ZIP Exception

Under 45 CFR § 164.514(b)(2)(i)(B) , geographic data smaller than a state must generally be stripped. However, the rule contains a precise mathematical carve-out for three-digit ZIP code prefixes :

The initial three digits of a ZIP code may be retained if, according to the current publicly available data from the Bureau of the Census:

The geographic unit formed by combining all 3-digit ZIP codes with the same initial 3 digits contains more than 20,000 people .

If the combined geographic unit contains 20,000 or fewer people , the initial three digits must be changed to 000 .

Historical Census Data Impact: According to U.S. Census Bureau data, there are several rural or specialized 3-digit ZIP code prefixes in the United States that represent populations of 20,000 or fewer (e.g., 036, 059, 102, 203, 556, 692, 821, 823, 830, 831, 878, 879, 884). In a Safe Harbor dataset, any patient residing within these designated prefixes cannot have their actual 3-digit prefix displayed; it must be recoded to 000 .

The Safe Harbor Temporal Rule: Dates and the 90+ Age Rule

Under 45 CFR § 164.514(b)(2)(i)(C) , temporal data is strictly controlled:

Permitted: The year of an event (e.g., birth year 1974, admission year 2023, discharge year 2023).

Prohibited: Any discrete month, day, day-of-week, or hour directly associated with an individual.

The 90+ Aggregation Mandate: Individuals aged 90 or older represent a small, statistically re-identifiable demographic cohort. Therefore, all ages over 89 and all elements of dates (including year of birth) indicative of such age must be aggregated into a single, combined category: "Age 90 or older." An analyst cannot display "Age 94" or "Born in 1930"—the record must read "90+".

The 'Actual Knowledge' Standard (45 CFR § 164.514(b)(2)(ii))

Removing all 18 identifiers is only the first prong of Safe Harbor. Under the second prong:

"The covered entity does not have actual knowledge that the information could be used alone or in combination with other information to identify an individual who is a subject of the information."

Actual knowledge does not mean theoretical or speculative risk. It means the covered entity has affirmative awareness or concrete information that an anticipated recipient has the capacity, auxiliary datasets, or contextual knowledge to re-identify a patient.

Scenario Example: A patient with an extremely rare genetic mutation (e.g., Fibrodysplasia Ossificans Progressiva) is treated at a specialty clinic. The clinic strips all 18 identifiers, including dates (retaining only year) and state of residence. However, the clinic's privacy officer is fully aware that the patient's case was recently featured in a prominent national television documentary detailing the patient's exact occupation, state, and rare diagnosis. The clinic has actual knowledge that a recipient could link the clinical dataset to the specific patient. Under § 164.514(b)(2)(ii), the dataset cannot be released as de-identified under Safe Harbor.

3. Formal Expert Determination Method (45 CFR § 164.514(b)(1))

While Safe Harbor is simple to administer, it strips critical data elements—such as exact dates of clinical interventions, geographic trends below the state level, and granular geriatric age tracking. In complex clinical research, epidemiological modeling, and health economics, Safe Harbor data is often analytically unusable. To solve this, HIPAA provides the Formal Expert Determination Method .

The Legal Standard

Under 45 CFR § 164.514(b)(1) , health information is deemed de-identified if:

A person with appropriate knowledge of and experience with generally accepted statistical and scientific principles and methods for rendering information not individually identifiable:

Applying such principles and methods, determines that the risk is very small that the information could be used, alone or in combination with other reasonably available information, by an anticipated recipient to identify an individual who is a subject of the information; and

Documents the methods and results of the analysis that justify such determination.

Who Qualifies as an Expert?

HHS does not designate a specific professional certification, but the expert must possess demonstrated academic training and professional experience in statistical disclosure limitation (SDL), data privacy engineering, cryptography, or biostatistics. Typical experts hold advanced degrees (PhD, MS) in computer science, statistics, or health informatics.

Statistical Principles and Disclosure Control Techniques

An expert does not merely glance at a database; they apply rigorous mathematical disclosure control methodologies:

K-Anonymity: A mathematical property ensuring that each individual record in a dataset cannot be distinguished from at least k − 1 k - 1 k − 1 other individuals whose data appear in the dataset with respect to quasi-identifiers (e.g., gender, ZIP code, age). If k = 10 k = 10 k = 10 , any combination of quasi-identifiers matches at least 10 individuals in the data.

L-Diversity: An extension of k k k -anonymity that prevents attribute linkage attacks by ensuring that sensitive attributes within each equivalence group have at least l l l distinct, well-represented values.

T-Closeness: Further refines l l l -diversity by requiring that the statistical distribution of a sensitive attribute within any equivalence class is close to the distribution of the attribute across the entire database.

Differential Privacy: A cryptographic mathematical definition of privacy where randomized noise is injected into database queries, mathematically bounding the probability that an observer can infer whether any specific individual is present in the dataset.

Generalization and Suppression: The expert selectively suppresses high-risk outliers (e.g., extreme heights, rare diagnoses) or generalizes exact numbers into broader analytical bands (e.g., recoding exact dates into 30-day intervention windows, or mapping 5-digit ZIP codes into regional zones).

Documentation and Retention Mandate

The expert must generate a formal Expert Determination Report that details:

The mathematical models, threat vectors, and data linkage sources evaluated;

The contextual environment of the anticipated recipient (e.g., open public release vs. restricted data enclave);

  • The statistical mitigations applied;
  • The objective calculation proving the re-identification risk is "very small."

Under 45 CFR § 164.530(j)(2) , the covered entity must retain this expert documentation for at least six (6) years from the date of its creation or the date when it was last in effect, whichever is later.

4. Comparative Analysis: Safe Harbor vs. Expert Determination

Dimension Safe Harbor Method (45 CFR § 164.514(b)(2)) Formal Expert Determination (45 CFR § 164.514(b)(1))

Core Mechanism Prescriptive, rules-based removal of 18 enumerated identifiers Mathematical, risk-based statistical disclosure analysis

Required Expertise Standard compliance / HIM operational staff Qualified statistical, scientific, or mathematical expert

Geographic Granularity State level only (3-digit ZIP permitted if population >20,000) Can retain 5-digit ZIP, city, or county if statistical risk is "very small"

Temporal Granularity Year only; all dates (month/day) stripped; ages >89 capped at 90+ Can retain exact dates of service, birth dates, or exact ages if mitigated

Risk Threshold Zero tolerance for 18 identifiers + no actual knowledge Quantified risk of re-identification must be "very small"

Implementation Cost & Speed Low cost, fast execution via automated redaction scripts High cost, extended timeline for customized expert evaluation

Vulnerability to Linkage Attacks Highly vulnerable if auxiliary public data exists (actual knowledge check critical) Highly resilient due to mathematical modeling of anticipated recipient context

Documentation Mandate Standard policy and procedure retention (6 years) Formal expert statistical methodology report required (6-year retention)

5. Re-Identification Codes (45 CFR § 164.514(c))

Covered entities frequently need to track de-identified records over time (e.g., longitudinal clinical trial updates) or re-link an outcome to a patient if a critical health finding emerges. Under 45 CFR § 164.514(c) , a covered entity may assign a code or other means of record identification to allow de-identified information to be re-identified by the covered entity, provided that:

Derivation Rule: The code or other means of record identification is not derived from or related to information about the individual (e.g., the code cannot be a cryptographic hash of the Social Security number, medical record number, birth date, or any combination of patient demographics).

Translation Rule: The code is not capable of being translated so as to identify the individual by anyone other than the covered entity (e.g., the algorithm or key cannot be publicly known or reversible).

Security & Non-Disclosure: The covered entity does not use or disclose the code or other means of record identification for any other purpose, and does not disclose the mechanism for re-identification to the recipient of the de-identified data.

Caution

The Hash Function Trap: Many health systems mistakenly believe that running a SHA-256 or MD5 cryptographic hash on an MRN satisfies § 164.514(c). It does not. Because the hash value is directly derived from the patient's MRN, it violates the derivation rule. If an attacker knows the hashing algorithm, they can execute a rainbow-table attack across known MRN sequences to instantly re-identify patients. Compliant re-identification codes must be randomly generated pseudonyms mapped via a segregated, encrypted cross-reference table maintained exclusively inside the covered entity.

6. CHPS Exam Tips and Common Candidate Traps

Tip

Exam Tip: The Geographic Population Threshold Commit the number 20,000 to memory. Safe Harbor permits 3-digit ZIP prefixes only if the combined population of all ZIP codes sharing that prefix exceeds 20,000 according to Census Bureau data. Any 3-digit prefix representing 20,000 or fewer individuals must be changed to 000 .

Warning

Candidate Trap: Dates in Safe Harbor A recurring CHPS exam question asks whether a dataset containing 'Year of Birth' and 'Year of Diagnosis' complies with Safe Harbor. Yes, it does. Safe Harbor permits the year of an event. What violates Safe Harbor is including the month or day (e.g., 'May 2023' or '05/12/2023'). Furthermore, remember that for any individual aged 90 or older, the year of birth must be suppressed and their age aggregated into '90 or older'.

Important

Candidate Trap: Re-Identification Key Transfer If a covered entity transmits a de-identified dataset to a researcher or vendor and inadvertently includes the cross-reference linkage table or cryptographic decryption key, the dataset is no longer de-identified . It immediately reverts to PHI under federal law. If an unauthorized entity receives it, it constitutes a potential breach of unsecured PHI under 45 CFR Part 164 Subpart D.

Loading diagram... Safe Harbor vs. Formal Expert Determination De-Identification Architecture