- Home
- Skills
- Agents & Orchestration
- hipaa readiness audit
Works with the AI Agents you already use
hipaa readiness audit
Audits codebases for HIPAA Security Rule gaps, identifies PHI leaks, and maps BAA requirements.
$16
hipaa readiness audit
Example session with this skill installed
Audit our Node.js patient portal repo. We use OpenAI for summaries and Sentry for logging. Are we HIPAA ready?
- Read your context and instructions
- Compiled the hipaa readiness audit
Findings
- §164.312(b): Audit Gap. Sentry logs capture request bodies containing PHI. No evidence of read-access logging.
- §164.308(b)(1): BAA Risk. OpenAI flow lacks an executed BAA; data contains 3 of 18 HIPAA identifiers.
- §164.312(a): Addressable. Missing documentation for encryption-at-rest.
Connects securely to your tools. The creator never sees your data.
About this skill
The problem
Developers often assume their stack is HIPAA compliant because they use AWS or Bitlocker. They lack a concrete map of how their specific code violates the HIPAA Security Rule or which vendors require a BAA.
What it does
- Scans codebases for ePHI-handling defects and maps them to specific HIPAA Security Rule citations.
- Identifies third-party vendors and AI providers that require a Business Associate Agreement (BAA).
- Finds missing audit controls, including failures to log record access (reads) rather than just writes.
- Detects ePHI leakage into client-side analytics, session replays, and unscrubbed error trackers.
- Generates severity-rated findings structured for OCR investigators or hospital security reviews.
Why this beats prompting it yourself
Generic LLM prompts often confuse proposed 2025 rules with current law or treat addressable requirements as optional. This skill uses a strict reference snapshot to ensure citations are accurate and distinguishes between code-level safeguards and organizational policies.
Use cases
- Preparing for a hospital CISO security review or vendor questionnaire.
- Auditing a healthtech repo to identify PHI exposure before a production launch.
- Generating evidence to feed an official 164.308(a)(1) risk analysis.
- Mapping AI usage to identify which LLM flows must stop due to missing BAAs.
Known limitations
Cannot verify physical safeguards (facility access) or administrative policies (employee training). Findings are unverified if repo access is not provided.
Cannot scan physical facilities or verify internal policies. Reporting is limited to technical safeguards. Code scans alone never prove compliance.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 4 months ago
Permissions
No special permissions declared or detected