HIPAA Safe Harbor Coverage Audit
maziyarpanahi/openmed
Checks OpenMed de-identified clinical text against the 18 HIPAA Safe Harbor identifier categories and reports gaps and residual re-identification risk.
Addresses HIPAA privacy and security requirements for health data interoperability under the 21st Century Cures Act, ONC Health IT Certification Program, and CMS Interoperability and Patient Access…
Install Hipaa Interoperability
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill hipaa-interoperability -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills hipaa-interoperability --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/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/privacy/hipaa-interoperability .claude/skills/hipaa-interoperability && 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 "hipaa-interoperability" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/hipaa-interoperability into .claude/skills/hipaa-interoperability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hipaa-interoperability", 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/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/hipaa-interoperabilityType 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 mukul975/Privacy-Data-Protection-Skills --skill hipaa-interoperability -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills hipaa-interoperability --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/privacy/hipaa-interoperability .agents/skills/hipaa-interoperability && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "hipaa-interoperability" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/hipaa-interoperability into .agents/skills/hipaa-interoperability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hipaa-interoperability", 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 mukul975/Privacy-Data-Protection-Skills --skill hipaa-interoperability -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills hipaa-interoperability --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/privacy/hipaa-interoperability .cursor/skills/hipaa-interoperability && 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 "hipaa-interoperability" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/hipaa-interoperability into .cursor/skills/hipaa-interoperability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hipaa-interoperability", 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/mukul975/Privacy-Data-Protection-Skills.git --path skills/privacy/hipaa-interoperability--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 mukul975/Privacy-Data-Protection-Skills --skill hipaa-interoperability -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills hipaa-interoperability --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/privacy/hipaa-interoperability .gemini/skills/hipaa-interoperability && 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 "hipaa-interoperability" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/hipaa-interoperability into .gemini/skills/hipaa-interoperability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hipaa-interoperability", 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 mukul975/Privacy-Data-Protection-Skills hipaa-interoperabilityInstalls 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 mukul975/Privacy-Data-Protection-Skills --skill hipaa-interoperability -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/privacy/hipaa-interoperability .github/skills/hipaa-interoperability && 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 "hipaa-interoperability" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/hipaa-interoperability into .github/skills/hipaa-interoperability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hipaa-interoperability", 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 mukul975/Privacy-Data-Protection-Skills --skill hipaa-interoperability -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills hipaa-interoperability --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/privacy/hipaa-interoperability .opencode/skills/hipaa-interoperability && 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 "hipaa-interoperability" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/hipaa-interoperability into .opencode/skills/hipaa-interoperability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hipaa-interoperability", 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.
Facts
- Skill name
hipaa-interoperability- GitHub stars
- 295
- Token cost
- ~1.8k tokens
- SKILL.md length
- 797 words
- Files
- 5 (incl. scripts, references, assets)
- Skills in repo
- 278
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Addresses HIPAA privacy and security requirements for health data interoperability under the 21st Century Cures Act, ONC Health IT Certification Program, and CMS Interoperability and Patient Access…
- Works in 4 steps: Identity verification: Verify patient… → Scope of access: HIPAA right of access… → Third-party app authorization: Patient… → …
- Tasks that involve Healthcare and finance regulation
- SKILL.md covers Overview, Regulatory Framework, HIPAA Privacy Safeguards for… and Security Requirements for…, plus 2 more sections
- Runs Python scripts from its folder
What it does
Hipaa Interoperability is an agent skill from mukul975/Privacy-Data-Protection-Skills. Addresses HIPAA privacy and security requirements for health data interoperability under the 21st Century Cures Act, ONC Health IT Certification Program, and CMS Interoperability and Patient Access Final Rule. Covers information blocking prohibitions, FHIR API patient access, TEFCA exchange purposes, and privacy safeguards for health information exchange. Keywords: interoperability, information blocking, FHIR, TEFCA, Cures Act, patient access API, health information exchange.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts, reference files and assets (for example `assets/template.md`, `references/standards.md` and `references/workflows.md`).
It sits in Legal & Compliance, covering Healthcare and finance regulation, Clinical and healthcare research and Privacy and GDPR. The repository describes itself as: 282+ structured privacy & data protection skills for AI agents. GDPR, CCPA, EU AI Act, HIPAA, LGPD, PIPL, DPDP Act. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Healthcare and finance regulation
- Tasks that involve Clinical and healthcare research
- Tasks that involve Privacy and GDPR
Example prompts
- “Use the hipaa-interoperability skill to address HIPAA privacy and security requirements for health data interoperability under the 21st Century…”
- “/hipaa-interoperability”
Requirements
- Python 3
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Identity verification: Verify patient identity using multi-factor authentication before granting API access (aligned with NIST IAL2/AAL2)
- Scope of access: HIPAA right of access (§164.524) — entire designated record set except psychotherapy notes, information compiled for…
- Third-party app authorization: Patient may direct data to third-party apps via SMART on FHIR; once data is shared with a non-covered…
- Minimum necessary: Does NOT apply to individual access requests (§164.502(b)(2)(v)) or treatment disclosures
What it can do on your machine
Read from SKILL.md and the folder at commit 9b2ef9e. 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
Ships 1 file in scripts/ (Python), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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 Interoperability loads about 1.8k tokens when it runs, and up to ~5.1k if it reads all its reference files. Until then it costs about 126 tokens; SKILL.md has 797 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.
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); the scripts in this folder are not scanned.
SKILL.md
The full file from mukul975/Privacy-Data-Protection-Skills at commit 9b2ef9e, republished under its Apache-2.0 licence (© mukul975). 797 words, ~1,847 tokens.
Download SKILL.mdSave it as
.claude/skills/hipaa-interoperability/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- hipaa-interoperability
- description
- Addresses HIPAA privacy and security requirements for health data interoperability under the 21st Century Cures Act, ONC Health IT Certification Program, and CMS Interoperability and Patient Access Final Rule. Covers information blocking prohibitions, FHIR API patient access, TEFCA exchange purposes, and privacy safeguards for health information exchange. Keywords: interoperability, information blocking, FHIR, TEFCA, Cures Act, patient access API, health information exchange.
- license
- Apache-2.0
- metadata.author
- mukul975
- metadata.version
- 1.0
- metadata.domain
- privacy
- metadata.subdomain
- healthcare-privacy
- metadata.tags
- hipaa, interoperability, information-blocking, fhir, tefca, cures-act, patient-access, hie
HIPAA Interoperability — Cures Act, ONC, and CMS Requirements
Overview
The 21st Century Cures Act (Public Law 114-255, 2016) fundamentally changed the interoperability landscape by prohibiting information blocking and mandating standardized API-based patient access. The ONC Health IT Certification Program (45 CFR Part 170) and the CMS Interoperability and Patient Access Final Rule (CMS-9115-F, 85 FR 25510, May 1, 2020) together require health IT developers, healthcare providers, health information exchanges (HIEs), and health information networks (HINs) to support seamless data exchange while maintaining HIPAA privacy and security protections. The Trusted Exchange Framework and Common Agreement (TEFCA), launched operationally in December 2023, establishes a nationwide framework for health information exchange with defined exchange purposes and privacy requirements.
Regulatory Framework
21st Century Cures Act — Information Blocking
- Section 4004: Defines information blocking as a practice that is likely to interfere with, prevent, or materially discourage access, exchange, or use of electronic health information (EHI)
- Actors covered: Health IT developers of certified health IT, HIEs, HINs, and healthcare providers
- EHI definition: As of October 6, 2022, EHI is the electronic protected health information (ePHI) in a designated record set as defined under HIPAA (45 CFR §171.102), plus any other electronic health information identified by the Secretary
Information Blocking Exceptions (45 CFR Part 171)
| Exception | Category | Description |
|---|---|---|
| Preventing Harm (§171.201) | Not fulfilling requests | Practice is reasonable and necessary to prevent harm to a patient or another person |
| Privacy (§171.202) | Not fulfilling requests | Practice is required by or consistent with HIPAA Privacy Rule obligations |
| Security (§171.203) | Not fulfilling requests | Practice is directly related to safeguarding the confidentiality, integrity, or availability of EHI |
| Infeasibility (§171.204) | Not fulfilling requests | Fulfilling the request is technically infeasible |
| Health IT Performance (§171.205) | Procedures | Practice is for reasonable maintenance or improvements to health IT |
| Content and Manner (§171.301) | Procedures | Actor fulfills a request in an alternative manner or with alternative content |
| Fees (§171.302) | Procedures | Fees charged are reasonable and based on objective, verifiable criteria |
| Licensing (§171.303) | Procedures | Licensing terms are reasonable and non-discriminatory |
CMS Interoperability and Patient Access Final Rule
- Patient Access API (§431.60): CMS-regulated payers (Medicaid, CHIP, QHP issuers on FFE) must implement a FHIR R4-based Patient Access API allowing patients to access claims, encounter, and clinical data
- Provider Directory API (§431.70): Payers must implement a publicly accessible FHIR-based provider directory
- Payer-to-Payer Data Exchange (CMS-0057-F, effective January 1, 2026): Payers must exchange patient data at the patient's request when they switch plans
- Prior Authorization API (CMS-0057-F): Payers must implement a FHIR-based prior authorization API
TEFCA Exchange Purposes
| Exchange Purpose | Description | HIPAA Basis |
|---|---|---|
| Treatment | Direct patient care | §164.506(c)(2) — TPO |
| Payment | Claims, eligibility, coordination of benefits | §164.506(c)(3) — TPO |
| Healthcare Operations | Quality assessment, care coordination | §164.506(c)(5) — TPO |
| Public Health | Reporting to public health authorities | §164.512(b) |
| Benefits Determination | Health plan coverage decisions | §164.506(c)(3) |
| Individual Access | Patient right of access | §164.524 |
HIPAA Privacy Safeguards for Interoperability
Show full SKILL.md (328 more words)Show less
Patient Access via FHIR API
- Identity verification: Verify patient identity using multi-factor authentication before granting API access (aligned with NIST IAL2/AAL2)
- Scope of access: HIPAA right of access (§164.524) — entire designated record set except psychotherapy notes, information compiled for legal proceedings, and certain lab results under CLIA
- Third-party app authorization: Patient may direct data to third-party apps via SMART on FHIR; once data is shared with a non-covered entity app, HIPAA protections may no longer apply — disclosure notice required
- Minimum necessary: Does NOT apply to individual access requests (§164.502(b)(2)(v)) or treatment disclosures
HIE/HIN Privacy Requirements
- Maintain BAAs with all participating providers per §164.502(e)
- Implement role-based access tied to exchange purpose
- Apply consent management per state law requirements (particularly for 42 CFR Part 2 substance abuse records and state-specific sensitive categories)
- Maintain accounting of disclosures per §164.528
Security Requirements for Interoperable Systems
| Requirement | Regulation | Implementation |
|---|---|---|
| Encryption in transit | §164.312(e)(1) | TLS 1.2+ for all FHIR API and HIE connections |
| Access controls | §164.312(a)(1) | OAuth 2.0 / SMART on FHIR authorization |
| Audit controls | §164.312(b) | Log all API requests, queries, and data exchanges with timestamps and actor identity |
| Integrity controls | §164.312(c)(1) | Digital signatures on exchange payloads; FHIR resource versioning |
| Authentication | §164.312(d) | Unique user identification for all API consumers; system-level certificates for point-to-point |
Enforcement
- Information blocking penalties: Health IT developers, HIEs, and HINs face civil monetary penalties up to $1 million per violation under ONC (final rule effective September 1, 2023). Healthcare providers face appropriate disincentives through CMS (final rule pending).
- HIPAA penalties: Standard HIPAA enforcement under OCR applies to all privacy and security violations in the interoperability context.
Integration Points
- hipaa-privacy-rule: Interoperability must comply with all Privacy Rule requirements for uses and disclosures
- hipaa-security-rule: Technical safeguards for API and exchange security
- hipaa-minimum-necessary: Minimum necessary standard applies to most interoperability disclosures (except individual access and treatment)
- hipaa-baa-management: BAAs required for all HIE/HIN participants and health IT vendors accessing PHI
- hipaa-breach-notification: Breach notification obligations extend to interoperability-related incidents
© mukul975, 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 4 other files (scripts, references, assets) in skills/privacy/hipaa-interoperability of mukul975/Privacy-Data-Protection-Skills.
- SKILL.md
- assets/template.md
- references/standards.md
- references/workflows.md
- scripts/process.py
Open the folder on GitHubat commit 9b2ef9e
Compare with similar skills
Hipaa Interoperability 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 Interoperability this skillmukul975/Privacy-Data-Protection-Skills | 295 | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| HIPAA Safe Harbor Coverage Auditmaziyarpanahi/openmed | 5.5k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Hipaa ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 942 | 1 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Clinical Reportsdavila7/claude-code-templates | 32k | 11 repos | ~9.9k | Automated safety check: Notes | MIT | |
| Audit Reportharness/harness-skills | 115 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Anne WojcickiK-Dense-AI/mimeographs | 129 | — | ~1.5k | Automated safety check: Pass | MIT |
Similar skills
Hipaa Compliance
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert HIPAA compliance assistant for healthcare and software contexts.
Clinical Reports
davila7/claude-code-templates
Write comprehensive clinical reports including case reports (CARE guidelines), diagnostic reports (radiology/pathology/lab), clinical trial reports (ICH-E3, SAE, CSR), and patient documentation…
Audit Report
harness/harness-skills
Generate audit reports and compliance trails using Harness audit trail data via MCP v2 tools.
Anne Wojcicki
K-Dense-AI/mimeographs
Applies the strategic frameworks and mental models of Anne Wojcicki, co-founder and CEO of 23andMe.
Dpa Checklist Review
LegalQuants/lq-ai
A skill your agent uses when the user provides a Data Processing Agreement, Data Processing Addendum, or HIPAA Business Associate Agreement and asks whether it contains the terms required under the…
More from mukul975/Privacy-Data-Protection-Skills
All 278 skills in this repoAge Gating Services
mukul975/Privacy-Data-Protection-Skills
Implements age-gating mechanisms for online services to restrict access based on user age.
AI Data Retention
mukul975/Privacy-Data-Protection-Skills
Manages AI model retention and machine unlearning requirements.
Dpia Mitigation Plan
mukul975/Privacy-Data-Protection-Skills
Structures risk mitigation planning and residual risk tracking for Data Protection Impact Assessments under GDPR Article 35(7)(d).
Gdpr Accountability
mukul975/Privacy-Data-Protection-Skills
Guides implementation of the GDPR accountability principle under Articles 5(2) and 24, including documentation requirements for policies, DPIAs, RoPA, training records, and breach logs.
Pia Threshold Screening
mukul975/Privacy-Data-Protection-Skills
Conducts pre-DPIA threshold screening to determine whether a full Data Protection Impact Assessment is required under GDPR Article 35.
Retention Schedule
mukul975/Privacy-Data-Protection-Skills
Designs and implements data retention schedules compliant with GDPR Article 5(1)(e) storage limitation principle.
Related
Categories
Questions about Hipaa Interoperability
What does Hipaa Interoperability do?
Addresses HIPAA privacy and security requirements for health data interoperability under the 21st Century Cures Act, ONC Health IT Certification Program, and CMS Interoperability and Patient Access…. Hipaa Interoperability is an agent skill from mukul975/Privacy-Data-Protection-Skills. Addresses HIPAA privacy and security requirements for health data interoperability under the 21st Century Cures Act, ONC Health IT Certification Program, and CMS Interoperability and Patient Access Final Rule.
When should I use Hipaa Interoperability?
Hipaa Interoperability fits situations like: tasks that involve Healthcare and finance regulation; tasks that involve Clinical and healthcare research; tasks that involve Privacy and GDPR.
How do I install Hipaa Interoperability in Claude Code?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill hipaa-interoperability -a claude-code`. Or copy the skill folder (skills/privacy/hipaa-interoperability in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/hipaa-interoperability in your project. Claude Code loads it when a task matches its description.
How do I install Hipaa Interoperability in Codex?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill hipaa-interoperability -a codex`. Or copy the skill folder (skills/privacy/hipaa-interoperability in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/hipaa-interoperability in your project. Codex loads it when a task matches its description.
Can I use Hipaa Interoperability 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 mukul975/Privacy-Data-Protection-Skills --skill hipaa-interoperability -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/hipaa-interoperability, .gemini/skills/hipaa-interoperability, .github/skills/hipaa-interoperability and .opencode/skills/hipaa-interoperability in your project.
What does Hipaa Interoperability need to run?
Going by SKILL.md and its folder, Hipaa Interoperability needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Hipaa Interoperability access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Hipaa Interoperability 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Hipaa Interoperability use?
Hipaa Interoperability 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 Interoperability use?
About 1.8k tokens (SKILL.md is roughly 7.4k 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 3.3k tokens, read only when the agent opens those files.
What are the alternatives to Hipaa Interoperability?
Skills that share tags, products or a category with Hipaa Interoperability: HIPAA Safe Harbor Coverage Audit (maziyarpanahi/openmed, 5.5k stars), Hipaa Compliance (Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, 942 stars), Clinical Reports (davila7/claude-code-templates, 32k stars) and Audit Report (harness/harness-skills, 115 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Hipaa Interoperability?
mukul975 (a GitHub user) maintains it in mukul975/Privacy-Data-Protection-Skills, which has 295 GitHub stars. The repository holds 278 skills in this directory. The repository was last updated on March 16, 2026.
Source: mukul975/Privacy-Data-Protection-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.