Pseudonymising Pathology, Radiology, and Imaging Reports – UK GDPR-compliant anonymisation per UK GDPR Art. 9

Pathology, radiology, and imaging reports embed patient identifiers in report headers, DICOM metadata, and printed overlays — sometimes repeated across dozens of images in a single study. anonym.legal pseudonymises patient name, date of birth, NHS number, and accession numbers in both document text and DICOM header tags, preserving diagnostic findings, imaging sequences, and measurement data for clinical review or medicolegal use.

When this applies

This task applies when pathology results, radiology reports, or DICOM image sets are shared with external radiologists for second-opinion review, disclosed in personal-injury litigation, or submitted as anonymised case studies for medical education, and the clinical findings must be preserved but patient identity must be protected.

  1. Upload the pathology report (PDF or DOCX) or export the DICOM study; anonym.legal processes both document and DICOM header formats.
  2. The engine detects patient identifiers in PDF headers, free-text report bodies, and DICOM tag fields (PatientName, PatientID, PatientBirthDate, InstitutionName).
  3. Each patient's identifiers are replaced with consistent pseudonyms across all images and report pages in the study.
  4. Diagnostic findings, imaging measurements, Hounsfield-unit values, and pathological grading are preserved in full.
  5. Requesting clinician and reporting radiologist names are pseudonymised.
  6. A mapping table and a de-identified DICOM export are produced with UK data residency.

What you provide

  • Pathology report (PDF or DOCX) or DICOM study export
  • Accession number list (to verify study completeness)
  • Any accompanying clinical request form naming the patient

Limitations & cautions

  • DICOM pixel data that overlays patient information (burned-in annotations) requires additional image-processing de-identification beyond header tag removal — confirm whether your DICOM series includes burned-in PHI before relying on header-only de-identification.
  • The tool pseudonymises header data but does not validate the diagnostic accuracy of the report.
  • Rare imaging findings may carry residual re-identification risk in small-population clinical settings.

FAQ

Does the DICOM de-identification comply with DICOM PS3.15 Attribute Confidentiality Profiles?

anonym.legal applies pseudonymisation to the patient-identifiable DICOM tags. For compliance with a specific PS3.15 profile (e.g. Basic Application Level Confidentiality), configure the tag-removal profile to match the profile's required attribute actions.

Can I share pseudonymised DICOM studies with overseas radiologists for second opinion?

After pseudonymisation, the study no longer contains personal data identifiable to a specific individual, so international transfer restrictions applicable to personal data under UK GDPR would not apply to the pseudonymised version. Confirm with your Data Protection Officer.

Are accession numbers and study instance UIDs replaced or removed?

Accession numbers and study UIDs that could link back to an identifiable patient record are replaced with synthetic values. New UIDs are generated consistently so multi-series studies remain internally coherent.

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.