Skip to main content
Quality & Patient Safety10 min read

HAI Benchmarking for Indian Hospitals: Comparing Rates Honestly

Why comparing your CLABSI or CAUTI rate against a published figure usually misleads, what the ICMR, INICC and NHSN networks actually report, and how to build an internal trend baseline that stands up to scrutiny instead.

Shreya Kamath

Hospital Quality and Accreditation Manager

#hai benchmarking#hospital acquired infection rates india#icmr hai surveillance#infection rate comparison#quality indicator baseline
HAI Benchmarking for Indian Hospitals: Comparing Rates Honestly

The comparison you are about to make is probably invalid

A quality committee sees a CLABSI rate of 6.2 per 1000 central line days, finds a published figure of 1.1 from a national network somewhere, and concludes that the ICU has a serious problem. Sometimes it does. More often the two numbers were produced by different definitions, different detection intensity, different patient populations and different denominators, and the gap between them measures those differences rather than any difference in care. Benchmarking is not looking up a number. It is establishing that two numbers describe the same thing before you subtract one from the other.

This matters because the wrong conclusion is expensive in both directions. A hospital that concludes it is failing will launch a bundle campaign, buy chlorhexidine dressings, and exhaust the goodwill of an ICU team that was already performing reasonably. A hospital that concludes it is doing well, because its rate sits below a published figure, may simply be missing infections it never cultured for. The second error is far more common in Indian hospitals than the first and it is much harder to see.

The useful posture is comparative humility. External figures are worth reading as context and as a sanity check on order of magnitude. They are not scorecards. The comparison that genuinely tells you whether your infection prevention is working is your own rate against your own rate, over a long enough series, with the methodology held constant. That is the argument this article makes, and the rest of it is about why the external comparison fails and what to build instead.

What the published surveillance networks actually report

Four sources come up most often. The Indian Council of Medical Research runs a healthcare-associated infection surveillance network across participating tertiary hospitals and publishes periodic reports of device-associated infection rates by unit type. The International Nosocomial Infection Control Consortium publishes multinational data drawn largely from limited-resource settings, including many Indian sites. The US National Healthcare Safety Network publishes extensive American data. The European Centre for Disease Prevention and Control maintains its own network for European hospitals.

These do not measure the same thing. The definitions differ in detail, the participating hospitals are self-selected, and crucially the settings differ in how aggressively they look. NHSN data comes from a system with mature electronic surveillance and high blood culture rates. INICC data has consistently described higher device-associated rates in limited-resource settings than the American figures, and the authors themselves attribute part of that to real differences in practice and part to differences in the systems being compared. Read the methods section of any report before you read its tables.

There is also a participation bias that nobody can adjust away. Hospitals that join a voluntary surveillance network are hospitals that have an infection control programme good enough to join one. Their published rates are not a national average; they are the rates of the better-organised end of the distribution. Comparing yourself against them is closer to comparing yourself against a peer group you have not yet been admitted to than against a typical hospital.

We spent a quarter trying to explain why our VAP rate was five times a published benchmark. It turned out the benchmark used ventilator-associated events and we were still using the older clinical VAP definition. Nothing about our care was in question.

Quality manager at a 260-bed NABH-accredited hospital

Surveillance intensity: you find what you look for

The most powerful hidden variable in any infection rate is how hard the hospital looked. A unit that draws blood cultures from every febrile patient will identify bloodstream infections that a unit which starts empirical antibiotics without culturing will never see. Both units may deliver identical care. Only one has a numerator. This is why a low reported HAI rate in a hospital with low culture rates should be read as a data quality finding rather than a clinical achievement.

You can measure your own detection intensity, and you should, because it makes your trend interpretable. Blood cultures per 1000 patient days, urine cultures per 1000 catheter days, and the proportion of ventilated patients with a respiratory sample sent are all straightforward to derive from laboratory data. Track them alongside the infection rates on the same report. When your CLABSI rate rises in a quarter where blood culture rates also rose sharply, you have a plausible explanation for at least part of the movement.

Case-finding method matters as much as culture volume. A dedicated infection control nurse reviewing every positive blood culture daily will find more than a system relying on ward staff to notify. Adding an ICN, or moving from paper notification to an automated laboratory alert, will raise your measured rate without any change in what happened to patients. Log every such change on the trend chart, because otherwise your own improvement in surveillance will be read by a future committee as a deterioration in care.

Detection intensity measures to publish beside every HAI rate

  • Blood culture sets per 1000 patient days, by unit
  • Urine cultures per 1000 indwelling catheter days
  • Proportion of ventilated patients with a respiratory sample sent
  • Case-finding method in use and the date it last changed
  • Number of trained surveillance staff and hours allocated per week

Case mix, definitions and denominators: three ways comparison breaks

Case mix is the obvious one and the least often quantified. A unit taking transplant recipients, prolonged-ventilation cases and referrals arriving with established sepsis carries a fundamentally different infection risk from a post-operative step-down unit that keeps patients for forty-eight hours. Published network figures are usually stratified by unit type, which helps, but a medical-surgical ICU in a Delhi referral centre and a medical-surgical ICU in a district private hospital share a label and very little else. Severity scoring, if you already collect APACHE or SOFA data, gives you at least a describable position.

Definitions break comparison more quietly. VAP and ventilator-associated events are different constructs and produce different counts from the same patients. Laboratory-confirmed bloodstream infection and catheter-related bloodstream infection, which requires paired cultures or tip culture evidence, are not interchangeable. Secondary bloodstream infection exclusions vary. Before comparing anything, write down the exact definition version you use and the exact version the comparator used. If you cannot determine the comparator's version, you cannot use it.

Denominator practice is the third. Whether a hospital counts device days by daily census or estimates them from bed occupancy, whether it counts per patient or per device, and whether it includes step-down beds all shift the rate by amounts comparable to the differences people are trying to interpret. Two hospitals with identical care and identical detection can report rates differing by half simply through denominator convention. None of this is visible in a published table.

Three comparison failure points shown side by side: case mix, definition version and denominator convention
Three comparison failure points shown side by side: case mix, definition version and denominator convention

Questions to answer before accepting any external benchmark

  • Which definition set and which version produced the comparator numerator
  • How the comparator counted device days, and per patient or per device
  • What unit types and case mix the comparator population contained
  • What culture and case-finding intensity the comparator setting had
  • Whether participation in the comparator network was voluntary and selective

Standardised infection ratios, and why they do not travel

The standardised infection ratio is the methodological answer to case mix. Instead of comparing a raw rate, you compare observed infections against the number predicted for a hospital with your particular unit types, bed sizes, medical school affiliation and other risk factors, using a regression model fitted to the reference population. A ratio above one means more infections than predicted. It is a genuine improvement on raw rate comparison and it is what mature national programmes report.

It also cannot be borrowed. The predictive model is fitted on the reference network's own data, and applying an American model to an Indian hospital assumes the relationships between risk factors and infection are the same in both settings, which is exactly the assumption in question. Until an Indian network publishes a risk model fitted on Indian data with sufficient coverage, an SIR calculated against a foreign model is a precise-looking number resting on an unexamined assumption.

What you can borrow is the logic. Build your own internal standardisation by splitting your data along the dimensions you know drive risk in your hospital, then compare each stratum only against itself over time. Your ICU against your ICU last year. Your ventilated patients against your ventilated patients. It is less sophisticated than a fitted model and it does not let you claim a position against a national figure, but every comparison it produces is one you can defend line by line.

Standardised infection ratio model fitted to a reference population being misapplied to a different setting
Standardised infection ratio model fitted to a reference population being misapplied to a different setting

Building the internal baseline that actually guides you

An internal baseline needs three things: a long enough series, a frozen methodology, and annotation. Twelve consecutive months is the minimum before you have any sense of your own normal variation, and twenty-four is better. During that period the case definitions, the denominator rule, the census time and the case-finding method must not change. If they must change, the series restarts and you say so on the chart rather than splicing the old and new together.

Plot it as a run chart or a statistical process control chart rather than a bar comparison against last month. The question a control chart answers is the only question worth asking of a monthly infection rate: is this month's value within the range this process normally produces, or is it a signal? Two events instead of one in a small ICU is almost never a signal. Eight consecutive months above the median is, even if no single month looked alarming.

Set improvement targets against your own baseline, expressed as a sustained shift rather than a threshold. A target of reducing the median CLABSI rate by a stated proportion and holding it for six consecutive months is measurable, honest and achievable. A target of getting below a published national figure may be unachievable for reasons that have nothing to do with your care, and missing it repeatedly does real damage to the credibility of the quality programme inside the hospital.

Control chart of monthly device-associated infection rates with annotated methodology changes and a median shift
Control chart of monthly device-associated infection rates with annotated methodology changes and a median shift

What a defensible internal baseline contains

  • At least twelve consecutive months on a single frozen methodology
  • A control or run chart with the median and control limits drawn
  • Dated annotations for every definition, staffing or system change
  • Detection intensity measures plotted on the same time axis
  • Targets expressed as a sustained shift, not a single-month threshold

What to say to the board, the payer and the assessor

Boards want a single number and a comparison, and giving them one uncritically is how bad decisions get made. The better format is a short standard page: your rate, your trend with control limits, your detection intensity, and one line stating explicitly what external comparison is and is not possible. Boards accept this readily when it is presented as rigour rather than evasion, and it protects the quality team from being asked to explain a gap that is an artefact.

Payers, corporate clients and empanelment processes increasingly ask for infection rates, and the honest answer includes methodology. Submit the rate with the definition set, the period and the denominator method attached. A hospital that submits a slightly higher rate with a clear method reads as credible; one that submits a suspiciously low rate with no method invites a closer look. Insurers comparing bids have started to notice which is which.

For a NABH assessment, the expectation is not that your rate is low. It is that the indicator is defined, collected consistently, analysed, compared over time, and acted upon where analysis showed something. An assessor will ask to see the definition, the raw collection sheets, the trend, the minutes where the trend was discussed, and the action that followed. A hospital with a moderate rate and that full chain in place is in a far stronger position than one with an excellent rate and no evidence of how it was produced.

Share this article
Back to all articles

Keep reading

Related articles

See HealUDoc in action

From EHR to analytics, watch how one platform runs your entire hospital. Book a personalized walkthrough with our team.