Admission Record Anonymisation with anonym.plus

Clear identifiers from intake files while the clinical context stays.

Admission-record anonymisation removes the intake identifiers from a file under DPA 2018 and the NHS Confidentiality Code before reuse. anonym.plus works on your device and keeps the complaint and history for analysis.

When this applies

Intake files are identifier-dense: full demographics, insurance, next of kin, and contacts. To use them for capacity work or teaching, strip that data first.

How anonym.plus handles it

  1. Open the file in anonym.plus on your device.
  2. It finds demographic, insurance, and next-of-kin fields.
  3. Contact names and numbers get flagged as related-party identifiers.
  4. Swap or black out the confirmed items.
  5. Save the clean intake file on your device.

What you need to provide

Patient data entity types detected

Categoryanonym.plus entity typeExample
NamesPERSONpatient & next of kin → [NAME]
NHS NumberUK_NHSNHS 943 476 5919 → [NHS_NO]
ContactPHONE_NUMBERemergency tel → [PHONE]
LocationLOCATIONhome address → [ADDRESS]
DatesDATE_TIMEadmit date → [DATE]
Record IDsMEDICAL_RECORD_NUMBERencounter ID → [ENCOUNTER]

Compliance achieved

Anonymise admission records offline — see plans & start free →

Limitations & cautions

Intake forms often pack NHS number and guarantor data into fixed layouts. Check that your custom fields are mapped, so nothing slips by. Relatives’ identifiers must go too, since they are personal data when tied to the patient.

Frequently asked questions

Are contact details personal data?

Yes. When a relative’s name or number sits in the patient’s file, it is personal data and must go for de-identification.

Can I keep diagnosis codes?

Yes. Non-identifier clinical and admin codes can stay while personal data goes, via an allow-list.

Does this work on EPR intake summaries?

Yes. Printed forms and structured EPR intake exports are both supported.