Anonymising NHS SAR Responses Before Release – UK GDPR-compliant anonymisation per UK GDPR Art. 9

An NHS Subject Access Request response bundles together records from multiple care settings — GP notes, hospital letters, mental health assessments, and medication records — creating a high-density personal-data package under UK GDPR Art. 15. anonym.legal pseudonymises third-party personal data (named clinicians, other patients inadvertently mentioned) in the bundle before release, ensuring the requester receives their own health information without exposing third parties.

When this applies

This task applies when an NHS Trust or GP surgery has compiled a SAR response bundle and must redact or pseudonymise third-party personal data — other patients named in ward notes, named clinicians in records about disciplinary matters — before releasing the bundle to the requesting patient.

  1. Upload the compiled SAR response bundle to anonym.legal.
  2. The engine scans the entire bundle for third-party personal data: other patients named in shared ward notes, clinicians named in complaint correspondence, and family members mentioned in social-history sections.
  3. Third-party individuals are pseudonymised; the requesting patient's own data is preserved in full.
  4. Clinical content, dates, diagnosis codes, and care-plan entries directly relating to the requesting patient are preserved.
  5. A review report flags all pseudonymisation actions for the Data Controller to verify before release.
  6. The processed bundle is prepared for release to the requester under the UK GDPR Art. 15 right of access.

What you provide

  • Compiled SAR response bundle (PDF or DOCX)
  • Patient identity confirmation (to distinguish the requester from third parties)
  • List of known third-party individuals to flag (optional, improves detection)

Limitations & cautions

  • The tool pseudonymises third-party personal data but does not constitute a legal assessment of whether particular information is exempt from disclosure under DPA 2018 Schedule 2 exemptions — obtain legal advice on exemption claims.
  • Complex ward notes where multiple patients are discussed in a single entry require careful review of the pseudonymisation output before release.
  • The NHS one-month SAR response deadline cannot be extended solely on account of pseudonymisation processing time; plan accordingly.

FAQ

Must the NHS Trust pseudonymise third-party clinician names in the SAR bundle?

Whether clinician names constitute third-party personal data that must be withheld depends on whether the clinician has a reasonable expectation of privacy in that context. The ICO's subject access guidance indicates that healthcare professionals' names in their professional capacity may not require redaction. Obtain legal advice for your specific facts.

Can the engine distinguish between the requesting patient's own data and third-party data?

Yes, provided the requesting patient's identity is supplied as a reference. The engine preserves occurrences of the requester's identifiers while pseudonymising those of other named individuals.

Does the tool handle SAR bundles that include scanned handwritten notes?

Scanned handwritten notes require OCR pre-processing. After OCR conversion, the engine detects named individuals in the transcribed text. OCR accuracy affects coverage for poorly legible handwriting.

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 servers live in Falkenstein, Germany.

We use Hetzner. They hold 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.