Admission-record anonymisation removes the intake identifiers from a hospital admission file before it is reused. The NHS number on that form is not an incidental field: NHS Act 2006 s.251A makes it the consistent identifier that health and adult social care bodies must use, so it appears on almost every intake record and must always be cleared. anonym.plus works on your device and keeps the presenting complaint and history for analysis.
When this applies
Intake files are identifier-dense: full demographics, next of kin, emergency contacts, and often a capacity note. Next-of-kin details were never collected from the person they describe, which is what UK GDPR Art. 14 covers, and they come out with the patient's own data.
How anonym.plus handles it
- Open the file in anonym.plus on your device.
- It finds demographic, funding, and next-of-kin fields.
- Contact names and numbers get flagged as related-party identifiers.
- Swap or black out the confirmed items.
- Save the clean intake file on your device.
What you need to provide
- The intake file (PDF, DOCX, or EPR export).
- An operator (Redact for slim audit copies).
- Optional rules to keep non-identifying admin codes.
Patient data entity types detected
| Category | anonym.plus entity type | Example |
|---|---|---|
| Names | PERSON | patient & next of kin → [NAME] |
| NHS Number | UK_NHS | NHS 943 476 5919 → [NHS_NO] |
| Contact | PHONE_NUMBER | emergency tel → [PHONE] |
| Location | LOCATION | home address → [ADDRESS] |
| Dates | DATE_TIME | admit date → [DATE] |
| Record IDs | MEDICAL_RECORD_NUMBER | encounter ID → [ENCOUNTER] |
Compliance achieved
- Always flags the NHS number, which NHS Act 2006 s.251A makes the consistent identifier across health and adult social care.
- Treats next-of-kin data as personal data in its own right — UK GDPR Art. 14 governs data not obtained from the individual it describes.
- A capacity note recorded at admission engages Mental Capacity Act 2005 ss.2-3 and is health data in itself.
- The underlying record is held under DPA 2018 Schedule 1, Part 1, paragraph 2 (health or social care purposes).
- Follows the NHS Confidentiality Code of Practice for reuse of intake data.
- Offline work keeps intake data inside your site.
Anonymise admission records offline — see plans & start free →
Limitations & cautions
Intake forms pack the NHS number and funding data into fixed layouts, so check that your custom fields are mapped and nothing slips by. Relatives' identifiers must go too. A capacity assessment recorded under Mental Capacity Act 2005 ss.2-3 often quotes what the person said, which can carry indirect clues that need a human read.
Frequently asked questions
Are next-of-kin contact details personal data?
Yes. A relative's name or number in the patient's file is that relative's personal data, and because it was collected from the patient rather than from them, UK GDPR Art. 14 is the provision that applies. It must be removed for de-identification alongside the patient's own details.
Why is the NHS number always flagged?
Because it is designed to be linkable. NHS Act 2006 s.251A requires health and adult social care bodies to use the NHS number as the consistent identifier for an individual, which is precisely what makes it the single most re-identifying field on an intake form.
What about the capacity assessment in the pack?
Treat it as clinical content, not admin. A capacity assessment applies the tests in Mental Capacity Act 2005 ss.2-3 and often quotes the person directly, so it carries both health data and indirect identifiers. Review it by hand after the automatic pass.