HIPAA / PHI Go-Live Gate for SaaS

    1

    Fail-closed go-live gate before a SaaS holds protected health information: 20 evidenced HIPAA Security Rule controls, two-person sign-off, control matrix, BAA worksheet, procedure pack and runbooks.

    $49

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    HIPAA / PHI Go-Live Gate for SaaS

    Example session with this skill installed

    We're about to let our first clinic customer, Acme Health Partners, put real patient data into our scheduling app. Run the PHI go-live gate on this repo (compliance/phi-gate.yaml is filled in) and tell me whether we can flip PHI_ENABLED.

    • Read your context and instructions
    • Compiled the hipaa phi go-live

    Verdict

    GATE FAIL · organization=Acme Health Partners · phi_switch=off · complete=16 / waived=1 / unmet=2 / missing_evidence=1

    PHI must stay off. PHI_ENABLED defaults to false in config/schema.ts:41 and tests/config/phi-switch.test.ts proves it, so step 1 is satisfied. Four findings block activation.

    Findings

    ControlProblemWhat would satisfy it
    recoveryunmet (status 'incomplete')A passed restore exercise record: archive id, SHA-256 verified, restored into an isolated instance, integrity check ok, measured RPO/RTO, reviewer. Your nightly backup exists but no restore has ever been run, and it lives on the same host as the database.
    baa_subprocessorsunmet (status 'incomplete')The BAA worksheet row for your error-tracking vendor is "unknown". Exceptions with stack traces can carry PHI. Either sign their BAA, scrub PHI before capture, or remove the SDK from PHI-handling routes.
    access_reviewplaceholder evidence 'done'A dated access-review record: every role, every member, who approved, with removals listed. Reference it like EV-2026-0143, not "done".
    sign_offsplatform_security_official sign-off missingYour side has not signed. The customer's privacy officer (privacy.officer@acme.example, 2026-10-20) has. Two different identities are required.

    Waived with justification: workforce_training (approved_by: compliance lead, customer runs its own program; keep the approval reference).

    Repository findings fixed during this run

    • src/api/intake.ts accepted PHI-marked fields while the switch was off. Added the guard and a test (tests/api/intake-phi-off.test.ts).
    • /api/config returned phiAvailable: true from a hardcoded literal. Now derived from the live config.

    Hand-offs

    • compliance/control-matrix.md filled: 3 rows have implementation but no retained evidence (session timeout, audit integrity verification, emergency access).
    • compliance/baa-worksheet.md: 9 services inventoried, 1 unresolved (above).
    • compliance/procedures/ generated from the pack with your organization names.

    Exact command and output

    $ python -I scripts/phi_gate.py compliance/phi-gate.yaml
    GATE FAIL  organization=Acme Health Partners  phi_switch=off  complete=16 waived=1 unmet=2 missing_evidence=1
    
      recovery           unmet (status 'incomplete')
      baa_subprocessors  unmet (status 'incomplete')
      access_review      placeholder evidence 'done'
      sign_offs          platform_security_official sign-off missing (needs identity and date)
    
    4 finding(s). PHI must stay off.
    

    Next: run the restore drill from reference/backup-restore-runbook.md, resolve the error-tracking BAA, record the access review, then have your security official sign. Re-run the gate; only an exit of 0 authorizes the controlled change that sets PHI_ENABLED.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    A web app that is about to hold protected health information usually has decent technical controls and no proof that anyone checked them: a spreadsheet of "done" ticks filled by one admin, a feature flag somebody flips in production, a vendor security page offered as evidence. This skill makes the go-live decision mechanical and attributable.

    What your agent does with it

    1. Finds or implements a default-off PHI switch in configuration (server-level switch plus per-organization activation, PHI writes rejected while off, a test that proves the default).
    2. Walks twenty readiness controls across governance and contracts, identity and access, data protection, operations and privacy, and attestation. Each control needs a stable, non-secret evidence reference (a ticket id, a versioned document path), an owner and a review date. "Yes", "done" and screenshots are rejected.
    3. Fills a HIPAA Security Rule control matrix that cites HHS guidance and NIST SP 800-66r2, and a Business Associate readiness worksheet covering every subprocessor that can touch ePHI.
    4. Generates a procedure pack from placeholders and hands the organization an incident-response runbook (the breach decision stays with humans, never automated) and a backup-and-restore drill runbook.
    5. Runs scripts/phi_gate.py (Python, standard library, offline). It exits non-zero until every control is complete with valid evidence inside the review window and two different people, one customer-side and one platform-side, have signed. A PHI switch that is already on while the gate fails is reported as a critical finding.

    What you get

    • SKILL.md with the full procedure, gate rules and report format
    • scripts/phi_gate.py plus a checklist template and a passing sample
    • reference/readiness-controls.md, control-matrix.md, baa-readiness-worksheet.md, phi-activation-checklist.md, phi-switch-patterns.md, procedure-pack.md, incident-response-runbook.md, backup-restore-runbook.md

    What it is not

    It checks that controls are claimed with evidence by named people. It cannot verify the evidence is true or that a BAA is enforceable. It does not cover state health-privacy laws, 42 CFR Part 2 or non-US regimes. This is engineering guidance, not legal advice or a certification.

    Checks that controls are claimed with evidence; cannot verify evidence truth. Bundled runbooks assume a single-database web service. Script detects secrets but cannot recognize PHI in text.

    How to use

    1. 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. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 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 19 days ago

    Requires

    Python 3.8+

    Permissions

    Environment Variables
    Listed19 days ago

    What's inside

    Frequently Asked Questions

    This skill provides a fail-closed technical gate that prevents PHI storage until twenty specific security controls are evidenced and signed off, transforming subjective compliance into a mechanical engineering requirement.

    The purchase includes a standalone Python-based gate script, a YAML checklist template for tracking evidence, and professional documentation templates for NIST-mapped control matrices and BAA worksheets.

    The included gate script is compatible with any environment running Python 3.8+ and does not require external libraries, making it easy to integrate into CI/CD pipelines or local developer workflows.

    No, the script is designed for "non-secret evidence references" (such as file paths or ticket IDs); it purposefully scans for and rejects secret-shaped values to ensure your compliance documentation doesn't become a security risk.

    While the skill provides the technical framework for HIPAA readiness, it does not provide legal advice or formal certification; it is designed to prepare your infrastructure for the technical requirements of the HIPAA Security Rule.

    This skill is agent-agnostic and functions as a structured workflow that can be executed by any AI agent capable of file manipulation and running Python scripts.

    New in Legal & Compliance