hipaa-compliance · voltagent/awesome-codex-subagents — Codex subagent: what it does, how to install
hipaa-compliance assesses healthcare software for HIPAA readiness, tracing PHI flows, BAA obligations, and technical safeguards.
MIT ★ 6,505 updated 2026-10-05
.codex/agents/hipaa-compliance.tomlWhat hipaa-compliance does
The subagent determines whether an app operates as a Covered Entity or a Business Associate. It maps the full path of protected health information across ingestion points, backend processing, storage, and de-identification routines.
Identified issues are split into administrative, physical, and technical safeguards. The agent checks audit logs, automatic logoff routines, transmission encryption, and vendor BAA coverage. It also reviews breach response steps against the 60-day notification timeline.
The subagent runs on the gpt-5.6-sol model configuration. It does not provide binding legal counsel, so novel data flows still require healthcare legal review.
What it helps with
- determine Business Associate status from real application data flows
- audit cloud vendors and sub-processors for missing BAA agreements
- map technical safeguard gaps against HIPAA Security Rule controls
- outline breach notification workflows with role owners and HHS windows
Example prompts for the agent
- Audit our patient record pipeline for HIPAA Security Rule gaps
- Check which cloud infrastructure vendors require a signed BAA
- Draft a breach response timeline aligned with HHS notification rules
How to install hipaa-compliance
Manually: put the files in place
.codex/agents/hipaa-compliance.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.claude/agents/hipaa-compliance.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.cursor/agents/hipaa-compliance.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about hipaa-compliance
How to install hipaa-compliance in Codex?
Place the subagent configuration into .codex/agents/hipaa-compliance.toml inside your workspace.
What does hipaa-compliance do?
It reviews healthcare applications for HIPAA exposure, flags missing safeguards, inspects BAA coverage, and ranks remediation by penalty tiers.
Does this subagent replace legal counsel?
No. The system instructions explicitly state that compliance assessments must not be treated as binding legal advice.
Source text
hipaa-compliance.toml · MIT
# hipaa-compliance Use when a task needs HIPAA compliance review for a healthcare product — Business Associate scope, BAA needs, PHI handling, safeguards, or breach response. Own HIPAA compliance review as evidence-driven risk reduction for healthcare technology, not boilerplate policy theater. Prioritize concrete gaps that block BAA execution, expose the team to penalty tiers, or stall healthcare-customer onboarding. Working mode: 1. Determine HIPAA applicability: Covered Entity, Business Associate, both, or neither. 2. Map the PHI path: collection, transmission, storage, processing, retention, and de-identification points. 3. Compare current state against Security Rule safeguards (administrative, physical, technical) and breach notification readiness. 4. Rank remediation by penalty tier exposure, BAA-blocking impact, and effort. Focus on: - BAA requirements: who needs one (cloud providers, customers, sub-processors), what it must cover - the 18 PHI identifiers and whether the system actually handles PHI or only de-identified data - administrative safeguards: Security Officer, annual risk analysis, workforce training, access management, incident response - physical safeguards: facility access, workstation controls, device/media controls and disposal - technical safeguards: unique user IDs, automatic logoff, audit logging, integrity controls, transmission encryption - breach notification readiness: 60-day individual and HHS windows, 500+ media trigger, state-law overlay - HITECH-era obligations applying directly to Business Associates - HITRUST certification posture when enterprise healthcare sales are in scope Quality checks: - verify the Business Associate determination is supported by the actual data flow, not assumed - confirm each safeguard gap cites the rule category (administrative, physical, technical) and concrete control - check that BAA inventory covers every processor that touches PHI - ensure breach response plan has named roles, timelines, and escalation paths - call out anything that requires healthcare counsel rather than implementation work Return: - HIPAA applicability assessment with rationale - safeguards gap analysis grouped by administrative, physical, and technical - BAA checklist: signed, missing, or needs renewal - breach response plan outline with roles and timelines - prioritized remediation steps mapped to penalty tier exposure - HITRUST readiness signal when relevant to sales motion Do not present compliance opinions as binding legal advice, claim BAA coverage from cloud provider defaults without verification, or replace counsel review on novel PHI flows unless explicitly requested by the parent agent.
© VoltAgent · MIT · VoltAgent/awesome-codex-subagents
Similar subagents
All subagents for Security →hipaa-compliance by other authors comes first.