Wooble
Back to Dakshta's profile
Verified on Wooble

Clinic Queue

Achieved <50ms real-time queue synchronization across TV displays using a custom Socket.IO engine.

Dakshta MethwaniClinic Queue

< 50ms

Sync latency

1

Click patient call

0

Manual refreshes

Overview

Over 76% of India’s 1.5 million healthcare clinics rely entirely on manual, paper-based token slips and verbal shouting to manage patient flow. This outdated approach creates intense friction: patients endure hours of waiting room anxiety with zero visibility into their actual wait times, receptionists face immense administrative fatigue trying to track sequential numbers from memory, and doctors lack any data-driven visibility into operational efficiency Process Built a unified Next.js full-stack architecture with a custom Node.js server to natively support WebSocket lifecycles in a single repo. To avoid database cluster overhead during prototyping, I engineered a server-side state machine backed by persistent JSON storage. Replacing high-lag polling with an event-driven Socket.IO pipeline, the system isolates data payloads (queue:state) from micro-interaction hooks (token:called). This enables the patient display to instantly trigger 3D transitions and audio cues while dynamically calculating wait times using deterministic O(1) client-side operations. Results Delivered a full-stack prototype that connects the receptionist dashboard, admin panel, and waiting-room TV display with sub-50ms synchronization via Socket.IO. By eliminating manual refreshes and verbal token shouting, the application lowers operational overhead to single-click workflows. Patients get total queue visibility via a high-visibility TV layout, complete with fluid 3D airport-style digit-flipping animations and gentle audio chimes that transform a stressful waiting room into a calm, structured environment. Reflection For production, I would swap the local JSON store for PostgreSQL via Prisma ORM to ensure thread-safe concurrency and secure multi-tenant isolation across parallel clinics. Additionally, I would implement a Redis Adapter to decouple WebSocket connections, allowing the real-time server layer to scale horizontally across cloud instances without dropping broadcast states or event synchronization for thousands of active displays.

Links & files

Artifacts

5

Gallery

4