Agent skill

HIPAA Pre-Deployment Compliance Check

by maziyarpanahi in maziyarpanahi/openmed

Walks a data pipeline against the HIPAA Privacy and Security Rule checklist and produces a gap report before it processes patient data.

Apache-2.0Auto-check passedLegal & Compliance

Install HIPAA Pre-Deployment Compliance Check

skills CLI
$ npx skills add maziyarpanahi/openmed --skill checking-hipaa-compliance -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install maziyarpanahi/openmed checking-hipaa-compliance --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/maziyarpanahi/openmed.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/checking-hipaa-compliance .claude/skills/checking-hipaa-compliance && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
checking-hipaa-compliance
GitHub stars
5.5k
Token cost
~2k tokens
SKILL.md length
738 words
Files
2 (incl. references)
Skills in repo
74
Repo updated
First seen
Licence
Apache-2.0

At a glance

Walks a data pipeline against the HIPAA Privacy and Security Rule checklist and produces a gap report before it processes patient data.

  • Works in 2 steps: Safe Harbor — remove all 18 identifier… → Expert Determination — a qualified…
  • Reviewing a pipeline before it touches real patient data
  • SKILL.md covers When to use, The two paths to "no longer PHI", Quick start and Workflow, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

This skill reads a control list of administrative, physical, and technical safeguards with their 45 CFR citations from its reference file, then works through mapping the data flow, confirming whether the operator is a covered entity or business associate, and checking whether a BAA is in place with every downstream vendor.

It documents which of the two de-identification paths applies, Safe Harbor's removal of eighteen identifier categories or Expert Determination's statistician certification, and shows where on-device de-identification and a signed, PHI-free audit report satisfy a given safeguard. It states plainly that it is a self-assessment aid, not legal advice, and that a Privacy Officer must still sign off.

When your agent uses it

  • Reviewing a pipeline before it touches real patient data
  • Documenting safeguards for a BAA or security questionnaire
  • Choosing between Safe Harbor and Expert Determination de-identification

Example prompts

  • “Run a HIPAA gap analysis on this patient-intake pipeline before we deploy.”
  • “Which safeguards are we missing for our BAA with this vendor?”
  • “Help me document minimum-necessary controls for this audit.”

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

  1. Safe Harbor — remove all 18 identifier categories and have no actual
  2. Expert Determination — a qualified statistician certifies "very small"

What it can do on your machine

Read from SKILL.md and the folder at commit 34d7b8c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are python).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • hhs.gov
    • ecfr.gov
    • healthit.gov
    • csrc.nist.gov

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

HIPAA Pre-Deployment Compliance Check loads about 2k tokens when it runs, and up to ~3.4k if it reads all its reference files. Until then it costs about 231 tokens; SKILL.md has 738 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~231
When it runs · the whole SKILL.md, loaded when a task matches
~2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from maziyarpanahi/openmed at commit 34d7b8c, republished under its Apache-2.0 licence (© maziyarpanahi). 738 words, ~2,037 tokens.

Download SKILL.mdSave it as .claude/skills/checking-hipaa-compliance/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
checking-hipaa-compliance
description
Runs a HIPAA Privacy and Security Rule checklist over a data pipeline and produces a gap report before deploying OpenMed on PHI. Use when the user is about to process protected health information, needs a pre-deployment compliance review, wants to know which administrative, physical, and technical safeguards apply, is scoping a Business Associate Agreement, or must document minimum-necessary and de-identification controls. Trigger keywords: HIPAA, Privacy Rule, Security Rule, 45 CFR 164, PHI, BAA, business associate, minimum necessary, safeguards, Safe Harbor, Expert Determination, gap analysis, compliance review. Pairs adjacent to OpenMed: the checklist shows where openmed.deidentify and signed audit reports satisfy the de-identification and audit-control requirements. The control list lives in references/hipaa-checklist.md. This is a structured self-assessment aid, not legal advice.
license
Apache-2.0
metadata.project
OpenMed
metadata.category
compliance-regulatory
metadata.pairs
adjacent
metadata.version
1.0

Checking HIPAA compliance before deploying on PHI

Before any pipeline touches protected health information (PHI), the operating entity (a covered entity or its business associate) must have the HIPAA Privacy Rule and Security Rule safeguards in place. This skill walks a concrete pipeline against those requirements and emits a gap report: which controls are met, which are missing, and where OpenMed's on-device de-identification and signed audit trail satisfy a requirement.

The full control list — administrative, physical, and technical safeguards with their 45 CFR citations — is in references/hipaa-checklist.md. This skill is a self-assessment aid, not legal advice; a Privacy Officer signs off on compliance.

When to use

  • You are about to deploy OpenMed (or any pipeline) on real PHI and need a go/no-go compliance review.
  • You must document safeguards and minimum-necessary controls for an audit, a BAA, or a security questionnaire.
  • You want to decide between Safe Harbor and Expert Determination de-identification and record the rationale.
  • You need a reproducible gap report you can hand to a Privacy/Security Officer.

The two paths to "no longer PHI"

HIPAA recognizes two de-identification methods (45 CFR 164.514):

  1. Safe Harbor — remove all 18 identifier categories and have no actual knowledge the result can re-identify. Deterministic, the common path.
  2. Expert Determination — a qualified statistician certifies "very small" re-identification risk. Used when you must keep some quasi-identifiers.

OpenMed's deidentify(..., policy="hipaa_safe_harbor") targets the Safe Harbor identifier set on-device, and deidentify(..., audit=True) produces a signed, PHI-free AuditReport that documents what was removed — the evidence a Safe Harbor attestation and a Security Rule audit control both want.

Quick start

python
import openmed

# A representative record from the pipeline (synthetic — never log real PHI).
sample = "John Doe (MRN 1234567), DOB 1970-01-15, seen 2024-03-02 in Boston."

# 1) De-identify on-device under the Safe Harbor policy.
result = openmed.deidentify(sample, method="replace", policy="hipaa_safe_harbor")
print(result.deidentified_text)        # identifiers removed/surrogated

# 2) Produce the signed, no-PHI audit record for the compliance file.
report = openmed.deidentify(sample, policy="hipaa_safe_harbor", audit=True)
report.sign(b"<release-hmac-key-from-vault>", key_id="hipaa-2026")

# 3) Walk the checklist (see references/hipaa-checklist.md) and record gaps.
controls = {
    "encryption_at_rest": True,
    "encryption_in_transit": True,
    "access_controls_rbac": True,
    "audit_logging": True,          # satisfied in part by the signed AuditReport
    "minimum_necessary": False,     # <-- gap: pipeline pulls full notes
    "baa_in_place": True,
    "deidentification_method": "safe_harbor",
}
gaps = [name for name, ok in controls.items() if not ok]
print("GAPS:", gaps)

Workflow

  1. Map the data flow. Diagram every place PHI is created, received, maintained, or transmitted — including model caches, temp files, and logs.
  2. Confirm the legal basis. Is the operator a covered entity or business associate? Is a BAA in place with every downstream vendor that touches PHI? OpenMed running on-device means no third-party processor for the NLP step — note that as a control in your favor.
  3. Run the three safeguard groups from references/hipaa-checklist.md: administrative (risk analysis, workforce training, sanctions), physical (facility/device controls), and technical (access control, audit controls, integrity, transmission security).
  4. Enforce minimum necessary. Pull only the fields the task needs; mask the rest. De-identify as early in the flow as the use case allows.
  5. Record the de-identification method (Safe Harbor vs Expert Determination) and attach the signed AuditReport as evidence.
  6. Emit the gap report — met / not-met / N/A per control, with the 45 CFR citation and the remediation owner. Hand it to the Privacy Officer.
Show full SKILL.md (316 more words)Show less

Hand-off to / from OpenMed

  • De-identification: deidentifying-clinical-text (openmed.deidentify, policy="hipaa_safe_harbor") is the technical control that converts PHI to non-PHI on-device — the heart of a HIPAA pipeline.
  • Identifier coverage: auditing-safe-harbor-checklist maps detected spans to the 18 Safe Harbor categories so you can prove each is handled.
  • Audit control: auditing-deidentification-runs (audit=True → AuditReport.sign()/.verify()) gives the tamper-evident, PHI-free record the Security Rule audit-controls standard (164.312(b)) expects.
  • No-PHI logging: enforcing-nophi-logging keeps identifiers out of logs and traces (a recurring audit finding).
  • OpenMed is local-first — the NLP step adds no new business associate.

Edge cases & gotchas

  • De-identified data is out of scope — but only if done right. Safe Harbor requires all 18 categories removed and no actual knowledge of re-identifiability. A residual rare ZIP3 or a free-text name the model missed re-introduces PHI. Verify coverage; don't assume.
  • Limited Data Sets are still PHI. Dates and ZIPs retained under a Data Use Agreement (164.514(e)) are not de-identified — different rules apply.
  • Logs and caches are PHI too. Model caches, exception messages, and temp files holding raw notes are in scope. This is the most common gap.
  • A BAA is required for every vendor that creates/receives/maintains/ transmits PHI on your behalf — including cloud storage and any LLM API. Running OpenMed on-device avoids adding one for the NLP step.
  • Minimum necessary is a duty, not a nicety (164.502(b)). Don't pull full charts when a problem list suffices.
  • Breach notification clock. Unsecured PHI exposure triggers 164.400-414 duties; encryption to NIST standards renders data "secured" and can avoid the notification trigger.
  • Not legal advice. This checklist supports, but does not replace, a Privacy Officer's determination and (for Expert Determination) a qualified statistician.

Standards & references

© maziyarpanahi, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/checking-hipaa-compliance of maziyarpanahi/openmed.

  • SKILL.md
  • references/hipaa-checklist.md

Open the folder on GitHubat commit 34d7b8c

Compare with similar skills

HIPAA Pre-Deployment Compliance Check next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

HIPAA Pre-Deployment Compliance Check compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
HIPAA Pre-Deployment Compliance Check this skillmaziyarpanahi/openmed5.5k—~2kAutomated safety check: PassApache-2.0
Hipaa ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance9461 repos~2.3kAutomated safety check: PassMIT
ISO Standards Readiness EvidenceK-Dense-AI/scientific-agent-skills48k1 repos~4.6kAutomated safety check: NotesMIT
Policy OpaAgentSecOps/SecOpsAgentKit2201 repos~3.5kAutomated safety check: PassCustom licence
Implementing Complianceancoleman/ai-design-components525—~4kAutomated safety check: PassMIT
Security Compliance Compliance Checkaiskillstore/marketplace4338 repos~600Automated safety check: PassNone

Similar skills

  • Hipaa Compliance

    Sushegaad/Claude-Skills-Governance-Risk-and-Compliance

    Expert HIPAA compliance assistant for healthcare and software contexts.

    946 GitHub starsUsed in 1 repo~2.3k tokens
    Legal & ComplianceAuto-check passed
  • ISO Standards Readiness Evidence

    K-Dense-AI/scientific-agent-skills

    Organizes scope, controlled documents, risk files and traceability into draft evidence for human review against ISO 13485, 14971, 17025 and 15189.

    48k GitHub starsUsed in 1 repo~4.6k tokens
    Legal & ComplianceAuto-check: notes
  • Policy Opa

    AgentSecOps/SecOpsAgentKit

    Policy-as-code enforcement and compliance validation using Open Policy Agent (OPA).

    220 GitHub starsUsed in 1 repo~3.5k tokens
    Legal & ComplianceAuto-check passed
  • Implementing Compliance

    ancoleman/ai-design-components

    Implement and maintain compliance with SOC 2, HIPAA, PCI-DSS, and GDPR using unified control mapping, policy-as-code enforcement, and automated evidence collection.

    525 GitHub stars~4k tokensUpdated 10 mo ago
    Legal & ComplianceAuto-check passed
  • Security Compliance Compliance Check

    aiskillstore/marketplace

    You are a compliance expert specializing in regulatory requirements for software systems including GDPR, HIPAA, SOC2, PCI-DSS, and other industry standards.

    433 GitHub starsUsed in 8 repos~600 tokens
    Legal & ComplianceAuto-check passed
  • Compliance Testing

    proffesor-for-testing/agentic-qe

    Regulatory compliance testing for GDPR, CCPA, HIPAA, SOC2, PCI-DSS and industry-specific regulations.

    495 GitHub stars~1.8k tokensUpdated yesterday
    Legal & ComplianceAuto-check passed

More from maziyarpanahi/openmed

All 74 skills in this repo
  • Checks OpenMed de-identified clinical text against the 18 HIPAA Safe Harbor identifier categories and reports gaps and residual re-identification risk.

    5.5k GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • OpenMed Model Card Writer

    maziyarpanahi/openmed

    Fills in a model card for an OpenMed clinical NER or de-identification model from its evaluation reports: intended use, metrics, subgroups and limitations.

    5.5k GitHub stars~1.8k tokensUpdated today
    Auto-check passed
  • ICD-10 Coding Assistant

    maziyarpanahi/openmed

    Suggests candidate ICD-10-CM diagnosis and ICD-10-PCS procedure codes for clinical text extracted by OpenMed, with rationale for a certified coder to review.

    5.5k GitHub stars~2k tokensUpdated today
    Auto-check passed
  • OpenMed ETL to OMOP CDM

    maziyarpanahi/openmed

    Maps OpenMed-extracted, terminology-coded conditions, drugs and measurements into OMOP CDM v5.4 tables for OHDSI and ATLAS analytics.

    5.5k GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • Extracting SDOH and Z-Codes

    maziyarpanahi/openmed

    Finds social risks such as housing instability or food insecurity in clinical notes and proposes matching ICD-10-CM Z-codes for a coder to confirm.

    5.5k GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • Clinical Document Ingestion

    maziyarpanahi/openmed

    Converts scanned faxes, images, CSV/TSV exports and C-CDA XML into clean text on-device, ready for OpenMed de-identification and named-entity recognition.

    5.5k GitHub stars~2k tokensUpdated today
    Auto-check passed

Questions about HIPAA Pre-Deployment Compliance Check

What does HIPAA Pre-Deployment Compliance Check do?

Walks a data pipeline against the HIPAA Privacy and Security Rule checklist and produces a gap report before it processes patient data. This skill reads a control list of administrative, physical, and technical safeguards with their 45 CFR citations from its reference file, then works through mapping the data flow, confirming whether the operator is a covered entity or business associate, and checking whether a BAA is in place with every downstream vendor.

When should I use HIPAA Pre-Deployment Compliance Check?

HIPAA Pre-Deployment Compliance Check fits situations like: reviewing a pipeline before it touches real patient data; documenting safeguards for a BAA or security questionnaire; choosing between Safe Harbor and Expert Determination de-identification.

How do I install HIPAA Pre-Deployment Compliance Check in Claude Code?

Run `npx skills add maziyarpanahi/openmed --skill checking-hipaa-compliance -a claude-code`. Or copy the skill folder (skills/checking-hipaa-compliance in maziyarpanahi/openmed) into .claude/skills/checking-hipaa-compliance in your project. Claude Code loads it when a task matches its description.

How do I install HIPAA Pre-Deployment Compliance Check in Codex?

Run `npx skills add maziyarpanahi/openmed --skill checking-hipaa-compliance -a codex`. Or copy the skill folder (skills/checking-hipaa-compliance in maziyarpanahi/openmed) into .agents/skills/checking-hipaa-compliance in your project. Codex loads it when a task matches its description.

Can I use HIPAA Pre-Deployment Compliance Check in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add maziyarpanahi/openmed --skill checking-hipaa-compliance -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/checking-hipaa-compliance, .gemini/skills/checking-hipaa-compliance, .github/skills/checking-hipaa-compliance and .opencode/skills/checking-hipaa-compliance in your project.

What does HIPAA Pre-Deployment Compliance Check need to run?

SKILL.md names no scripts, command-line tools or credentials: HIPAA Pre-Deployment Compliance Check is instructions for the agent only.

Does HIPAA Pre-Deployment Compliance Check access the network?

SKILL.md names 4 domains. As links in the text: hhs.gov, ecfr.gov, healthit.gov and csrc.nist.gov. This is read from the text; nothing was executed.

Is HIPAA Pre-Deployment Compliance Check safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does HIPAA Pre-Deployment Compliance Check use?

HIPAA Pre-Deployment Compliance Check is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does HIPAA Pre-Deployment Compliance Check use?

About 2k tokens (SKILL.md is roughly 8.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.4k tokens, read only when the agent opens those files.

What are the alternatives to HIPAA Pre-Deployment Compliance Check?

Skills that share tags, products or a category with HIPAA Pre-Deployment Compliance Check: Hipaa Compliance (Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, 946 stars), ISO Standards Readiness Evidence (K-Dense-AI/scientific-agent-skills, 48k stars), Policy Opa (AgentSecOps/SecOpsAgentKit, 220 stars) and Implementing Compliance (ancoleman/ai-design-components, 525 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains HIPAA Pre-Deployment Compliance Check?

maziyarpanahi (a GitHub user) maintains it in maziyarpanahi/openmed, which has 5,506 GitHub stars. The repository holds 74 skills in this directory. The repository was last updated on October 11, 2026.

Source: maziyarpanahi/openmed on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.