On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshooting ECG, SpO2, and NIBP acquisition failures caused by accessories, patient connection, settings, or monitor input issues.
Step-by-Step Troubleshooting
Ensure Patient Safety First
Confirm the Philips IntelliVue MX100 is not the only active source of patient monitoring before disconnecting ECG leads, SpO2 sensors, NIBP tubing, or accessories.
If the patient requires continuous monitoring, have clinical staff move the patient to another verified monitor first.
Expected outcome: Patient monitoring remains safe while the suspect MX100 is evaluated.
Confirm Which Parameter Is Failing
Ask clinical staff whether the issue affects ECG, SpO2, NIBP, or all three. Determine whether the failure is constant, intermittent, or only occurs during movement, transport, docking, or after patient admission.
Expected outcome: The issue is narrowed to one acquisition path, multiple accessories, patient setup, configuration, or monitor hardware.
Check for On-Screen Messages or Missing Parameter Tiles
Look for lead-off messages, SpO2 sensor messages, NIBP timeout messages, dashed values, missing waveforms, or unavailable parameter indicators.
Expected outcome: The monitor provides clues about whether the issue is accessory-related, patient-related, setup-related, or internal.
Verify the Correct Patient and Monitoring Setup
Confirm the patient is admitted or assigned correctly if the monitor is connected to a central station or networked monitoring system. Check that the expected parameters are enabled and visible on the screen layout.
Expected outcome: Parameter failure is not being mistaken for a patient assignment, display layout, or configuration issue.
Check ECG Electrodes and Skin Contact
Inspect ECG electrodes for dryness, poor adhesion, expired pads, loose snaps, hair, lotion, sweat, or poor skin preparation. Replace electrodes if questionable.
Expected outcome: ECG waveform and heart rate return if the issue was caused by poor electrode contact. If resolved, stop.
Inspect the ECG Lead Set and Trunk Cable
Check the ECG lead wires and trunk cable for bent pins, cracked insulation, loose snaps, pulled strain reliefs, fluid contamination, or intermittent connection when gently moved.
Swap with a known-good ECG cable set when available.
Expected outcome: If ECG acquisition returns with a known-good cable, replace the defective accessory and stop.
Check SpO2 Sensor Placement and Condition
Verify the SpO2 sensor is properly positioned, appropriate for the patient, and not placed on a cold, poorly perfused, moving, or restricted extremity. Inspect for damaged sensor clips, worn adhesive, or cable kinks.
Expected outcome: SpO2 value and pleth waveform return if the issue was caused by sensor placement or patient signal quality. If resolved, stop.
Swap the SpO2 Sensor and Interface Cable
Use a known-good compatible SpO2 sensor and cable. Avoid assuming monitor failure until the sensor and cable have been ruled out.
Expected outcome: If SpO2 acquisition works with the known-good sensor or cable, remove the defective accessory from service and stop.
Check NIBP Cuff Size and Placement
Confirm the cuff is the correct size, applied snugly, aligned properly, and placed on an appropriate limb. Make sure the cuff is not over clothing, folded, loose, or leaking.
Expected outcome: NIBP readings complete successfully if the issue was caused by cuff size or placement. If resolved, stop.
Inspect the NIBP Hose and Cuff for Leaks or Blockage
Check the cuff bladder, hose, fittings, and connectors for cracks, loose connections, pinching, fluid contamination, or audible leaks during inflation.
Swap with a known-good cuff and hose.
Expected outcome: If NIBP completes with known-good accessories, replace the failed cuff or hose and stop.
Check the MX100 Input Connectors
Inspect ECG, SpO2, and NIBP connection points for bent pins, damaged ports, loose fit, debris, or signs of fluid intrusion. Do not force connectors into the monitor.
Expected outcome: Visible connector damage supports removing the device from service for bench evaluation.
Power Cycle the Monitor Only When Safe
If the MX100 is not connected to an active patient, restart the monitor and allow it to fully boot. Recheck ECG, SpO2, and NIBP using known-good accessories.
Expected outcome: A temporary software or acquisition lockup may clear. If acquisition returns, document the restart and monitor performance.
Test the Monitor Off Patient Using Known-Good Accessories
On the bench, connect known-good ECG leads, SpO2 sensor, and NIBP cuff/hose using approved test methods or simulators available to Clinical Engineering.
Expected outcome: If all parameters pass with known-good accessories, the original failure was likely accessory, patient setup, or use-condition related.
Look for Pattern Across Multiple Parameters
If ECG, SpO2, and NIBP all fail at the same time, consider shared causes such as configuration, power instability, software lockup, damaged connector area, fluid exposure, or internal acquisition failure.
Expected outcome: Multiple simultaneous parameter failures increase suspicion of monitor-level failure after external causes are ruled out.
Check Battery and External Power Stability
Confirm the monitor has stable power and is not shutting down, rebooting, or dropping parameters during low battery or charging transitions.
Expected outcome: Parameter acquisition should remain stable on known-good AC power or a properly charged battery.
Remove From Service if Failure Remains
If ECG, SpO2, or NIBP acquisition still fails after known-good accessories, safe restart, proper setup, and bench checks, remove the MX100 from clinical use.
Expected outcome: The device is properly escalated instead of repeatedly returned with an unresolved monitoring issue.
If the Problem Persists
Common external causes have been ruled out, and the issue is likely related to internal acquisition hardware, connector damage, internal communication, software corruption, or power-related monitor failure.
The device should be:
- Removed from service
- Labeled Out of Service
- Sent for repair or bench evaluation
Knowing when to stop is proper troubleshooting. Do not continue swapping accessories on an active patient or return the monitor to use if acquisition remains unreliable.
Clinical Use Tip
Do not troubleshoot ECG, SpO2, or NIBP acquisition failures on an active patient unless clinical staff have already transferred monitoring to another reliable device. Loss of ECG, oxygen saturation, or blood pressure monitoring can create a patient safety risk, especially in higher-acuity areas.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Clinical staff reported that the Philips IntelliVue MX100 was not acquiring ECG, SpO2, or NIBP readings during patient monitoring."
Cause
What was observed during troubleshooting.
Example:
"Troubleshooting found that ECG leads, SpO2 sensor, and NIBP cuff/hose were checked with known-good accessories, but parameter acquisition remained intermittent."
Resolution
What action was taken.
Example:
"Removed the MX100 from service, labeled it Out of Service, and sent it for bench evaluation due to suspected monitor acquisition or connector failure."
Helpful Details to Include (If Known)
- Whether ECG, SpO2, NIBP, or all parameters failed
- Exact alarm, INOP, or message displayed
- Whether waveforms, numerics, or both were missing
- Patient assignment or central station behavior
- ECG electrodes replaced
- ECG cable swapped
- SpO2 sensor and interface cable swapped
- NIBP cuff and hose swapped
- Whether NIBP inflated, timed out, or failed to start
- Battery and external power status
- Any connector damage, looseness, fluid exposure, heat, smell, or unusual behavior
- Final device status
Final Thought
ECG, SpO2, and NIBP acquisition problems should be approached logically from the outside in. Verify patient safety first, then rule out patient setup, accessories, cables, settings, and power before suspecting internal failure. Clear CCR documentation protects patient safety, supports repair decisions, and helps prevent repeat unresolved work orders.
That is successful troubleshooting.