Operation theatre utilisation tracking in India: the four numbers a promoter should see every Monday

Four operation theatre numbers every Indian hospital promoter should see weekly, why the data is usually missing, and what to fix before buying software.

Ask an Indian hospital promoter how the theatres did last week and you will usually get a case count. Forty-one cases. Sixty-three. The number arrives on Monday, it sounds like performance, and nobody in the room can say whether it was a good week or an expensive one.

Operation theatre utilisation tracking in India is mostly done this way: a count of cases, sometimes a count of hours, assembled by hand from the OT register. That is not utilisation. Utilisation is what share of the theatre day you sold, at what margin, and what you gave away without noticing. Four numbers answer that question, and a hospital that can produce all four every Monday morning is running a different business from one that cannot.

The four numbers

• First-case start against scheduled start. Measured in minutes, by theatre, by day. The first case sets the shape of the entire list. A theatre that starts forty minutes late every morning loses a case a week without a single cancellation appearing anywhere.
• Turnaround between cases in the same theatre. Wheels-out of one patient to wheels-in of the next. This is the number that separates theatres that are busy from theatres that are productive, and it is almost always owned by nobody.
• Same-day cancellations, with a coded reason on each. Not a narrative in a register. A closed list: patient not fasting, consent incomplete, fitness not done, implant not available, blood not reserved, surgeon unavailable, prior case overran, equipment down. Reasons you cannot count are reasons you cannot fix.
• Charge capture per case. Implants and consumables issued to the theatre, set against implants and consumables billed on that case. This is the revenue-leakage number, and in most hospitals it has never been calculated even once.

Why the numbers are usually missing

The data does exist. It exists in the wrong places, at the wrong times, in the wrong hands.

The schedule lives in an OT register or a whiteboard, written the evening before and amended by phone. Actual times are noted by nursing staff on the anaesthesia record, in a handwriting intended for clinical use, and are entered into any system hours later if at all. The cancellation gets a line in the register and an explanation in a corridor conversation. The implant sticker goes into the case file. The consumables leave the store against a departmental indent for the theatre, not against a patient.

That last one is the mechanism behind most theatre leakage. The moment stock moves against a department rather than against a case, the link between what was used and what was billed is broken, and it can only be rebuilt manually. Nobody has time to rebuild it for forty cases a week, so nobody does, and the difference quietly becomes the cost of doing business.

A theatre does not leak money because people are careless. It leaks because the record of what happened and the record of what was charged are created by different people, at different times, in different books.

What to fix before you buy anything

None of the following requires a purchase order.

• Agree one definition of each number and write it down. Start time means knife-to-skin or it means patient-in-room, but it cannot mean both on alternate weeks. Most disputes about theatre performance are actually disputes about definitions.
• Put a clock on the theatre wall and four timestamps on one sheet. Patient in, start, finish, patient out. One sheet per case, collected by the OT in-charge at the end of the day. Manual, ugly, and enough to produce two of the four numbers within a fortnight.
• Convert cancellation reasons into a closed list of eight codes. Tick a box. Review the codes monthly and ask which of them are pre-admission problems dressed up as theatre problems, because most of them are.
• Run one reconciliation by hand. Take four weeks of theatre indents and four weeks of surgical bills for the same period and reconcile them at the item level. It is a tedious week for one person. The number that falls out of it usually decides the next three years of your IT budget.
• Give the four numbers an owner and a slot. A number nobody presents on Monday is a number that stops being collected by March.

Where Ospia fits

Ospia HOS is an AI-native hospital operating system rather than a hospital management package. It runs as a workforce of AI agents, each with a defined scope, permissions, KPIs and escalation path, on one patient record across the hospital. Ospia HOS is built and running hospitals in production today; the clinical core is live, while the AI Workforce Console shown on our site is still labelled an interface preview.

For theatres specifically, the OT Coordinator agent plans theatre lists against real case durations rather than the surgeon's optimistic estimate, and checks readiness across consent, implants, blood and staffing before the day starts. Chief Executive Digest puts one honest picture of the hospital in front of leadership every day, and follow-up questions are answered in plain language under your own permissions, so the four numbers are a question you ask rather than a report someone compiles.

Because inventory, billing and the surgical record sit on the same record, an implant issued to a case and a charge on that case are the same event rather than two entries to be reconciled later. Every event is retained permanently, so a case you want to examine in March is still fully examinable in November. How much any agent may do on its own is a dial the hospital sets, per task; at the highest level the system acts inside boundaries the hospital wrote, and every run still produces a replayable ledger entry, an event trail and a reversal path. Every AI response carries its recommendation, why, evidence, confidence, alternatives considered, policy references and expected outcome.

What we will not tell you is how much this recovers. We publish no case studies and no ROI figures; the case-study slots on our site are unfilled placeholders describing what we intend to measure, and they stay that way until a hospital has a full cycle behind it and agrees to publish. Our stated intent is that the platform should pay for itself within the first year through billing leakage recovered, claim rejections avoided and admission and discharge hours released. That is a target we hold ourselves to, not a result we have published.

If you want a number of your own to start from, the revenue leakage calculator is published openly, with no email address and no form. If you want to see this argued against your own theatre data, the executive demonstration takes forty-five minutes and runs on your numbers rather than a canned dataset.