Drug Safety Narrative De-Identification with anonym.plus

Clear IDs from the narrative while the event timeline stays.

Safety-narrative de-identification is the removal of patient and reporter IDs from the free-text event story. It supports ICH E2B(R3). anonym.plus runs locally and keeps the suspected product and the timeline of the event.

When this applies

An event story is dense free text. It names the patient, the reporter, and places. To submit or pool it, you clear those IDs but keep the product and timeline.

How anonym.plus handles it

  1. Open the narrative in anonym.plus on your device.
  2. It reads the free text for patient and reporter names.
  3. Dates, ages, and places get flagged across the story.
  4. Confirm the flags; the suspected product stays as a non-ID.
  5. Swap the IDs and shift the dates to keep the gaps.
  6. Save the clean file; the source stays on your machine.

What you need to provide

PHI entity types detected

Categoryanonym.plus entity typeExample
NamesPERSONInes Novak → [PATIENT]
NamesPERSONreporting GP → [REPORTER]
DatesDATE_TIMEdose 09 Feb → shifted [DATE]
AgeAGEage 81 → [AGE_BAND]
LocationLOCATIONPrague site → [SITE]
IdentifiersIDnarrative ref 5521 → [ID]

Compliance achieved

Anonymize safety narratives offline — see plans & start free →

Limitations & cautions

The story is free text with mixed clues. The suspected product must stay, as it is the signal. A rare event on a known date at a small site can still narrow identity, so band the age and shift dates for odd cases.

Frequently asked questions

Is the suspected product removed?

No. The product name is not patient PHI and carries the safety signal, so it stays. Only the patient and reporter IDs are taken out.

How is the timeline kept useful?

Date-shift moves all dates by one steady offset, so the gaps between dose and event stay while the real dates hide.

Can narratives be pooled for signal work?

Yes. A steady label map lets one patient or reporter map to one alias across many files.