Triage patient messages and care-team tasks by urgency, patient context, owner, and follow-up timing. The screen connects Inbox and Assigned so care teams can find the “Send reply” action while checking open and urgent.
Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Ava Carter · medication question and Marcus Lee · lab follow-up, rather than an empty visual shell.

Inbox
Send reply
Inbox
Default, loading, empty, error, permission, success
Adaptable product UI theme
Care teams need a clear “Send reply” action without losing sight of open, urgent and the affected records. Keep the decision and its outcome clear before moving to the next task.
Inbox → Assigned → Send reply → Review outcome
Inbox, Inbox, Assigned, Patients, accessible states, contextual actions
Keep the active record close to its history, owner and status. Make urgent items easy to find without hiding the rest.
In this design, people should be able to compare Ava Carter · medication question with Marcus Lee · lab follow-up. Make open clear, then use urgent to explain whether the next step needs attention.
Before handing this to a designer or engineer, check keyboard focus, error copy, permissions and what happens after they choose the “Send reply” action. The happy path alone is not enough.
Related UI examples: Care Plan, Provider Roster, Patient Scheduling.
Design a clinical inbox screen for our existing software product. Use our real design-system tokens, components and product language. Show Inbox and Assigned, include believable records such as Ava Carter · medication question, and make send reply easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.