Queue Cure '26

76% of India's 1.5 million clinics run on paper token slips. Patients wait 2-3 hours with zero visibility into when they'll be called. Doctors have no dashboard. Receptionists manage everything from memory. This creates anxiety for patients, overwhelms receptionists, and wastes hours of people's time every day. Process I started by understanding the two users — the receptionist and the waiting patient — and what each one needs to see. The receptionist needs to add patients fast and call the next token without mistakes. The patient needs to know their position and how long to wait without refreshing. I chose WebSockets over polling because both screens need to update the moment Call Next is clicked. I built a Node.js server with Socket.io that holds the queue in memory and broadcasts the full state to every connected client on every change. The React frontend uses a shared context with one socket connection so both screens always show the same data. Results Both screens update live the moment Call Next is clicked — no refresh needed. Wait time is computed from real queue data and recalculates on every change. The receptionist screen handles edge cases like empty queue, patient removal, and double clicks. The project is fully open source on GitHub with a README, socket event diagram, and setup instructions. Reflection I would persist the queue to a database so it survives server restarts. I would also add SMS notifications so patients get a ping when they are 2 tokens away — so they can step out and come back.