auditing-deid-leakage
作为去标识化后的二次把关，能阻断单一残留标识导致的数据泄露风险。
会处理敏感 PHI/PII，部署与运行需满足合规与最小权限原则
对已去标识化文本进行对抗式扫描，报告任何残留身份信息泄露点。
在去标识化后做一轮对抗式扫描，找出任何残留的身份证据（SSN、银行卡号模式、邮箱、电话、异常日期等）并生成泄露报告，发现即阻止数据外发。适用于在分享数据前复核红action、证明没有 PHI/PII 泄露或做第二道检测时。结合格式/校验和检测、熵启发式和严重性评分，本地优先、免授权，并可与 openmed.extract_pii 的期望做差分验证。
▸ 展开 SKILL.md 英文原文
Adversarially scan already-de-identified clinical text for residual identifiers and emit a leakage report that blocks release on any hit. Use after OpenMed de-identification when the user asks to verify a redaction, prove no PHI/PII leaked, gate a dataset before sharing, or run a second-pass detector. Covers format and checksum detectors (SSN, Luhn for card numbers, MRN/account patterns, emails, phones, dates), entropy heuristics for high-randomness tokens, severity scoring, and a hard block-on-leak rule. This is the verification half of OpenMed's leakage-first ethos. Hand-off: re-run openmed.extract_pii on the de-id output and diff against expectations. License-free, local-first. Pairs after deidentifying-clinical-text.
帮我安装这个 skill：https://raw.githubusercontent.com/maziyarpanahi/openmed/master/skills/auditing-deid-leakage/SKILL.mdcurl -fsSL "https://raw.githubusercontent.com/maziyarpanahi/openmed/master/skills/auditing-deid-leakage/SKILL.md"# Auditing de-id leakage De-identification is **verified, not assumed**. A model-driven redaction can miss a structured identifier (an SSN typo'd with spaces, an account number in a footer, a date in an odd format) — and a single residual identifier defeats the whole release. This skill is the adversarial second pass: scan the *output* of de-identification for anything that still looks like an identifier, score it, and **block release on any leak**. It is the verification half of OpenMed's leakage-first ethos — gate on leakage, not on F1. ## When to use - Right after `deidentifying-clinical-text`, before the de-identified text leaves a trust boundary (export, share, train, publish). - W