Clinic Triage Inbox
Design a clinical inbox that helps a nursing team prioritize patient messages without hiding uncertainty or urgent escalation.
The brief
Understand the problem
Background
Primary care teams receive refill requests, symptom updates, form questions, and urgent concerns in one queue. Simple chronological sorting can delay important work, while automated urgency labels still need accountable human review.
User context
Nurse Alia starts a morning shift with eighty unread messages shared across three clinicians. She needs to identify time-sensitive symptoms, assign routine work, and avoid duplicate responses.
Product problem
The team needs a safe triage workspace that makes ownership, rationale, patient context, and service targets visible at a glance.
Objective
Design queue overview, message assessment, assignment, and escalation for a multidisciplinary clinic inbox.
What to design
Define the experience
Required experience
- Scan workload by urgency, type, age, and owner
- Open a message with relevant patient context
- Set priority and assign the next action
- Escalate urgent risk and document the handoff
Screens and states
- Triage inbox
- Message workspace
- Assignment panel
- Urgent escalation
Core user flow
Follow the critical path
- 01
Alia opens the unassigned queue and filters for symptom messages
- 02
She reviews one patient's note, recent contacts, and stated red flags
- 03
She assigns a routine callback to a clinician with a due time
- 04
A second message meets the clinic's urgent protocol and she records direct escalation
Product rules
Requirements and constraints
Requirements
- Expose queue age, service target, priority source, and current owner
- Keep original patient wording beside structured triage fields
- Prevent simultaneous responders from duplicating work
- Require rationale and acknowledgement for urgent handoffs
Constraints
- Priority suggestions cannot replace clinical judgment
- Access follows care-team role and patient relationship
- The design must support keyboard-heavy workflows
Reality check
States worth considering
Ready-to-use content
Mock data
Use this content to test hierarchy and realistic data states. You can expand it when the concept needs more depth.
Inbox cases
- Refill request, 18 minutes old, unassigned
- New shortness of breath, 6 minutes old, urgent review
- School form question, 2 hours old, assigned
Queue owners
- Triage nurse
- Primary clinician
- Covering clinician
- Front desk
Finish line
What to deliver
- Four desktop screens plus annotations for concurrency and escalation states
Optional direction
Visual resources
Use these as a starting constraint if you want one. They are not part of the required solution.