By · Last updated 2026-03-10

返回博客医疗保健

云端HIPAA:PHI的零知识保护

业务伙伴协议无法在您的云端AI供应商以明文处理PHI时防止HIPAA违规。了解零知识架构能做什么。

March 10, 20269 分钟阅读
HIPAA compliancezero-knowledge architecturePHI anonymizationcloud securityBAA limitations

2026年更新

将患者置于风险中的HIPAA误区

每个医疗IT团队都听过同样的建议:签署业务伙伴协议,您就在HIPAA框架下受到保护了。

BAA要求确实存在。HIPAA隐私规则要求覆盖实体与业务伙伴签署BAA——这些第三方代表覆盖实体处理受保护的健康信息。任何接触临床笔记的AI工具都需要先签署BAA。

但BAA覆盖的是法律关系,而不是合同签署后患者记录在AI供应商服务器上的遭遇。

关键问题不是您是否有BAA,而是AI供应商能否读取您的患者健康记录,以及他们遭受攻击时会发生什么。

业务伙伴协议实际上做了什么

BAA约束业务伙伴承担四项义务:

  • 仅将患者记录用于约定目的
  • 建立保障措施加以保护
  • 向覆盖实体报告任何泄露
  • 合同终止时归还或销毁文件

BAA是一份合同。供应商承诺谨慎处理临床文件、应用合理的安全措施,并在出现问题时通知您。

BAA不能做到的事情:

  • 阻止攻击者攻破供应商服务器
  • 消除以解密形式读取患者记录的能力
  • 在供应商遭受攻击时保护您的组织免受HIPAA责任

当云端AI供应商遭受攻击时,BAA覆盖的是通知环节。但健康记录的暴露是真实的,患者受到了伤害,覆盖实体面临HHS调查——合同无法改变这一事实。

服务端问题

处理健康记录的云端AI工具共享一种核心设计:文件传输至供应商服务器,AI在那里处理,结果返回给用户。

为了实现这一点,供应商必须以可用形式读取文件,这意味着两种情况之一:文件未加密存储,或者供应商管理加密密钥。

供应商管理的加密不是端到端加密。如果供应商持有密钥,供应商就能解密。如果服务器遭到攻击,患者记录就会以明文形式暴露。

这正是BAA无法弥补的缺口。

零知识架构如何解决这个问题

零知识设计从根本上解决了服务端访问问题。

在任何文件离开您的环境之前,患者详情就被替换为令牌。AI供应商收到的只是匿名化内容:临床笔记中的姓名已被替换,账单记录中的账号已被替换,护理计划中的个人信息已被移除。

AI处理匿名化版本,您的系统使用令牌映射表将结果重新链接到原始患者记录。该映射表从未离开您的控制。

实际变化:

AI供应商从未收到受保护的健康信息。 通过零知识匿名化发送的临床笔记不包含姓名、出生日期、地址或记录编号。

供应商发生泄露不会暴露任何内容。 如果他们的服务器遭到攻击,存储的内容没有任何患者信息,暴露根本不可能发生。

技术保障措施超越了合同要求。 覆盖实体已从技术上使患者记录暴露变得不可能,而不仅仅是通过合同加以禁止。

请参阅安全合规页面法律合规文档了解匿名化层的工作原理。

参考资料

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

开始使用 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.