Feature

Built

Walk-ins and appointments in one queue.

Token numbers issued at check-in, an arrivals board the front desk watches, and vitals taken wherever your hospital takes them.

All features

An OPD queue system decides who is seen next and tells everybody where they are. Its real job is preventing the two arguments every busy outpatient department has: whether a walk-in jumped the queue, and where a patient has got to.

What is built

Check-in, tokens, the board, and the vitals step in between.

  • One queue holding walk-ins and booked appointments together
  • A token number issued per branch, per day, at check-in
  • An arrivals board filtered by branch, provider, date and status
  • Vitals captured at the point your hospital captures them, configured per hospital
  • Patient self check-in from a QR code, announcing an arrival for the desk to complete
  • The consultation fee raised at check-in and collected at reception
  • A patient who is not there moved back a few places by the desk, with the token unchanged and the move marked
  • Call next, in the order the desk has set
  • A full-screen queue board for a screen at the desk or a TV run from a desk computer

What is scheduled

A screen that runs on its own, and telling the patient where they are.

  • A public display for a waiting-room screen, with no sign-in and no names(planned)
  • Queue position notifications to the patient(planned)
  • A cashier shift close(planned)

How it runs

  1. 01

    Arrive

    A walk-in is registered, or a booked patient is checked in. Either way they join one queue.

  2. 02

    Token

    A token number is issued for the branch and the day.

  3. 03

    Vitals

    Recorded where your hospital records them: at the desk, in a vitals room, or by the doctor.

  4. 04

    Consult

    The doctor takes the next patient from the queue; the chart is already open on the right visit.

What this does not do

The queue board is a Portal page for staff: it runs full screen on a screen at the desk, or on a TV connected to a desk computer that someone is signed in to and using, and it shortens names to a first name and initial. A display computer left on its own signs out, which is the security rule doing its job. A public token display that runs by itself is a different thing, an unauthenticated, PHI-free surface with its own trust boundary, which is why it is scheduled as its own piece of work rather than a variation of the staff screen. There are no spoken announcements, and patients are not notified of their queue position, because that needs the messaging channel that is not live yet.

Questions we are asked

Can we show a token display in the waiting room?

From a desk computer, yes: the queue board runs full screen on a TV connected to a computer that staff are signed in to and using, and shows first names and initials, or tokens only. A display that runs on its own, with no sign-in, is scheduled as its own module because it has to be designed as one: no patient names, no clinical data, and its own trust boundary.

What happens when a called patient is not there?

The desk moves them back a few places, or wherever it chooses. They keep their token number, the move is marked on every screen with who made it, and Call next follows the new order.

Do walk-ins and appointments share a queue?

Yes, deliberately. Two queues is how a clinic ends up arguing about who jumped.

Who takes the vitals?

Whoever your hospital says. It is configuration rather than a fixed workflow, so a clinic where the doctor takes them and a hospital with a vitals room are both expressible.

Is the consultation fee collected before or after the consultation?

Your choice, configured per hospital. Reception collects the bill that check-in raised, and when that fee is due is a setting rather than an assumption.

See it running with your own workflows.

Book a walkthrough and we will map your clinic or hospital onto the platform, module by module.