run-compliance-review — Claude Code command: HIPAA/FDA/FTC review
run-compliance-review — a Claude Code command that runs a regulatory compliance review for healthcare marketing campaigns against HIPAA, FDA, and FTC rules. Covers email, landing, paid, webinar, field, and events channels.
Apache-2.0 ★ 450 updated 2026-04-03
.claude/commands/run-compliance-review.mdWhat run-compliance-review does
The command takes a campaign identifier, a comma-separated list of channels, a risk level (low, moderate, or high), and optionally a file with clinical claims and an audience type (providers, payers, patients, or mixed). Risk level determines the approval path and SLA.
Execution follows five steps: pulling campaign context and data flows, running a regulatory checklist across HIPAA, FDA, FTC, and regional privacy rules, flagging unsupported claims or consent gaps, routing to reviewers — legal, medical, privacy — with tasks and due dates, then logging decisions and expiration dates to a compliance archive. Output is a compliance memo, a reviewer task list, and an audit-ready packet with annotated assets.
The command calls two skills — compliance-briefing-kit and regulatory-review-checklist — and two sub-agents: compliance-marketing-director and clinical-campaign-strategist. All four components must be present from the gtmagents/gtm-agents repository for the full workflow to run.
What it helps with
- check healthcare marketing materials against HIPAA, FDA, and FTC requirements
- surface unsupported clinical claims before a campaign goes live
- route a review to legal, medical, and privacy stakeholders with due dates
- produce an audit-ready packet with annotated assets and approval history
- apply different approval paths depending on campaign risk level
Example prompts for the agent
- Run a compliance review for a cardiology webinar over email and landing pages at moderate risk:
/healthcare-marketing:run-compliance-review --campaign "Cardio Webinar" --channels email,landing --risk-level moderate - Review a paid campaign targeting patients at high risk and attach a claims file:
/healthcare-marketing:run-compliance-review --campaign "DiabetesCare Q3" --channels paid --risk-level high --claims claims.pdf --audience patients - Check a webinar campaign for providers at low risk level:
/healthcare-marketing:run-compliance-review --campaign "Oncology Webinar" --channels webinar --risk-level low --audience providers
How to install run-compliance-review
Manually: put the files in place
.claude/commands/run-compliance-review.mdCall it with /run-compliance-review. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/run-compliance-review.mdCall it with /prompts:run-compliance-review. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/run-compliance-review.prompt.mdManually: put the files in place
.gemini/commands/run-compliance-review.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about run-compliance-review
How do I install run-compliance-review in Claude Code?
Place the command file at .claude/commands/run-compliance-review.md inside your project. Claude Code will pick it up automatically.
What does the run-compliance-review command do?
It runs a five-step compliance workflow for healthcare marketing: gathers campaign context, evaluates it against HIPAA/FDA/FTC rules, flags gaps, routes tasks to reviewers, and packages everything for audit.
Which components does run-compliance-review depend on?
It calls the compliance-briefing-kit and regulatory-review-checklist skills, plus the compliance-marketing-director and clinical-campaign-strategist sub-agents — all from the gtmagents/gtm-agents repository.
Source text
run-compliance-review.md · Apache-2.0
--- name: run-compliance-review description: Executes HIPAA/FDA/FTC compliance review for healthcare marketing campaigns. usage: /healthcare-marketing:run-compliance-review --campaign "Cardio Webinar" --channels email,landing --risk-level moderate --- # Command: run-compliance-review ## Inputs - **campaign** – campaign/program identifier or brief ID. - **channels** – comma-separated list (email, landing, paid, webinar, field, events). - **risk-level** – low | moderate | high; influences approval path and SLA. - **claims** – optional file/URL to clinical claims or messaging hierarchy. - **audience** – providers | payers | patients | mixed. ## Workflow 1. **Brief Intake** – pull campaign context, creative, data flows, and offer details. 2. **Regulatory Checklist** – evaluate HIPAA, FDA, FTC, regional privacy rules per channel. 3. **Gap Analysis** – flag unsupported claims, consent gaps, or escalation requirements. 4. **Approval Routing** – generate reviewer list (legal, medical, privacy) with tasks + due dates. 5. **Documentation** – log decisions, conditions, and expiration dates in compliance archive. ## Outputs - Compliance memo summarizing risks, mitigations, and approvals needed. - Reviewer task list with due dates and supporting materials. - Audit-ready packet (evidence, annotated assets, approval history). ## Agent/Skill Invocations - `compliance-marketing-director` – leads assessment + escalation. - `clinical-campaign-strategist` – validates claims vs supporting evidence. - `compliance-briefing-kit` skill – enforces checklist + output format. - `regulatory-review-checklist` skill – ensures routing rules and documentation completeness. ---
© gtmagents · Apache-2.0 · gtmagents/gtm-agents