Queue Cure '26: Real-time Clinic Queue Sync & Mobile Tracking
Eliminated 100% of paper token slips using sub-millisecond Socket.io syncing and dynamic EMA wait-time algorithms.
100%
Real-time Sync Uptime
0
Paper Tokens Needed
< 1ms
Queue Update Latency
Overview
76% of India's 1.5 million clinics rely on archaic paper token slips and verbal shouting to manage patients. Patients suffer through 2–3 hours of wait times with zero visibility into when they'll be called, leading to crowded waiting rooms and immense anxiety. Receptionists lack a digital dashboard, forcing them to manage high-stress environments entirely from memory. Process I started by analyzing the core bottleneck: communication latency between the doctor, receptionist, and patient. I initially considered a standard REST API polling mechanism but discarded it, as it would hammer the server and cause delayed updates. Instead, I architected a full-stack solution using Node.js and Socket.io for sub-millisecond, bi-directional event broadcasting. To address inaccurate wait time estimates, I bypassed hardcoded values and implemented an Exponential Moving Average (EMA) algorithm to weigh recent consultation times more heavily. Finally, to eliminate waiting room crowding, I integrated a QR code system allowing patients to track their token on mobile, and used the Web Speech API for automated audio announcements. Results The resulting application completely eliminates the need for paper tokens. The real-time sync operates with near-zero latency, ensuring the patient waiting room screen perfectly mirrors the receptionist's dashboard. The EMA algorithm successfully adjusts wait time estimates dynamically based on live consultation data. The inclusion of mobile QR tracking successfully decoupled patients from the physical waiting room, vastly improving the clinic experience. Reflection If I had more time, I would replace the local JSON persistence layer with a robust database like PostgreSQL to handle historical analytics over several months. I would also add a dedicated "Doctor View" screen so the physician can pull the next token themselves, entirely removing the receptionist as a bottleneck in the calling process. Finally, I'd implement SMS integrations using Twilio to notify patients when they are 2 tokens away.