Allergy Record Anonymisation with anonym.plus

Clear identifiers from the file while the clinical detail stays.

Allergy-record anonymisation removes personal data from allergy and reaction files, which are health data under UK GDPR Art. 9. anonym.plus does this on your device and keeps the trigger, reaction, and severity for safety work.

When this applies

Safety registries lean on true trigger and reaction data, but the file names the patient and the reporter. Make it anonymous and you can pool safety signals with no personal data.

How anonym.plus handles it

  1. Load the file into anonym.plus on a local device.
  2. It finds patient and reporter identifiers.
  3. The trigger and severity fields stay.
  4. Swap identifiers with the map off for true anonymity.
  5. Save the anonymous file on your device.

What you need to provide

Patient data entity types detected

Categoryanonym.plus entity typeExample
NamesPERSONpatient name → [PATIENT]
NamesPERSONreporting clinician → [REPORTER]
DatesDATE_TIMEreaction date → [DATE]
ContactPHONE_NUMBER0113 496 0123 → [PHONE]
NHS NumberUK_NHSNHS 943 476 5919 → [NHS_NO]
LocationLOCATIONclinic → [CLINIC]

Compliance achieved

Anonymise allergy records offline — see plans & start free →

Limitations & cautions

The trigger and reaction stay and are not usually identifying. But a very rare allergy plus a place could add to re-identification. Turn off any re-link key and weigh the residual risk for true anonymity.

Frequently asked questions

Is the trigger data removed?

No. The trigger, reaction, and severity stay. Only personal identifiers like patient and reporter names go.

Why is this data special under UK GDPR?

It is health data under Art. 9, so it needs a legal basis to use. Making it anonymous drops that need for second uses.

Can I pool anonymous allergy files?

Yes. Once anonymous, the files can be pooled for safety signals with no UK GDPR consent limits.