Healthcare

Queue management in hospitals and clinics

Run registration desks, department queues and call displays in a single flow. Appointment holders are prioritised, walk-in patients take a ticket at the kiosk, and waiting time is measured per department.

What changes in this sector

Patient flow becomes measurable

Appointments and tickets in one flow

Appointment holders are pulled forward when called, while walk-in patients take a ticket at the kiosk. The two lists are not managed separately.

Department-level queues

Each clinic carries its own queue, and the call display guides patients with the department name and ticket number. Density is tracked per department.

Waiting-time reporting

Ticket, call and completion timestamps are recorded, so average wait, service time and abandonment rate are reported per department.

Typical flow

Four steps from registration to report

Registration / kiosk

The patient picks a department at the kiosk or registers at the desk; appointments are matched.

Department queue

The ticket joins that clinic's queue and priority rules are applied.

Call

The physician or nurse calls from the terminal; number and department appear on screen.

Report

The visit ends and wait and service times are reflected in the report immediately.

Recommended hardware

A light device set per department

Kiosk — registration and department selection
Call display (LCD or LED) — department and number
Counter terminal — calling and completing visits
Ding dong — audible alert over network or RS-485 (optional)

Devices communicate over the network (TCP/IP) and Wi-Fi, as described in the hardware section; the audible alert unit can also use RS-485.

Frequently asked

Common questions in healthcare

Do appointment holders and walk-ins wait in the same queue?

They run in the same flow but not the same position: appointment holders are called according to a defined priority rule, while walk-ins move in ticket order.

Does it integrate with our hospital information system?

Yes. The system exposes an integrated RESTful API, and patient and department definitions can be synchronised with your user database.

Where is the data stored?

Deployment is on-premise; queue data stays on your own server and is not sent outside.

Can multiple buildings or campuses be managed?

With the central edition each building is defined as a separate branch, so you get per-building reports while monitoring the whole estate from one panel.

Let's plan your scenario together

We will determine the right edition and hardware together, based on your branch count and integration needs.

Request a Demo