https://github.com/aman-kumar5/queue_management.git

Queue Cure addresses the inefficiencies of paper-based clinic queues, where patients have no visibility into their token status or waiting time and receptionists manually manage tokens, leading to confusion and delays. We identified a gap in affordable solutions that provide live queue tracking and multi-screen synchronization for small clinics. Our biggest challenge was ensuring that the Receptionist Dashboard and Patient Display remained perfectly synchronized in real time, with every token update instantly reflected across both screens without refreshes while maintaining accurate queue stat Process Our approach was to first understand the core issue: patients needed live queue visibility, and receptionists needed an easy way to manage tokens. We chose React for building responsive interfaces, Node.js and Express for handling queue logic and APIs, and MySQL for persistent data storage. Initially, we relied on API calls and page refreshes to update the patient display, but this approach introduced delays, inconsistent data, and a poor user experience because both screens were not synchronized instantly. We then adopted Socket.IO for real-time, event-driven communication. By emitting events whenever a patient was added or a token was called, both the Receptionist Dashboard and Patient Display updated immediately without refreshing. Results Queue Cure successfully transformed the traditional paper-based clinic queue into a fully digital, real-time management system. By integrating React, Node.js, MySQL, and Socket.IO, we achieved sub-second synchronization between the Receptionist Dashboard and Patient Display, enabling instant token updates without page refreshes. The system provides live queue visibility and estimated waiting times, reducing patient uncertainty and repetitive inquiries while significantly lowering the receptionist's manual workload. With persistent MySQL storage and automatic state recovery after refreshes or r Reflection Instead of using traditional request-response APIs and periodic page refreshes, we adopted an event-driven architecture using Socket.IO for bidirectional communication. This enabled sub-second synchronization between the Receptionist Dashboard and Patient Display, ensuring that every token update was instantly reflected across all connected screens.