Q
Ippokratis QueueFlow prototype · HelloWorld IKE
Interactive walkthrough
01
Patient enters
02
Ticket & QR
03
Patient view
04
Room monitors
05
Run the queue
06
Verify at door
Step 01 — Their system

A patient checks in

Reception works exactly as today. One new action — Add to queue — sends only the agreed fields to our platform. The doctor / room field decides which queue the patient joins, automatically.

Clinic's existing software
patient record · ippokratis
NameMaria Santos
Patient IDIPK-04471
Mobile+63 917 ···· 882
Doctor / RoomDr. Reyes · Room 2
Visit typeWalk-in
The only integration point. Their system pushes a small set of fields to one endpoint of ours. We never read their database — they hand us exactly what we need.
What travels to us
Press Add to queue to see the data that reaches the platform →
name: "Maria Santos",
patient_id: "IPK-04471",
mobile: "+63917····882",
doctor: "Dr. Reyes",
room: "room-2",
visit_type: "walk-in"
POST /api/queue/enqueue
✓ Routed to Room 2 queue · ticket #15 · QR generated
Step 02 — Ticket

A personal ticket and QR

The platform assigns the next number in the Room 2 queue and generates a unique QR tied to this one patient. Printed at reception, shown on screen, or sent as a link.

Hand-out / printed slip

Queue ticket

Room 2 · just now
#15
Maria Santos · Dr. Reyes, Room 2
Scan to follow your place in line
Why a personal QR
Their own live position

Each QR is bound to one ticket, so the patient sees their number and how many are ahead — not a generic board.

No dependence on the monitor

Solves the core problem — patients no longer have to watch a wall screen to know when they're close.

Fully ours, zero external cost

The QR and status page run entirely on our platform — no SMS or messaging fees for this part.

Identity link. Because the QR is bound to ticket #15 and patient IPK-04471, scanning it later confirms the right person is at the door — see step 06.
Step 03 — Patient phone

Following the queue, and getting back in

The patient gets an SMS link at check-in and lands on this live page — also reachable by scanning their QR. SMS carries the key alerts on any phone; the live page and app alerts add to it for free. If they miss their turn, they can request to rejoin from here; staff approve it.

Patient's phone · status page
Ippokratis · Dr. Reyes · Room 2
You are number
#15
6 patients ahead of you
#09
Now serving
~38 min
Est. wait
Auto-updating — no need to refresh
We'll text you as your turn nears. Want instant alerts here too? Turn them on — optional.
TICKET IPK-04471 · #15
How notifications reach the patient

If the clinic has a mobile number, we send one SMS at the start — the link to this page. Opening it lets the patient turn on free in-app alerts, so we don't pay for a message at every step.

We send SMS at the points that matter, to everyone — reliable on any phone. The live page and free app alerts run alongside as a bonus for those who have them.

1 · SMS — reliable, every device
Ippokratis Clinic
You're #15 in Dr. Reyes' queue. Follow it live: queue.ippokratis.ph/t/9f3a — we'll text you again as your turn nears.
Check-inLink to live status pageSMS
2 aheadTime to head backSMS
Your turnNow serving — come inSMS
2 · Live page + app alerts — free bonus
Live pagePosition updates by itselfNo cost
App pushExtra alerts where supportedNo cost
Why SMS for the key points. App push is unreliable on iPhone unless the patient installs the page — almost nobody does. So SMS covers the moments that matter on every device; push is a free extra, never the thing we depend on.
Configurable & clear cost. The clinic chooses which events send an SMS (balancing reach vs. cost). The SMS account and per-message cost stay on the clinic's side; we build the integration. Live page and app alerts carry no fee.
Step 04 — Waiting area

One screen per room, by URL

Each room's display opens its own address and shows only that room's queue. Add a room, add a URL — nothing to configure on the screen itself. A combined view exists for reception.

Each display is just a URL in kiosk mode
Room 1queue.ippokratis.ph/monitor/room-1Dr. Cruz · 4 waiting
Room 2queue.ippokratis.ph/monitor/room-2Dr. Reyes · 7 waiting
Room 3queue.ippokratis.ph/monitor/room-3Dr. Lim · 2 waiting
Allqueue.ippokratis.ph/monitor/allReception overview
Room 2 display · live
Q

Room 2 — Dr. Reyes

10:42
Now serving
09
Room 2 · Dr. Reyes
J. DELA CRUZ
Privacy-aware. Names can be shortened or hidden entirely on the public screen — an open question for the clinic, since this is health data in a shared space.
Step 05 — Control center

Staff run the queue

Switch between rooms; each is its own queue. Calling, finishing, missing and re-queuing all happen here — the single source of truth that updates phones, monitors and notifications at once.

Live queue

10:42
Rejoin request — #15 Maria Santos. Missed their turn, asking to be placed back in line.
#09
Now serving
7
Waiting
~6 min
Avg / patient
1
Missed
One action updates monitor, phone and notifications together.
Two ways a missed patient comes back — kept fair and explicit. A missed patient (e.g. #08) gives staff two clear choices: Recall now keeps their place and calls them again — for someone who just stepped away; Move to end sends them to the back, the fair option when they have been gone a while. A patient who asks to rejoin from their own phone (e.g. #15) always goes to the end, and only after staff approve. Whoever initiates it, the position is shown plainly so no one silently jumps the line.
“Is this really AI?” Most of the system is reliable, deterministic queue logic. The genuinely AI-flavoured parts would be a no-show prediction and a smarter wait-time estimate — flagged as a question, so the clinic can confirm what they mean by “AI-powered.”
Step 06 — At the door

The right person at the door

Today, someone sees “#15” on the wall, notices nobody at the door, and walks in — though they're not next. Here's how we stop that without slowing anyone down.

The 3-second check

Confirm patient

Scan their QR · or confirm by name

Calling token#10
Name on ticketR. Aquino
Patient IDIPK-04472
RoomRoom 2 · Dr. Reyes
Scanned QR matches ticket #10 — this is R. Aquino. Cleared to enter.
Three layers
1
Token ≠ permission

The monitor shows the number, but the call happens in the staff panel. Being #15 on the wall isn't permission to enter.

2
QR = proof of identity

Each QR is bound to one ticket and patient ID. A quick scan confirms the person is who the ticket says.

3
Staff stay in control

A patient becomes “now serving” only when staff press Call. A walk-up that doesn't match isn't cleared.

Result. No more “I saw #15 and nobody was there, so I went in.” The check is fast, but it's a real check.
Now serving Next / waiting Missed Notification sent