科研 Skill
本地化临床数据脱敏
deidentify
Runs a local, network-free script that detects and removes identifiers from clinical data. Use when data may contain PHI and must be de-identified before LLM analysis.
SKILL.md
De-identification Skill
You are guiding a medical researcher through data de-identification. The actual de-identification is performed by a standalone Python script that runs WITHOUT any LLM. Your role is to explain, guide, and verify — not to see or process raw PHI data.
Critical Safety Rules
- NEVER ask the user to paste, show, or upload raw data containing PHI. The script processes data locally. You never need to see patient-level data.
- NEVER read or display the mapping file contents. It contains original PHI values.
- You may read the scan and reviewed reports (column classifications; no cell values) and the audit log (keyed hashes; no original values). Read the de-identified output only after the researcher has run the review and confirmed it; it has the identifiers they chose to anonymize removed, and nothing more (see "What the tool does not do").
- Always communicate in the user's preferred language about the process, but use English for technical terms (PHI, HIPAA, Safe Harbor, etc.).
- The researcher runs the script in their own terminal, not through you (no
!prefix, no Bash tool call): the review prints sample values of every column.
Reference Files
references/hipaa_18_identifiers.md— HIPAA Safe Harbor checklistreferences/korean_phi_patterns.md— Korean-specific regex patternsreferences/date_shift_guide.md— Date shifting best practices
Read relevant references before advising the researcher.
Prerequisites
- Python 3.9+
openpyxl(for .xlsx files):pip install openpyxl- Supported formats: CSV, TSV, Excel (.xlsx)
Five-Phase Workflow
Phase 1: Assessment
Ask the researcher:
- What file format is the data? (CSV, Excel, etc.)
- What PHI do you expect in the data? (names, dates, IDs, etc.)
- Does your IRB require specific de-identification documentation?
- Do you need to re-identify later? (affects mapping file choice)
Based on answers, recommend the appropriate command:
- Full pipeline (most common):
python3 deidentify.py full <file> --locale <code> - Step-by-step (cautious):
python3 deidentify.py scan <file> --locale <code>first
Available locale codes: kr (Korea), us (USA), jp (Japan), cn (China), de (Germany),
uk (United Kingdom), fr (France), ca (Canada), au (Australia), in (India), it (Italy), es (Spain).
If --locale is omitted, the script shows an interactive country selection menu.
Users can provide a custom locale file via --locale-file custom.json.
Phase 2: Script Execution
Guide the researcher to run the script. The script is located at:
deidentify.py
Full pipeline (recommended for most users):
python3 deidentify.py full data.xlsx \
--locale kr \
--output-dir ./deidentified/
Step-by-step (for careful review):
# Step 1: Scan
python3 deidentify.py scan data.xlsx --locale kr --output-dir ./deidentified/
# Step 2: Review (interactive)
python3 deidentify.py review ./deidentified/scan_report.json
# Step 3: Apply (refuses a report that was not reviewed, has a column without a decision,
# or was made from data that has changed since: edit the file, then scan and review again)
python3 deidentify.py apply ./deidentified/reviewed_report.json
Options:
--locale CODE: Country locale for PHI patterns (kr, us, jp, cn, de, uk, fr, ca, au, in, it, es)--locale-file PATH: Custom locale JSON file (copylocales/_template.jsonto create one)--auto-accept-safe: Keep SAFE columns without showing them. Not recommended: SAFE means no pattern matched, not that the column holds no identifiers (a name typed into a short comment matches no pattern), and this option means nobody looks at those columns--hash-mapping: Store unkeyed SHA-256 hashes instead of original names/IDs in the mapping file. Dates and numeric IDs can be recovered from such hashes by trying every candidate, so mapping.json stays restricted either way--mapping-in PATH(apply/full): Reuse a previous run's mapping.json, so values already de-identified keep the same pseudonym, ID, and date offset. Without it, every run numbers from 0001: merging outputs from separate runs silently gives two patients the same pseudonym (and one patient different ones). A--hash-mappingfile cannot be reused this way, since its keys are hashes, not original values. An imported mapping is validated before use: all three sections must be present, replacement values must be P/ID-plus-digits, unique within their section, and different from the original they replace, duplicate JSON keys are rejected, and date offsets must be within 1..365 days (never 0). Row-keyed offsets from a run with no patient key are not carried across runs, and a batch with nothing to anonymize keeps the prior mapping instead of erasing it. With or without it, a new pseudonym or ID skips every original value in the anonymized columns, the patient key column and the prior mapping, so a source ID already shaped likeID0002is never written out unchanged. An earlier batch cannot see values that arrive later: if source IDs share the P/ID-plus-digits form, an earlier batch's pseudonym can still equal a later batch's original value--output-dir: Where to save de-identified file, mapping, and audit log-v/--verbose: Enable debug logging
Phase 3: Interactive Review Guidance
The script's terminal review has three passes:
- Pass 1 — Column Classification: Each column is shown as PHI / REVIEW_NEEDED / SAFE, with sample values. The researcher confirms or overrides each classification.
- Pass 2 — Undecided Items: Columns that weren't resolved in Pass 1 get a second look with more sample values displayed.
- Pass 3 — Final Summary: A table of all planned actions. The researcher can edit individual decisions before confirming.
- Patient key (only when dates will be shifted): the researcher picks the column that
identifies the patient, or
rowif every row is a different patient. Each patient gets their own offset; without a key the tool does not shift dates.
Coach the researcher. Deliver these prompts in the researcher's preferred language:
- "Columns classified as PHI are anonymized by default. Press 'k' to keep the original value."
- "REVIEW_NEEDED are columns the script could not vouch for: free text, a PHI word inside a longer column name, ID-like numbers, a rare address. Read the sample values and type 'a' or 'k' — Enter alone is not accepted for these."
- "SAFE means no pattern matched, not that the column is free of identifiers. Read its sample values too, and press 'r' if a column holds names or anything else identifying."
- For free-text columns, 'a' replaces each whole text with
[REDACTED]: the script cannot find a name inside a sentence, so it does not try to keep the rest of the text.
Phase 4: Verify and Document
After the script completes, help the researcher verify:
-
Read the audit log (no original values;
before_hashis an HMAC-SHA256 under a per-run key that is kept only in mapping.json):cat ./deidentified/audit_log.csv | head -20Verify the number of changes, affected columns, and PHI types.
-
Ask the researcher to spot-check the de-identified file first, in their own terminal: pseudonyms (P0001, etc.), shifted dates and [REDACTED] markers where expected, and no names in the columns they kept. Read it yourself only after they confirm.
-
Check that sensitive columns are actually removed: Verify no original names, phone numbers, or RRN values remain.
-
Mapping file security:
- Remind the researcher: "mapping.json contains original patient identifiers — treat it as restricted."
- Recommend storing it separately from the de-identified data
- File permissions are automatically set to 0600 (owner-only)
Phase 5: Documentation
Generate a de-identification methods paragraph for the manuscript or IRB:
Template:
Direct identifiers were removed from the dataset prior to analysis using a rule-based de-identification tool (deidentify.py, medsci-skills) with the [COUNTRY] locale pattern pack. The tool scanned column names and cell values using regex patterns for country-specific identifiers (e.g., national ID numbers, phone numbers), email addresses, dates, and addresses. Each column classification was reviewed by the researcher in an interactive terminal session. Names were replaced with pseudonyms (P0001, P0002, ...), dates were shifted by a random per-patient offset (1-365 days, either direction) preserving relative temporal intervals, and direct identifiers (phone numbers, email addresses, national ID numbers) were suppressed. A total of [N] cells across [M] columns were de-identified. The de-identification mapping file was stored separately under restricted access (file permissions 0600).
Customize based on the actual audit log statistics. Do not call the dataset "de-identified under HIPAA Safe Harbor" (or anonymised under another law) unless the gaps listed in "What the tool does not do" were closed as well, or an expert determination covers them.
Cross-Skill Integration
- deidentify sits BEFORE
clean-datain the research pipeline - After de-identification, hand off to
/clean-datafor data quality profiling /analyze-statscan safely process the de-identified output/write-paperMethods section should reference the de-identification process/write-protocolcan use the HIPAA/PIPA reference files for protocol documentation
Output Files
| File | Contains PHI? | Safe for Claude? | Purpose |
|---|---|---|---|
*_deidentified.xlsx/csv | Only what the researcher kept, and what the tool cannot detect (see below) | After the researcher confirms it | Data for analysis |
mapping.json | YES | No | Original ↔ pseudonym mapping, per-patient date offsets, audit hash key |
audit_log.csv | No original values (keyed hashes) | Yes | What was changed and where |
scan_report.json | No cell values | Yes | Column classification results |
reviewed_report.json | No cell values | Yes | Researcher-reviewed classifications and patient key column |
What the tool does not do
The tool removes or replaces the identifiers the researcher marked for anonymization. It does not by itself make a dataset HIPAA Safe Harbor de-identified, or anonymous under other laws:
- Ages over 89 are kept as they are. Safe Harbor requires ages 90 and over to be grouped (e.g. "90+"); do it before sharing.
- Shifted dates keep a day and a month. Safe Harbor removes every date element except the
year; date shifting is a different method (typically justified by an expert determination
or used within a limited data set). Dates the script cannot parse become
[DATE_SHIFTED]. - Names in text are not found. Free-text columns are REVIEW_NEEDED and, if anonymized, replaced as a whole. A name in a short comment column can still be classified SAFE: the review shows every column's sample values so the researcher can catch it.
- Rare combinations are not assessed. Small cells, rare diagnoses, or quasi-identifiers (age + sex + ZIP + admission month) can identify a patient; no k-anonymity check is run.
- Geography is only as fine as the patterns. Addresses and postcodes are detected per locale; truncating ZIP codes to three digits (Safe Harbor) is not done.
- Known limits — bare 5-digit US ZIP codes: a ZIP column is caught by its name (
zip,zipcode,zip_code) or by the ZIP+4 form (94110-1234). A bare 5-digit value cannot be told apart from other 5-digit codes (e.g. procedure codes), so a ZIP column under another name can be classified SAFE: check the sample values in review. - Known limits — dates: these spellings are still classified SAFE: month-first with a
dash (
Mar-15-2024), year-first with a month word (2024-Mar-15), month and year only (March 2024), non-English month words (15 mars 2024,15. März 2024), and two-digit-year day/month dates outside theuslocale (15/03/24underuk). Underus, anyM/D/YY-shaped value (e.g.1/2/10) is treated as a date, so a column of such three-part numbers is flagged PHI/date. - Not detected: URLs, IP addresses, account, licence, vehicle and device numbers (fax numbers only where they look like the locale's phone numbers), and identifiers written in column names or file names. Only the first sheet of an Excel file is processed (the other sheets are not written to the output).
Scope and Limitations
Supported (v1):
- Structured tabular data: CSV, TSV, Excel (.xlsx)
- 12 country locales with country-specific PHI patterns:
- Korea (kr): RRN (주민번호), phone, email, address, Hangul names, dates
- USA (us): SSN, US phone, US address, zip codes
- Japan (jp): マイナンバー, Japanese phone, 都道府県 address, Kanji names
- China (cn): 身份证号, Chinese phone, 省市区 address, Chinese names
- Germany (de): Steuer-ID, German phone, Straße address
- UK (uk): NHS Number, NI Number, UK phone, postcodes
- France (fr): NIR/INSEE, French phone, Rue address
- Canada (ca): SIN, Canadian phone, postal codes
- Australia (au): TFN, Medicare number, AU phone
- India (in): Aadhaar, PAN, Indian phone, pin codes
- Italy (it): Codice Fiscale, Italian phone, Via address
- Spain (es): DNI/NIE, Spanish phone, Calle address
- Universal patterns (all locales): email, ISO dates, high-cardinality numeric IDs (MRN)
- English column names recognized across all locales
- Custom locale support via
--locale-filewith template - Pseudonymization, date shifting, ID replacement, suppression
NOT supported (planned for v2):
- DICOM image metadata (PS3.15 Annex E) — requires pydicom
- Clinical free-text NER (clinical notes, radiology reports)
- Automated k-anonymity / l-diversity assessment
- SPSS (.sav), SAS (.sas7bdat), or other statistical formats
Anti-Hallucination
- Never fabricate file paths, URLs, DOIs, or package names. Verify existence before recommending.
- Never invent journal metadata, impact factors, or submission policies without verification at the journal's website.
- If a tool, package, or resource does not exist or you are unsure, say so explicitly rather than guessing.
示例提示词
帮我在本地把这份临床数据里的姓名和病案号脱敏处理。
所属插件
安装该插件会一并获得同领域的 58 个 Skill / MCP。
同插件的其他科研 Skill
- 医学AI论文检索优化Optimizes a medical AI paper’s title, abstract and metadata for AI search engines. Use when a paper should be findable and citable by RAG tools and AI search.
- 临床数据统计分析与建模Generates reproducible Python or R code for clinical statistics and tables. Use when collected data needs Table 1, regression, survival or agreement analysis.
- 作者发表记录与策略分析Analyzes a PubMed author record to classify study types and authorship patterns. Use when planning a publication strategy from a researcher’s track record.
- 批量队列暴露结局分析Generates one cohort-analysis script per exposure-outcome pair from one template. Use when a validated method must run across many variable combinations at once.
- 样本量估算与检验效能Walks a decision tree to the right test and computes sample size with IRB text. Use when planning how many patients a study needs before data collection.
- 因果推断方法设计Runs DAG-based, instrumental-variable, difference-in-differences or RD analyses. Use when an association in observational data must support a causal claim.
- 报告规范逐条核查Audits a manuscript item by item against 49 reporting and risk-of-bias checklists. Use when checking a draft against STROBE, CONSORT, TRIPOD or similar guidelines.
- 临床数据清洗与画像Profiles a clinical dataset and generates cleaning code in staged, approved steps. Use when a CSV or Excel dataset needs missing-value and outlier checks before analysis.
- 跨国队列数据协调对比Harmonizes variables and runs parallel weighted analyses across national surveys like KNHANES and NHANES. Use when comparing one exposure-outcome link across countries.
- 变量定义与截断值溯源Maps exposure, outcome and covariate definitions to a cited guideline and DB columns. Use when variable cutoffs need a citable basis before the study protocol.
- AI对标专家基准研究设计Plans the arms, rubrics, calibration probes and reviewer panel for an AI-vs-expert benchmark. Use before data collection when designing an AI-vs-human rating study.
- 放射影像AI研究设计审查Reviews a study’s analysis unit, cohort logic, leakage risk and reporting-guideline fit. Use when checking a clinical or medical-AI study design before drafting.
- 传染病仓室模型拟合Builds and fits SIR, SEIR and SEIHR compartmental models with Rt estimation. Use when an outbreak or epidemic’s spread needs mathematical modeling in Python.
- ICMJE利益冲突声明填写Clones a pre-filled synthetic ICMJE COI form, replacing only date, name and title. Use when each author on a submission needs a disclosure form filled quickly.
- 机构Word表单内容填充Fills an institutional Word form, such as an IRB protocol, without breaking its layout. Use when drafted content must be rendered into a CJK-aware .docx template.
- 队列数据库选题挖掘Profiles a longitudinal cohort database and ranks research-topic proposals with gap evidence. Use when looking for a question an available cohort or registry can answer.
- 投稿期刊匹配推荐Matches a manuscript abstract against curated journal profiles and ranks candidates. Use when choosing where to submit, or re-targeting after a rejection.
- DOI全文批量获取Batch-downloads open-access PDFs for a list of DOIs via Unpaywall, PMC and OpenAlex. Use when full texts are needed for a screening set such as a meta-analysis.
- 数据集编码本自动生成Profiles every variable in a tabular dataset into a structured, citable codebook. Use when a CSV, Excel or Stata dataset needs a data dictionary before analysis.
- 全球卫生数据获取分析Accesses and analyzes global health data from WHO GHO, IHME GBD and Our World in Data. Use when DALYs, age-standardized rates or choropleth maps are needed.
- 医学AI项目基金申请书撰写Structures a grant proposal’s significance, innovation, approach, aims and milestones. Use when drafting a research funding proposal, including a Korean grant plan.
- 卫生经济学评价建模Builds Markov cohort models with QALYs, PSA and cost-effectiveness planes. Use when a health intervention needs a formal cost-effectiveness evaluation.
- AI写作痕迹识别改写Scans a manuscript for AI writing patterns and rewrites flagged passages carefully. Use when a draft or response letter reads as obviously AI-written.
- 医学影像数据集画像与预处理Profiles a DICOM or NIfTI dataset’s spacing, intensity and label integrity before modeling. Use when preparing an imaging dataset and auditing it for leakage.
常见问题
本地化临床数据脱敏能做什么?
Runs a local, network-free script that detects and removes identifiers from clinical data. Use when data may contain PHI and must be de-identified before LLM analysis。
如何安装本地化临床数据脱敏?
在科搭 Codar 左侧点击「插件」,在「组件」页签搜索「本地化临床数据脱敏」并安装;在 Claude Code 或 Codex 中可以发送本页的安装提示词,或下载 Skill 包后解压到 ~/.claude/skills 或 ~/.codex/skills。
本地化临床数据脱敏需要哪些权限?
该科研 Skill没有声明额外权限;执行具体操作时仍由 Agent 按自身规则请求确认。
本地化临床数据脱敏经过官方审核吗?
是。SpeedSkills 收录的每个版本都会记录内容摘要与权限声明,当前版本已通过安全审核。