hipaa-compliance

Applies HIPAA decision gates and PHI guardrails to US healthcare software tasks.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/freedom909/real-estate-saas --skill hipaa-compliance-freedom909
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hipaa-compliance
Source: https://github.com/freedom909/real-estate-saas/tree/main/.trae/skills/hipaa-compliance
Command: npx skills add https://github.com/freedom909/real-estate-saas --skill hipaa-compliance-freedom909

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams building or reviewing US healthcare software risk exposing PHI through logs, analytics, LLM prompts, or unvetted vendors, and need a clear HIPAA-specific entrypoint that routes work to the right compliance checks. ## Core Features & Use Cases - HIPAA Decision Gates: Determines whether data is PHI, whether actors are covered entities or business associates, and whether a BAA is required before vendors touch data. - PHI Guardrails: Blocks PHI from logs, analytics events, URLs, browser storage, prompts, and error strings while enforcing minimum necessary access and audit trails. - Skill Routing: Delegates implementation rules to healthcare-phi-compliance and escalates clinical or regulated architecture decisions to healthcare-reviewer. - Use Case: When asked to add AI-generated visit summaries to a clinician dashboard for US clinics, this Skill verifies BAA coverage for the summarization provider and reviews PHI movement before any data is sent. ## Quick Start Ask the AI to review your healthcare feature for HIPAA compliance, for example whether sending patient messages into an analytics stack is acceptable.

Frequently Asked Questions about hipaa-compliance

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

FAQPage Schema
How do I check if a healthcare feature is HIPAA compliant?▼

Start by determining whether the data is PHI and whether the actors are covered entities or business associates. Then verify minimum necessary access, audit trails for reads and writes, and BAA status for any vendor touching the data.

When should I use a HIPAA compliance review for my software?▼

Use it when a request explicitly mentions HIPAA, PHI, covered entities, or BAAs, or when building US healthcare software that stores, processes, exports, or transmits patient data through logs, analytics, or LLM prompts.

Can I send patient messages to an analytics or LLM provider?▼

Treat third-party SaaS, observability, and LLM providers as blocked by default until BAA status and data boundaries are confirmed. Prefer redaction or a non-PHI event model, and never place PHI in prompts or analytics events.

What data must never appear in logs under HIPAA?▼

PHI must never appear in logs, analytics events, crash reports, prompts, URLs, browser storage, screenshots, or client-visible error strings. Use opaque internal IDs instead of names, MRNs, phone numbers, or addresses.

What are the limitations of this HIPAA entrypoint skill?▼

It is intentionally thin and does not contain implementation rules itself. Concrete PHI handling rules come from healthcare-phi-compliance, and clinical or regulated architecture decisions are escalated to healthcare-reviewer.