Internal Audit Dataset De-Identification with anonym.plus

Clean a compliance audit extract before it reaches reviewers.

Audit-dataset de-identification is the removal of all 18 HIPAA Safe Harbor IDs (45 CFR §164.514(b)) from a compliance extract. anonym.plus runs on your own device. The findings stay testable, but the rows no longer name patients or staff.

When this applies

A compliance team samples charts and access entries to test a control. The sample names patients and the workers who touched each chart, and that must come out.

How anonym.plus handles it

  1. Point anonym.plus at the sample on your server.
  2. It scans ID columns and any free-text fields.
  3. Steady labels keep links across joined rows.
  4. Review the summary and adjust the column rules.
  5. Swap each ID, shifting dates to keep the gaps.
  6. Save the clean sample. Source rows stay local.

What you need to provide

PHI entity types detected

Categoryanonym.plus entity typeExample
PatientPERSONsubject → [PATIENT_n]
StaffPERSONreviewer → [AUDITOR_n]
Staff IDIDlogin bweiss → [USERNAME]
DatesDATE_TIMEsampled → shifted [DATE]
Record IDsMEDICAL_RECORD_NUMBERmrn field → [MRN_n]
NetworkIP_ADDRESS10.2.7.40 → [IP]

Compliance achieved

Anonymize audit datasets offline — see plans & start free →

Limitations & cautions

A compliance sample mixes tidy columns with note fields. The columns are easy to map; notes need the same care as any chart. Test a small slice first, and confirm that date-shifting keeps the gaps your test relies on.

Frequently asked questions

Does an audit sample hold PHI?

Yes. It names patients in the charts and the staff who handled them. Both are cleared so the findings can be shared without exposing people.

Can the rows still be tested after the swap?

Yes. A steady map keeps joins intact, so the control can be checked on the clean data.

Are staff logins and IPs handled?

Yes. Usernames, IPs, and timestamps in access entries are flagged alongside patient IDs.