anonym.legal

By · Last updated 2026-04-26

Nazaj na blogZdravstvo

Reverzibilno sifriranje za ponovni stik v raziskavah

Pacienta_001 ne morete kontaktirati za kontrolni obisk. IRB zdaj zahteva dokumentirane protokole za ponovno identifikacijo - dokazati morate, da LAHKO ponovno identificirate pod dolocenimi pogoji.

April 26, 20268 min branja
research re-identification protocollongitudinal study follow-upIRB pseudonymization requirementcontrolled re-identificationdeterministic encryption

Protokol IRB za ponovni stik: Vodic po reverzibilnem sifriranju

IRB zdaj prosijo za vec kot samo nacrt de-identifikacije. Potrebujejo tudi nacrt ponovnega stika. Dokazati morate dve stvari. Prvic, zunanje stranke ne morejo doseci pravih imen pacientov. Drugic, vasa ekipa lahko - ko eticno dovoljenje to dopusca.

To dvosmerno pravilo izhaja iz resnicnih izkusenj. Dolge studije so odkrile nujne rezultate sredi preskusanja. Ampak zapisi so bili zaklenjeni. Pot nazaj ni obstajala. To je blokiralo zdravnisko oskrbo. Regulatorji so to opazili.

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

Zakaj IRB potrebuje dvosmernat vhod

Globe GDPR so se v letu 2024 povecale za 56 % (Letno porocilo DLA Piper 2025). Clen GDPR 89 se odziva na ta trend. Zahteva psevdonimizacijo - ne popolno odstranitev - za raziskovalne podatke. Pravilo sprejema, da raziskave vcasih potrebujejo pot nazaj do resnicnega zapisa.

Stevilka NEJM AI iz leta 2024 je proucila de-identifikacijo na podlagi LLM. Nasla je temeljni problem. Ociscene klinicne beleske ostanejo vezane na identiteto pacienta skozi iste klinicne vzorce, ki jih delajo koristne. Stevilka pravi: uporabite psevdonimizacijo z dokumentiranim nacrtom kljucev. To ohranja pot za ponovni stik odprto.

Vas IRB mora videti obe strani tistih vrat. Kdo lahko ponovno identificira? Pod katerimi pogoji? Kdo hrani kljuc? Kaj se evidentira?

Kako deluje nastavitev

AES-256-GCM deluje v fiksnem nacinu. Vsak ID pacienta vsakic preslika na isti zeton. "Pacient_001" da vsac isti izhod. Tisti zeton se pojavi pri izhodiscu, pri 3 mesecih in pri koncem pregledu. Ekipa sledi vsakemu pacientu samo z zetonom. V delovne datoteke ne vstopijo nobena prava imena.

Razcep kljucev izpolnjuje pravilo EDPB. Raziskovalna ekipa hrani sifrirane podatke. Skrbnik podatkov hrani kljuc v loceni sistem. Nobena stran sama ne more ponovno identificirati. Ekipa ne more desifrirati. Skrbnik ne more povezati kljucev s pacienti brez podatkov.

Ko je odobren ponovni stik, skrbnik uporabi kljuc za poimenovane zapise. Vsak korak se evidentira: kateri zapisi, kdaj, kdo je dal odobritev. Ta dnevnik je vase dokazilo po Clenu GDPR 89.

Kako to izgleda v praksi

Onkoloski center vodi kohorto 5.000 pacientov v treh drzavah. Vsako mesto dela samo z zetoni. Odgovorni uradnik za podatke vodilnega centra hrani kljuc.

Sredi studije skeniranje oznaci 47 pacientov z visokim tveganjem. Etieni odbor odobri ponovni stik. Uradnik odsifrira tistih 47 zapisov. Negovsalna ekipa doseze tistih 47 pacientov. Ostalih 4.953 ostane skritih na vseh treh mestih.

Kljuc se ne premakne. Podatki ostanejo sifrirani. Le tistih 47 zapisov je kdaj koli povezano s pravimi imeni.

Za vec o psevdonimizaciji v primerjavi s popolno anonimizacijo glejte nas vodic po reverzibilni de-identifikaciji.

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.