On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshooting SpO2 dropout, poor signal, intermittent readings, or sensor recognition failures before repair escalation.
Step-by-Step Troubleshooting
Ensure Patient Safety First
Confirm the patient is clinically stable before disconnecting or swapping SpO2 sensors, cables, or modules.
If continuous SpO2 monitoring is required, move the patient to another working monitor or parameter source first.
Expected outcome: Patient oxygen saturation monitoring is maintained without relying on a questionable SpO2 channel.
Confirm the Exact SpO2 Complaint
Ask clinical staff what they observed. Determine whether the issue is:
- No SpO2 value displayed
- SpO2 drops out intermittently
- Sensor not recognized
- Poor signal or low perfusion message
- Pleth waveform missing or unstable
- Readings differ from another monitor
- Issue follows one patient, one sensor, one cable, or one monitor
Expected outcome: The issue is narrowed to sensor, patient condition, cable, parameter module, monitor configuration, or internal hardware.
Verify the Device Is Not Being Used on an Active Patient Before Testing
Do not perform repeated disconnects, cable manipulation, or reboot testing while the device is actively relied on for patient monitoring.
Expected outcome: Troubleshooting is performed only when safe.
Check the Patient and Application Site
Confirm the sensor is placed correctly and that the patient has adequate perfusion at the measurement site. Check for cold extremities, motion, nail polish, artificial nails, poor circulation, edema, or incorrect sensor placement.
Expected outcome: SpO2 signal improves when the sensor site is appropriate and properly applied.
If this resolves the issue, stop troubleshooting.
Inspect the SpO2 Sensor
Check the sensor for cracked housing, damaged cable jacket, exposed wires, contamination, bent connector pins, loose adhesive, or improper patient size.
Expected outcome: Sensor is physically intact, clean, compatible, and appropriate for the patient.
If the sensor is damaged or incorrect, replace it and stop if readings return.
Try a Known-Good Compatible Sensor
Connect a known-good Philips-compatible SpO2 sensor of the correct type.
Expected outcome: The monitor recognizes the sensor and displays a stable pleth waveform and SpO2 value.
If the known-good sensor works, remove the original sensor from use.
Inspect the SpO2 Extension Cable or Adapter Cable
Check for loose connections, damaged strain relief, bent pins, worn locking tabs, intermittent response when lightly moved, or contamination in the connector.
Expected outcome: Cable connection remains secure and signal does not drop out during gentle movement.
If the issue follows the cable, replace the cable and stop.
Reconnect the Sensor and Cable Firmly
Disconnect and reconnect the SpO2 sensor, extension cable, and monitor-side connector. Make sure each connector is fully seated.
Expected outcome: Sensor recognition returns and the SpO2 parameter remains stable.
If this resolves the issue, document a loose connection.
Check for Port or Module-Specific Behavior
If the IntelliVue 6000 Series configuration uses a parameter module, MMS, or external module rack, confirm the SpO2 source is properly seated and recognized by the monitor.
Expected outcome: The monitor detects the parameter source and displays SpO2 without intermittent loss.
If reseating the module restores SpO2, monitor the device briefly before returning it to service.
Swap the Parameter Source When Available
If a compatible known-good parameter module, MMS, or SpO2-capable source is available, test the monitor with that known-good source.
Expected outcome: The failure either follows the original module/source or remains with the monitor/connection point.
If the problem follows the module, remove that module from service.
Check Monitor Configuration and Parameter Display
Confirm SpO2 is enabled, assigned to the expected parameter area, and not hidden due to profile, screen layout, or parameter priority settings.
Expected outcome: SpO2 appears in the expected location when the parameter source is connected and active.
If configuration was the issue, restore the correct monitoring profile or screen layout.
Check for Alarm or INOP Messages
Review the monitor for SpO2-related messages such as no sensor, sensor off, poor signal, low perfusion, or parameter unavailable.
Expected outcome: The displayed message matches the observed failure and helps separate patient/sensor problems from device recognition problems.
Power Cycle Only When Clinically Safe
If the monitor is not in active clinical use, power cycle the monitor or reinitialize the parameter source according to local Clinical Engineering practice.
Expected outcome: Temporary software or communication recognition issues clear after restart.
If the issue returns, continue troubleshooting.
Inspect for Environmental or Interference Causes
Check whether dropout occurs during patient movement, cable tension, electrosurgical activity, transport, poor cable routing, or when the sensor cable is stretched or pinched.
Expected outcome: Dropout is not caused by motion, strain, routing, or external interference.
If rerouting or strain relief resolves the issue, document the correction.
Compare Against Another Monitor if Needed
Place the same known-good sensor and cable on another compatible monitor or test the suspect monitor with another known-good setup.
Expected outcome: The fault is isolated to the sensor, cable, module, monitor, or patient/application condition.
Perform a Final Functional Check
With a known-good sensor, cable, and parameter source, verify that the monitor recognizes SpO2, displays a stable pleth waveform, shows a believable saturation value, and responds appropriately to sensor removal.
Expected outcome: SpO2 acquisition is stable and sensor recognition is reliable.
If the Problem Persists
If the SpO2 signal still drops out or the sensor is not recognized after checking the patient site, sensor, cable, connections, module seating, configuration, and known-good accessories, common external causes have been ruled out.
The issue is likely internal to the SpO2 parameter source, module connector, acquisition hardware, monitor communication pathway, or monitor main unit. The device or affected module should be removed from service, labeled Out of Service, and sent for repair or bench evaluation.
Knowing when to stop is proper troubleshooting. Do not continue clinical use with unreliable oxygen saturation monitoring.
Clinical Use Tip
Do not troubleshoot SpO2 dropout on a patient who depends on that monitor for continuous oxygen saturation monitoring. Move the patient to another working monitor first, then evaluate the sensor, cable, module, and monitor safely.
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 6000 Series monitor intermittently lost SpO2 readings and displayed sensor recognition issues."
Cause
What was observed during troubleshooting.
Example:
"Troubleshooting found the SpO2 extension cable had an intermittent connection at the sensor interface, causing signal dropout when the cable was moved."
Resolution
What action was taken.
Example:
"Replaced the SpO2 extension cable, verified stable pleth waveform and SpO2 reading with a known-good sensor, and returned the monitor to service."
Helpful Details to Include (If Known)
- Patient was moved to another monitor before troubleshooting
- SpO2 sensor type and condition checked
- Known-good sensor tested
- Extension cable swapped
- Connector pins inspected
- Parameter module or MMS reseated
- Any SpO2 INOP or alarm message observed
- Pleth waveform behavior
- Whether dropout occurred with motion or cable movement
- Final device status
- Whether device was returned to service or sent for repair
Final Thought
SpO2 failures should be approached logically from the outside in. Patient condition, sensor placement, cable condition, accessory compatibility, and module seating should be checked before suspecting internal failure. Reliable oxygen saturation monitoring is a patient safety issue, and clear CCR documentation supports safe repair decisions and future troubleshooting.
That is successful troubleshooting.