Anonymise Occupational Health Reports for HR Decision-Making and Disclosure – UK GDPR-compliant anonymisation per UK GDPR Art. 9

Occupational health reports contain special category health data under UK GDPR Art. 9 and DPA 2018 Schedule 1, identifying the employee by name and linking that identity to detailed clinical findings, fitness assessments, and recommended workplace adjustments. anonym.legal pseudonymises this sensitive data so that occupational health advice can be reviewed by HR decision-makers or shared with advisers without unnecessary disclosure of the employee's medical identity.

When this applies

Use this workflow when occupational health reports need to be reviewed by HR personnel, management, or external advisers who require the occupational health recommendations but do not need to know the specific employee's identity in conjunction with the clinical findings.

  1. Upload the occupational health report in its original format.
  2. The engine identifies the employee's name, date of birth, role, and any personal identifiers alongside the health and clinical content, flagging the entire document as containing special category data.
  3. The employee's personal identifiers are pseudonymised consistently, while clinical recommendations, fitness-for-work conclusions, and suggested adjustments are retained in plain text.
  4. The occupational health provider's details are retained or pseudonymised according to your configuration.
  5. The reversible mapping is encrypted and stored with EU data residency, with enhanced access controls reflecting the sensitivity of the data.
  6. The pseudonymised report is shared with the authorised HR recipient; re-identification is available via the stored key when required for formal proceedings or further clinical referral.

What you provide

  • Occupational health report in PDF or DOCX format
  • Employee's name and employee number for reference
  • Confirmation of which clinical content fields should be retained versus pseudonymised

Limitations & cautions

  • Occupational health reports contain special category data under UK GDPR Art. 9 and DPA 2018 Schedule 1; even after pseudonymisation, these documents should be shared only with authorised recipients and under a data-processing agreement.
  • Clinical content — diagnoses, prognoses, and treatment references — is retained in plain text and may itself be identifying in the context of a small workplace; manual review of the output is strongly recommended.
  • anonym.legal does not provide clinical advice or interpret occupational health recommendations; that remains the occupational health physician's responsibility.

FAQ

Is occupational health data automatically treated as special category data?

Yes. Health data is special category data under UK GDPR Art. 9 and DPA 2018 Schedule 1 Part 1. The engine automatically applies enhanced pseudonymisation to occupational health reports and flags them for additional access controls.

Will fitness-for-work recommendations be retained after pseudonymisation?

Yes. The occupational health recommendations — fit for work, fit with adjustments, or not fit — and the suggested workplace adjustments are retained as clinical content. Only the personal identifiers linking those conclusions to the named employee are pseudonymised.

Can pseudonymised occupational health reports be shared with line managers?

HR best practice is to share only the recommendations relevant to workplace adjustments with line managers, not the full clinical report. Pseudonymisation supports this by separating the clinical content from the employee's identity. The full re-identified report remains accessible to authorised HR personnel via the stored key.

How should I handle occupational health reports in an employment tribunal disclosure?

For formal employment tribunal disclosure, re-identified reports must be provided as part of the disclosure bundle. The pseudonymised version is useful for internal review and adviser consultation prior to disclosure, but the original identified document must be used in tribunal proceedings.

Employment Law

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.