Experience Measurement & Feedback Triage Workflow

Welcome

This toolbox helps teams capture patient feedback reliably, route it to the right owner quickly, and close the loop so concerns become improvements instead of complaints. Use the templates and rules below as a starting point — adapt fields, categories, timelines, and owners to match your setting.

Why a triage workflow matters

Untriaged feedback accumulates and erodes trust. A simple, consistent workflow ensures urgent safety issues get immediate attention, routine operational problems are fixed quickly, and learning is captured to prevent recurrence.

High-level workflow

Sample intake form (use as checklist or electronic form)

Purpose: capture consistent, actionable data so triage rules can route feedback automatically when possible.

• Submission ID (auto-generated)
• Date/Time received
• Reporter name (optional) and preferred contact method
• Patient name / MRN (if applicable)
• Location / Unit / Clinic
• Channel (phone, email, portal, in-person, complaint form, social media)
• Brief description (free text)
• Suggested category (auto-suggest from text—see taxonomy below)
• Perceived severity (reporter selects: Safety, Urgent, Routine)
• Related staff or service (name or role)
• Attachments (photos, documents)
• Consent to follow-up (yes/no)

Categorization taxonomy (starter)

Use a small, consistent set of categories so data can be aggregated and trended.

• Type: Clinical care, Communication, Access/Wait time, Environment, Safety event, Medication, Billing/Financial, Staff behavior, Compliment, Suggestion
• Severity: Safety (actual/potential harm), Urgent (needs prompt review), Routine (service/improvement feedback)
• Source: Patient, Family, Visitor, Staff, Vendor

Example rule-based triage (implementable manually or with basic automation)

• If text contains keywords: "fell", "not breathing", "wrong medication", "allergic reaction" → mark as Safety and notify Patient Safety Officer immediately.
• If reporter selects severity "Safety" → immediate escalation regardless of category.
• If category is "Medication" with words like "wrong dose" or "given to wrong patient" → escalate to Pharmacy & Safety team within 1 hour.
• If channel is social media and complaint is public → escalate to Communications and Unit lead within 2 hours.
• All other routine items → assign to Unit Improvement Lead with SLA below.

Escalation triggers and recommended actions

• Safety trigger (actual or likely harm): Immediate phone/secure message to on-call clinician and Patient Safety team. Create incident record and begin local mitigation. Acknowledge reporter within 1 hour if contact info provided.
• Urgent clinical or operational risk: Notify unit manager/clinical lead and Quality within 4 hours. Provide interim mitigation and plan next steps.
• Public or reputation-sensitive feedback: Notify Communications and senior leadership within 2 hours.
• High-impact operational issues (e.g., repeated access failures): Escalate to Operational Improvement team within 24 hours for root-cause review.

Recommended response timelines (SLA examples)

• Safety: Acknowledge within 1 hour; initial mitigation & assignment within 4 hours; full investigation plan within 72 hours.
• Urgent: Acknowledge within 24 hours; assigned owner within 48 hours; resolution or interim plan within 7 days.
• Routine: Acknowledge within 72 hours; assigned owner within 7 days; resolution or improvement plan within 30 days.
• Compliments / praise: Acknowledge and forward to unit/hospital recognition program within 7 days.

Closed-loop reporting template (use as final report or email)

Use clear, empathetic wording and closed-loop language. Record actions taken and measurable outcomes.

Suggested roles & responsibilities

• Intake owner: ensures submissions are logged and assigned within SLA (often Patient Experience or Unit Admin).
• Triage coordinator: applies categorization rules and escalates safety/urgent items (Quality or Patient Safety).
• Improvement owner: unit lead or process owner responsible for investigation and corrective actions.
• Communications: for public/postable items or reputation risk.
• Leadership sponsor: ensures resources for systemic fixes and monitors trends.

KPIs and measurement (track these to ensure the workflow works)

• Percent of submissions acknowledged within SLA
• Time from submission to assignment
• Time from assignment to resolution
• Percent of safety reports escalated within 1 hour
• Repeat complaints by topic/unit (trend monthly)
• Reporter satisfaction with follow-up (simple 3-question survey)

Practical tips for adoption

• Keep categories short and consistent — granularity hurts reporting.
• Make the intake form quick to complete; require only essential fields at first contact.
• Encourage staff to flag suspected safety events directly to the Safety team while still using the feedback form for records.
• Review weekly trends in a short huddle and escalate system issues monthly with data-backed proposals.
• Publicize closed-loop stories to rebuild trust — share what changed because patients spoke up.

Next steps — templates to implement

1) Copy the sample intake fields into an electronic form (patient portal, intranet form, or simple web form). 2) Configure keyword-based alerts for obvious safety words. 3) Assign triage hours and a rotation for the triage coordinator. 4) Start with a 30–60 day pilot on one unit, measure KPIs, then iterate.

Where this toolbox can be extended (capability notes)

Consider using an interactive intake form that saves submissions and drives automated alerts to on-call roles. Captured data can feed dashboards for trend detection and support follow-up analytics. See Capability Enhancement Notes for specific suggestions.