How a Delhi private hospital turned invisible leakage into a finance-led recovery program
A finance-led audit revealed that leakage was not just a billing issue. It was tied to late block release, weak refill discipline, and missing case-level visibility across operations and revenue teams.
Billing leakage
2.9%
from 11.4%
Revenue recovered / OR / month
₹10.8L
from ₹0.0L
Released blocks refilled
67%
from 22%
Leadership quote
“The insight that changed the project was simple: unused premium OR time is a finance issue even when it never becomes a bill.”
P. Malhotra · Chief Financial Officer
The Delhi hospital in this case did not begin with a scheduling complaint. It began with a finance question. Surgical activity looked strong in monthly summaries, yet contribution quality per OR remained uneven and hard to explain. Some weeks appeared commercially healthy despite visible idle time. Other weeks looked busy but delivered less realized value than leadership expected. The finance team suspected leakage, but it could not confidently separate billing gaps from operational underuse, and that uncertainty made it difficult to prioritize action.
Context
The operating rooms were commercially important, but the control language around them was split. Finance reviewed billed activity, implant reconciliation, and broad service-line yield. OT leadership reviewed schedule adherence, cancellations, and staffing pressure. Both sides could sense that value was leaking, yet each side was looking through a different window. That made leakage feel real but strangely unprovable.
The tipping point came when the CFO asked a sharper question: how much of the hospital's surgical value was being lost before billing ever had a chance to capture it? That reframed the discussion immediately. Instead of treating the OR as a source of completed cases alone, the team started treating it as a source of premium capacity whose economic quality depended on block discipline, refill behavior, and case-level truth.
Operational baseline
Before the project, block release was inconsistent. Sessions that were clearly weakening by late afternoon were not always released early enough for recovery. The OT desk often knew a case would move or fall off, but the information reached potential replacement pathways too late to refill the time. Finance saw the consequence as under-realized value. Operations saw it as routine churn. Neither description was wrong, but neither one was strong enough to change the system on its own.
The hospital also had familiar reconciliation challenges. Implant and consumable usage was generally documented, but the case-level link between what happened in the room and what arrived in the billing trail was not consistently transparent to leadership. That meant leakage discussions drifted between anecdote and audit rather than settling into a disciplined, recurring review.
Diagnosis
The audit combined schedule events, cancellations, room occupancy, charge capture patterns, and block utilization into one view. Three things stood out. First, a surprising amount of value disappeared through late release and weak refill behavior rather than through headline cancellation count alone. Second, several apparent billing issues were actually downstream expressions of poor operational traceability. Third, some cases were being billed correctly but performed inside such inefficient sessions that their effective economic quality was still compromised.
That last point mattered. The hospital had been discussing revenue leakage as though it began in billing. In practice, some of it began earlier, when premium room time was lost through avoidable drift and no replacement case could be mobilized in time. Once the team saw that pattern, the conversation stopped being about whether finance or operations was right. Both were right, but only when reviewed together.
Rollout approach
Rather than launch a broad transformation, the hospital focused on a narrow set of recovery loops. The first was visibility: create one case-level view that connected planned schedule, actual event sequence, and final economic interpretation. The second was block release discipline: define earlier decision points for whether a weakening session could still be recovered. The third was refill behavior: give the OT desk clearer logic for which waiting cases could be advanced without destabilizing the rest of the day.
This work was intentionally finance-led but operationally grounded. The CFO sponsored the review, yet the interventions were shaped with OT leadership, billing teams, and the daily control desk. That mix mattered because the hospital did not need a report that proved leakage existed. It needed a method that changed how time, cancellation, and case movement were managed in real operations.
Changes introduced during the recovery window
- Block-release checkpoints were moved earlier so weak sessions became recoverable before the slot lost all value
- The OT desk received a refill view that prioritized feasible backfills rather than ad hoc case pulling
- Case-level finance review began linking room events, implant logic, and billing interpretation in the same pack
- Service-line reviews started separating pure billing gaps from operational underuse of premium OR time
- Leadership meetings adopted one definition of recovered value per OR rather than debating multiple proxy measures
What changed operationally
The new discipline was not dramatic from the outside. There were no theatrical war rooms. What changed was the timing of decisions. Cancellations and likely slippages were surfaced earlier. Release logic became more explicit. OT coordinators could assess whether a block still had refill value or whether the window had already been lost. Because the hospital acted sooner, fewer sessions dissolved into dead space that everyone regretted but no one could monetize.
The finance team also stopped waiting for month-end to understand deterioration. Once operational underuse and billing leakage appeared in the same review language, executives could see whether a disappointing economic week was caused by reconciliation gaps, weak schedule discipline, or a combination of both. That made the response far more precise.
Measurable outcomes
Billing leakage fell from 11.4 percent to 2.9 percent in the focused recovery window, but leadership considered that only part of the story. The more strategic gain was the jump in recovered value per OR, which reached approximately Rs10.8 lakh per room per month once refill behavior and case-level reconciliation improved together. Released blocks that were actually refilled rose from twenty-two percent to sixty-seven percent, giving the hospital a tangible measure of how much premium time had previously been slipping away unused.
Just as important, the hospital gained a cleaner definition of payback. It no longer evaluated OR improvement only as a schedule nicety. It could describe recovered value in finance language while still tracing that value back to operating decisions. That is what gave the leadership team confidence to keep expanding the model after the initial audit window.
Leadership takeaway
The case changed how the executive team thought about surgical economics. Billing and operations were no longer reviewed as parallel stories. They became two interpretations of the same case-level truth. That shift reduced the tendency to blame one function for a problem that had actually formed across multiple weak handoffs.
It also changed governance quality. The CFO did not need more abstract dashboards; the hospital needed a disciplined way to review where monetizable OR time was being lost, what portion of leakage sat in documentation or charge logic, and what portion sat in daily control choices. Once that frame existed, the improvement program became much easier to defend internally.
What happened next
After the initial recovery period, the hospital extended the model into more routine weekly review. Finance retained sponsorship, but OT leadership owned the day-level control improvements. That balance proved useful because the program stayed commercially serious without becoming disconnected from how surgery actually moved on the floor.
Hospital profile
Hospital: Illustrative private hospital program, Delhi
OR footprint: 6 ORs
HMIS: SAP IS-H
Segment: Private Hospitals
Want your own outcome story?
We’ll review your current OR performance, quantify the recoverable opportunity, and show which ORS AI modules should lead the rollout.
Book a free OR audit