Secure & Govern · Prompt
Structure the required HIPAA risk analysis from the client's ControlMap data.
Needs an LLM client connected to ScalePad MCP — Claude Desktop, Cursor, Windsurf or similar. Without it the assistant cannot call the recipe's tools.
Prepare a HIPAA security risk analysis for [CLIENT NAME] using ControlMap. Organize it as: 1. Scope: where ePHI is created, received, stored and sent 2. Threats and vulnerabilities for each system 3. Current safeguards (administrative, physical, technical) with their evidence 4. Likelihood, impact and risk level for each 5. A prioritized risk management plan Use only real ControlMap data, mark anything I need to confirm, and note that a qualified person should review it before it's finalized. Read-only. How to work with the ControlMap API (ScalePad MCP): - Find the client with GET /controlmap/v1/clients/health and use its tenant ID (for example "dundmif") in every request. Some clients have no UUID. - Send the header Content-Type: application/json on every POST, PUT and PATCH, including searches. - Use page_size of 50 or less and follow next_cursor. The "fields" parameter is ignored, so responses are large. - Judge controls by "status", not the "compliant" flag. Objective lists include sub-objectives, so take totals from objective_summary. - Use framework-level scores and labels. The overall score_label on client health can be wrong. - Older policy sections may be URL-encoded twice: decode them and use the highest version of each section. - If a call returns 502 or fails to connect, wait a few seconds and retry once. If it still fails, tell me exactly which data is missing.
# HIPAA security risk analysis
Hook: Structure the required HIPAA risk analysis from the client's ControlMap data.
Annually, or after a major change to systems handling ePHI.
A risk analysis document organized the way HHS expects.
Tested against the ControlMap API on October 16, 2026. Only asks for what the API supports.
