Queue Cure - Full-Stack Real-Time Patient Queue Management System
Built a dual-view clinic manager that synchronizes tokens instantly via WebSockets to eliminate patient wait-time confusion.
0
Paper Slips Needed
100%
Live Sync Accuracy
Overview
Medical clinic waiting lounges rely heavily on manual paper tokens or verbal calls, creating extreme confusion for patients tracking their turn. This uncertainty spikes patient anxiety and causes crowded. Simultaneously, receptionists face immense administrative fatigue from constantly answering status inquiries instead of focusing on patient admissions. Traditional workflows lack live updates, leading to systemic scheduling bottlenecks. "Queue Cure" addresses this gap by digitizing the process introducing real-time synchronization to completely eliminate paper slips & waiting room friction. Process I designed a dual-interface system separating the Receptionist Control Panel from the Patient Monitor. The backend architecture was built using Node.js and Express to static-serve the frontend modules and handle operational routing. To achieve instant, refresh-free synchronization across screens, I integrated WebSockets via Socket.io for persistent, bi-directional event broadcasting. During development, I initially tried standard HTTP short-polling, but it caused unnecessary server overhead and slight lag. Switching to WebSockets resolved this, ensuring zero-latency updates. I focused heavily on edge cases, such as preventing duplicate token generation and maintaining data integrity during sudden disconnection spikes. The final system achieves a flawless, real-time reactive workflow. Results The project successfully yielded a fully operational, high-performance real-time queue synchronization application. The Reception Desk Control panel seamlessly updates the live intake logs and handles incoming patient token generation immediately. Testing simulated immediate state reflections across multiple simultaneous browser sessions with zero latency, establishing a stable blueprint for reducing patient wait confusion. Reflection If given more time, I would integrate a persistent database layer like MongoDB or PostgreSQL to maintain token logs across server restarts. I would also add SMS or email notification alerts using an API like Twilio, allowing patients to securely monitor their queue position remotely on their mobile devices without needing to remain inside the waiting lounge area.