By · Last updated 2026-04-21

返回博客医疗保健

临床研究中的可逆去标识化

当研究在 5,000 名受试者中发现 47 人存在意外的生物标志物风险时,研究人员需要联系真实患者。然而仅有 23% 的匿名化工具支持这一功能。

April 21, 20269 分钟阅读
reversible de-identificationclinical research pseudonymizationpatient re-contact protocolIRB data managementHIPAA reversible encryption

临床研究中的可逆去标识化

长期试验面临一个两难困境。研究期间必须保护患者隐私——这是 IRB 的强制要求,也是患者信任的基础。但某些结果可能需要在事后重新联系患者。永久性去标识化彻底封闭了这条路;可逆去标识化则将这扇门留着。

我们如何支持这一需求,请参阅合规概览安全实践

重新联系患者的难题

一家肿瘤中心开展了一项纳入 5,000 名患者的研究。试验进行中,47 名患者的生物标志物显示与一种侵袭性癌症类型相关——这超出了原始研究范围。伦理委员会审查后批准重新联系,「告知义务」原则适用。

如果当初采用的是永久去标识化,研究团队将束手无策。随机编码没有映射关系,无法溯源;那 47 条记录无法对应到真实患者,发现无法转化为行动,需要医疗干预的患者无从联系。隐私保护机制在最关键的时刻失效了。

这并非罕见情形。任何长期试验都可能出现意外发现。「告知义务」原则要求在发现风险时采取行动——如果没有重新识别的路径,这一行动就无从实现。

GDPR 密钥分离规则

EDPB 05/2022 指南直接回应了这一问题。假名化是有效的数据保护手段,它保留了在需要时重新识别的可能性,经批准的流程可在必要时使用。

核心规则是密钥分离:解密密钥必须与假名化数据分开存储,必须有控制措施阻止任何未经授权的访问,使用数据的团队不得同时持有密钥,重新识别必须经过正式记录的步骤。

IAPP 2024 年调查显示,仅有 23% 的匿名化工具提供真正的可逆性。大多数工具采用永久遮蔽或替换方式,而这些方式恰恰阻断了「告知义务」所要求的重新联系。

架构原理

合规方案采用基于 AES-256-GCM 的可逆加密。每个患者 ID 转换为一个令牌,同一患者在所有研究文件中始终映射到同一令牌,数据关联关系完整保留,工作数据集中不出现任何真实 ID。

解密密钥由数据托管人保管,与数据物理隔离。任何使用密钥的操作都需要书面的正式审批。

分析阶段,团队仅与令牌打交道。当那 47 名受影响的患者被标记后,伦理委员会批准重新识别,托管人仅对这 47 条记录应用密钥,团队获得这 47 人的真实 ID,其余 4,953 名患者始终受到保护。

精准的定向重新识别成为可能,数据集的其余部分从不被触碰。

关于假名化与完全匿名化的区别,请参阅我们的 GDPR 匿名化与假名化指南

参考来源

准备好保护您的数据了吗?

开始使用 285 种实体类型在 48 种语言中匿名化 PII。

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.