CMMS for the healthcare sector

In a healthcare facility, maintenance doesn’t compete with production: it competes with patient care. An operating room without air treatment gets cancelled, a down imaging room delays diagnoses, and a failure in the electrical backup is a problem of a different category.

That changes three things compared to any other sector: what counts as critical, how long the response can take, and what has to be provable afterward.

Criticality has to be declared

In healthcare, you can’t leave it to the judgment of the day. Every asset must carry an explicit priority, because that’s what determines attention order and the committed deadline.

In asset management, priority is a field on the equipment, alongside its location, model, serial number, installation date, warranty expiry, and whatever custom fields each type needs, each with its unit.

And it’s worth being clear that two distinct fleets coexist: clinical equipment — with its manufacturer protocols and verifications — and facilities — air treatment, medical gases, electricity and backup power, domestic water, refrigeration, elevators, fire protection. Both fit in the same system, grouped by system, family, and model.

Deadlines that get audited here

Incidents carry their type and subtype, priority, zone, affected service, and who handles them. Statuses can carry an associated maximum time, and there’s an SLA entity with its name, priority, and limit.

That enables two things that a hospital typically asks for separately: what’s overdue shows up in a list instead of being discovered when the department calls again, and afterward you can measure response time and resolution time, which aren’t the same.

Without that configuration, everything arrives marked as urgent, and the system can’t tell what’s urgent from what’s just noise.

Getting the report in properly from the ward

Whoever spots the fault is usually clinical staff, who aren’t technicians and have other priorities. If the only channel is calling maintenance, the report arrives incomplete.

A report can come in from the backend, from a dedicated access with description and photo, or from an email inbox that the system empties and converts into incidents, with a different inbox per type if needed. What matters is that every channel ends up in the same list.

Measuring, not ticking boxes

It’s the difference between a record that stands up as evidence and one that only proves someone showed up.

Checklists support fields with their type, label, and minimum and maximum value — a filter’s differential pressure, a chamber’s temperature, an equipment’s parameters — so an out-of-range reading gets logged as an anomaly on the spot. They resolve in cascade — asset, model, subfamily, family — so an equipment type’s protocol is defined only once.

That anomaly then has to turn into an incident with its priority and owner. If it gets logged and nothing happens, the technician stops logging it and the system loses its reason for existing.

Preventive maintenance for what can’t be skipped

Much of hospital maintenance is dictated by a regulation or the manufacturer.

It’s worth knowing this before looking for it in the menu: statutory maintenance isn’t a separate module. It’s handled with the general preventive maintenance mechanism, by attaching to the asset, its model, or its family the checklist the regulation requires and setting the frequency. The system generates the work orders on its own, checking beforehand whether the day is a holiday and whether the technician is available.

A single piece of equipment can have several schedules at once: the quarterly verification is one thing, and the annual review with component replacement is another.

And when wear depends on usage — running hours of a machine, cycles of an autoclave — the asset can carry a counter with a limit and a warning percentage, so the preventive order gets generated automatically once the threshold is exceeded.

To put it precisely: the software records and proves. Complying with the regulation is the facility’s job.

Documentation, which is half the file

Verification certificates, manufacturer protocols, official inspection reports, contracts, approvals.

The document manager attaches documents to the asset, the service, the supplier, the order, or the incident, and decides who sees them — client, technician, supplier — or whether they need validation. Certificates carry their number, scope, issuer, holder, and fingerprint.

Any document can carry an expiry date, with a daily check of what’s about to expire and its notification. Same for staff personal protective equipment.

Contractors, inside the system

A large share of hospital maintenance is carried out by outside companies, often one per type of facility or equipment. If they work outside the system, the facility loses the history precisely on the most expensive interventions and can’t check whether the contract specs are being met.

Suppliers are registered and receive the orders that belong to them, with their times, materials, documentation, and signature. Since licenses are unlimited across all three plans, registering all of them isn’t a budget decision. And there’s a connector between GMAO Cloud installations for when the contractor also uses it, so work moves from one system to the other without an intermediate file.

The technician, with context in front of them

In the app they have their orders, the equipment’s history, its documentation, and open anomalies, log time with a stopwatch, consume material from the warehouse, fill in the checklist, and collect the department head’s signature.

It works without coverage, which in a technical basement or a radiology bunker is exactly the situation.

Coordination with the care service

An operational detail that doesn’t show up in product sheets and that decides quite a lot: in a hospital, almost no intervention can happen whenever the technician wants. It depends on the operating room being free, the room having no patients scheduled, or the ward having lower occupancy.

That’s why it matters that the plan can be moved easily. The calendar lets you see the workload and drag work to another day, and if rescheduling costs more than ignoring the plan, the plan gets ignored and the system stops reflecting reality.

It also helps for the department head to see what’s coming. With their own access, they can check their area’s upcoming preventive work and arrange access without anyone having to call them, which is the practical way to stop scheduled reviews from getting cancelled.

What gets checked afterward

The reports on executed annual plan, anomalies, response and resolution times by priority, cost per equipment and per service, and hours per contractor.

In a hospital, the most useful one usually isn’t the cost report but the plan compliance one: it’s the one that gets shown and the one that lets you correct frequencies with data.

There’s more operational detail in CMMS for hospitals. If you want to see it applied to your fleet, you can request a demo.