Best for
- 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-deid…
maziyarpanahi/openmed/skills/auditing-safe-harbor-checklist/SKILL.md
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 / deiden
Decision brief
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-identi…
Compatibility matrix
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/maziyarpanahi/openmed --skill "skills/auditing-safe-harbor-checklist"Inspect the Agent Skill "auditing-safe-harbor-checklist" from https://github.com/maziyarpanahi/openmed/blob/e412ae8f3b04ae79b13663d34a422efc22109a3a/skills/auditing-safe-harbor-checklist/SKILL.md at commit e412ae8f3b04ae79b13663d34a422efc22109a3a. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
python import openmed from openmed.core.labels import LABELTOHIPAA, HIPAASAFEHARBORCLASSES
1. De-identify with a Safe Harbor profile: openmed.deidentify(note, policy="hipaasafeharbor"). This masks every identifier class by default and runs the mandatory structured-ID safety sweep. 2. Map detected spans to the 18 classes via LABELTOHIPAA (as above). Build a table of ca…
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.
detected = openmed.extractpii(note)
covered = set() for ent in detected.entities: canonical = openmed.normalizelabel(ent.label) - CANONICALLABELS form hipaaclass = LABELTOHIPAA.get(canonical) - one of 18 classes if hipaaclass: covered.add(hipaaclass)
Permission review
No configured static risk pattern was detected
This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.
Evidence record
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 87/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 4,847 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
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 —
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.
openmed.deidentify(note, policy="hipaa_safe_harbor"). This masks every
identifier class by default and runs the mandatory structured-ID safety sweep.LABEL_TO_HIPAA (as above).
Build a table of category → detected? → action taken.AGE) must be aggregated to "90+"; OpenMed flags but does
not auto-cap — see shifting-clinical-dates.PHONE label; biometrics and full-face photos
are out of scope for text — handle in the imaging/intake pipeline.audit=True and read residual_risk
(auditing-deidentification-runs). Non-zero projected leakage → review.openmed.extract_pii (spans) and openmed.deidentify
(rewrite) — see deidentifying-clinical-text.openmed.CANONICAL_LABELS, openmed.normalize_label, and
LABEL_TO_HIPAA / HIPAA_SAFE_HARBOR_CLASSES in openmed/core/labels.py.auditing-deidentification-runs
(audit=True → AuditReport.residual_risk).configuring-privacy-policies — if you must keep dates or
geography, Safe Harbor fails; use Expert Determination
(hipaa_expert_review_assist) or a Limited Data Set
(research_limited_dataset).strict_no_leak exists for high-stakes data.openmed/core/labels.py (LABEL_TO_HIPAA,
HIPAA_SAFE_HARBOR_CLASSES, CANONICAL_LABELS, normalize_label).Alternatives
alirezarezvani/claude-skills
App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklist
wanshuiyin/Auto-claude-code-research-in-sleep
Use it for operations and research tasks; the detail page covers purpose, installation, and practical steps.
K-Dense-AI/scientific-agent-skills
Distributed computing for larger-than-RAM pandas/NumPy workflows. Use when you need to scale existing pandas/NumPy code beyond memory or across clusters. Best for parallel file processing, distributed ML, integration with existing pandas code. For out-of-core analytics on single machine use vaex; for in-memory speed use polars.
K-Dense-AI/scientific-agent-skills
Use NeuroKit2 to build or audit reproducible research workflows for physiological time-series preprocessing, event/interval analysis, multimodal alignment, variability, and complexity. Trigger when code imports neurokit2 or needs its current APIs, schemas, and method-aware validation—not for diagnosis or device validation.