By · Last updated 2026-06-05

返回博客GDPR 与合规

丹麦Datatilsynet:医疗数据GDPR执法指南2024

丹麦数据保护局2024年处理的31起GDPR案件中,45%涉及医疗系统。全球领先的数字化医疗体系带来的不仅是研究优势,更是严苛的合规要求。本文解析CPR号码识别难题与患者数据复用规则。

June 5, 20268 分钟阅读
Denmark DatatilsynetCPR numberhealthcare GDPRNordic data protectionhealth data

丹麦医疗数据GDPR:Datatilsynet 2024年执法解析

丹麦数据保护局Datatilsynet 2024年共处理31起GDPR案件,其中14起——占比45%——涉及医疗系统。丹麦仅有590万人口,这一比例极为突出,折射出丹麦在数字医疗领域的高度发展,也体现了该领域严苛的监管要求。

丹麦的医疗数据体系

每位丹麦公民都拥有一个CPR号码,与其患者档案、药品注册系统、医院病历及Statens Serum Institut组织样本库全部关联。医院病历数据可追溯至1977年。

这套体系使丹麦医学研究跻身全球顶尖行列,同时也意味着患者数据极为敏感——这正是Datatilsynet将医疗领域作为执法重点的根本原因。

CPR号码的识别难题

CPR号码是10位身份标识符,格式为DDMMYY-XXXX,最后一位是依据模11算法计算的校验位。

CPR号码出现在每一份临床档案中,与医疗、税务、银行和选举记录全面关联。

Datatilsynet明确要求:在将患者记录用于任何新目的之前,必须核验去标识化工作的有效性。然而,67%的常见NLP工具会跳过CPR号码的模11校验步骤,由此产生两类问题。

误报: 日期字符串、账单编号和参考码被错误标记为真实CPR号码,导致大量人工复核工作。

漏报: 数字位移的CPR号码无法通过校验,使真实患者身份标识符从检测中漏网。输出结果看似干净,实则存在隐患。

关于其他欧盟国家身份证件校验位规则的详细解析,请参阅我们的欧盟国家税务身份标识符PII检测指南

患者数据复用的四项规则

丹麦医疗注册系统为顶尖科学研究提供数据支撑。Datatilsynet 2024年发布的数据复用指南确立了四项核心规则。

书面记录处理过程: 列明每个被删除或修改的字段,注明数值如何进行了舍入或分组处理。仅一份简短的政策说明不符合要求。

提交测试结果证明: 证明工具确实识别出了CPR号码及其他丹麦身份标识符,声明本身不构成证明。

最小化数据提取范围: 仅提取研究所必需的个人数据,即使是假名化数据集也应遵守这一原则。

为AI工具进行DPIA: 任何处理丹麦患者档案的AI工具均须完成数据保护影响评估(DPIA),使用Datatilsynet提供的标准表格。

哥本哈根医疗科技领域的三大风险焦点

哥本哈根医疗科技企业包括Leo Pharma、Bavarian Nordic及众多初创公司,Datatilsynet重点关注以下三类风险。

AI训练数据集: 监管机构在2024年发现多家企业使用含有真实CPR号码的数据训练AI模型,且无一具备有效的合法处理依据。

境外数据传输: 部分企业将患者档案传输至美国云服务商用于AI开发,监管机构明确表示,仅凭标准合同条款(SCC)不足以满足合规要求,还须采取额外技术措施——例如使用在欧洲境内保管密钥的加密方案。

访问日志: 日志必须记录谁在何时以何种目的访问了哪些档案,且须保存至少五年。

2024年56%的丹麦医疗数据泄露事件源于去标识化不充分。采用支持丹麦语的、经CPR校验的检测工具,可消除最常见的合规失效原因。

关于北欧地区的GDPR执法情况,请参阅我们的瑞典IMY 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.