
Complaint Severity Triage & Systemic Issue Analyzer
Triage patient complaints by severity and identify systemic operational issues
What You Can Do
This skill standardizes your complaint triage workflow by analyzing incoming patient feedback against structured severity criteria, automatically identifying whether issues are isolated incidents or systemic patterns affecting multiple patients. You'll generate consistent escalation recommendations (frontline response vs. department review vs. leadership investigation), surface hidden operational problems driving complaints, and create data-driven quality improvement priorities for your leadership team.
Features
Evaluates complaints across clinical impact, safety risk, regulatory exposure, and patient satisfaction dimensions to assign consistent triage levels (routine, elevated, urgent, critical)
Distinguishes between individual staff errors, process failures, resource constraints, and systemic breakdowns to guide proportionate response strategies
Analyzes complaint themes, frequency, and affected departments to surface recurring issues that warrant process redesign or staff retraining
Automatically recommends appropriate response pathways (direct staff resolution, departmental quality review, clinical investigation, legal review, regulatory notification)
Produces concise, structured summaries for quality committees, regulatory bodies, or leadership review with key findings and recommended actions
Ranks complaints by urgency to ensure high-risk cases (safety issues, regulatory exposure) receive immediate attention ahead of lower-risk feedback
Identifies and quantifies patterns across your complaint database to support data-driven operational improvement initiatives
Example Output
Example 1: Isolated vs. Systemic Triage
Input: Three complaints about wait times in the scheduling department over two weeks.
Output:
- Severity Level: Elevated (patient satisfaction impact, no safety risk)
- Root Cause: Temporary staffing shortage during vacation coverage
- Systemic Assessment: Pattern detected—4 similar complaints in past 60 days affecting 8% of scheduled patients
- Recommendation: Escalate to Scheduling Department Head for process review; implement backup coverage protocol
- Response Action: Courtesy callback + service recovery offer
Example 2: Critical Safety Escalation
Input: Complaint about medication discrepancy not caught during discharge.
Output:
- Severity Level: Critical (patient safety risk, regulatory exposure)
- Root Cause: Breakdown in discharge medication verification process
- Systemic Assessment: Isolated incident; no pattern detected in past 90 days
- Recommendation: Immediate clinical investigation + incident report; escalate to Quality/Risk Management
- Response Action: Urgent patient outreach + clinical review + staff retraining on verification protocol
What's Included
- SKILL.md instruction file with triage framework and severity criteria:
- Severity Assessment Rubric: Detailed matrix for rating complaints across clinical, safety, regulatory, and satisfaction dimensions
- Root Cause Analysis Template: Structured worksheet for investigating individual vs. systemic causes
- Escalation Decision Tree: Flowchart mapping severity levels to appropriate response pathways
- Pattern Detection Checklist: Guidance for identifying recurring themes and systemic issues across complaint database
Who It's For
- Patient Experience Officers — Managing complaint intake, triage, and escalation workflows
- Quality Assurance Managers — Identifying systemic issues and driving process improvements from complaint data
- Department Heads — Triaging complaints affecting their units and responding proportionately
- Patient Relations Specialists — Determining appropriate response strategies based on complaint severity
- Risk Management/Compliance Teams — Flagging complaints with regulatory or legal implications
Best For
- Rapid severity assessment of incoming patient complaints (verbal, written, survey feedback)
- Escalation protocol decisions (frontline resolution vs. leadership investigation vs. legal review)
- Root cause analysis to distinguish individual errors from systemic operational failures
- Complaint pattern analysis across departments or time periods to identify improvement priorities
- Complaint summary preparation for quality committees, leadership meetings, or regulatory bodies
- Data-driven quality improvement planning based on complaint themes and systemic issues







