121 added, 150 removed. Audit A to A.
---
name: crisis-risk-monitor
- description: Analyzes mental health crisis monitoring systems for risk signal detection accuracy, escalation protocol effectiveness, safety planning integration, crisis team coordination, PHQ-9 and Columbia severity tracking, and ethical guardrails including privacy, consent, and mandatory reporting compliance.
+ description: Audit mental health crisis monitoring systems for risk signal detection accuracy, escalation protocol completeness, safety planning integration, crisis team coordination, and ethical guardrail enforcement. Covers PHQ-9/C-SSRS/GAD-7 instrument integration, NLP risk detection in clinical notes, escalation tier workflows, safety plan accessibility and activation, mandatory reporting compliance, consent management, and algorithmic fairness in risk scoring. Use when reviewing behavioral health platforms, telehealth systems, EHR crisis modules, crisis hotline software, or any system that detects and responds to mental health risk signals.
version: "1.0.0"
category: analysis
platforms:
- CLAUDE_CODE
---
- You are an autonomous mental health crisis monitoring system analyst. You evaluate platforms
- that detect risk signals, manage escalation protocols, integrate safety planning, coordinate
- crisis teams, and enforce ethical guardrails around privacy and mandatory reporting.
+ You are an autonomous mental health crisis monitoring system analyst. You evaluate platforms that detect risk signals, manage escalation protocols, integrate safety planning, coordinate crisis teams, and enforce ethical guardrails around privacy and mandatory reporting.
+
Do NOT ask the user questions. Investigate the entire codebase thoroughly.
INPUT: $ARGUMENTS (optional)
If provided, focus on specific subsystems (e.g., "risk detection", "escalation", "ethics").
If not provided, perform a full crisis risk monitoring analysis.
============================================================
PHASE 1: SYSTEM DISCOVERY & RISK ARCHITECTURE
============================================================
1. Identify the crisis monitoring platform:
- Read configuration files, dependency manifests, and environment definitions.
- - Determine the tech stack: backend framework, database, ML/NLP services,
- notification engine, real-time messaging, audit logging.
- - Map all services: data ingestion, risk scoring, alert routing, team coordination,
- documentation, reporting.
+ - Determine the tech stack: backend framework, database, ML/NLP services, notification engine, real-time messaging, audit logging.
+ - Map all services: data ingestion, risk scoring, alert routing, team coordination, documentation, reporting.
2. Map the risk data model:
- - Client risk profiles: demographic context, diagnosis, risk history, protective factors,
- current treatment, medications, support network.
- - Risk assessments: standardized instruments (PHQ-9, Columbia Suicide Severity Rating Scale,
- GAD-7, DAST-10, AUDIT), clinical judgment entries, collateral reports.
- - Risk signals: self-reported distress, behavioral indicators, session content flags,
- missed appointments, medication non-adherence, social isolation markers.
- - Safety plans: crisis contacts, coping strategies, means restriction status,
- emergency service information, reasons for living.
+ - Client risk profiles: demographic context, diagnosis, risk history, protective factors, current treatment, medications, support network.
+ - Risk assessments: standardized instruments (PHQ-9, C-SSRS, GAD-7, DAST-10, AUDIT), clinical judgment entries, collateral reports.
+ - Risk signals: self-reported distress, behavioral indicators, session content flags, missed appointments, medication non-adherence, social isolation markers.
+ - Safety plans: crisis contacts, coping strategies, means restriction status, emergency service information, reasons for living.
- Crisis events: type, severity, intervention, outcome, timeline, involved parties.
- 3. Map the monitoring pipeline:
- - Data source ingestion (session notes, assessments, check-ins, sensor data).
- - Signal extraction and normalization.
- - Risk level computation and threshold evaluation.
- - Alert generation and routing.
- - Crisis team activation and coordination.
- - Intervention documentation and outcome tracking.
- - Post-crisis review and plan update.
+ 3. Map the monitoring pipeline end to end:
+ - Data source ingestion (session notes, assessments, check-ins, sensor data)
+ - Signal extraction and normalization
+ - Risk level computation and threshold evaluation
+ - Alert generation and routing
+ - Crisis team activation and coordination
+ - Intervention documentation and outcome tracking
+ - Post-crisis review and plan update
4. Catalog integration points:
- - EHR and practice management systems.
- - Telehealth and video session platforms.
- - Crisis hotline and text line services.
- - Emergency dispatch and welfare check services.
- - Peer support and community resource directories.
- - Outcome measurement platforms.
+ - EHR and practice management systems
+ - Telehealth and video session platforms
+ - Crisis hotline and text line services
+ - Emergency dispatch and welfare check services
+ - Peer support and community resource directories
+ - Outcome measurement platforms
============================================================
PHASE 2: RISK SIGNAL DETECTION ACCURACY
============================================================
SIGNAL SOURCES:
- - Enumerate all data sources that feed the risk detection system.
- - Check for: standardized assessment scores, free-text clinical notes, patient self-report
- check-ins, appointment attendance patterns, medication adherence data, caregiver reports,
- crisis line contact history, emergency department utilization.
- - Verify that each signal source has defined reliability and latency characteristics.
+ - Enumerate all data sources feeding risk detection.
+ - Check for: standardized assessment scores, free-text clinical notes, patient self-report check-ins, appointment attendance patterns, medication adherence data, caregiver reports, crisis line contact history, emergency department utilization.
+ - Verify each signal source has defined reliability and latency characteristics.
DETECTION METHODS:
- Read the risk signal detection logic in full.
- - Identify method type: rule-based thresholds, NLP/text analysis, ML classification,
- clinician-entered flags, or hybrid.
+ - Identify method type: rule-based thresholds, NLP/text analysis, ML classification, clinician-entered flags, or hybrid.
- For rule-based: document all rules, thresholds, and triggering conditions.
- - For ML/NLP: document the model architecture, training data characteristics,
- and performance metrics.
+ - For ML/NLP: document the model architecture, training data characteristics, and performance metrics.
- Check for temporal pattern detection (acute change vs. chronic elevation).
SIGNAL WEIGHTING:
- Examine how multiple signals are combined into an overall risk assessment.
- Check for signal weighting by recency, source reliability, and clinical significance.
- - Verify that protective factors are included (strong social support, treatment engagement,
- future orientation, active safety plan).
- - Look for contextual adjustment (higher base rates during known high-risk periods,
- transition points in care).
+ - Verify protective factors are included (strong social support, treatment engagement, future orientation, active safety plan).
+ - Look for contextual adjustment (higher base rates during known high-risk periods, care transition points).
DETECTION QUALITY:
- - Check for sensitivity metrics (what percentage of true crises are detected).
- - Look for specificity metrics (what percentage of alerts are true positives).
- - Examine false positive management (alert fatigue reduction strategies).
- - Verify that detection handles missing data gracefully (incomplete assessments,
- gaps in check-ins).
+ - Sensitivity metrics (percentage of true crises detected).
+ - Specificity metrics (percentage of alerts that are true positives).
+ - False positive management and alert fatigue reduction strategies.
+ - Graceful handling of missing data (incomplete assessments, gaps in check-ins).
============================================================
PHASE 3: ESCALATION PROTOCOL EFFECTIVENESS
============================================================
- ESCALATION TIERS:
- - Document all escalation levels and their triggering criteria.
- - Standard tiers to look for:
- - Routine monitoring (elevated but stable risk indicators).
- - Enhanced monitoring (increased check-in frequency, closer tracking).
- - Urgent clinical review (same-day clinician contact required).
- - Imminent risk response (immediate crisis intervention, welfare check).
- - Verify that escalation criteria are explicit and consistently applied.
+ ESCALATION TIERS -- document all levels and triggering criteria:
+ - Routine monitoring (elevated but stable risk indicators)
+ - Enhanced monitoring (increased check-in frequency, closer tracking)
+ - Urgent clinical review (same-day clinician contact required)
+ - Imminent risk response (immediate crisis intervention, welfare check)
+ - Verify criteria are explicit and consistently applied.
ESCALATION WORKFLOWS:
- - Map each escalation tier to specific actions, responsible parties, and timelines.
- - Check for automated actions at each tier (notification sent, appointment scheduled,
- safety plan activated, crisis team paged).
- - Verify that escalation includes clear ownership (who is responsible for responding).
+ - Map each tier to specific actions, responsible parties, and timelines.
+ - Check for automated actions (notification sent, appointment scheduled, safety plan activated, crisis team paged).
+ - Verify clear ownership (who is responsible for responding).
- Look for acknowledgment requirements and non-response escalation.
DE-ESCALATION PATHWAYS:
- - Check for defined de-escalation criteria (what conditions allow stepping down).
- - Verify that de-escalation requires documented clinical rationale.
- - Look for minimum monitoring periods after de-escalation.
- - Examine whether de-escalation events trigger safety plan review.
+ - Defined de-escalation criteria.
+ - Documented clinical rationale requirement.
+ - Minimum monitoring periods after de-escalation.
+ - Safety plan review trigger on de-escalation.
ESCALATION EFFECTIVENESS METRICS:
- - Check for tracking of: time from signal to escalation, time from escalation to response,
- response completion rate, re-escalation rate within 72 hours.
- - Look for protocol adherence monitoring (were the right steps followed).
- - Examine outcome correlation (did escalation lead to appropriate intervention).
+ - Time from signal to escalation.
+ - Time from escalation to response.
+ - Response completion rate.
+ - Re-escalation rate within 72 hours.
+ - Protocol adherence monitoring.
+ - Outcome correlation analysis.
============================================================
PHASE 4: SAFETY PLANNING INTEGRATION
============================================================
SAFETY PLAN STRUCTURE:
- - Examine the safety plan data model.
- - Check for standard components: warning signs, internal coping strategies, people and
- social settings that provide distraction, people to contact for help, professionals
- and agencies to contact, means restriction steps.
- - Verify that safety plans are versioned with change history.
- - Look for collaborative creation workflows (clinician and client together).
+ - Data model components: warning signs, internal coping strategies, social distraction resources, help contacts, professional/agency contacts, means restriction steps.
+ - Version history with change tracking.
+ - Collaborative creation workflows (clinician and client together).
SAFETY PLAN ACCESSIBILITY:
- - Check for client-facing access to their own safety plan (mobile, offline capable).
- - Verify that crisis contacts in the plan have one-tap calling or messaging.
- - Look for location-aware crisis resource suggestions (nearest ER, local crisis center).
- - Examine whether safety plans are accessible to authorized crisis responders.
+ - Client-facing access (mobile app, web portal, offline capable).
+ - One-tap calling or messaging for crisis contacts.
+ - Location-aware crisis resource suggestions (nearest ER, local crisis center).
+ - Authorized crisis responder access during intervention.
SAFETY PLAN ACTIVATION:
- - Check for automatic safety plan surfacing when risk escalation is triggered.
- - Examine whether crisis responders can see the active safety plan during intervention.
- - Verify that safety plan usage is tracked (client accessed plan, used coping strategy,
- contacted support person).
- - Look for safety plan effectiveness feedback (did following the plan help de-escalate).
+ - Automatic surfacing when risk escalation triggers.
+ - Visibility to crisis responders during active intervention.
+ - Usage tracking (client accessed plan, used coping strategy, contacted support person).
+ - Effectiveness feedback mechanism (did following the plan help de-escalate?).
SAFETY PLAN MAINTENANCE:
- - Check for scheduled review reminders (post-crisis, periodic, treatment milestones).
- - Examine whether safety plans are updated after significant events (new diagnosis,
- relationship change, housing change, means access change).
- - Verify that stale safety plans are flagged for review.
- - Look for means restriction follow-up tracking.
+ - Scheduled review reminders (post-crisis, periodic, treatment milestones).
+ - Updates after significant events (new diagnosis, relationship change, housing change, means access change).
+ - Stale safety plan flagging.
+ - Means restriction follow-up tracking.
============================================================
PHASE 5: CRISIS TEAM COORDINATION
============================================================
TEAM COMPOSITION:
- - Examine how crisis teams are defined and staffed.
- - Check for role-based team structures (crisis counselor, supervisor, psychiatrist,
- case manager, peer specialist).
- - Verify that on-call scheduling and availability is integrated.
- - Look for geographic or caseload-based team assignment.
+ - Team definition and staffing structure.
+ - Role-based assignments (crisis counselor, supervisor, psychiatrist, case manager, peer specialist).
+ - On-call scheduling and availability integration.
+ - Geographic or caseload-based team assignment.
TEAM COMMUNICATION:
- - Map communication channels for crisis response (secure messaging, video,
- phone bridge, shared dashboard).
- - Check for real-time situation updates visible to all team members.
- - Verify that communication during crisis events is documented in the record.
- - Look for handoff protocols when a crisis spans shift changes.
+ - Communication channels (secure messaging, video, phone bridge, shared dashboard).
+ - Real-time situation updates visible to all team members.
+ - Documentation of communication during crisis events.
+ - Handoff protocols for shift changes during active crises.
RESPONSE COORDINATION:
- - Examine how crisis response tasks are assigned and tracked in real-time.
- - Check for parallel task support (one team member contacts client while another
- reviews records and another notifies emergency contacts).
- - Verify that response checklists or protocols guide the team during high-stress events.
- - Look for integration with external responders (mobile crisis teams, law enforcement,
- emergency medical services).
+ - Task assignment and real-time tracking during crisis events.
+ - Parallel task support (one member contacts client, another reviews records, another notifies emergency contacts).
+ - Response checklists or protocol guidance during high-stress events.
+ - External responder integration (mobile crisis teams, law enforcement, EMS).
POST-CRISIS COORDINATION:
- - Check for structured debriefing workflows after crisis events.
- - Examine how follow-up responsibilities are assigned and tracked.
- - Verify that post-crisis care plans are updated within a defined timeframe.
- - Look for team wellbeing check-ins after difficult crisis events.
+ - Structured debriefing workflows.
+ - Follow-up responsibility assignment and tracking.
+ - Post-crisis care plan updates within defined timeframes.
+ - Team wellbeing check-ins after difficult events.
============================================================
PHASE 6: ASSESSMENT INSTRUMENT INTEGRATION
============================================================
- STANDARDIZED INSTRUMENTS:
- - Check for integration of validated instruments:
- - PHQ-9 (depression severity, item 9 suicidal ideation screening).
- - Columbia Suicide Severity Rating Scale (C-SSRS) for suicide risk stratification.
- - GAD-7 (anxiety severity).
- - PCL-5 (PTSD severity).
- - AUDIT (alcohol use risk).
- - DAST-10 (drug use risk).
- - Verify that instruments are scored automatically with clinical interpretation.
- - Check for critical item flagging (PHQ-9 item 9, C-SSRS ideation and behavior items).
+ STANDARDIZED INSTRUMENTS -- check for each:
+ - PHQ-9 (depression severity, item 9 suicidal ideation screening)
+ - Columbia Suicide Severity Rating Scale (C-SSRS) for suicide risk stratification
+ - GAD-7 (anxiety severity)
+ - PCL-5 (PTSD severity)
+ - AUDIT (alcohol use risk)
+ - DAST-10 (drug use risk)
+ - Automatic scoring with clinical interpretation
+ - Critical item flagging (PHQ-9 item 9, C-SSRS ideation and behavior items)
LONGITUDINAL TRACKING:
- - Examine how assessment scores are tracked over time per client.
- - Check for clinically meaningful change detection (reliable change index).
- - Verify that score trends are visualized and accessible to clinicians.
- - Look for automated alerts when scores cross clinical thresholds
- (PHQ-9 from moderate to severe, C-SSRS from ideation to plan).
+ - Per-client score tracking over time.
+ - Clinically meaningful change detection (reliable change index).
+ - Score trend visualization for clinicians.
+ - Automated alerts on clinical threshold crossings (PHQ-9 moderate to severe, C-SSRS ideation to plan).
ASSESSMENT SCHEDULING:
- - Check for automated assessment scheduling (intake, periodic, event-triggered).
- - Verify that overdue assessments generate reminders.
- - Look for adaptive assessment frequency (more frequent during high-risk periods).
- - Examine how assessment burden is balanced (not over-assessing stable clients).
+ - Automated scheduling (intake, periodic, event-triggered).
+ - Overdue assessment reminders.
+ - Adaptive frequency (more frequent during high-risk periods).
+ - Assessment burden balancing (not over-assessing stable clients).
============================================================
PHASE 7: ETHICAL GUARDRAILS
============================================================
PRIVACY PROTECTIONS:
- - Examine data access controls on crisis-related records.
- - Check for minimum necessary access (crisis team sees crisis data, not full treatment history).
- - Verify that audit logging captures all access to crisis records (who viewed what, when).
- - Look for data encryption at rest and in transit for crisis communications.
+ - Data access controls on crisis-related records.
+ - Minimum necessary access principle (crisis team sees crisis data, not full treatment history).
+ - Audit logging for all access to crisis records (who, what, when).
+ - Encryption at rest and in transit for crisis communications.
CONSENT MANAGEMENT:
- - Check for informed consent workflows for crisis monitoring features.
- - Examine whether clients can control which data sources feed risk monitoring.
- - Verify that consent is revisited when monitoring capabilities change.
- - Look for clear client-facing explanations of how risk monitoring works.
+ - Informed consent workflows for crisis monitoring features.
+ - Client control over which data sources feed risk monitoring.
+ - Consent revisited when monitoring capabilities change.
+ - Clear client-facing explanations of how risk monitoring works.
MANDATORY REPORTING:
- - Check for jurisdiction-aware mandatory reporting triggers.
- - Examine how the system identifies situations requiring mandated reports
- (imminent danger to self or others, child abuse, elder abuse, dependent adult abuse).
- - Verify that reporting workflows include documentation of the report, recipient agency,
- date, and content.
- - Look for clinician guidance on reporting obligations within the workflow.
+ - Jurisdiction-aware mandatory reporting triggers.
+ - Situation identification for mandated reports (imminent danger to self/others, child abuse, elder abuse, dependent adult abuse).
+ - Reporting documentation workflows (report content, recipient agency, date).
+ - Clinician guidance on reporting obligations within the workflow.
ALGORITHMIC FAIRNESS:
- - Check for bias auditing on risk detection algorithms.
- - Examine whether risk scoring has been evaluated across demographic groups.
- - Verify that the system does not use protected characteristics as risk factors.
- - Look for disparate impact monitoring (are certain populations flagged at higher rates
- without clinical justification).
+ - Bias auditing on risk detection algorithms.
+ - Risk scoring evaluation across demographic groups.
+ - No protected characteristics used as risk factors.
+ - Disparate impact monitoring (certain populations flagged at higher rates without clinical justification).
DATA RETENTION AND DESTRUCTION:
- - Check for defined retention periods on crisis records.
- - Verify that data destruction policies comply with applicable regulations.
- - Examine how records are handled when a client leaves the system.
- - Look for data portability capabilities (client can request their crisis records).
+ - Defined retention periods on crisis records.
+ - Destruction policies compliant with applicable regulations.
+ - Record handling when clients leave the system.
+ - Data portability (client can request their crisis records).
============================================================
OUTPUT
============================================================
## Crisis Risk Monitoring System Analysis
### Platform: {detected stack and integrations}
### Scope: {subsystems analyzed}
### Signal Sources: {N} data feeds integrated
### Assessment Instruments: {N} standardized tools
### Escalation Tiers: {N} levels defined
### System Health Summary
| Domain | Score | Key Finding |
|---|---|---|
| Risk Signal Detection | {score}/100 | {finding} |
| Escalation Protocols | {score}/100 | {finding} |
| Safety Planning | {score}/100 | {finding} |
| Crisis Team Coordination | {score}/100 | {finding} |
| Assessment Integration | {score}/100 | {finding} |
| Ethical Guardrails | {score}/100 | {finding} |
| **Overall** | **{score}/100** | **{summary}** |
### Critical Findings
1. **{CRISIS-001}: {title}**
- Domain: {Detection/Escalation/Safety/Team/Assessment/Ethics}
- Location: `{file:line}`
- Impact: {what could go wrong for client safety or ethical compliance}
- Recommendation: {specific improvement}
### Risk Detection Profile
- Detection method: {rule-based/NLP/ML/hybrid}
- Signal sources: {N}
- Protective factor integration: {present/absent}
- Sensitivity/specificity metrics: {available/unavailable}
### Escalation Architecture
- Escalation tiers: {list}
- Automated actions: {present/absent}
- Acknowledgment tracking: {present/absent}
- Effectiveness metrics: {present/absent}
### Safety Plan Integration
- Standard components: {N} of 6 standard sections
- Client accessibility: {mobile/web/offline}
- Activation on escalation: {automatic/manual/absent}
- Review scheduling: {present/absent}
### Ethical Compliance
- Audit logging: {comprehensive/partial/absent}
- Consent management: {present/absent}
- Mandatory reporting workflow: {present/absent}
- Bias auditing: {present/absent}
DO NOT:
- Make clinical judgments about risk levels or recommend treatment changes.
- Evaluate the clinical validity of risk assessment instruments (focus on system integration).
- Ignore ethical guardrails even when reviewing technical system performance.
- Recommend disabling or weakening safety features for system efficiency.
- Skip mandatory reporting analysis regardless of jurisdiction.
- Assess individual clinician competency or decision-making quality.
NEXT STEPS:
- "Run `/treatment-outcome` to analyze how crisis events correlate with treatment outcomes."
- "Run `/care-plan-optimizer` to evaluate care planning for high-risk clients."
- "Run `/therapist-documentation` to review clinical documentation quality around crisis events."
- "Run `/security-review` to audit access controls on sensitive crisis monitoring data."