Wooble
Back to Shivam's profile
Verified on Wooble

Queue Cure 26 Real-Time Digital Clinic Queue Management System

Replaces paper-based clinic tokens with zero-delay WebSocket synchronization and a smart moving-average wait time estimator.

ShivamQueue Cure 26        Real-Time Digital Clinic Queue Management System

10s Registrations

0ms Sync Delay

Overview

Traditional clinic waiting rooms rely on static, paper-based token slips that breed patient anxiety. Patients are left entirely blind to their actual waiting duration, forcing them to remain tightly packed inside crowded waiting areas. For clinic receptionists, manually calculating dynamic wait times while managing a chaotic stream of incoming patient registrations is practically impossible, leading to clerical bottlenecks, extended data entry friction, and degraded operational efficiency. Process We designed a dual-portal application separating the high-speed administrative needs of the receptionist from the data-focused needs of the patient. Initially, we tried simple periodic polling for live updates, but dropped it due to severe network overhead and stale state issues during peak simulator spikes. We migrated to a full WebSocket event loop using Socket.io to achieve real-time, zero-delay broadcasts. To handle inaccurate static wait estimates, we developed a moving average engine tracking the last 5 completed consultation times. Finally, we engineered a standalone C++ simulator tool to continuously stress-test our queue logic and edge cases under simulated high-load clinic conditions. Results The prototype successfully replaces manual paper token tracking with an automated digital pipeline. By using an auto-focused, single-form entry system on the Receptionist Dashboard, patient onboarding time drops drastically to ~10 seconds. Integration of Socket.io guarantees 0ms latency for cross-device queue updates, instantly reflecting queue status variations on patient screens. If we had more time, we would implement persistent database storage (MongoDB) to maintain historical metrics across server restarts and design an SMS alert fallback gateway for patients waiting outside the clinic. Reflection Given more time, I would replace the current in-memory state tracking with a persistent database like MongoDB to ensure queue data isn't lost if the server restarts. I would also implement robust role-based authentication to secure the receptionist dashboard from unauthorized access. Finally, to truly maximize patient freedom, I’d integrate an SMS gateway like Twilio to text updates directly to patients when they are next in line, removing the need for them to keep the web portal open or stay inside the clinic's physical environment.

Walkthrough

Links & files

Artifacts

5

Gallery

7