Refraction is a department
Optometrists get their own screen and queue: five-stage refraction, retinoscopy, cycloplegia, keratometry, IOP, CCT and colour vision — visible to the doctor in the record.
Healthcare · Eye Hospital Management System
Run your eye hospital on one system
Registration, refraction, OPD, lab, pharmacy, lenses, theatre and billing — in one place, on your own machine.
Why eye-specific matters
Where a generic HMS falls short
An eye hospital works differently from a general one. These are the places it shows.
What an eye hospital does
A generic HMS
This system
Refraction by an optometrist, recorded in detail
A free-text "vision" field
A refraction department: own worklist, 5 stages · both eyes, amendment history
Buys one lens model in 15 dioptric powers
One stock item called "IOL", counted by quantity
One entry per model per power; stock as individual boxes with serial, lot and expiry
Must prove which lens went into which eye
A batch number typed by hand, if at all
The implanted lens is the box scanned and reserved — traceable both ways, recall by lot
Reserves lens and kit when surgery is decided
Stock issued on the day, if the lens is there
Reserved at the OPD decision; kit QR-labelled and scan-verified in theatre
What makes it different
Three things a generic HMS cannot do
Every IOL tracked by serial
Boxes are scanned in; serial, lot and expiry are read from the code. That exact lens is reserved for that patient and recorded against the eye it went into.
One connected surgical journey
From the OPD decision through counselling, biometry, lens booking and pre-op fitness to theatre and post-op review — each step knows what the last one decided.
The patient journey
Counter to post-op, in one record
- 1
Reception
Aadhaar scan or manual entry; UHID slip prints with a QR code.
- 2
Refraction
Queued automatically; the optometrist records the observation.
- 3
Consultation
Diagnosis, then medicines, lab tests, referral — or surgery.
- 4
Counselling
Options, lens choice and cost explained; operation date booked.
- 5
Biometry
A-scan, keratometry and the decided lens power recorded.
- 6
Lens booking
One physical lens reserved for this patient, by serial number.
- 7
Pre-op fitness
HIV, HbA1c, HBsAg through the lab; unfit cases re-dated.
- 8
Theatre
Kit scan-verified; implant recorded from the reserved lens.
- 9
Post-op review
Bandage, drops, notes and follow-up dates from the surgery date.
Lens traceability
A manufacturer recalls a lot. You have every box and every patient who received one — in seconds, not after a day in the store room.
Serial, lot and expiry are read from the box itself. The implanted lens is the one that was scanned and reserved — traceable from box to eye, and from eye back to box.
Built-in safeguards
The system refuses what should be refused
- ✕No expired lens reserved
- ✕No expired medicine dispensed
- ✕No lens box received twice
- ✕No encounter closed without a diagnosis
- ✕No surgery marked without one
- ✕Only the room's incharge doctor edits
When an inspector asks
NABH evidence becomes a by-product
Nothing is ever deleted
Records are deactivated, not removed. Every change keeps who, what and when in a full history.
Access by named permission
15 roles ship ready; every permission can be re-assigned. A doctor can read a refraction, not edit it.
Statuses are derived, not typed
"Expired" is computed from the date on every read, so nothing claims to be usable because a job didn't run.
History stays true
Prices and reference ranges are snapshotted, so today's edit never rewrites last month's bill or report.
What is in the system
About 50 screens across nine areas
Front office
PatientsOPD visitsIPD admissionsAppointments
Clinical
EMRRefractionCounsellingBiometryLaboratory
Surgical
OT schedulesPre-opSurgeryPost-opKits
Pharmacy
PrescriptionsMedicinesStockIOL booking
Lenses
IOL stock and usageCatalogueTraceability
Stores
InventoryOptical store products and orders
Money
BillsLine itemsPackagesPayments
Compliance
NABHAuditWasteIncidentsEquipment
Administration
UsersRolesPermissionsSettings
How it runs
One computer, inside your hospital
Your data stays on your machine, in an open format.
Staff PCs
Chrome, Edge or Firefox — nothing installed.
Hospital server
One application + PostgreSQL, on the LAN. A modest desktop is enough: 4 cores, 8 GB RAM minimum; on a UPS, wired to the LAN.
Second disk
All data + nightly backups. 30 days kept; restore rehearsed at installation.
No internet needed to run
No cloud subscription, no per-user licence.
Upgrades in under five minutes
Replace one file; the database updates itself.
Your data stays yours
Open PostgreSQL format, no licence server, you hold the password. Nothing phones home. Source-code escrow can be discussed if your board needs it.
A typical rollout
Seven stages, from walkthrough to settled
Stage
What happens
Your part
1Walkthrough
Full journey demonstrated
Half a day with OPD, theatre, lab, store
2Fit review
What matches, what to configure or build
Answers on clinical workflow
3Install
Server, system, backups, restore test
The machine, a network point, a UPS
4Master data
Rooms, staff, catalogues, prices imported
Price lists; a few senior hours
5Staff testing
Your people run your own patients through
Most important — real gaps surface here
6Go live
Demo data cleared, passwords changed
A decision on the date
7Settling in
Fixes from the first weeks of real use
Telling us what is awkward