How can you create effective medical device maintenance schedules?

Two hospitals run the same imaging fleet and report the same maintenance budget. One replaces transducers on a two-year cycle because that is what the spreadsheet says; the other replaces them when the calibration trend says the element is drifting. Same spend on paper, very different uptime — because one schedule is a calendar and the other is a measurement.

Last updated: October 4, 2026

Why calendar-based scheduling disappoints

Manual scheduling lives in spreadsheets, physical logs or separate departmental databases. That structure has three predictable consequences: no real-time visibility, so bottlenecks between procurement, maintenance and compliance teams go unnoticed; communication gaps with vendors, so a service call takes longer to close than the fault took to find; and no connection between the schedule and how hard the device is actually worked.

The last one is the expensive one. A calendar cannot distinguish a device that runs eight hours a day from one that runs twice a week, so it over-maintains the second and under-maintains the first. Over-maintenance consumes technician hours and parts; under-maintenance produces the failure that arrives mid-list.

Cost control suffers in the same way. Without usage data, forecasting a service budget becomes reactive, and facilities either overspend on contractors or lose devices to early obsolescence because nobody noticed the drift.

What a schedule has to cover

The WHO’s maintenance guidance is a useful spine, because it separates the functions that a calendar tends to merge: a maintenance strategy includes inspection as well as preventive and corrective maintenance, with performance inspections confirming correct operation, safety inspections confirming the equipment is safe for patients and operators, and preventive maintenance aiming to extend life and reduce failure rates.

A schedule that covers only the third of those is a servicing plan, not a maintenance strategy. The comparison below is what changes when all three are scheduled from data rather than from a calendar.

Building a risk-based interval

Four inputs set an interval, and each one is answerable.

Clinical criticality. What happens if this device is unavailable for a day. Failure probability. How often this model fails, from your own work-order history rather than from a general figure. Utilisation. Hours run per week, which is what converts a calendar interval into an actual duty cycle. Consequence of drift. Whether an out-of-specification reading changes a clinical decision, which is true of dosing and monitoring devices and less true of a device that produces an image a clinician interprets.

The interval then follows from the answer rather than from a default: a high-criticality, high-utilisation device with a consequential drift mode goes into the shortest band, and one with none of those three characteristics goes into the longest, even if a vendor offers a shorter one.

From schedule to system

Implementation follows a sequence, and the order matters because each step supplies the data for the next.

Register every device with its identifier, location, service history, and the instructions that govern its reprocessing or servicing. Profile each one to set frequency from manufacturer guidance, usage and safety criticality. Automate the alerts so that reminders are issued and assigned before the deadline rather than after. Capture the service event, including calibration data and component changes, so traceability is a by-product of doing the work. Review performance periodically and move intervals on the evidence.

Where the facility has a computerised maintenance management system, it should hold the schedules, the history, the spare-parts inventory and the compliance reports in one place. Where it does not, the minimum viable version is a shared record with an owner and a monthly compliance review — the same artefact, without the automation.

What an audit actually asks for

Documentation is the deliverable. Standardised log templates, digital records with technician sign-off, findings linked to the corrective or preventive action taken, and a service history per asset. Where a device has been serviced or refurbished by a third party, the FDA’s Remanufacturing of Medical Devices guidance matters: servicing returns a device to the specification it was cleared with, while remanufacturing changes performance, safety characteristics or intended use and shifts the regulatory duties to whoever did the work. A service history that does not say which one occurred is incomplete, because the two carry different obligations.

Authenticity belongs in the same record. A service history is only as useful as the certainty that the part fitted was the part specified, which is the problem addressed in spotting counterfeit medical devices.

A worked example: what an interval is worth

The metrics that keep it honest

Three numbers do most of the work: mean time between failures, downtime rate, and preventive maintenance compliance expressed as completed tasks against scheduled tasks. Report them per asset class rather than as a facility average, because an average hides the device that is failing repeatedly.

Add a fourth if the facility compares in-house work with a contractor: service spend per asset per year. That figure is what turns a renewal conversation into a comparison, and it is only available if the schedule has been capturing cost alongside the task.

Where this is heading

Maintenance is moving from reactive repair to lifecycle optimisation, with condition monitoring and analytics supplying the intervals rather than a calendar. The direction is right, but the foundation is unchanged: a register that names every device, a schedule that reflects how each one is used, and records that show what was done and against which specification.

References

• WHO: Medical equipment maintenance programme overview — the maintenance strategy, and the split between performance inspections, safety inspections and preventive maintenance.
• FDA: Remanufacturing of Medical Devices — servicing against remanufacturing, final guidance May 2024.
• FDA: Reprocessing of Reusable Medical Devices.
• FDA: Medical Device Recalls and Early Alerts.

FAQ

What should a maintenance schedule include?

For every device: an identifier and location, an interval set from manufacturer guidance plus usage and criticality, the specific tasks, a named owner, and a record of each completed event with calibration data and parts used. Add performance inspections and safety inspections, not only preventive servicing.

How do I set intervals without a maintenance history?

Start from the manufacturer’s schedule and the device’s criticality, then tighten where a drift would change a clinical decision. Review after the first year against actual failures and move the interval on that evidence rather than leaving the initial guess in place.

Is a CMMS necessary?

A maintenance management system makes the schedule enforceable because it issues reminders and stores the history, but the minimum viable version is a shared register with a named owner and a monthly compliance review. Automation adds reliability; it does not replace the register.

How do I align schedules with regulatory expectations?

Map each device to the requirements that apply to it, define risk-based intervals, and document every preventive task with calibration records and technician sign-off. Then audit your own records quarterly, so that a regulatory inspection is a review of a working system rather than a reconstruction.

How can maintenance costs come down without adding risk?

Optimise intervals using performance data, compare in-house servicing with outsourced contracts on service spend per asset, and target monitoring at the assets where a failure is genuinely expensive. Cutting the interval on a low-consequence device saves money; cutting it on a dosing device does not.

Part of the Medical Equipment Maintenance & Service guide.