Hospital operating system · 12 portals · one record
CH 01Registration
Reception registers the patient once and issues their portal login at the desk. From that moment every appointment, prescription, scan, bed and bill is bound to the same ID — nobody types the name twice.
Reception → patient portal
CH 02Consultation
The doctor signs a prescription and orders tests. Pharmacy, the lab and radiology find them in their queues the same second, and results flow back to the doctor and the patient — no slips, no phone calls, no refresh button.
Doctor → pharmacy · laboratory · radiology
CH 03Admission
Bed maps, ICU boards and medication rounds update the moment they change. Discharge releases the bed automatically, so the next admission never waits on a call to the ward.
Nursing · IPD · ICU
CH 04Discharge
Consultation, pharmacy, lab, radiology and room charges land on a single invoice while cashless pre-authorisation runs in the same pipeline. The patient leaves with one bill — and nothing leaves unbilled.
Billing · insurance
One record · every department
Twelve portals and thirteen scoped roles read and write the same record in real time — from the front desk to the final bill.
12
Portals
30+
Modules
13
Scoped roles
Realtime
Sync
Built for hospitals like these
Verdant Life Hospital
220 beds
Nirvaan Health City
540 beds
Aruna Meadows Hospital
180 beds
Havenwell Medical Centre
60 beds
Suvarna Kiran Hospital
130 beds
Tulsi Grove Speciality
95 beds
Illustrative deployment profiles. We name real customers only with their written consent.
End-to-end patient journey
Why hospitals choose it
Software that a ward clerk uses two hundred times a day has different requirements from software that photographs well.
Screens render from a static shell and stream their data in, so a page opens the moment it is asked for rather than waiting on the network.
Queues, bed maps, lab statuses and dashboards update the instant anything changes. There is no refresh button anywhere in the product.
Every login is issued by the hospital and revocable, scoped to one of 13 roles and enforced in the database — with an immutable audit entry per action.
The workspaces
Each team gets a workspace built for its job — all reading and writing the same central record.
OPD consults, e-prescriptions, IPD rounds, telemedicine
Book visits, reports, payments, family records
Registration, tokens, live queues, admissions
Vitals, medication rounds, ward boards, handover
Dispensing, stock, expiry alerts, GST billing
Sample tracking, results, instant doctor alerts
X-Ray to MRI workflow with image archives
OPD/IPD invoices, payments, refunds, GST
Cashless pre-auth, claims pipeline, documents
Attendance, leave, payroll in two clicks
Bed maps, admissions, discharge summaries
Triage board, ambulance fleet dispatch
In practice
Registration to token used to be three registers and a phone call. It is now one screen, and the doctor sees the patient in the queue before they have sat down.
Dr. Meghana Rao
Medical Superintendent, Verdant Life Hospital
6 min
average check-in
Discharge was where money leaked. Pharmacy and lab billed separately, and nobody saw the whole picture until the patient had gone. Now the final bill shows every open charge on one screen.
Anil Kurup
Head of Finance, Nirvaan Health City
₹0
unbilled at discharge
Every login is issued by us and revocable by us, and the audit trail answers who touched a record before the question is finished.
Sana Fernandes
Chief Information Officer, Aruna Meadows Hospital
13
scoped roles
Composite examples drawn from typical deployments, not statements by named individuals.
Questions
Most hospitals run their first OPD day within two weeks. Departments switch on one at a time — reception and billing first, then clinical — so nobody is asked to change everything on a Monday morning.
No, and that is deliberate. Portal logins are issued at reception against a verified identity and can be revoked from the same screen, so a hospital record is never created by an anonymous sign-up.
Patient masters, doctors, departments and tariffs are imported before go-live. Historical visits can be brought across as read-only history so the timeline does not start empty.
Screens render from a static shell and data streams in, so a page opens immediately rather than waiting on the network. Writes are queued and reconciled when the connection returns.
Access is scoped to one of 13 roles and enforced in the database, not just the interface. EcoGenius keeps an immutable audit entry for every read-sensitive action and every write.
Each hospital runs against its own database instance with its own credentials. There is no shared table with a tenant column, so there is no query that can cross the boundary.
We load a slice of your patient master, doctors and tariffs into a sandbox, then walk your team through a full day — registration to discharge.