Skip to main content
Skip to main content

Hospital IoT: Monitoring the Critical Facilities Behind Care

November 19, 202612 min
Cover image for Hospital IoT: Monitoring the Critical Facilities Behind Care

Hospital IoT doesn't start at the bedside. It starts with the fridges, operating rooms, water, and oxygen that fail quietly, at night, when nobody is looking.

One Friday night, the cleaning crew on a pediatric ward unplugged the vaccine refrigerator to mop behind it and never plugged it back in. Nobody noticed until 9 a.m. on Saturday, when the nurse on shift read the min/max thermometer: 14 hours out of range. The vaccines were set aside, pharmacy was consulted, and in the end they were discarded. The thermometer worked. What was missing was someone who found out at 11 p.m.

Stories like this happen in every hospital, and they rarely have anything to do with medicine. They're about facilities: the pharmacy cold chain, the pressure in an operating room, the hot water temperature, the level in the oxygen tank. These systems work fine 99% of the time, and when they fail, it's usually in the small hours or on a weekend.

This guide is for hospital maintenance companies, system integrators, and facilities engineers. It covers what hospital IoT includes and what it doesn't, what to measure in each area, what the rules ask for, and how to deploy without touching the clinical network.

What Hospital IoT Covers and What It Doesn't

When people hear "hospital IoT," many think of connected vital-sign monitors, smart infusion pumps, or patient wristbands. Those exist, but they belong to a different world. A device that measures or monitors a patient for a medical purpose is a medical device. In Europe it falls under the Medical Device Regulation (EU) 2017/745, with CE marking, clinical evaluation, and post-market surveillance; in the United States, under FDA oversight. That's not something you solve with a sensor and a general-purpose platform.

This article is about the other half of the hospital: the facilities run by the engineering department or the maintenance contractor. IoT fits there very well, because the problems are temperature, pressure, level, flow, and equipment status, and missing them is expensive.

AreaWhat to measureWhat it prevents
Pharmacy and vaccine refrigeratorsTemperature, door, powerDiscarded stock, cold chain breaks
Operating rooms and clean roomsTemperature, humidity, differential pressurePostponed surgeries, infection risk
Domestic hot waterTemperature at heaters, returns, and outletsLegionella growth
Medical gasesTank and manifold level and pressureSupply interruptions, emergency orders
Power and backup equipmentConsumption, generators, UPSFailures at the moment they're needed

Keeping the two apart has a practical upside: a facilities monitoring project handles no patient data. That makes the conversation with IT and the privacy office far simpler.

Pharmacy and Vaccine Refrigerators

A mid-sized hospital has dozens of refrigerators holding medicines: pharmacy, each ward, vaccination, the blood bank, and the labs. Most run between 2 and 8 °C (36 and 46 °F). The CDC vaccine storage and handling guidance recommends a digital data logger with a buffered probe, and many hospital protocols still ask staff to record minimum and maximum temperatures at the start and end of each day.

Manual records have two limits. The first is the schedule: between the evening check and the morning one, ten or twelve hours go by with nobody looking. The second is effort: in a hospital with 60 refrigerators, that's 120 readings a day that someone has to take, write down, and file.

With one sensor per refrigerator, both change. Temperature is logged every few minutes, the history is stored without paper, and an alert reaches the on-call person when a unit goes out of range, even at 11 p.m.

A few details make the difference:

  • A probe in a buffer that mimics the product, such as a small bottle of glycol. An air probe jumps every time the door opens; a buffered probe tracks what the medicine experiences.
  • A door contact. It explains most temperature rises and catches the door that didn't close properly.
  • Power loss and silent-sensor alerts. An unplugged fridge doesn't show up in the temperature for the first hour. A dropped power signal or a sensor that stops reporting shows up much sooner.
  • Night escalation. Nobody reads an email at 3 a.m. A voice call to the on-call supervisor gets answered.

Not every unit runs at 2-8 °C. Pharmacy and labs also keep freezers at around -20 °C and, in some cases, ultra-low freezers near -80 °C for certain reagents and samples. Each class needs its own probe and its own limits: a standard probe doesn't read -80 °C, and an alarm threshold copied from a refrigerator is meaningless on a freezer. It pays to build the inventory first, unit by unit, with its location, its contents, its range, and who answers for it.

The logic is the same as in any cold chain. Our guide to cold chain monitoring goes deeper into designing alarms that don't end up muted.

Operating Rooms and Clean Rooms: Temperature, Humidity, and Pressure

An operating room has some of the strictest air requirements in any building. In Spain, the UNE 100713 standard classifies it as a class I room, with reference values of 22 to 26 °C, 45% to 55% relative humidity, and at least 20 air changes per hour; in the United States, ASHRAE Standard 170 plays a similar role. In both cases, the room must be kept at positive pressure relative to the corridor, so air flows out of the room and never in.

The surgical suite's HVAC controls those parameters, usually through the hospital's building management system. What's often missing is a continuous view and a history you can show to someone:

  • Differential pressure per room. A sensor between the OR and the corridor logs positive pressure all day. If it drops, because a door was left open or a filter is clogging, the alert arrives before the next procedure.
  • Temperature and humidity. Out of range, staff are uncomfortable and some materials behave worse. Low humidity in winter is a classic.
  • Air handling unit status. Running state, alarms, and filter pressure drop, where they can be read.

Sarah is a maintenance engineer at a hospital in Ohio with eight operating rooms. Every time infection prevention asked for a room's pressure history, someone had to export data from the BMS, which only kept a month of trends. With differential pressure sensors and a separate data platform, the report for any OR and any week takes a minute, and the loss-of-pressure alert goes straight to the on-call technician's phone.

As in any building, the IoT layer reads and alerts, but it doesn't replace the controls. We cover this in our guide to building management systems and IoT.

Domestic Hot Water and Legionella

Hospitals are high-risk sites for Legionella: long water networks, many outlets that are rarely used, and vulnerable patients. The CDC Legionella water management toolkit has a dedicated section for healthcare facilities, and in Spain, Royal Decree 487/2022 sets the requirements. In practice, temperature is the first line of defense: water heaters above 60 °C (140 °F), hot water in the network above 50 °C (122 °F), and cold water preferably below 20 °C (68 °F).

The usual control is periodic measurements at representative outlets, written into the facility log. It works, but it only shows the network at the moment of measuring. What happens between two rounds stays invisible.

Temperature sensors on heaters, on the supply leaving the plant room, and on the return of each branch give the continuous picture:

  • Cold returns. A branch whose return drops below 50 °C points to a recirculation or balancing problem. That's where bacteria have the best chance.
  • Heaters that don't reach temperature. A heater that stays below 60 °C for hours usually signals a failure in hot water production.
  • Thermal shocks. The continuous record proves that thermal disinfection happened and that the temperature held long enough at each point.
  • Cold water that warms up. Cold pipes running next to hot ones, or through unventilated shafts, go above 20 °C in summer.

None of these sensors replaces water sampling or the water management program the rules require. What they add is that a deviation is caught the same day, not at the next round of measurements.

Medical Gases, Power, and Backup Equipment

Medical oxygen reaches many hospitals through an outdoor cryogenic tank, with cylinder manifolds as backup. The supplier usually tracks the level and schedules refills, but the hospital needs to see it too, especially when consumption changes suddenly, as it did in 2020.

A level sensor on the tank and pressure sensors on the manifolds and the distribution network tell you how many days of reserve are left and alert you if network pressure drops. The same goes for medical air and vacuum, which depend on compressors and pumps that also fail.

Power is the other front. A hospital can't lose electricity, which is why it has generators and uninterruptible power supplies (UPS). The trouble with backup equipment is that it's only used when it's needed, and that's exactly when the flat battery or the fuel that doesn't flow shows up. Watching generator status, fuel level, periodic tests, and UPS charge turns those surprises into alerts with days of warning. Measuring consumption per building or per panel also feeds energy management, as we explain in our guide to energy monitoring systems.

Dave coordinates maintenance at a regional hospital. During the monthly generator test, the technician used to note that it started and not much else. Once the generator was connected to the platform, Dave saw that its start time had been creeping up for three months. It was the starter battery, replaced before it could fail during a real outage.

How to Deploy Hospital IoT Without Touching the Clinical Network

A hospital's biggest objection to an IoT project isn't technical. It's the network. IT departments protect the clinical network, rightly, and don't want hundreds of new devices on it. The simplest deployment avoids the problem from day one.

  • Battery-powered wireless sensors. For refrigerators, water temperatures, and rooms, LoRaWAN (Long Range Wide Area Network) is a good fit: sensors last for years, need no cabling, and the signal gets through floors. Our guide to LoRaWAN range explains what to expect indoors.
  • Gateways with their own backhaul. The gateway can send data over 4G instead of using the hospital network, so the project doesn't need a single open port on the clinical network.
  • Equipment reads through an edge gateway. To read the BMS, generators, or power meters over Modbus, a gateway in the plant room reads locally and publishes outward over MQTT with TLS.
  • No patient data. Temperatures, pressures, and levels identify nobody, and it's worth putting that in writing from the start.

A First Project in Three Steps

  1. Pick one area and one building. Pharmacy refrigerators are the usual choice: the value is easy to explain, the sensors are cheap, and the rules are clear.
  2. Agree on the alarms before installing anything. Ranges, delays, who gets called at night, and what happens if nobody answers. This conversation with pharmacy and nursing takes longer than the installation.
  3. Run it for two months and review. Look at which alarms fired, which were real, and how long it took to respond. Then extend to operating rooms, water, or gases with the same platform and the same on-call rules.

Starting small also gives the IT department time to see that the project doesn't touch their network, which makes the second phase much easier to approve.

Cloud Studio IoT is a white-label IoT platform for system integrators and maintenance companies. In a hospital project it is the data layer: it receives readings, stores the history, runs the alarm rules, and produces reports. LoRaWAN sensors arrive through the project's network server, and industrial equipment through a software module we install at the edge as a gateway. Alerts go out by email, SMS, WhatsApp, voice call, or push notification, with escalation when nobody responds.

When a hospital needs its data to stay on its own servers, the platform can also be installed on-premise, and it runs without internet access: in that mode, alarms appear as notifications in the control room's own web interface.

For a maintenance company running several hospitals, a multi-tenant architecture lets each site see only its own facilities under the contractor's brand, while the contractor's team sees the whole portfolio. Our facility management page covers the use cases, elderly care covers care homes, and the IoT platform page explains the rest.

Conclusion

The hospital IoT you can deploy tomorrow isn't about patients. It's about the facilities they depend on. The essentials:

  • Keep facilities monitoring separate from medical devices: different projects, rules, and teams.
  • Start with pharmacy and vaccine refrigerators, where manual logs leave the most blind hours.
  • In operating rooms, continuous differential pressure is the data point that reassures infection prevention most.
  • For Legionella, sensors on heaters and returns catch the same day what a round of measurements finds weeks later.
  • Deploy with wireless sensors and gateways that have their own backhaul, without touching the clinical network.

If you maintain hospital facilities and want to start with one specific area, talk to the team about your site.

Frequently Asked Questions

What can be monitored with IoT in a hospital?

The critical facilities: pharmacy and vaccine refrigerators, operating room temperature, humidity, and pressure, domestic hot water, medical gases, generators, UPS, and energy use. Patient monitoring is a separate field, regulated as medical devices.

Can an IoT sensor replace the min/max log on a vaccine refrigerator?

It can automate the log, keep it stored without paper, and alert outside working hours. Before dropping manual checks, confirm what your own facility's protocol and your health authority require.

Do the sensors need to connect to the hospital network?

No. LoRaWAN sensors talk to a gateway, and the gateway can send data out over 4G. The project doesn't need access to the clinical network.

Does water temperature monitoring meet Legionella requirements?

It helps, because it keeps a continuous record of temperatures and thermal treatments. It doesn't replace water sampling or the water management program your regulations require.

Related Articles

Take the Next Step

Ready to Transform Your Business?

Contact us to discover how Cloud Studio IoT can help you achieve your goals.