MedMulti-specialty clinic software that keeps every department in one flow
The hard part of running a polyclinic isn't any single consult — it's the hand-offs. A patient seen in medicine needs cardiology; a doctor runs late and three queues back up; the owner wants one collections number across every consulting room. MedQuePMS makes the hand-offs first-class: referrals that move patients between live queues, schedules and favourites that stay personal to each doctor, and money that rolls up cleanly.
A 20-minute walkthrough — a live referral between two departments, queue to queue.
A multi-specialty clinic fails at the seams, not the centre
Every doctor in a polyclinic can be excellent and the clinic can still feel chaotic — because the failures happen between people. The referral scribbled on a slip that never reaches the other room. The cashier who can't tell which doctor a payment belongs to. The receptionist juggling five queues on paper while one doctor is stuck in a long case.
MedQuePMS treats coordination as the product. It's the same clinic management platform a single-room practice uses — a GP clinic and a ten-doctor polyclinic run the same software — but the multi-doctor machinery underneath is what this page is about.
Referrals that move patients, not paper
Inside the clinic, a referral is a workflow. Outside it, it's a branded letter. Either way, it's on the record.
Refer in one tap
From the consultation, a doctor refers the patient to a colleague. "Referred to … for …" prints on the prescription and shows in the record.
The colleague accepts
The target doctor sees it in a "Referrals to me" inbox — with the context, not a chit passed down the corridor.
The patient lands in the next queue
Accepting drops the patient straight into the target doctor's live queue. No re-registration, no second token battle at the desk.
Or ask for a second opinion
Any visit can be sent for a second opinion: a server-built case snapshot gives the colleague context, the reply lands on the patient record, and both doctors are notified.
When the patient has to leave the building, the clinic still looks organised: a branded external referral-letter PDF on the clinic's letterhead goes to a named centre or specialist, and verified diagnostic centres can upload the resulting reports back against the patient's MRN.
Many doctors, one queue that doesn't panic
Multi-doctor by design
One real-time token list across doctors, with room assignments and a public TV board using privacy-aware naming. Each doctor's ETA comes from their own actual consult pace. Explore queue management →
Auto-rebalance and bulk reassign
When one doctor runs late or takes a break, the queue auto-rebalances. Flip a doctor to "Out today" and their waiting patients are bulk-reassigned in one action.
Departments and schedules
Define your departments in admin settings, and manage each doctor's schedule individually — with a two-state unavailability flow so planned leave and sudden absence are both handled.
Personal tools per doctor
Per-doctor SOAP snippets, ICD-10 favourites and prescription favourites — each specialist keeps their own shorthand without stepping on anyone else's.
Nine roles, and each sees only its surface
In a building full of staff, "who can see what" is a feature, not a setting.
| Role | What they work with |
|---|---|
| Admin | Users, departments, schedules, reports and clinic settings. |
| Doctor | Their queue, consultation workspace, referrals and second opinions. |
| Billing admin & cashier | Invoices, collections, the pay-to-consult gate and the ledger — not clinical notes. |
| Diagnostic centre | Uploads reports against a patient's MRN, linked to the fulfilling referral. |
| Medical rep & wholesaler | Meeting requests with doctor approval; the pharmacy's restock order inbox. |
| Patient | Their own records, queue position, payments and reminders. |
| Super admin | Group-level oversight — subscriptions, tickets, activity, per-clinic collections. |
Underneath all of it: PostgreSQL row-level security on every core table, encrypted payment and AI credentials, and audit logging — so separation is enforced by the database, not by good intentions.
One pharmacy, one ledger, one view of the money
Shared resources stay shared. The pharmacy hub serves the whole clinic: every doctor's prescriptions flow into the same pending-Rx queue at the counter, with batch-wise stock and server-computed GST behind it. On the revenue side, billing works across doctors — consultation fees, pharmacy sales, cash, card, UPI and cashless insurance — and rolls up into a collections ledger covering consult and pharmacy revenue, exportable to CSV.
For groups with more than one location, each branch runs as its own isolated clinic with a branded per-clinic login, and the super admin watches the whole estate: subscriptions, support tickets, activity and per-clinic collections. The owner gets oversight; the branches keep their data walls.
Frequently asked questions
How do cross-referrals between our own doctors work?
A doctor refers the patient to a colleague from inside the consultation. The target doctor gets a 'Referrals to me' inbox, and accepting the referral drops the patient straight into that doctor's live queue — the referral note also prints on the prescription and shows in the patient's record. For advice without a hand-off, any visit can be sent for a second opinion: the system builds a case snapshot server-side, the reply lands on the patient record, and both doctors are notified.
Can each doctor keep their own schedule, templates and favourites?
Yes. Schedules are managed per doctor, with a two-state unavailability flow — flipping a doctor to 'Out today' triggers a bulk reassign of their queue. Clinical preferences are personal too: per-doctor SOAP snippets, per-doctor ICD-10 favourites and per-doctor prescription favourites, so a dermatologist's shortcuts never clutter a cardiologist's screen.
Who in the clinic can see the money?
Only the roles built for it. MedQuePMS ships nine roles — admin, doctor, billing admin, cashier, diagnostic centre, medical rep, wholesaler, patient and super admin — and each sees only its own surface. Billing admins and cashiers work collections and the ledger; doctors see their consultations, not the cash position; and the collections ledger covers both consultation and pharmacy revenue, exportable to CSV.
Does it support multiple branches?
Each branch runs as its own clinic on the platform, fully isolated by row-level security and with its own branded login. Group-level visibility comes through the super admin, who oversees the hospitals on the platform — subscriptions, support tickets, activity and per-clinic collections — so an owner can watch every branch's numbers without merging their data. Multi-branch groups are onboarded on the Chain/Hospital plan.
How does the queue cope with many doctors at once?
The queue is multi-doctor by design: one real-time token list with room assignments, a per-doctor ETA computed from each doctor's actual completed-consult average, and a public TV board with privacy-aware naming. When one doctor runs late, the queue auto-rebalances; when a doctor is marked out, their patients are bulk-reassigned. Accepted internal referrals drop patients into the target doctor's queue automatically.
How do we evaluate it for our clinic?
Request a demo at medquepms.com/request-demo, call +91 81432 10000, or message us on WhatsApp. Bring two departments' workflows and we'll run a referral between them live — queue to queue — in about 20 minutes.
Related solutions
See a referral cross departments, live
A 20-minute demo — multi-doctor queue, internal referral, roles and the collections ledger. No obligation.