annotating-variants
Annotates VCF variants and normalizes HGVS nomenclature with public, license-free annotators…
Verify OpenMed de-identified output against all 18 HIPAA Safe Harbor identifier categories and report residual re-identification risk. Use when the user must confirm a note meets HIPAA Safe Harbor (45 CFR 164.514(b)(2)), needs a coverage checklist mapping detected entities to
$ npx -y skills add maziyarpanahi/openmed --skill auditing-safe-harbor-checklist --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/auditing-safe-harbor-checklistContext preview
The summary Claude sees to decide when to auto-load this skill.
Verify OpenMed de-identified output against all 18 HIPAA Safe Harbor identifier categories and report residual re-identification risk. Use when the user must confirm a note meets HIPAA Safe Harbor (45 CFR 164.514(b)(2)), needs a coverage checklist mapping detected entities to
name: auditing-safe-harbor-checklist description: "Verify OpenMed de-identified output against all 18 HIPAA Safe Harbor identifier categories and report residual re-identification risk. Use when the user must confirm a note meets HIPAA Safe Harbor (45 CFR 164.514(b)(2)), needs a coverage checklist mapping detected entities to the 18 categories, wants to flag gaps like ages over 89, rare geography, fax vs phone, or biometrics, or asks whether masking was complete. Maps OpenMed CANONICAL_LABELS to the 18 HIPAA classes and uses extract_pii / deidentify to check coverage. Pairs with OpenMed deidentifying-clinical-text and auditing-deidentification-runs." license: Apache-2.0 metadata: project: OpenMed category: de-identification pairs: after version: "1.0"
The Safe Harbor method (45 CFR 164.514(b)(2)) de-identifies PHI by removing **18 specific identifier categories** for the individual and their relatives, employers, and household members — and requires the covered entity to have **no actual knowledge** that the remainder could re-identify anyone. This skill turns that legal checklist into a concrete coverage check over OpenMed output: which of the 18 categories were detected and handled, and where the gaps are.
The full mapping table lives in [references/safe-harbor-identifiers.md](references/safe-harbor-identifiers.md) — all 18 categories, their OpenMed HIPAA class, the matching `CANONICAL_LABELS`, and per-category cautions. Read it when you need the authoritative cross-walk.
Use it after a de-identification run to *prove* coverage, or before release to decide whether Safe Harbor is even achievable for this text. If the user needs a signed, retained record of the run, hand off to `auditing-deidentification-runs`.
import openmed
from openmed.core.labels import LABEL_TO_HIPAA, HIPAA_SAFE_HARBOR_CLASSES
note = (
"Patient John Doe (MRN 1234567), age 92, of Smalltown, seen 2024-03-02. "
"SSN 123-45-6789, phone 617-555-0142."
)
# 1) Detect identifiers (spans only; no rewrite).
detected = openmed.extract_pii(note)
# 2) Roll each detected span up to its HIPAA Safe Harbor class.
covered = set()
for ent in detected.entities:
canonical = openmed.normalize_label(ent.label) # -> CANONICAL_LABELS form
hipaa_class = LABEL_TO_HIPAA.get(canonical) # -> one of 18 classes
if hipaa_class:
covered.add(hipaa_class)
# 3) Report which of the 18 classes were touched and which weren't observed.
missing = sorted(HIPAA_SAFE_HARBOR_CLASSES - covered)
print("covered:", sorted(covered))
print("not observed in this note:", missing)"Not observed" is **not** the same as "absent" — a category may simply not occur in this note, or may have been missed. That is exactly what the human review step (below) is for.
1. **De-identify** with a Safe Harbor profile: `openmed.deidentify(note, policy="hipaa_safe_harbor")`. This masks every identifier class by default and runs the mandatory structured-ID safety sweep. 2. **Map detected spans to the 18 classes** via `LABEL_TO_HIPAA` (as above). Build a table of category → detected? → action taken. 3. **Walk the checklist** in [references/safe-harbor-identifiers.md](references/safe-harbor-identifiers.md) and flag the known gaps explicitly:
not auto-cap — see `shifting-clinical-dates`.
occupation) can re-identify even when masked field-by-field.
are out of scope for text — handle in the imaging/intake pipeline. 4. **Assess residual risk.** Run `audit=True` and read `residual_risk` (`auditing-deidentification-runs`). Non-zero projected leakage → review. 5. **Record the "no actual knowledge" judgment.** A human must sign off that the remaining text cannot re-identify the individual. Automated coverage is necessary, not sufficient.
(rewrite) — see `deidentifying-clinical-text`.
`LABEL_TO_HIPAA` / `HIPAA_SAFE_HARBOR_CLASSES` in `openmed/core/labels.py`.
(`audit=True` → `AuditReport.residual_risk`).
geography, Safe Harbor fails; use Expert Determination (`hipaa_expert_review_assist`) or a Limited Data Set (`research_limited_dataset`).
Harbor on its own — the "no actual knowledge" residual-risk judgment is required and is a human decision.
fine; if you keep age, aggregate to "90+". OpenMed will not cap automatically.
3-digit ZIP (population-gated) and the year — implement the truncation; do not assume detection handles it.
them N/A for text and ensure another pipeline stage covers them.
together (rare diagnosis + small town + outlier age) can identify someone; this is precisely why `strict_no_leak` exists for high-stakes data.
Local-first healthcare AI: clinical NER and HIPAA PII de-identification on hardware you control. 2,200+ medical models, 35 model-backed PII languages, and Python, MLX, Android and browser runtimes. Apache-2.0 SDK.
Repo: maziyarpanahi/openmed
Annotates VCF variants and normalizes HGVS nomenclature with public, license-free annotators…
Choose the first OpenMed workflow skill for an intake, privacy, extraction, exchange, or…
Package multiple FHIR R4 resources produced from OpenMed output into a single valid…
Adversarially scan already-de-identified clinical text for residual identifiers and emit a…
Produce a signed, reproducible, no-PHI audit trail for an OpenMed de-identification run via…
Generates and verifies 21 CFR Part 11-style audit trails — who/what/when, electronic…