# Service-Queues: Clinic Administrator screen — design for feedback

**URL:** <https://talk.openmrs.org/t/service-queues-clinic-administrator-screen-design-for-feedback/49862>\
**Category:** Development\
**Tags:** openmrs, developers-forum, design-forum, o3\
**Created:** [July 30, 2026, 1:25pm UTC](https://talk.openmrs.org/t/service-queues-clinic-administrator-screen-design-for-feedback/49862 "2026-07-30T13:25:21Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ujjawalprabhat](https://talk.openmrs.org/letter_avatar/ujjawalprabhat/32/5_5575768a8748004e209b776fc1b2916d.png) [@ujjawalprabhat](https://talk.openmrs.org/u/ujjawalprabhat)\
**Post date:** [July 30, 2026, 1:25pm UTC](https://talk.openmrs.org/t/service-queues-clinic-administrator-screen-design-for-feedback/49862/1 "2026-07-30T13:25:21Z")

</div>

## Context

Queue workflows are split between two audiences that currently share one screen. Clinic administrators need to monitor **any** queue in a clinic; normal queue users sit in a **single** queue location watching one or more services. Today `/home/service-queues` only serves the second group, so an administrator asking “which queue is backing up?” changes dropdowns one combination at a time and holds the comparison in their head.

[O3-5770](https://openmrs.atlassian.net/browse/O3-5770) asks for a dedicated monitoring screen, styled like the bed-management / billing-administration screens, shown in place of the normal view when the user holds `App: Service Queues Clinic Administrator`.

**Mockup:**

 ![image](https://talk.openmrs.org/uploads/default/original/3X/7/a/7a9b167eea85ab14afbfe46f989543edc92a49f2.jpeg) ![image](https://talk.openmrs.org/uploads/default/original/3X/0/f/0f3ff5e34e2394a634c86c2cfa2413fa0c4680b5.jpeg) ![image](https://talk.openmrs.org/uploads/default/original/3X/4/5/4549d6a060dc4ee32e60732e20a3ee2f7e6e54c5.png)

## The design

Same URL, `/home/service-queues`, privilege-swapped. Top to bottom:

1. **Clinic at a glance** — a flat strip: Waiting · Attending · Avg. wait · Longest wait · Appointments today.
2. **Queues** — one row per queue: Queue · Location · Service · Waiting · Attending · Avg. wait · Longest wait, sorted by longest wait descending, with a totals row. Each row drills into that queue.
3. **Tabbed patient list** — All patients / Waiting / Attending / Expected appointments, clinic-wide, with Queue, Location and Status columns.

Drilling into a queue lands on the **existing** per-queue screen, unchanged, so the row actions (call, transition, move, edit, remove) already work.

## Things that may not be obvious

- **The default tab is All patients, not Waiting.** Per the brief, an administrator should see every status while a clerk or clinician sees waiting. So, the privilege drives the default and not just the screen choice.
- **A patient’s name links to Edit patient, not the chart** , since the administrator privilege is not the clinician one.
- **The alert styling is borrowed from the patient chart’s vitals strip** — a tinted fill and coloured border on the out-of-range value. A backed-up clinic reads the same way an abnormal temperature does, rather than introducing new vocabulary.

I’d appreciate any feedback you may have.

CC: @ibacher @veronica @nethmi @dennis @chibongho

---

<div class="post-metadata">

**Author:** ![veronica](https://talk.openmrs.org/user_avatar/talk.openmrs.org/veronica/32/20174_2.png) [@veronica](https://talk.openmrs.org/u/veronica)\
**Post date:** [August 3, 2026, 7:04am UTC](https://talk.openmrs.org/t/service-queues-clinic-administrator-screen-design-for-feedback/49862/2 "2026-08-03T07:04:39Z")

</div>

@ujjawalprabhat Thanks for these mock-ups. Here are my thoughts

1. Consider removing the QUEUES group from the left nav. It also duplicates the Queues table - a facility with thirty would flood the left navigation.

2. I’m worried about performance on the table with patients list - lists across four tabs (all patients, waiting, attending, etc). The busier the facility, the longer these lists are and might be costly in terms of performance. Worth confirming performance with long lists.

3. I’m wondering honestly whether the first table is enough. The administrator isn’t managing the queue - they’re watching for where it’s going wrong. The row-level actions in the patients list table belong to the team that sees the patients, not to the admin. So we may be building and paying for a level of detail that an admin does not need.

Curious to hear what others think.

---

<div class="post-metadata">

**Author:** ![nethmi](https://talk.openmrs.org/user_avatar/talk.openmrs.org/nethmi/32/19734_2.png) [@nethmi](https://talk.openmrs.org/u/nethmi)\
**Post date:** [August 11, 2026, 12:40pm UTC](https://talk.openmrs.org/t/service-queues-clinic-administrator-screen-design-for-feedback/49862/3 "2026-08-11T12:40:54Z")

</div>

@fanderson tagging you in this loop as well to get your thoughts 😃

---

<div class="post-metadata">

**Author:** ![ujjawalprabhat](https://talk.openmrs.org/letter_avatar/ujjawalprabhat/32/5_5575768a8748004e209b776fc1b2916d.png) [@ujjawalprabhat](https://talk.openmrs.org/u/ujjawalprabhat)\
**Post date:** [September 3, 2026, 12:05pm UTC](https://talk.openmrs.org/t/service-queues-clinic-administrator-screen-design-for-feedback/49862/4 "2026-09-03T12:05:02Z")

</div>

PR [here](https://github.com/openmrs/openmrs-esm-patient-management/pull/2681).