Pharmacy Claims De-Identification with anonym.plus

Strip member IDs from claims while the fill and cost data stay.

Pharmacy-claims de-identification is the removal of all 18 HIPAA Safe Harbor IDs (45 CFR §164.514(b)) from a claims extract. anonym.plus does this locally. The fill and cost fields stay; the data no longer names the member.

When this applies

A claims extract ties many fills to one named member with a plan number. For analytics, you strip the IDs but keep the medicine, cost, and fill timing.

How anonym.plus handles it

  1. Point anonym.plus at the extract on your device.
  2. It scans ID columns and any free-text notes.
  3. Member names, plan numbers, and dates get flagged.
  4. Confirm the flags; the medicine and cost stay as non-IDs.
  5. Swap IDs with a steady map to keep row joins.
  6. Save the clean dataset; the source stays on your machine.

What you need to provide

PHI entity types detected

Categoryanonym.plus entity typeExample
NamesPERSONmember_name → [MEMBER_n]
IdentifiersNATIONAL_IDplan no. → [PLAN_ID]
DatesDATE_TIMEfill_date → shifted [DATE]
Record IDsMEDICAL_RECORD_NUMBERclaim no. → [CLAIM_ID]
LocationLOCATIONzip field → [ZIP]
IdentifiersUS_SSNssn field → [ID]

Compliance achieved

Anonymize pharmacy claims offline — see plans & start free →

Limitations & cautions

A full zip is a Safe Harbor identifier; cut it to the first three digits where the rule allows. The medicine and cost stay. Test a sample before a full run, and check that date-shift keeps the gaps your analysis needs.

Frequently asked questions

Can claims stay linkable after the swap?

Yes. A steady label map swaps each ID the same way, so rows for one member still join while no real identity is left.

Are the medicine and cost fields kept?

Yes. They are not member identifiers, so they stay. Only the 18 ID types are removed.

Why work locally rather than in the cloud?

Sending raw claims to a cloud tool is itself a disclosure with breach risk. Local work skips that risk; the data stays on your device.