Anonymising Hospital Discharge Summaries for Clinical Audit – UK GDPR-compliant anonymisation per NHS Records Management Code of Practice 2021

A hospital discharge summary is a clinical episode record constituting special-category health data under UK GDPR Article 9(2)(h), documenting diagnoses, procedures, and follow-up instructions. The NHS Records Management Code of Practice 2023 (NHS RMC 2023) requires adult records to be retained for 8 years; maternity records for 25 years. anonym.legal pseudonymises patient and clinician identifiers, preserving ICD-10 codes and discharge medications for clinical audit.

When this applies

This task applies when discharge summaries are extracted for clinical audit, NHS National Clinical Audit submissions, or service improvement reviews where the reviewing team requires episode-level clinical data but not the identity of individual patients or named responsible clinicians. The Care Quality Commission, which registers over 41,000 active providers in England, may inspect discharge summary governance as part of its regulatory oversight.

  1. Upload discharge summaries individually or in batch (PDF, DOCX, or HL7 CDA format).
  2. The engine detects patient name, NHS number, date of birth, ward location (where named after a patient or clinician), and the responsible consultant's name.
  3. Each patient and named clinician is pseudonymised consistently; admission and discharge dates, procedure codes, and medication names are preserved.
  4. ICD-10 diagnosis codes, OPCS-4 procedure codes, and SNOMED CT terms in structured fields are not altered.
  5. Discharge instructions and follow-up clinic references are preserved in clear text; any named specialist in follow-up referrals is pseudonymised.
  6. A mapping table is produced with UK data residency.

What you provide

  • Hospital discharge summary documents (PDF, DOCX, or HL7 CDA)
  • Patient encounter identifier list (to verify batch completeness)

Limitations & cautions

  • The NHS Records Management Code of Practice 2023 sets retention periods of 8 years for adult health records and 25 years for maternity records; pseudonymised summaries used for audit must still be managed under the applicable retention schedule.
  • Discharge summaries referencing rare surgical procedures or unusually complex multimorbidity may carry residual re-identification risk in small patient populations.
  • The tool does not validate clinical coding accuracy — obtain clinical coding review separately. Breaches can attract fines of up to £17.5 million or 4% of annual global turnover under DPA 2018 s.157.

FAQ

Can pseudonymised discharge summaries be submitted to NHS national clinical audit programmes?

Pseudonymised summaries are suitable for internal pre-submission review and quality checking. Check the specific national audit programme's data specification; most require either identified or formally anonymised data rather than pseudonymised data for submission. According to the ICO's 2021–22 guidance, pseudonymised records remain personal data under UK GDPR.

Are procedure-specific complication rates and readmission flags preserved?

Yes. Clinical episode data — procedure outcomes, complication flags, and readmission indicators — are preserved; only identifiers are pseudonymised. The 8-year retention period under the NHS Records Management Code of Practice 2023 applies to the original identified record, not to pseudonymised audit extracts.

Does the engine handle batches of summaries from multiple wards or specialties?

Yes. Batch processing applies consistent pseudonyms across all summaries in the upload, so a patient admitted to two different wards receives the same pseudonym throughout the batch. The 8 Caldicott Principles (updated 2013, with Principle 8 added in 2020) require data minimisation and purpose limitation in all such sharing.

Healthcare Records

About this page

We update this page when our platform or the law changes.

Read our founder note for how we work.

Each change shows up in the timestamp at the top.

We follow these rules

  • GDPR (EU 2016/679).
  • ISO/IEC 27001:2022.
  • NIS2 (EU 2022/2555).
  • HIPAA safe harbor under 45 CFR § 164.514(b)(2).

Our promise

We do not sell your data.

We do not train models on your text.

We store your files in Germany.

You can delete your account at any time.

You own your work.

Where we run

Our company HQ is in Saarbrücken, Germany. Our servers run in Hetzner's Falkenstein datacenter.

Hetzner holds ISO 27001 certification.

All data stays in the EU.

Backups run every day.

Need help?

Email support@anonym.legal.

We reply within one business day.

How we test

We run a full check suite on every release.

Each surface gets its own sweep script and report.

Human reviewers spot-check the output each week.

We track recall and precision on a labelled set.

Bad runs block the deploy.

What we never do

  • We never sell your information to third parties.
  • We never train models on what you upload.
  • We never keep your work after you delete it.
  • We never share keys with any outside firm.
  • We never run ads inside the product.

Plans in plain words

We sell credits, not seats.

One credit covers one short job.

Long jobs use a few credits each.

You can top up at any time.

Unused credits roll over each month.

Read the plans page for current rates.

Who built this

A small team of engineers and lawyers built this.

We ship from Europe and work in the open.

Our founder note spells out why we started.

Where to start

How the parts fit

A browser add-on cleans text inside Chrome.

A Word plug-in handles drafts in Office.

A small desktop tool works on whole folders.

An agent protocol link feeds large models safely.

All four share one core engine and one rule set.

Words from our team

We started this work after a lunch about cookies.

One friend kept getting odd ads on her phone.

We asked why a court file leaked through a draft.

We sketched the first build on a napkin that week.

By month three we had a tiny demo for a friend.

She used it on her first case the next day.

Common questions we hear

Can the tool read scanned PDFs? Yes, with OCR.

Does it work on long files? Yes, in small chunks.

Can I roll my own rule set? Yes, save it as a preset.

Does it run offline? The desktop build runs offline.

Do you keep my files? No, the cloud build wipes after each run.

Will it learn from my work? No, we never train on inputs.

A short tour of the workflow

Upload a file or paste a snippet of prose.

Pick the entities you want gone from the draft.

Choose a method: replace, mask, hash, encrypt, or redact.

Press run and watch the side panel show each hit.

Skim the result and tweak any rule that misfired.

Save the cleaned file or send it to a teammate.