anonym.legal

By · Last updated 2026-04-21

Terug na BlogGesondheidsorg

Omkeerbere De-ID vir Kliniese Navorsing

Wanneer 'n studie onverwagse biomarkrisiko by 47 van 5 000 deelnemers vind, moet navorsers werklike pasiente kontak. Slegs 23% van anonimiseringsnutsgoed bied.

April 21, 20269 min lees
reversible de-identificationclinical research pseudonymizationpatient re-contact protocolIRB data managementHIPAA reversible encryption

Omkeerbere De-ID vir Kliniese Navorsing

Lang proewe staan voor 'n moeilike kompromis. Pasiente moet gedurende die studie versteek bly. IRB-reels vereis dit. Pasientvertroue hang daarvan af. Maar 'n resultaat mag later her-kontak vereis. Permanente de-ID verwyder daai pad. Omkeerbere de-ID hou dit oop.

Sien hoe ons dit ondersteun in ons nakomingsoorsig en sekuriteitspraktyke.

Die Her-Kontakprobleem

'n Onkologiesentrum voer 'n 5 000-pasient-studie uit. Halfpad deur die proef toon 47 pasiente merkers wat verband hou met 'n aggressiewe kankertipe. Dit was nie in die oorspronklike omvang nie. Die etiekraad hersien die bevinding. Dit keur her-kontak goed. Plig-om-te-waarsku is van toepassing.

As die oorspronklike de-ID permanent was, sit die span vas. Ewekansige kodes sonder 'n kaart gee geen pad terug nie. Die 47 rekords kan nie gekoppel word aan werklike pasiente nie. Op die bevinding kan nie opgetree word nie. Pasiente wat moontlik sorg benodig, kan nie bereik word nie. Die privaatheidopstelling het op sy mees kritieke punt misluk.

Dit is nie skaars nie. Enige lang proef kan 'n onverwagse bevinding tref. Plig-om-te-waarsku-leer vereis optrede wanneer risiko gevind word. Sonder 'n her-ID-pad is daai optrede nie moontlik nie.

GDPR Sleutelskeidingsreels

EDPB Riglyne 05/2022 spreek hierdie probleem direk aan. Pseudonimisering is 'n geldige databeskermingstap. Dit hou die opsie oop om weer te identifiseer. 'n Goedgekeurde proses kan dit gebruik wanneer nodig.

Die kernreel is sleutelskeiding. Die dekripsiesleutel moet afsonderlik van die gepseudo-nimiseerde data gehou word. Kontroles moet enige toegang blokkeer wat nie goedgekeur is nie. Die span wat die data gebruik, moet nie ook die sleutel hou nie. Her-ID moet 'n formele, geregistreerde stap vereis.

IAPP se 2024-opname het bevind dat slegs 23% van anonimiseringsnutsgoed ware omkeerbaarheid bied. Die meeste pas permanente maskering of vervanging toe. Daai metodes blokkeer die her-kontak wat plig-om-te-waarsku vereis.

Hoe die Argitektuur Werk

'n Voldoenende opstelling gebruik omkeerbere enkripsie met AES-256-GCM. Elke pasient-ID word in 'n token omgesit. Dieselfde pasient wys na dieselfde token in alle studielees. Datakoppelings bly ongeskonde. Geen rou ID's verskyn in die werkstelsel nie.

Die dekripsiesleutel word gehou deur 'n dataversorger. Dit word afsonderlik van die data gehou. Enige gebruik van die sleutel vereis 'n skriftelike, goedgekeurde versoek.

Die span werk slegs met tokens tydens analise. Wanneer die 47 geraakte pasiente gemerk word, keur die etiekraad her-ID goed. Die versorger pas die sleutel toe op slegs daai 47 rekords. Die span kry werklike ID's vir daai 47. Die ander 4 953 pasiente bly beskerm.

Slegs geteikende her-ID is moontlik. Die res van die datastel word nooit aangeraak nie.

Vir meer oor hoe pseudonimisering van volle anonimisering verskil, sien ons GDPR-anonimisering vs. pseudonimisering-gids.

Bronne

Gereed om u data te beskerm?

Begin om PII te anonimiseer met 285+ entiteitstipes in 48 tale.

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.

Related reading

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.