anonym.legal

By · Last updated 2026-04-21

Nazaj na blogZdravstvo

Reverzibilna de-identifikacija za klinicne raziskave

Ko studija odkrije nepricakovano tveganje biomarkerja pri 47 od 5.000 udelezencev, morajo raziskovalci stopiti v stik z resnicnimi pacienti. Le 23 % orodij za anonimizacijo ponuja pravo reverzibilnost.

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

Reverzibilna de-identifikacija za klinicne raziskave

Dolgorocne studije soocajo s tezko kompromis. Pacienti morajo ostati skriti med studijo. Pravila IRB to zahtevajo. Zaupanje pacientov je od tega odvisno. Toda rezultat lahko zahteva poznejsi ponovni stik. Trajna de-identifikacija odstrani to pot. Reverzibilna de-identifikacija jo ohranja odprto.

Glejte, kako to podpiramo v nasem pregledu skladnosti in varnostnih praksah.

Tezava ponovnega stika

Onkoloski center izvaja studijo s 5.000 pacienti. Sredi studije 47 pacientov pokaze markerje, povezane z agresivno vrsto raka. To ni bilo v prvotnem obsegu. Eticki odbor pregleda ugotovitev. Odobri ponovni stik. Velja dolznost opozarjanja.

Ce je bila prvotna de-identifikacija trajna, je ekipa v slepi ulici. Nakljucni kodi brez karte ne dajeta nobenega nacina nazaj. 47 zapisov se ne da povezati z resnicnimi pacienti. Na ugotovitev se ne da ukrepati. Pacientov, ki morda potrebujejo nego, ni mogoce doseci. Nastavitev zasebnosti je v svojem najbolj kriticnem trenutku spodletela.

To ni redkost. Katera koli dolgorocna studija lahko naleti na nepricakovano ugotovitev. Doktrina dolznosti opozarjanja zahteva ukrepanje, ko je najdeno tveganje. Brez poti za re-identifikacijo to ukrepanje ni mogoco.

Pravila locevanja kljucev po GDPR

Smernice EDPB 05/2022 neposredno obravnavajo to tezavo. Psevdonimizacija je veljaven korak pri varstvu podatkov. Ohranja moznost re-identifikacije odprto. Odobren postopek jo lahko uporabi, ko je potrebna.

Osnovno pravilo je locevanje kljucev. Sifrirni kljuc mora biti shranjen loceno od psevdonimiziranih podatkov. Kontrole morajo blokirati kakrsen koli dostop, ki ni odobren. Ekipa, ki uporablja podatke, ne sme imeti tudi kljuca. Re-identifikacija mora zahtevati formalen, evidentiran korak.

Anketa IAPP iz leta 2024 je ugotovila, da le 23 % orodij za anonimizacijo ponuja pravo reverzibilnost. Vecina jih uporablja trajno maskiranje ali zamenjavo. Te metode blokirajo ponovni stik, ki ga zahteva dolznost opozarjanja.

Kako deluje arhitektura

Skladna nastavitev uporablja reverzibilno sifriranje z AES-256-GCM. Vsak ID pacienta se pretvori v zeton. Isti pacient se v vseh studijskih datotekah preslika na isti zeton. Podatkovne povezave ostanejo nedotaknjene. V delovnem naboru se ne pojavljajo nobeni surovi ID-ji.

Sifrirni kljuc hrani skrbnik podatkov. Shranjen je loceno od podatkov. Vsaka uporaba kljuca zahteva pisno, odobreno zahtevo.

Ekipa med analizo dela samo z zetoni. Ko je oznacenih 47 prizadetih pacientov, eticki odbor odobri re-identifikacijo. Skrbnik aplicira kljuc samo na teh 47 zapisov. Ekipa dobi prave ID-je za teh 47. Ostalih 4.953 pacientov ostane zascitenih.

Mogoca je samo ciljna re-identifikacija. Preostanek nabora podatkov se nikoli ne dotakne.

Za vec o tem, kako se psevdonimizacija razlikuje od popolne anonimizacije, glejte nas vodnik za anonimizacijo in psevdonimizacijo GDPR.

Viri

Ste pripravljeni zaščititi svoje podatke?

Začnite z anonimizacijo PII z več kot 285 tipi entitet v 48 jezikih.

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.