Wooble
Back to Somesh-coding's profile
Verified on Wooble1view

Queue Cure '26 – Real-Time Smart Clinic Queue Management System

2 Screens Live synchronized via WebSocket

Somesh-codingQueue Cure '26 – Real-Time Smart Clinic Queue Management System

Overview

76% of India's 1.5 million clinics still run on paper token slips and shouting. Patients wait 2–3 hours with zero visibility into when they'll be called. Doctors have no dashboard. Receptionists manage everything from memory. Process I started by analyzing the workflow of a typical clinic waiting area and identified two primary user groups: receptionists and patients. Based on these requirements, I designed a two-screen architecture consisting of a Receptionist Dashboard and a Patient Waiting Room. The backend was developed using Java and Spring Boot with REST APIs for queue operations. To achieve real-time synchronization, I implemented WebSocket communication using STOMP and SockJS. Whenever a receptionist performs an action such as generating a token or calling the next patient, the backend broadcasts updates to all connected clients. Results The final solution successfully provides real-time synchronization between receptionist and patient views without requiring page refreshes. Receptionists can generate tokens, call patients, and update consultation timings through a single dashboard, while patients gain instant visibility into queue progress and expected waiting time. Key outcomes achieved: • Real-time queue updates across multiple screens. • Automatic estimated waiting-time calculation. • Elimination of manual queue tracking and repeated patient inquiries. • Cloud deployment using Render and Vercel for public accessibility. Reflection Given more time, I would extend the platform beyond a prototype into a production-grade healthcare solution. Planned improvements would include patient self-check-in through QR codes, SMS/WhatsApp notifications when a patient's turn approaches, appointment scheduling integration, analytics dashboards for clinic administrators, and persistent database storage for historical queue records.

Links & files

Artifacts

2

Gallery

4