Hipaa Compliance
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert HIPAA compliance assistant for healthcare and software contexts.
Walks a data pipeline against the HIPAA Privacy and Security Rule checklist and produces a gap report before it processes patient data.
$ npx skills add maziyarpanahi/openmed --skill checking-hipaa-compliance -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install maziyarpanahi/openmed checking-hipaa-compliance --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "checking-hipaa-compliance" agent skill from https://github.com/maziyarpanahi/openmed/tree/master/skills/checking-hipaa-compliance into .claude/skills/checking-hipaa-compliance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "checking-hipaa-compliance", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/maziyarpanahi/openmed/tree/master/skills/checking-hipaa-complianceType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add maziyarpanahi/openmed --skill checking-hipaa-compliance -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install maziyarpanahi/openmed checking-hipaa-compliance --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/maziyarpanahi/openmed.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/checking-hipaa-compliance .agents/skills/checking-hipaa-compliance && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "checking-hipaa-compliance" agent skill from https://github.com/maziyarpanahi/openmed/tree/master/skills/checking-hipaa-compliance into .agents/skills/checking-hipaa-compliance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "checking-hipaa-compliance", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add maziyarpanahi/openmed --skill checking-hipaa-compliance -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install maziyarpanahi/openmed checking-hipaa-compliance --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/maziyarpanahi/openmed.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/checking-hipaa-compliance .cursor/skills/checking-hipaa-compliance && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "checking-hipaa-compliance" agent skill from https://github.com/maziyarpanahi/openmed/tree/master/skills/checking-hipaa-compliance into .cursor/skills/checking-hipaa-compliance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "checking-hipaa-compliance", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/maziyarpanahi/openmed.git --path skills/checking-hipaa-compliance--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add maziyarpanahi/openmed --skill checking-hipaa-compliance -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install maziyarpanahi/openmed checking-hipaa-compliance --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/maziyarpanahi/openmed.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/checking-hipaa-compliance .gemini/skills/checking-hipaa-compliance && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "checking-hipaa-compliance" agent skill from https://github.com/maziyarpanahi/openmed/tree/master/skills/checking-hipaa-compliance into .gemini/skills/checking-hipaa-compliance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "checking-hipaa-compliance", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install maziyarpanahi/openmed checking-hipaa-complianceInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add maziyarpanahi/openmed --skill checking-hipaa-compliance -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/maziyarpanahi/openmed.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/checking-hipaa-compliance .github/skills/checking-hipaa-compliance && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "checking-hipaa-compliance" agent skill from https://github.com/maziyarpanahi/openmed/tree/master/skills/checking-hipaa-compliance into .github/skills/checking-hipaa-compliance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "checking-hipaa-compliance", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add maziyarpanahi/openmed --skill checking-hipaa-compliance -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install maziyarpanahi/openmed checking-hipaa-compliance --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/maziyarpanahi/openmed.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/checking-hipaa-compliance .opencode/skills/checking-hipaa-compliance && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "checking-hipaa-compliance" agent skill from https://github.com/maziyarpanahi/openmed/tree/master/skills/checking-hipaa-compliance into .opencode/skills/checking-hipaa-compliance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "checking-hipaa-compliance", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
checking-hipaa-complianceWalks 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.
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.
2 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 34d7b8c. It shows what the files ask for, not the result of running them.
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.
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.
Links to these hosts (documentation or services it may open):
hhs.govecfr.govhealthit.govcsrc.nist.govFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from maziyarpanahi/openmed at commit 34d7b8c, republished under its Apache-2.0 licence (© maziyarpanahi). 738 words, ~2,037 tokens.
.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.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.
HIPAA recognizes two de-identification methods (45 CFR 164.514):
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.
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)AuditReport as evidence.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.auditing-safe-harbor-checklist maps detected spans
to the 18 Safe Harbor categories so you can prove each is handled.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.enforcing-nophi-logging keeps identifiers out of logs and
traces (a recurring audit finding).© 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
SKILL.md and 1 other file (references) in skills/checking-hipaa-compliance of maziyarpanahi/openmed.
Open the folder on GitHubat commit 34d7b8c
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| HIPAA Pre-Deployment Compliance Check this skillmaziyarpanahi/openmed | 5.5k | — | ~2k | Automated safety check: Pass | Apache-2.0 | |
| Hipaa ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 946 | 1 repos | ~2.3k | Automated safety check: Pass | MIT | |
| ISO Standards Readiness EvidenceK-Dense-AI/scientific-agent-skills | 48k | 1 repos | ~4.6k | Automated safety check: Notes | MIT | |
| Policy OpaAgentSecOps/SecOpsAgentKit | 220 | 1 repos | ~3.5k | Automated safety check: Pass | Custom licence | |
| Implementing Complianceancoleman/ai-design-components | 525 | — | ~4k | Automated safety check: Pass | MIT | |
| Security Compliance Compliance Checkaiskillstore/marketplace | 433 | 8 repos | ~600 | Automated safety check: Pass | None |
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert HIPAA compliance assistant for healthcare and software contexts.
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.
AgentSecOps/SecOpsAgentKit
Policy-as-code enforcement and compliance validation using Open Policy Agent (OPA).
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.
aiskillstore/marketplace
You are a compliance expert specializing in regulatory requirements for software systems including GDPR, HIPAA, SOC2, PCI-DSS, and other industry standards.
proffesor-for-testing/agentic-qe
Regulatory compliance testing for GDPR, CCPA, HIPAA, SOC2, PCI-DSS and industry-specific regulations.
maziyarpanahi/openmed
Checks OpenMed de-identified clinical text against the 18 HIPAA Safe Harbor identifier categories and reports gaps and residual re-identification risk.
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.
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.
maziyarpanahi/openmed
Maps OpenMed-extracted, terminology-coded conditions, drugs and measurements into OMOP CDM v5.4 tables for OHDSI and ATLAS analytics.
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.
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.
Categories
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.
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.
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.
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.
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.
SKILL.md names no scripts, command-line tools or credentials: HIPAA Pre-Deployment Compliance Check is instructions for the agent only.
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.
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.
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.
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.
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.
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.