Capacity Planning Dataset Anonymisation with anonym.plus

Turn occupancy and flow data into anonymous data outside UK GDPR scope.

Capacity-planning anonymisation is the removal of personal information from occupancy and flow files. Once the result is truly anonymous, it leaves scope under Recital 26. anonym.plus does this on a local device and keeps the bed and timing detail usable.

When this applies

Flow files track each admission, the bed, and the staff on shift. To model demand or share with planners, you can anonymise them and drop the compliance burden.

How anonym.plus handles it

  1. Open the file in anonym.plus on a local device.
  2. It scans patient, staff, bed, and timestamp fields.
  3. Turn the reversible map off so no key is kept.
  4. Shift the times so flow gaps and trends survive.
  5. Swap each person for a non-reversible label.
  6. Save the result. The source never leaves your machine.

What you need to provide

Patient data entity types detected

Categoryanonym.plus entity typeExample
PatientPERSONadmission: O. Okafor → [PATIENT_n]
StaffPERSONshift lead: RN Vidal → [STAFF_n]
DatesDATE_TIMEadmit 13:20 → shifted [TIME]
LocationLOCATIONBed 8, Ward C → [BED]
Record IDsMEDICAL_RECORD_NUMBERencounter NHS No. → [ENCOUNTER]
Staff IDIDlogin rvidal → [USERNAME]

Compliance achieved

Anonymise capacity datasets offline — see plans & start free →

Limitations & cautions

Bed and timing detail is usually safe, but a rare admission at an odd hour on a small ward can re-identify after names go. Shift the times, coarsen rare cells, and keep no key before you treat the result as anonymous.

Frequently asked questions

Is occupancy information personal?

Each admission row names a patient and often the staff on shift, so it is personal. The bed and timing fields are not, once names go and times shift.

Do the flow curves survive?

Yes. Shifting times by a steady offset keeps the gaps, so occupancy and demand curves still hold.

Anonymous or pseudonymous?

Keep a key and it stays in scope. Turn the key off and, with low residual risk, Recital 26 takes it out of scope.