configuring-privacy-policies
内置多种策略并支持自定义，便于满足不同合规与研究场景需求。
去标识并非零风险，不当配置可能仍具再识别风险，需评估残余风险。
选择并定制 OpenMed 的去标识隐私策略，并构建自定义替代器（surrogate）。
帮你从 OpenMed 提供的预设隐私策略里选出最合适的一套（比如 HIPAA Safe Harbor、Expert Determination、GDPR 等），并把每类标签的保留/替换/掩码规则细化。还能注册自定义替代器（surrogate），通过 AnonymizerConfig/Anonymizer 或 register_clinical_provider 等接口把 MRN、姓名、地址换成指定格式。适合在去标识前定策略或科研场景保留准标识符时使用。
▸ 展开 SKILL.md 英文原文
Select and customize OpenMed's seven bundled privacy policy profiles for de-identification, and build custom surrogate generators. Use when the user asks which policy fits HIPAA Safe Harbor vs Expert Determination vs GDPR vs PIPEDA vs a research limited dataset vs strict no-leak, wants to pass policy= to deidentify(), needs to keep quasi-identifiers for research, or must register a custom MRN/name/address surrogate provider. Covers the profile-to-use-case map, AnonymizerConfig/Anonymizer for fine control, and register_clinical_provider / register_label_generator. Pairs with OpenMed deidentifying-clinical-text and generating-synthetic-surrogates.
帮我安装这个 skill：https://raw.githubusercontent.com/maziyarpanahi/openmed/master/skills/configuring-privacy-policies/SKILL.mdcurl -fsSL "https://raw.githubusercontent.com/maziyarpanahi/openmed/master/skills/configuring-privacy-policies/SKILL.md"# Configuring privacy policies A **policy profile** is a named bundle of de-identification decisions: which action (mask/redact/replace/keep) applies to each label, how aggressively detectors arbitrate, whether the mandatory safety sweep runs, and whether a reversible mapping is produced. OpenMed ships seven profiles. Pass one by name to `deidentify(policy=...)` and you get a compliance-aligned default without hand-wiring 50+ per-label actions. Everything runs **on-device**. ## When to use this skill Use it to pick the right `policy=` for a regulatory context, to understand what a profile actually changes, or to go beyond the bundle — keeping quasi- identifiers for research, or registerin