A polyclinic is not a small hospital. It is a shared reception, a shared pharmacy and a shared lab serving consultants who each run their own hours. HIMS gives each doctor their own queue and record while the counter works from one screen.
A polyclinic has one thing a single-doctor clinic does not: several consultants working the same building on different days and different hours, sharing a reception, a pharmacy and often a small laboratory. The software problem is not clinical depth. It is keeping each doctor's patients, queue and record separate while the front desk handles all of them from one screen.
HIMS does that by keeping the patient identity shared and the workflow per doctor. A patient is registered once under a UHID, whichever consultant they came to see. Each doctor has their own appointment book and token queue. Prescriptions go to the shared pharmacy, investigations to the shared laboratory, and billing collects for whoever did the work, with the collections readable doctor by doctor at the end of the day.
Everything that works in a single clinic gets awkward as soon as a second consultant shares the reception.
Patients waiting for three different doctors sit in one corridor with no idea whose turn it is.
Each consultant keeps their own book, so the same patient is registered again for every department.
The counter serves prescriptions from several doctors with no common format and no stock visibility.
Nobody can say cleanly how many consultations each doctor did or what was collected against them.
Which consultant sits on which day lives in one person's head, and collapses when they are away.
The counter searches, finds or creates the UHID, whichever doctor is being seen.
A token is issued against that consultant, not the clinic as a whole.
The doctor writes on the shared patient record and prescribes from it.
The prescription reaches the shared pharmacy queue; investigations reach the shared laboratory.
Consultation, drugs and tests are collected at one counter, attributed to who did what.
The day's volume and collections can be read per doctor and per service.
Workflow: Each doctor has their own token queue and the waiting area knows which number is with whom.
Result: One corridor, three orderly queues.
Workflow: Both consultations sit on the same UHID, so the second doctor sees the first one's notes and prescription.
Result: The patient stops being the messenger.
Workflow: Prescriptions from every consultant arrive in one dispensing queue, drawn from stock the counter actually holds.
Result: No handwriting, no unavailable items.
Workflow: Consultations and collections are read per doctor for the period from the same records that billed them.
Result: The settlement conversation starts from agreed numbers.
Several specialties, one reception.
Doctors who sit two evenings a week.
Prescription to counter without a slip.
Orders and verified results on the record.
Volume and collections per doctor.
Yes. Tokens are issued against the consultant rather than the clinic, so three doctors sitting at the same time each have their own order of patients while the front desk works from one screen. See queue management.
The patient record is shared, and what each role can see is controlled by role-based access configured at setup. Most polyclinics want continuity across consultants, which is the point of one UHID, but the access rules are yours to decide.
Consultations and collections are readable per doctor for any period, which is the data a settlement needs. If you want a specific share or payout calculation automated, describe the arrangement on the call so it is scoped rather than assumed.
It is the same platform with the multi-doctor parts switched on: a book and queue per consultant, shared pharmacy and lab, and per-doctor reporting. A single-doctor practice needs less. See clinic management software.
The IP modules, bed management, admission and discharge, sit in the same platform and are switched on when you need them. Nothing has to be migrated because the patient record is already there.
HIMS is delivered to a fixed scope and goes live in 30 working days where the scope allows. Setup, data migration from your existing sheets and training at your own counter are part of that.
Tell us how you work today. We will show you what the platform would look like for you, and give you a clear scope and timeline.
Founder-led · Chennai, India · Built and supported by the person who wrote it