hipaa-compliance-audit

Audits Django codebases against HIPAA Technical Safeguards and generates a compliance matrix.

Updated May 11, 2026
One-click install
npx skills add https://github.com/thachrocky12345/local-agent-train-workstation --skill hipaa-compliance-audit-thachrocky12345
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hipaa-compliance-audit
Source: https://github.com/thachrocky12345/local-agent-train-workstation/tree/main/.claude/skills/hipaa-compliance-audit
Command: npx skills add https://github.com/thachrocky12345/local-agent-train-workstation --skill hipaa-compliance-audit-thachrocky12345

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually verifying HIPAA Technical Safeguards (45 CFR 164.312) across a healthcare codebase is slow and error-prone. This Skill systematically greps a Django backend for access control gaps, missing audit logging, unencrypted PHI fields, insecure transmission settings, and Privacy Rule violations, then produces a structured compliance matrix with evidence and remediation steps. ## Core Features & Use Cases - Section-by-Section Audits: Run targeted checks for access controls, audit controls, integrity, transmission security, encryption at rest, minimum necessary, BAA boundaries, or Privacy Rule requirements. - PHI Model Targeting: Audits specific PHI-containing models (Notes, UserResponse, Appointment, Session) for IDOR vulnerabilities, missing permission classes, and overexposed serializers. - Compliance Matrix Output: Generates a dated Markdown or JSON report mapping each HIPAA requirement to PASS/FAIL status, file-level evidence, and concrete remediation such as installing django-auditlog. - Use Case: Before deploying a telehealth feature touching clinical notes, run a full audit to confirm every PHI endpoint enforces authentication, role-based authorization, and audit logging, then hand the matrix to your compliance officer. ## Quick Start Ask the AI to run a HIPAA compliance audit on the backend codebase and generate the full compliance matrix report.

Frequently Asked Questions about hipaa-compliance-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a Django app for HIPAA compliance?

Run targeted grep checks across views, serializers, and settings for each HIPAA safeguard: verify permission_classes on PHI views, check for audit logging packages, confirm TLS security settings, and inspect field-level encryption. The audit produces a compliance matrix mapping each 164.312 requirement to evidence and remediation.

What does a HIPAA Technical Safeguards audit check?

It checks access controls (164.312(a)), audit controls (164.312(b)), integrity (164.312(c)), person/entity authentication (164.312(d)), and transmission security (164.312(e)). This includes authentication enforcement, IDOR vulnerabilities, emergency access procedures, MFA, encryption at rest, and CORS/TLS configuration.

How do I add HIPAA audit logging to Django models?

Install django-auditlog and register each PHI model in the app's apps.py with auditlog.register(), specifying include_fields for sensitive columns. The audit log should capture user_id, action, model, record_id, timestamp, IP address, and changed fields to satisfy 164.312(b).

Which vendors need a BAA for a telehealth platform?

Vendors that touch PHI require a Business Associate Agreement: Twilio (video sessions and SMS), SendGrid (appointment emails), and Azure Cognitive Search (provider profiles). Payment processors like Stripe and PayPal handle no clinical data, so they need PCI DSS compliance instead of a BAA.

Can I run the audit on only one HIPAA section?

Yes, pass a section argument such as access, audit, integrity, transmission, encryption, minimum-necessary, baa, or privacy-rule to scope the checks. Output can be formatted as markdown or json depending on the --output flag.

What are common HIPAA violations found in Django settings?

Typical findings include DEBUG=True, ALLOWED_HOSTS set to wildcard, CORS_ORIGIN_ALLOW_ALL=True, a hardcoded SECRET_KEY, and missing session timeout. These violate encryption, transmission security, and automatic logoff requirements and must be overridden for production.