mcpField
H
hipaa-compliance-guard

hipaa-compliance-guard

github.com/jorgealvesSecurity2238 installsUpdated 2d ago
Repository

About hipaa-compliance-guard

hipaa-compliance-guard is a technical auditing skill for healthcare application systems, focused on HIPAA Security Rule protections for ePHI. It reviews infrastructure configuration without accessing patient data and is intended for design reviews, self-assessments, and infrastructure changes.

Key features

  1. 01HIPAA Security Rule configuration checks
  2. 02ePHI system security assessment
  3. 03Infrastructure code scanning
  4. 04Local analysis without PHI access

Use cases

  1. 01Review encryption and logging during architecture design
  2. 02Find technical issues before a HIPAA audit
  3. 03Recheck security after Terraform or cloud-script changes

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/jorgealves/agent_skills --skill hipaa-compliance-guard

After installing, type/hipaa-compliance-guardin Claude Code to confirm it loaded.

Bundled filesskill.yaml

Details

From the project README

HIPAA Compliance Guard

Purpose and Intent

The hipaa-compliance-guard is a specialized auditing tool for the healthcare industry. Its goal is to provide a technical assessment of how well an application adheres to the HIPAA Security Rule, specifically focusing on the protection of Electronic Protected Health Information (ePHI).

When to Use

  • Architecture Reviews: Run during the design phase to ensure encryption and logging are planned.
  • Pre-Audit Self-Assessment: Use before a formal 3rd-party HIPAA audit to identify and fix low-hanging violations.
  • Infrastructure Changes: Run after modifying Terraform or Cloud scripts to ensure security groups or encryption haven't been compromised.

When NOT to Use

  • Real Patient Data: This tool should NOT be used on live databases containing PHI. It is for checking the systems that handle the data.
  • Legal Certification: Passing this audit does not mean you are "HIPAA Certified"; it means your technical configuration follows best practices.

Error Conditions and Edge Cases

  • Obfuscated Infrastructure: If cloud resources are created via manual console actions (ClickOps) instead of code, this tool cannot see them.
  • Custom Encryption: Proprietary or non-standard encryption methods may be flagged as warnings.

Security and Data-Handling Considerations

  • No PHI Access: The tool is designed to look at configurations, not data.
  • Local Analysis: Keep your infrastructure code local and run the scan within your trusted environment.

Comments

Markdown supported