Patient monitors generate a steady stream of service calls in every hospital, and a large share of them are not monitor failures at all. Cables, leads, sensors, and network drops account for a big portion of "monitor is broken" tickets.
This guide walks the failure categories in the order a working BMET should check them: accessories first, then modules, then the monitor itself, then the network. Working in that order keeps you from opening a chassis on a bad SpO2 cable.
Start with accessories, always
Before any teardown, swap the accessory. Leads, SpO2 sensors, NIBP hoses, and temperature probes take the most physical abuse in the room and fail far more often than the monitor electronics behind them.
If a known-good accessory clears the fault, document the part swapped and close it. Do not go deeper.
- Swap the suspect cable or sensor with a known-good one and reproduce the complaint
- Inspect connectors for bent pins, corrosion, and cleaning-solution ingress
- Check the lead wires for intermittent breaks by flexing while watching the trace
- Confirm the accessory is an approved part for that monitor model — third-party sensors cause plenty of false artifact calls
Display and touchscreen faults
Display complaints break into three buckets: no image, degraded image, and unresponsive touch. Each points somewhere different.
- No image but the unit powers and alarms audibly — backlight or inverter/LED driver, or a seated-but-failed display cable
- Dim, flickering, or color-shifted image — backlight aging or driver board; common on monitors past 7-8 years
- Dead zones or drifting touch — digitizer damage or a calibration drift; run the OEM touch calibration before condemning the panel
- Image present but frozen while alarms continue — main processor board or software fault, not the display
SpO2, ECG, and NIBP module failures
Modular monitors make this straightforward: move the suspect module to a known-good host, and move a known-good module into the suspect host. That single test separates module failure from backplane or host failure in under five minutes.
On integrated monitors the same logic applies through the parameter self-tests. Run the built-in test with a simulator attached and record actual versus expected values — that record is what makes the repair defensible later.
- ECG: verify against a patient simulator at multiple rates, check lead-off detection on every lead
- SpO2: verify against a simulator at a known saturation, check the probe and the extension cable separately
- NIBP: leak-test the pneumatic circuit first, then verify pressure accuracy against a calibrated gauge, then check overpressure cutoff
- Temperature: verify at two points across the clinical range, not just one
Power problems
Random reboots, failure to charge, and short battery runtime are the three you will see. Batteries are the first suspect and the cheapest fix — check cycle count and capacity before touching the power supply.
If the battery tests good and the unit still reboots under load, look at the DC power supply board and the internal power connectors. Intermittent reboots that follow physical movement are almost always a connector or solder joint, not a component.
Network and central station dropouts
A monitor that "keeps disconnecting" is usually a network problem, not a device problem. Before escalating to biomed repair, establish whether the drop is device-specific or location-specific: move the monitor to a different port or room and see if the fault follows the device.
- Fault follows the monitor — network card, antenna, or monitor configuration
- Fault stays with the room or port — cabling, switch port, or wireless coverage; this is an IT ticket
- Multiple monitors dropping at once — infrastructure or central station, escalate immediately
Document it so the next tech is not starting over
The most valuable part of a monitor repair is not the fix — it is the record. A monitor with three vague "checked, no fault found" entries in its history is a monitor nobody can make a replace decision about.
Record the exact complaint, what you swapped, the simulator values you measured, and the outcome. That history is what turns the fourth service call into a five-minute diagnosis.