Patient Monitoring Engineering
ECG/SpO2/NIBP/capnography fundamentals in depth, simulator-based verification, network/telemetry layer isolation, and alarm limit configuration.
Patient monitors combine several independent parameter modules - ECG, SpO2, NIBP, capnography, invasive pressure, temperature - each with its own measurement principle and its own real, distinct failure modes. Treating "the monitor" as one thing rather than a bundle of separate subsystems is the most common way troubleshooting time gets wasted on this equipment class.
Parameter-by-parameter verification
A multi-parameter patient simulator is the right tool for essentially all of them: it injects a known ECG waveform, a known SpO2 signal, and a known pressure into the monitor and lets you compare the display against ground truth, rather than trusting a self-test pass. NIBP deserves particular attention because it's the one parameter that's both mechanical (pump, valve, cuff) and algorithmic (oscillometric calculation) - verify cuff pressure against a calibrated reference manometer, not just the monitor's own reading of itself, since a monitor can accurately report a pressure its own pump/valve system is actually generating incorrectly.
Capnography specifics
Capnography (end-tidal CO2) modules come in two real designs with different service implications: mainstream sensors sit directly in the breathing circuit and need periodic cleaning of the optical window, while sidestream sensors draw a sample through tubing to a remote sensor and are prone to occlusion from condensation or secretions in that sampling line - a "no CO2 reading" complaint on a sidestream system is very often a clogged sample line, not a sensor fault.
Isolating the network/telemetry layer
When a monitor's central-station or telemetry connection is involved, the fault isolation question changes: is this a bedside-module problem, a network/access-point problem, or a central-station software problem? A useful first test is checking whether the same bedside unit fails identically at a different physical location on the same network - if the fault follows the unit, suspect the bedside hardware; if it stays tied to the location, suspect the local network infrastructure; if multiple units at multiple locations show the same intermittent issue simultaneously, suspect the central station itself.
Alarm limit configuration
Alarm limits are commissioned per care area, not left at factory default - a neonatal unit's heart-rate alarm range looks nothing like an adult ICU's, and a monitor moved between units without a limit-profile change will either alarm constantly on normal readings or fail to alarm on a genuinely abnormal one. Confirming the correct population profile is loaded is a real commissioning and PM check, not an assumption to skip.