Thirty modules. One system.
No hospital runs all thirty. Which ones you switch on matters far less than what sits underneath them: one patient record and one ledger, shared by every module on this page. So this page is the catalogue first, then three points in a day where that sharing is the whole of the work — the consulting room, the counter, the printer — and then the register itself, thirty rows, each one marked for what it is.
- Reception & token queue
- Appointments & slots
- Patient registry & family accounts
- Day board
- Doctor EMR
- e-Prescriptions
- Laboratory
- Document vault (old reports)
- Pharmacy dispensing
- Pharmacy purchase & stock
- OPD billing
- Accounts & ledger
- Expense register
- Concession & refund controls
- MIS & analytics
- Patient app
- Messaging & reminders
Start with a consulting room. Add pharmacy when there's a counter, a laboratory when there's a bench, the family app when patients ask for it. Same system throughout — nothing to migrate later.
Sign once. Three desks already have it.
A patient is registered, takes a token, and is seen. The note the doctor signs is the same object the pharmacy queue, the lab requisition and the bill are made from — so nothing is retyped between one desk and the next, and no two of them can quietly disagree.
Every department. One bill.
Consultation, pharmacy and laboratory all post onto the same folio for that visit — and so does whatever else the hospital switches on later. One total at the counter, and one day book at the end of it.
Prescriptions your patients can actually read.
One signed note prints in English, in Gujarati, or in both together. The doctor writes it once; the language is a setting on the printed sheet, not a second prescription to keep in step.
The drug name, the dose, the day count and the total print in Latin script whichever setting is used — those are what the pharmacist dispenses against, and transliterating a drug name is a dispensing error waiting to happen. Only the instruction words change: a fixed vocabulary of dose timings and food relations, written for this product.
A Gujarati-only sheet prints the same way, with the English line left off.
SPECIMEN SHEET
Three made-up lines, set to show the columns. Not a real patient and not a real prescription.
Six columns — the sheet scrolls sideways →
| Medicine | Dose | Time | When | Days | Total |
|---|---|---|---|---|---|
| Amoxicillin 500 mg | 1-0-1 | Morning · Night | After food | 5 | 10 tablets |
| Paracetamol 650 mg | 1-1-1 | Morning · Afternoon · Night | After food | 3 | 9 tablets |
| Pantoprazole 40 mg | 1-0-0 | Morning | Empty stomach | 5 | 5 tablets |
- Four columns — Latin script in every mode.
- Two columns — the instruction words, and all the setting changes.
All thirty, row by row.
Grouped by where they live in the hospital. Every one of them writes to the same record and the same ledger.
IN DEVELOPMENTEverything unmarked is part of the OPD product we sell today. The rows marked IN DEVELOPMENT are built and working, but not yet on sale — which is a different thing from the roadmap on the front page, where the work has not been done at all.
Front of house
Clinical
Diagnostics
Inpatient & critical
Pharmacy & supply
Money
Governance & back office
Patient-side
See it running on your OPD's busiest morning.
A thirty-minute walkthrough on your own cases — a token queue, a part-dispense, a refund, a concession that needs an approver. Bring your hardest workflow.