Nursing-note anonymisation removes personal details until the file is no longer health data under UK GDPR Art. 9(1). Section 10 of the NMC Code requires the nurse's original record to be clear and accurate, made at the time, and attributed, dated, and timed — so anonymisation is done on a copy, never on the record of care. If you keep the alias key, the copy is only pseudonymous under UK GDPR Art. 4(5) and stays in scope. Drop the key and Recital 26 takes it out. anonym.plus does all of this on a local device.
When this applies
Ward notes are special-category health data and need an Art. 9 condition before you can use them. Make them genuinely anonymous and that burden falls away for staffing analysis, teaching, or audit.
How anonym.plus handles it
- Open a copy of the notes in anonym.plus on a local device.
- The tool spots patient names, care dates, bay, and contacts.
- Swap each one for a non-reversible label to reach true anonymity.
- Keep no alias key if you want the data outside UK GDPR scope.
- Save the clean file on your device.
What you need to provide
- A copy of the notes (DOCX, PDF, TXT, or EPR export).
- Replace, with the reversible map turned off for full anonymity.
- Optional language setting for Welsh or other languages.
Patient data entity types detected
| Category | anonym.plus entity type | Example |
|---|---|---|
| Names | PERSON | Mr Bennett → [PATIENT] |
| Dates | DATE_TIME | Night shift 12/03 → [DATE] |
| Location | LOCATION | Bay 3, Bed 7 → [ROOM] |
| NHS Number | UK_NHS | NHS 943 476 5919 → [NHS_NO] |
| Contact | PHONE_NUMBER | 0113 496 0123 → [PHONE] |
| Names | PERSON | Nurse Sara → [STAFF] |
Compliance achieved
- Strips the health data UK GDPR Art. 9(1) treats as special category.
- Preserves what section 10 of the NMC Code requires of the original: clear, accurate records, attributed, dated, and timed.
- Keeping an alias key leaves the file pseudonymous under UK GDPR Art. 4(5), still personal data; dropping it is what Recital 26 requires.
- The provider's own record still has to satisfy reg. 17(2)(c) of the HSCA 2008 (Regulated Activities) Regulations 2014.
- On-device work supports NHS data-residency expectations under the NHS Data Security and Protection Toolkit.
Anonymise nursing notes offline — see plans & start free →
Limitations & cautions
True anonymity is a high bar. The file is anonymous only if no one can reasonably re-identify it. A kept alias key makes the output pseudonymous under Art. 4(5), not anonymous, and it stays in scope. Turn the map off and apply the ICO motivated-intruder test before you treat the result as outside the regulation.
Frequently asked questions
Anonymous or pseudonymous — what is the difference?
Pseudonymous output keeps a key that can re-link it to the person, so UK GDPR Art. 4(5) still treats it as personal data and every duty continues to apply. Anonymous output drops that key for good. Only then does Recital 26 take the file out of scope, and only if the remaining text cannot single anyone out.
Can I anonymise the nursing record itself?
No. Section 10 of the NMC Code requires the record of care to be accurate and attributed, and regulation 17(2)(c) of the HSCA 2008 (Regulated Activities) Regulations 2014 requires the provider to keep it complete. Export a copy and anonymise that.
Can I reuse the file without patient consent?
Truly anonymous data is no longer personal data, so UK GDPR consent rules do not apply to it. The whole question turns on whether the result really cannot be reversed, which is a judgement you make with the ICO motivated-intruder test, not something the tool can decide for you.