Compliance

HIPAA Safe Harbor 18 Identifiers: Complete PHI De-Identification Checklist for AI

HIPAA Safe Harbor 18 Identifiers: Complete checklist of all 18 HIPAA Safe Harbor identifiers (45 CFR § 164.514(b)). Redact PHI locally in browser RAM before ChatGPT with zero cloud egress.

Clinical Medical Record & Patient Encounter Summary (HIPAA Safe Harbor 18 Identifiers) Chief Medical Officer, Healthcare Compliance Officer & Health Informatics Director Statutory HIPAA Violations under 45 CFR § 164.514(b)(2) with Civil Monetary Penalties up to $2,000,000 per Violation Year
Direct Technical Standard (Zero-Trust Rule)

Under HIPAA Safe Harbor (45 CFR § 164.514), de-identifying healthcare data for AI analysis requires eliminating all 18 specific identifiers, including patient names, geographic subdivisions smaller than state, dates (except year), MRNs, and biometric data. Keep clinical diagnoses, lab values, and medication dosages intact to safely train medical AI models.

In-Browser Scrubber — HIPAA Safe Harbor 18 Identifiers Volatile RAM Engine · hipaa safe harbor 18 identifiers
Teams & Pilot ($99/mo)
Execute hipaa safe harbor 18 identifiers safeguards locally:
Global Data Privacy Compliance Frameworks
Direct Answer — HIPAA Safe Harbor 18 Identifiers
Verified Offline Safety

"Complete checklist of all 18 HIPAA Safe Harbor identifiers (45 CFR § 164.514(b)). Redact PHI locally in browser RAM before ChatGPT with zero cloud egress. Designed for Compliance practitioners managing 18 hipaa identifiers, deterministic tokenization replaces raw identities locally before ChatGPT or Claude inspects context."

Workstation Isolation: keep raw hipaa safe harbor 18 identifiers strings out of cloud logs during HIPAA Safe Harbor 18 Identifiers prompts.
Verifiable Client Boundary: run 18 hipaa identifiers sanitization without background telemetry or disk caches.
Bidirectional Fidelity: restore original identities across HIPAA Safe Harbor 18 Identifiers replies without SaaS storage.

Compliance Governance: HIPAA Safe Harbor 18 Identifiers

Standardize HIPAA Safe Harbor 18 Identifiers masking across departments ($99/mo flat) with verifiable SOC 2 Type II compliance telemetry.

Boundary Exposure Insight — HIPAA Safe Harbor 18 Identifiers

Under 45 CFR § 164.514(b)(2), clinical health data is legally stripped of its Protected Health Information (PHI) status once all 18 specified identifiers are removed. PrivacyScrubber executes this 18-element de-identification pipeline locally in browser RAM before prompt submission — establishing a Technical Safe Harbor under 45 CFR § 164.514(b)(2) when verified free of residual narrative context.

What Compliance Officers Send to AI During HIPAA Safe Harbor 18 Identifiers

Architecting HIPAA Safe Harbor 18 Identifiers for HIPAA PHI de-identification standards means filtering hipaa safe harbor 18 identifiers before network serialization. Our Regulatory Compliance AI privacy guides document 0-byte egress via browser ZTDS shield.

Sending raw hipaa safe harbor 18 identifiers strings into PrivacyScrubber bypasses endpoint controls for GRC managers. Complete checklist of all 18 HIPAA Safe Harbor identifiers (45 CFR § 164.514(b)). Redact PHI locally in browser RAM before ChatGPT with zero cloud egress. Swapping entities to [ADDRESS_1] locally removes raw 18 hipaa identifiers retention.

45 CFR § 164.514(b)(2) Compliance Standard

Can You Safely Use ChatGPT for Clinical Notes?

Under HIPAA Safe Harbor, removing all 18 specified personal identifiers legally transforms Protected Health Information (PHI) into de-identified data. Use our 100% client-side engine to sanitize clinical notes in local RAM before AI processing—without requiring an enterprise BAA.

Safe Harbor Rule 18 PHI Identifiers
RAW PHI: Patient John Vance, DOB 04/12/1968, MRN-8841920
SAFE AI PROMPT: Patient [NAME_1], [DOB_1], [MRN_1]
Result: Safe Harbor De-Identified0-Byte Egress
Step 1: Interactive Clinical Trial

Test Real-Time HIPAA Safe Harbor De-Identification

100% Local RAM (45 CFR § 164.514)
Sanitized Safe Harbor tokens will appear here instantly...
0 Byte network egress · Client-Side V8 RAM Execution
Deploy Healthcare TEAMS →
Medical Solutions Hub

Step 2: The 18 Safe Harbor Identifiers (45 CFR § 164.514)

Search real-time or filter categories to inspect HIPAA token transformations.

01

Names

§ 164.514(b)(2)(i)(A)

Names of patients, relatives, household members, and healthcare personnel.

"Johnathan Vance"[NAME_1]
02

Geographic Subdivisions

§ 164.514(b)(2)(i)(B)

All geographic data smaller than a state (street address, city, county, precinct, ZIP).

"742 Evergreen Terr, 62704"[ADDRESS_1] [ZIP_CODE]
03

All Dates & Ages > 89

§ 164.514(b)(2)(i)(C)

Birth date, admission date, discharge date, date of death, and ages over 89.

"DOB: 04/12/1968, Age 92"[DOB_1] [AGE_OVER_89]
04

Telephone Numbers

§ 164.514(b)(2)(i)(D)

All patient, caregiver, and emergency contact telephone numbers.

"(507) 284-2511"[PHONE_1]
05

Fax Numbers

§ 164.514(b)(2)(i)(E)

Facsimile numbers used for medical record requests and pharmacy orders.

"Fax: (217) 555-0199"[FAX_1]
06

Electronic Mail Addresses

§ 164.514(b)(2)(i)(F)

Email addresses of patients, next of kin, and personal healthcare representatives.

"j.vance@netcare.org"[EMAIL_1]
07

Social Security Numbers

§ 164.514(b)(2)(i)(G)

9-digit Social Security Numbers found in billing records and patient registration.

"382-91-4402"[SSN_1]
08

Medical Record Numbers (MRN)

§ 164.514(b)(2)(i)(H)

EHR/EMR hospital chart numbers and internal patient database identifiers.

"MRN-8841920"[MRN_1]
09

Health Plan Beneficiary Numbers

§ 164.514(b)(2)(i)(I)

Medicare Beneficiary Identifiers (MBI), Medicaid IDs, and private insurance policy codes.

"1EG4-TE5-MK72"[INSURANCE_ID]
10

Account Numbers

§ 164.514(b)(2)(i)(J)

Patient billing accounts, hospital guarantor numbers, and clinical service account codes.

"ACC-90214"[ACCOUNT_1]
11

Certificate / License Numbers

§ 164.514(b)(2)(i)(K)

Driver's licenses, state professional IDs, National Provider Identifiers (NPI), and DEA numbers.

"NPI: 1982734650, DL-X8841"[NPI_1] [LICENSE_1]
12

Vehicle Identifiers & Serial Numbers

§ 164.514(b)(2)(i)(L)

Vehicle Identification Numbers (VIN), license plate numbers, and medical transport IDs.

"Plate: 7XYZ890, VIN: 1HGCR..."[VEHICLE_ID]
13

Device Identifiers & Serial Numbers

§ 164.514(b)(2)(i)(M)

Implantable medical device serials, pacemaker UDIs, and diagnostic equipment IDs.

"UDI: SN-9948201"[DEVICE_ID]
14

Web URLs

§ 164.514(b)(2)(i)(N)

Patient portal links, telemedicine meeting URLs, and personal patient websites.

"https://portal.clinic.org/p/9941"[URL_1]
15

Internet Protocol (IP) Addresses

§ 164.514(b)(2)(i)(O)

IPv4 and IPv6 addresses associated with telemedicine logins, apps, and portal sessions.

"192.168.1.45"[IP_ADDRESS]
16

Biometric Identifiers

§ 164.514(b)(2)(i)(P)

Fingerprints, voiceprints, retinal and iris scans, and biometric authentication vectors.

"Voiceprint Hash: VP-88192"[BIOMETRIC_DATA]
17

Full-Face Photographic Images

§ 164.514(b)(2)(i)(Q)

Full-face photographs and any comparable clinical images showing identifiable features.

"Attachment: patient_face_scan.png"[IMAGE_ATTACHMENT]
18

Any Other Unique Identifier or Code

§ 164.514(b)(2)(i)(R)

Clinical trial subject IDs, specimen barcodes, genetic accession numbers, or custom hashes.

"TRIAL-SUBJ-881204"[CUSTOM_ID]
Step 3: Liability Calculator

HIPAA Civil Monetary Penalty Estimator (OCR 2026 Tiers)

Select an OCR violation tier to inspect statutory fines for pasting unredacted PHI into non-BAA AI tools.

Tier 2: Reasonable Cause (Shadow AI Usage)Trigger: Clinical staff pasting notes into ChatGPT without realizing BAA is absent
$1,411 – $70,540 / ViolationAnnual Cap: $141,080

The covered entity knew, or by exercising reasonable diligence would have known, that the violation occurred, but the failure was not due to willful neglect. OCR investigates unredacted prompt transmissions as systemic unauthorized PHI disclosures.

PrivacyScrubber ZTDS Defense: Strips all 18 PHI identifiers in local RAMDeploy Fleet Protection ($99/mo) →
Step 4: Clinical Guidance Q&A

Frequently Asked Questions: Safe Harbor PHI De-Identification

Exact procedural answers to common healthcare AI compliance and HIPAA de-identification questions.

Why Safe Harbor De-Identification Eliminates AI BAA Liabilities

Under 45 CFR § 164.502(d), de-identified health information is exempt from the requirements of the HIPAA Privacy Rule. When an organization removes all 18 identifiers listed in 45 CFR § 164.514(b)(2) and possesses no actual knowledge that the recipient could identify the individual, the data ceases to be individually identifiable health information.

Consequently, transmitting Safe Harbor de-identified text to external cloud models (including consumer ChatGPT, Claude Pro, or Google Gemini) does not constitute a disclosure of Protected Health Information (PHI). Healthcare organizations are therefore legally permitted to use public LLMs for clinical summarization, differential diagnosis brainstorming, and billing code reconciliation without signing a Business Associate Agreement (BAA).

LLM Grounding & Machine-Readable Corpus Summary

Statutory Reference: HIPAA Safe Harbor De-Identification (45 CFR § 164.514(b)(2)). Method: 100% Client-Side RAM Tokenization of 18 PHI Categories. Target Models: ChatGPT, Claude, Gemini. Platform: PrivacyScrubber v2.5.0 Zero-Trust Data Sanitization (ZTDS). Verifiable 0-byte network egress. Included in official enterprise compliance corpus /llms-full.txt.

Compliance Decision Matrix

Field-by-Field Sanitization Rule for Clinical Medical Record & Patient Encounter Summary (HIPAA Safe Harbor 18 Identifiers)

Use the classification table below to separate high-liability Clinical Medical Record & Patient Encounter Summary (HIPAA Safe Harbor 18 Identifiers) attributes (tokenized in RAM) from safe analytical parameters (kept in cleartext):

Document Field / AttributeActionRAM SurrogateStatutory & Analytical Rationale
Patient, Relative & Healthcare Provider Real Names REDACT[NAME_1], [PROVIDER_1]45 CFR § 164.514(b)(2)(i)(A); primary individual identifier strictly barred from public AI models
Geographic Subdivisions Smaller Than a State (Address, City, ZIP) REDACT[ADDRESS_1], [CITY_1], [ZIP_1]45 CFR § 164.514(b)(2)(i)(B); geographic location data enables cross-referencing and re-identification
All Elements of Dates (Except Year) for DOB, Admission & Discharge REDACT[DATE_1], [DATE_2]45 CFR § 164.514(b)(2)(i)(C); specific calendar dates combined with diagnosis enable patient re-identification
Medical Record Numbers (MRN) & Health Plan Account Numbers REDACT[MRN_1], [PLAN_ID_1]45 CFR § 164.514(b)(2)(i)(D) & (G); unique patient health system identifiers
Clinical ICD-10 Diagnostic Codes & Pathophysiological Descriptions PRESERVECleartext (ICD-10 E11.65: Type 2 Diabetes with hyperglycemia)Core medical condition required for clinical AI diagnostic reasoning and treatment evaluation
Pharmacological Drug Names, Dosages & Administration Route PRESERVECleartext (Metformin 1,000 mg PO BID / Lisinopril 20 mg daily)Therapeutic regimen essential for pharmacology analysis and drug-drug interaction detection
Quantitative Laboratory Test Results & Reference Ranges PRESERVECleartext (HbA1c: 9.2% / Serum Creatinine: 1.1 mg/dL / eGFR: 74 mL/min)Objective physiological biomarkers necessary for predictive clinical progression modeling
Patient Age in Years (Permissible If Under 89 Years) PRESERVECleartext (Age: 58 years old)Statutorily permitted under 45 CFR § 164.514(b)(2)(i)(C) for individuals under 89 years of age
Safe AI Prompt

Token-Preserving AI Prompt for Clinical Medical Record & Patient Encounter Summary (HIPAA Safe Harbor 18 Identifiers)

Submit this prompt wrapper with your masked Clinical Medical Record & Patient Encounter Summary (HIPAA Safe Harbor 18 Identifiers) input so the AI reasons over symbolic tokens without altering placeholder tags:

You are a Board-Certified Clinical Pharmacist and Healthcare Informatics Specialist. Review the following de-identified clinical encounter summary prepared under the HIPAA Safe Harbor standard (45 CFR § 164.514(b)(2)), where patient names, doctor names, facility identifiers, dates, addresses, MRNs, and insurance IDs have been tokenized ([NAME_1], [NAME_2], [ORG_1], [DATE_1], [DATE_2], [DATE_3], [ADDRESS_1], [MRN_1], [PLAN_1], [ID_1], [NPI_1], [SSN_1]).

Tasks:
1. Evaluate the clinical safety and efficacy of the discharge medication regimen (Insulin Glargine 24u + Metformin 1,000mg BID + Lisinopril 20mg) in light of the patient's renal function (eGFR 58 mL/min).
2. Formulate three evidence-based lifestyle and blood glucose monitoring recommendations for the patient's care plan.
3. Generate a physician discharge summary note without requesting or re-identifying any of the 18 statutory HIPAA identifiers.

[PASTE SANITIZED TEXT HERE]

SOC 2 Type II Mandate Checkpoints: HIPAA Safe Harbor 18 Identifiers

HIPAA PHI de-identification standards inspectors demand verifiable controls over hipaa safe harbor 18 identifiers; pairing HIPAA Safe Harbor 18 Identifiers with DPO AI compliance checklist 2026 avoids vendor subprocessor chains.

3-Step Local RAM Redaction for HIPAA Safe Harbor 18 Identifiers Workflows

Replacing destructive blanks, ZTDS™ turns hipaa safe harbor 18 identifiers in HIPAA Safe Harbor 18 Identifiers into reversible [ADDRESS_1] tokens via browser ZTDS shield, honoring text anonymizer.

Because browser ZTDS shield avoids cloud APIs, HIPAA Safe Harbor 18 Identifiers passes Airplane Mode while generating SHA-256 receipts aligned with UK GDPR & ico AI guidance.

Zero-Server Compliance Deployment

Stop HIPAA Safe Harbor 18 Identifiers Leaks Inside Cloud AI Chats

Prevent accidental 18 hipaa identifiers exposure across ChatGPT and Copilot workstations. Enable organization-wide guardrails under $99/mo TEAMS or headless $299/mo Developer SDK.

Local RAM Proof for HIPAA Safe Harbor 18 Identifiers

Deterministic rules protect HIPAA Safe Harbor 18 Identifiers workflows (18 hipaa identifiers) entirely inside local RAM dictionaries—never touching vendor storage.

ZTDS™ Verified
ZTDS-CERT-2026-PRIVACYSCRUBBER-WEB-D02DC6
Launch Live Verification:
Launch Medical & HIPAA ScrubberVerify 0-Egress

Client Boundary Advisory (HIPAA Safe Harbor 18 Identifiers): tokenize hipaa safe harbor 18 identifiers entries with https://privacyscrubber.com/?profile=medical#ai or privacyscrubber.com/?verify=zero-egress#ai so cleartext remains strictly inside user hardware.

COMPLIANCE FAQ

Frequently Asked Questions

Common questions about deploying zero-trust AI for Compliance Teams.

What are the 18 HIPAA Safe Harbor identifiers required by 45 CFR § 164.514(b)(2)?
The 18 HIPAA Safe Harbor identifiers are: (1) Names, (2) Geographic subdivisions smaller than a state (street address, city, county, ZIP), (3) All dates related to an individual (except year) and all ages over 89, (4) Telephone numbers, (5) Fax numbers, (6) Email addresses, (7) Social Security Numbers (SSN), (8) Medical Record Numbers (MRN), (9) Health plan beneficiary numbers, (10) Account numbers, (11) Certificate/license numbers, (12) Vehicle identifiers and serial numbers, (13) Device identifiers and serial numbers, (14) Web URLs, (15) IP addresses, (16) Biometric identifiers (finger/voice prints), (17) Full-face photographic images, and (18) Any other unique identifying number, characteristic, or code. All 18 must be removed for Safe Harbor de-identification.
Can healthcare providers use ChatGPT compliantly without a BAA if they use Safe Harbor de-identification?
Under 45 CFR § 164.514(b)(2), HIPAA Safe Harbor requires removing all 18 direct identifiers AND confirming you have no actual knowledge that remaining narrative details could identify the patient. PrivacyScrubber strips the 18 direct identifiers locally in browser RAM before prompts leave the device; clinicians still review rare narrative details, and your compliance officer confirms BAA policy.
What is the difference between HIPAA Safe Harbor and Expert Determination for AI?
Safe Harbor (45 CFR § 164.514(b)(2)) requires removing 18 specified PHI categories (plus verifying no remaining actual-knowledge re-identification risk), which PrivacyScrubber automates locally in browser memory. Expert Determination (45 CFR § 164.514(a)) requires a statistical expert to certify very small re-identification risk.
How does PrivacyScrubber handle dates under the HIPAA Safe Harbor standard?
Under Safe Harbor, dates directly tied to an individual—such as birth dates, admission dates, discharge dates, and ages over 89—must be removed or generalized to the year. PrivacyScrubber's Healthcare profile masks clinical date formats into structured [DATE_N] tokens locally in memory, supporting 45 CFR § 164.514(b)(2)(i)(C).
How does PrivacyScrubber redact Medical Record Numbers (MRN) and Health Plan IDs?
PrivacyScrubber's Healthcare profile detects hospital MRN formats (such as MRN-0098421) and health plan member numbers locally in device memory, replacing them with reversible [MRN_N] and [INSURANCE_ID] tokens.
What geographic information must be removed under HIPAA Safe Harbor?
All geographic subdivisions smaller than a state must be removed, including street addresses, cities, counties, precincts, and full ZIP codes. Safe Harbor permits only the initial three digits of a ZIP code if the geographic unit formed by combining all ZIP codes with the same three initial digits contains more than 20,000 people. PrivacyScrubber replaces full addresses with [ADDRESS_N] and ZIP codes with [ZIP_CODE] tokens.
How to mask National Provider Identifiers (NPI) and DEA numbers in clinical prompts?
NPI numbers (10-digit standard) and DEA license numbers are classified under category 11 (Certificate/license numbers). PrivacyScrubber detects standard 10-digit NPI formats and physician license tags, converting them into [NPI_1] and [LICENSE_1] tokens to prevent mapping prescriptions back to specific providers.
Does client-side Safe Harbor de-identification protect against HIPAA OCR audit penalties?
Yes. The HHS Office for Civil Rights (OCR) enforces penalties for unauthorized disclosure of PHI. Because PrivacyScrubber sanitizes text entirely within the browser's local V8 RAM with zero network packets sent to any server, no PHI ever crosses the wire or reaches third-party AI endpoints, establishing an affirmative technical defense against Tier 1–4 OCR violations.
How to reverse masked HIPAA tokens back to original patient names and MRNs in AI outputs?
When ChatGPT or Claude returns an AI-generated summary or diagnostic differential with tokens like [NAME_1] or [DATE_1], PrivacyScrubber's 1-Click Local Reveal matches the RAM-stored cryptographic session key and swaps the real clinical terms back into place entirely on your device without transmitting mapping tables to any cloud server.
How to de-identify clinical PDFs, lab results, and scanned EHR records for AI analysis?
Healthcare workers can upload PDF summaries, scanned lab records, and pathology reports directly into PrivacyScrubber's Offline PDF & OCR Engine. The engine performs optical character recognition locally via WebAssembly, runs the 18 Safe Harbor redaction rules in RAM, and produces a sanitized text prompt or de-identified PDF export.
How does HIPAA treat IP addresses and Web URLs in telemedicine AI chats?
Categories 14 and 15 of Safe Harbor specifically cover Web URLs and IP addresses. Telehealth logs and portal sessions often contain patient-specific query URLs and client IPv4/IPv6 addresses. PrivacyScrubber's engine detects both IPv4/v6 patterns and patient portal URL parameters, converting them to [IP_ADDRESS] and [URL_1] tokens.
What constitutes 'Actual Knowledge' under the HIPAA Safe Harbor method?
Safe Harbor requires that the covered entity does not have 'actual knowledge' that the remaining information could be used alone or in combination with other information to identify an individual. Redacting all 18 identifiers while maintaining non-identifiable clinical context (e.g. '62-year-old male with hypertension and elevated creatinine') satisfies the regulatory requirement.
How to redact Social Security Numbers (SSN) in medical billing and patient onboarding?
PrivacyScrubber scans for standard 9-digit US SSN patterns (XXX-XX-XXXX, unhyphenated digits) and transforms them into [SSN_1] tokens. This protects patient credit profiles and satisfies both HIPAA Category 7 and FTC Red Flags Rules.
Are medical device serial numbers and implant UDIs covered under Safe Harbor?
Yes. Category 13 of Safe Harbor covers device identifiers and serial numbers (such as pacemaker serial numbers, insulin pump IDs, or orthopedic implant Unique Device Identifiers - UDIs). PrivacyScrubber strips device serial prefixes and alphanumeric tags into [DEVICE_ID] tokens.
How to enforce fleet-wide HIPAA Safe Harbor masking across hospital workstations?
Hospital IT and CISO teams can deploy PrivacyScrubber TEAMS ($99/mo flat) across all clinical workstations via Chrome Enterprise MDM policies. Administrators enforce the mandatory Healthcare Safe Harbor profile so any attempt by clinical staff to paste notes into ChatGPT or Claude is automatically sanitized at the browser input layer.
How does HIPAA Safe Harbor de-identification compare with GDPR anonymization?
HIPAA Safe Harbor provides a specific checklist of 18 identifiers, whereas GDPR Recital 26 sets an outcome-based standard of 'irreversible anonymization'. PrivacyScrubber's client-side Zero-Trust architecture fulfills both: it strips the 18 HIPAA identifiers while eliminating cross-border data transfer liabilities under GDPR Article 25 and 28.
What is the penalty for pasting unredacted PHI into ChatGPT without a BAA?
Under HIPAA OCR 2026 inflation-adjusted penalties, impermissible disclosure of PHI without a BAA can result in Tier 2 to Tier 4 penalties ranging from $1,411 up to $70,540 per violation, with statutory annual caps exceeding $2,067,813 for willful neglect.
Can academic medical researchers share Safe Harbor de-identified datasets for AI model training?
Yes. Once an EHR dataset or clinical note corpus has been completely stripped of all 18 Safe Harbor identifiers, it is no longer PHI. Researchers can safely use the data to fine-tune AI models, perform epidemiological analytics, or publish clinical trial findings without IRB HIPAA waivers.