Staff-record anonymisation is the removal of personal details from a clinician’s HR file. Health and occupational information in it is special-category under UK GDPR Art. 9(1), and the employment gateway in Art. 9(2)(b) needs the domestic condition set out in DPA 2018 Schedule 1, Part 1, paragraph 1 to apply. anonym.plus does this on a local device, so the file no longer names the worker.
When this applies
An HR file holds a clinician’s name, ID, and health notes, processed under the employment condition rather than the patient’s own care. To study rota patterns or sickness trends across many staff, you can anonymise the file and drop that legal-basis burden entirely.
How anonym.plus handles it
- Open the HR file in anonym.plus on a local device.
- Local OCR reads any scanned pages first.
- It flags the worker’s name, ID, contacts, and health notes.
- Turn the reversible map off so no re-link key is kept.
- Swap each detail for a non-reversible label.
- Save the result. The source never leaves your machine.
What you need to provide
- The HR file (DOCX, PDF, TXT, or scan).
- Replace, with the map off for full anonymity.
- Optional language setting for Welsh or other supported tongues.
Patient data entity types detected
| Category | anonym.plus entity type | Example |
|---|---|---|
| Staff | PERSON | Dr. Ingrid Davies → [CLINICIAN] |
| Staff ID | ID | employee no. 20471 → [EMP_ID] |
| Dates | DATE_TIME | appointed 09/2019 → [DATE] |
| Identifiers | NATIONAL_ID | NI No. AB 12 34 56 C → [ID] |
| Contact | EMAIL_ADDRESS | i.davies@example.nhs.uk → [EMAIL] |
| Location | LOCATION | 12 High Street, Leeds → [ADDRESS] |
Compliance achieved
- Strips UK GDPR Art. 9(1) special-category staff information processed under the employment gateway.
- The employment condition in DPA 2018 Schedule 1, Part 1, paragraph 1 covers the original file; anonymising it removes the need to keep relying on that condition for a second use.
- True anonymity puts the result beyond the Act by Recital 26.
- On-device work keeps the dossier under your organisation’s control.
Anonymise staff records offline — see plans & start free →
Limitations & cautions
An HR file holds rich detail. Even with the name gone, a rare role at one small site can re-identify a worker. Apply the motivated-intruder test and keep no key before you call the output anonymous.
Frequently asked questions
Is employee information special-category under UK GDPR?
Health and trade-union records in an HR file are special-category under Art. 9(1). Processing them for the ordinary employment relationship relies on the Art. 9(2)(b) gateway together with the domestic condition in DPA 2018 Schedule 1, Part 1, paragraph 1. Anonymising the file for research or workforce planning removes the need to keep relying on that condition.
Anonymous or pseudonymous — which do I get?
Keep a key to re-link and the output is pseudonymous, still in scope. Turn the key off and, with low residual risk, Recital 26 takes it out of scope entirely, so neither Art. 9 nor the Schedule 1 condition needs to be revisited for the second use.
Does it read Welsh-language documents?
Yes. Multiple languages are supported, which matters for correct name and date detection across the devolved nations, not just England.