Pre-Authorisation Request Anonymisation with anonym.plus

Clear IDs from the request while the clinical justification stays.

Pre-authorisation anonymisation is the removal of patient and provider IDs from a pre-auth request. It meets DPA 2018 & UK GDPR. anonym.plus works on your device and keeps the medical reasoning the request rests on.

When this applies

A pre-auth packet names the patient, the referring doctor, and the diagnosis. To reuse it for turnaround analysis or training, strip those IDs first.

How anonym.plus handles it

  1. Load the request into anonym.plus on your device.
  2. It scans the cover sheet and the attached notes.
  3. The tool flags names, dates, and membership numbers.
  4. The diagnosis and the requested service stay in place.
  5. Swap or black out the confirmed IDs.
  6. Save the clean packet on your machine.

What you need to provide

Patient data entity types detected

Categoryanonym.plus entity typeExample
NamesPERSONPatient Ines Vogt → [PATIENT]
ProviderPERSONDr Amani → [REQUESTER]
Member IDUK_HEALTH_INSURANCE_MEMBERMbr BUP-88442 → [MEMBER_ID]
DatesDATE_TIMERequested 03/05 → [DATE]
PhonePHONE_NUMBER+44 1632 960221 → [PHONE]
Auth refIDAuth PA-9920 → [REF]

Compliance achieved

Anonymise pre-authorisation requests offline — see plans & start free →

Limitations & cautions

A pre-auth packet often staples notes to a cover sheet. Check that every page is scanned, since an ID can hide on an attachment. Free-text notes need the same review as any clinical note.

Frequently asked questions

Is the referring doctor’s name removed too?

Provider names are not patient data per se. But teams often swap them for blinded review. The tool can flag patient and provider names together or apart.

Will the clinical reasoning stay intact?

Yes. The diagnosis, the requested service, and the supporting notes stay. Only IDs change.

Can I process a whole queue at once?

Yes. Point anonym.plus at a folder and it works through each packet on your device.