The bed manager at a district hospital has a good screen. It shows every ward, every pending discharge and the two ICU beds that will free up after rounds. At 11 p.m. an ambulance arrives with a fever patient from a block forty minutes away, and the ICU is full. Her screen knows that perfectly. It has no idea which hospital nearby has a bed.
A hospital command centre answers "what is happening inside these walls", while a public health command centre software layer answers "what is happening across every facility, and who must act". Both are useful. They are not the same purchase, and a state that buys one expecting the other ends up reconciling numbers by phone again.
A hospital command centre manages one building's flow
In common usage, a hospital command centre is a room or a screen inside a single hospital or hospital group. It tracks beds by ward, admissions waiting in emergency, discharges planned for the day, theatre schedules and transfers between departments. Its users are the bed manager, the nursing superintendent and the medical superintendent.
Its unit of attention is the patient inside the building. Its success looks like shorter waits in emergency, fewer patients stuck after a discharge decision, and theatres that start on time.
A public health command centre manages a population's risk
A public health command centre sits above the facilities. It brings disease surveillance, hospital capacity, helpline calls, ambulances and stock onto one picture for a state or district. Its users are the health secretary, the mission director and the district health officers. The same idea also goes by health command and control centre, a state Health Emergency Operations Centre (HEOC) or, in WHO usage, a public health emergency operations centre (PHEOC).
Its unit of attention is the district and the block, not the ward. It asks whether fever cases in a block are rising above the seasonal baseline, which hospitals can still admit, and whether an ambulance is heading somewhere that cannot take the patient. We cover the design in more depth in our explainer on what a public-health command centre is.
| Question | Hospital command centre | Public health command centre |
|---|---|---|
| Who uses it | Bed manager, nursing and medical superintendent | Health secretary, mission director, district health officers |
| Unit of attention | Patient, ward, theatre | District, block, facility |
| Main signals | Admissions, discharges, transfers inside the hospital | Surveillance, capacity across hospitals, helpline, ambulances, stock |
| Typical decision | Which ward takes this patient | Which hospital takes this ambulance, which block needs a team |
| Failure it prevents | Patients stuck in emergency | Outbreaks seen late, patients sent to full ICUs |
A full ICU is a hospital problem, a full district is a public health problem
Here is an illustrative example with round numbers, not data from any district. Say a district has four hospitals with ICU beds. Hospital A has 0 of 20 free, Hospital B has 3 free, Hospital C has 1 free and Hospital D has 0.
Hospital A's own command centre correctly shows it is full. It can stop accepting ambulances. What it cannot see is that B and C together hold 3 + 1 = 4 free beds. Now say a fever cluster in one block is expected to send 6 serious patients over the next day. Six patients minus four free beds leaves a shortfall of 2. That shortfall is invisible to every individual hospital, because each one sees only itself.
Only a district view can do this sum, see the gap of two, and start a conversation with the neighbouring district before the ambulances leave. That is the job a public health command centre exists to do.
A hospital can know it is full. Only a district view can know where the patient should go instead.
The two centres work best when they feed each other
None of this makes the hospital command centre less important. In fact, the public health layer is only as good as the capacity figures hospitals send up. If a hospital reports its ICU count by phone twice a day, the district picture is out of date most of the time.
So the useful design is a chain. Hospital systems keep the ward-level truth. The public health layer reads ICU, oxygen and ventilator availability from them, shows each figure's source and age, and routes exceptions back to a named hospital owner. In HealthWatch, that capacity is refreshed every 15 minutes onto one facility map, and a diversion plan can notify ambulance dispatch in one click before beds run out. Our guide to hospital ICU and bed capacity tracking across a state walks through the data side.
The after picture is calm rather than dramatic. The bed manager at Hospital A still runs her wards from her own screen. When her ICU fills, the district desk already has a diversion plan in place. The ambulance crew is told before they leave which hospital has a free bed. Nobody calls four hospitals at midnight.
The fair objection: why not just give every hospital a better screen
A reasonable health official might say this. If every hospital ran a good command centre and shared its figures, would the state need another layer at all? Wouldn't a shared spreadsheet of bed counts do the job?
It is a serious point, and for a small district with two hospitals it may be close to true. Our answer is that capacity is only one of the signals. A hospital screen will never see a fever cluster building in a block with no hospital, a spike in helpline calls, or a stock gap at a primary health centre. Those signals live in surveillance, HMIS, helpline and ambulance systems that no single hospital owns.
The other half of the answer is ownership. A shared sheet tells everyone the number. It does not tell anyone that the problem is theirs. A public health command centre ranks exceptions by risk and puts each in front of a named district or hospital officer, with the time it was assigned and closed. That is the difference between a shared view and a shared decision.
Ask which question you need answered before you buy
Procurement documents in India sometimes use "command centre" for both, so the same title can describe very different scopes. Before a tender, it helps to write down the decision you most need made faster.
- If it is "which ward takes this patient", you are buying a hospital command centre.
- If it is "which hospital takes this ambulance" or "which block needs a team today", you are buying a public health command centre.
- If it is both, plan the hospital feeds first, because the district picture depends on them.
A district health officer reading a tender should also check who the named users are. If every user listed is inside one hospital, the scope is a hospital command centre, whatever the title says.
What to do this week
- Write down the three decisions your team most wants made faster, and mark each as ward-level or district-level.
- List every hospital in one district and note how, and how often, each reports ICU capacity today.
- Pick one recent busy night and count how many calls it took to find a free ICU bed.
- Name who in the district would own a diversion decision if the data were in front of them.
Clinical and admission decisions stay with doctors and hospital protocols. The command centre's job, at either level, is narrower: put the right number and the right owner together sooner. More is in our public health command centre guides and tools.