Hospital management software
for hospitals in India.

Polynexus HMIS is a cloud-based hospital management information system that runs a hospital’s clinical, diagnostic, pharmacy, billing and administrative records in one database, with a patient-facing CRM built into the same system.

It covers OPD and IPD, emergency, ICU, operation theatre, nursing, laboratory, radiology, blood bank, pharmacy, billing and insurance, inventory, finance and HR, plus enquiry handling, telephony, referrals and patient feedback. It is built and operated by Polynexus, an Indian software company headquartered in Nagpur, and is offered to hospitals across India.

Who it is for

Built for multi-department hospitals, not single clinics

The system assumes departments that hand work to each other — and that the handover is where most hospital software falls apart.

• Multi-speciality hospitals running OPD alongside inpatient wards, ICU, operation theatre and an emergency department, where a patient moves between all of them on one visit.
• Hospitals with in-house diagnostics — a laboratory, a radiology department or both — that want orders raised from the consultation rather than re-entered at the collection counter.
• Hospital groups where staff work across more than one unit and management wants comparable numbers from each, without each unit keeping its own spreadsheet.
• Hospitals with a front office that markets — enquiry desks, call centres, referring-doctor relationships, health camps and corporate tie-ups whose results currently never connect to what the hospital actually billed.

Problems it solves

The gaps that cost hospitals money quietly

Most hospital software problems are not missing features. They are seams — places where one system stops and a person with a register takes over. These are the seams this product is designed to close:

• Enquiries that never become appointments. Calls and web enquiries sit in a diary nobody reviews. Here they are a tracked pipeline with stages, reassignment and callback tasks, and the enquiry funnel report shows where they die.
• Billing assembled from memory. When investigations, pharmacy and bed charges live in separate books, the final bill is a reconstruction. Bills built from the actual clinical record stop leaking revenue.
• Occupancy nobody can quote. Bed and ICU occupancy come from real bed allocations rather than a whiteboard, so the number is current rather than remembered.
• Results released before they are checked. Lab results and radiology reports carry an explicit verification step, so a provisional value cannot reach a patient as a final one.
• Referrals that cannot be credited. Referring doctors are tracked as records with a league table, so the hospital knows who actually sends patients instead of guessing.
• Attendance re-keyed into payroll. Staff attendance, shifts and leave sit in the same system as employee records, so payroll input is not a monthly re-typing exercise.

Modules

What is in the system

Every module below corresponds to live functionality in the platform. Nothing here is roadmap.

Workflow

One record, from first call to final bill

How a patient moves through the hospital, and what each department writes to the shared record as they go.

A visit starts as an enquiry or a booking against a real doctor slot, moves through registration, check-in and the consultation itself, and picks up investigation orders and a prescription along the way. Diagnostics and pharmacy work off those orders directly, and the bill at the end is assembled from what actually happened rather than reconstructed afterwards. Every step below is a record in the same database, not a handover between separate systems.

See the full OPD visit walked through step by step, or read how the inpatient path works on admission, bed allocation and discharge.

Deployment

Cloud by default, dedicated where it is required

Polynexus HMIS is delivered as a cloud service. Polynexus builds, hosts and operates the infrastructure itself rather than outsourcing data handling to a third party, and the hosting region can be pinned to India on request. Hospitals that need their own instance — for procurement policy, for a group-wide deployment, or to keep data on named infrastructure — can have a dedicated or self-hosted deployment.

The platform is multi-tenant, with data isolated per hospital. A staff account can be scoped to a single unit, and users who work across a group can switch between hospitals without a second login.

Choosing between the two models is a real decision, not a formality. Our guide to cloud versus on-premise hospital software sets out what each one actually commits you to.

Security & privacy

Patient data handled as patient data

Hospital records are among the most sensitive categories the DPDP Act recognises. The platform is built accordingly.

Integrations

What it connects to

Implementation

How a hospital gets onto it

Nobody switches a running hospital over in a weekend. The sequence below is the one that works.

Evaluating an HMIS

What to compare before you sign anything

This section is deliberately vendor-neutral. These are the things that decide whether a hospital system works out, whoever you end up buying from.

• Workflow fit over feature count. Feature lists converge; almost every vendor ticks almost every box. What differs is whether the product matches your handovers, your tariff structure and your payer mix without customisation. Score against the journeys you actually run.
• One system versus several that talk to each other. A hospital running separate registration, pharmacy, lab and billing packages pays for the seams between them in re-keying, reconciliation and revenue leakage. Ask where the single record lives, and what happens at each boundary.
• Data ownership and exit. Who owns the records, in what format you can export them, how long a full export takes, and what happens to your data if you leave or the vendor does. Get the answer in the contract, not in the demo.
• Migration scope. Which of your existing patient records, outstanding bills and stock positions come across, who does the mapping, and what is deliberately left behind.
• Roles, permissions and audit. Whether a ward nurse, a billing clerk and a consultant genuinely see different systems, and whether administrative actions are logged in a way you could review after an incident.
• Reporting without manual work. Take the three numbers management asks for most often and ask to see them produced live, from the same data the clinical modules write.
• Interoperability claims, tested. For anything described as ABDM, ABHA or FHIR, ask whether the vendor is certified, empanelled, or building toward it — three different answers — and ask to see the step happen rather than hear it described.
• Training and support. Who trains which role, what support hours cover, how an issue raised at 9pm in the emergency department is handled, and what the response commitment actually says.

We have written the long version of this as a working document. The HMIS evaluation checklist is seventy-five questions grouped by department, written to be put to any vendor — including us. Alongside it, how to choose hospital management software in India covers running the evaluation itself, and what an HMIS costs in India explains the pricing models you will be quoted on.

Seeing it

A walkthrough on a live system

We do not publish screenshots of patient screens. We show the system running, against workflows that match your hospital.

A demo is a screen share against a working instance: we register a patient, book them into a doctor's slot, run the consultation, raise a lab order, dispense from pharmacy, admit and discharge, and produce the bill and the day's MIS. You see the real product doing your real sequence, and you can ask what happens when it goes wrong.

Explore the modules