Pseudonymising NHS Continuing Healthcare Assessment Packs – UK GDPR-compliant anonymisation per DPA 2018 Sch.1 Pt.1

NHS Continuing Healthcare (CHC) assessment packs contain multi-domain clinical assessments, decision-support tools, and care-funding determinations that link a patient's identity to diagnoses, care needs, and funding decisions — all constituting special-category data under DPA 2018 Schedule 1 Part 1. anonym.legal pseudonymises patient and assessor identifiers across the pack while preserving domain scores, clinical evidence, and funding rationale for appeal review or service audit.

When this applies

This task applies when CHC assessment packs are reviewed by appeal panels, NHS England regional teams, or independent advocates who require the clinical evidence base and domain scoring but do not need to identify the individual patient.

  1. Upload the CHC assessment pack (PDF or DOCX) to anonym.legal.
  2. The engine identifies patient name, date of birth, NHS number, address, and the names of named assessors and care coordinators.
  3. Each individual is pseudonymised consistently across all sections of the pack.
  4. Domain scores, clinical evidence citations, and eligibility determinations are preserved in clear text.
  5. The decision rationale and any dissenting assessor opinions are preserved in full.
  6. A reversible mapping table is produced with UK data residency.

What you provide

  • NHS Continuing Healthcare decision support tool and assessment documents
  • Any accompanying care plan or needs assessment report

Limitations & cautions

  • CHC appeal documentation submitted to NHS England must contain the patient's real identity — the pseudonymised version is for preparation and internal review only.
  • The tool does not assess the clinical or legal correctness of the eligibility determination — obtain specialist CHC advocacy or legal advice.
  • Named NHS care coordinators in the pack are pseudonymised; confirm that the pseudonymised version still identifies assessors by role for audit trail purposes.

FAQ

Can the pseudonymised assessment pack be shared with a patient's independent advocate?

Sharing with an advocate authorised by the patient would typically involve re-identifying the relevant patient. If the advocate requires the pack for training purposes only, the pseudonymised version may be appropriate — confirm the purpose and lawful basis with your Data Protection Officer.

Are the domain scores and eligibility determination preserved intact?

Yes. All domain scores, priority / severe / high / moderate classifications, and the eligibility determination are preserved; only the personal identifiers of the patient and named assessors are pseudonymised.

Does the tool handle multi-disciplinary assessment packs from different clinicians?

Yes. Input from multiple named assessors across different clinical specialties is pseudonymised consistently; each assessor receives a distinct pseudonym.

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.