# Hipaa Internal Tool Builder

> Use when you need to vibe-code and deploy HIPAA-compliant internal tools without an engineering team.

- Skill: `harishkotra/hipaa-internal-tool-builder` (Agent Skill)
- Install (CLI): `npx skillmds@latest add harishkotra/hipaa-internal-tool-builder`
- Raw SKILL.md: https://api.skillmd.com/api/skills/harishkotra/hipaa-internal-tool-builder/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: harishkotra (https://skillmd.com/u/harishkotra)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/harishkotra/hipaa-internal-tool-builder

---


# HIPAA Internal Tool Builder
Vibe-code and deploy HIPAA-compliant internal tools with no engineering team.

## When to use
- A team without engineers wants internal tools that handle protected health information.
- You need speed (vibe-coding) without violating compliance.

## Procedure
1. Scope the tool and confirm it touches PHI; if so, HIPAA applies.
2. Choose a compliant deployment: proper access controls, encryption, audit logging, BAA with providers.
3. Build the happy path fast (vibe-code the core flow).
4. Add the compliance essentials: authentication, least-privilege access, audit trail, encryption at rest/in transit.
5. Validate against HIPAA requirements before any real data is used.

## Pitfalls
- Speed never overrides compliance when PHI is involved; the audit trail is non-negotiable.
- Know the difference between HIPAA-compliant and merely "secure-looking."

## Verification
- The tool works, and it meets the compliance checklist (auth, encryption, audit, BAA) for its data.