Appointment Record De-Identification with anonym.plus

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

In simple terms, PII redaction is the on-device process of finding and masking personally identifiable information in a document before it is shared.

Record de-identification is the removal of personal identifiers from a scheduling list. Booking rows are still health data when they show who attended which clinic, so UK GDPR Art. 9(1) applies. Art. 5(1)(e) limits how long you may keep them in identifiable form, and the Records Management Code of Practice for Health and Social Care 2021 sets the NHS retention periods that give that principle a number. 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 number, and an email. No-show and utilisation studies need the timing pattern, not the people. Date-shifting keeps the pattern while the real appointment dates disappear.

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]
NHS numberNHS_NUMBERNHS 512 345 0099 → [NHS_NO]
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 once 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 survive. No-show and utilisation analysis still runs. Because the offset can reverse the shift, keeping it makes the file pseudonymous under Art. 4(5), so store it apart from the data.

How long may we hold identifiable booking records?

UK GDPR Art. 5(1)(e) says no longer than the purpose needs, and the Records Management Code of Practice for Health and Social Care 2021 turns that into specific NHS retention periods by record type. De-identifying the analytics copy lets you keep the operational value after the identifiable copy is disposed of.

Are clinician names removed?

They can be. A clinician's name is not the patient's personal data, but blinded capacity studies usually swap it so comparisons stay about the service rather than about individuals.