Appointment Record De-Identification with anonym.plus

Clear patient identifiers from booking rows while slot patterns stay usable.

Record de-identification is the removal of personal identifiers from a scheduling list. UK GDPR Art. 9 and DPA 2018 apply when health details appear in booking records. anonym.plus runs offline and keeps the slot times and visit types that drive capacity analysis.

When this applies

A booking list names each patient and ties them to a slot, a phone, and an email. For no-show or utilisation studies, those personal tags must go.

How anonym.plus handles it

  1. Open the booking list in anonym.plus on your device.
  2. It finds patient names, numbers, emails, and identifiers.
  3. Slot times and visit types stay in place.
  4. Shift the dates while you keep the spacing intact.
  5. Save the clean schedule on your device.

What you need to provide

Patient data entity types detected

Categoryanonym.plus entity typeExample
NamesPERSONbooked name → [PATIENT]
ContactPHONE_NUMBERreminder phone +44 → [PHONE]
ContactEMAIL_ADDRESSconfirm email → [EMAIL]
DatesDATE_TIMEslot 09:30 03 Jun → shifted [TIME]
Record IDsMEDICAL_RECORD_NUMBERNHS 512 345 0099 → [NHS_NUMBER]
NamesPERSONprovider column → [CLINICIAN]

Compliance achieved

Anonymise appointment records offline — see plans & start free →

Limitations & cautions

Shifting dates keeps the spacing but breaks links to outside calendars unless you move those by the same offset. A rare visit type at a small clinic can still narrow identity after the obvious tags are gone.

Frequently asked questions

How does date-shift keep the schedule useful?

Every booking moves by one steady offset, so the gaps between slots stay. No-show and utilisation work still runs while the real dates hide.

Are provider names removed?

They can be. Provider names are not patient personal data, but you can swap them for blinded capacity studies.

Can I clean a whole month at once?

Yes. Point the tool at the export and it works through every row locally.