On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshooting SureSigns VM Series SpO2 sensor, cable, connector, signal dropout, or sensor recognition failure before repair escalation.
Step-by-Step Troubleshooting
Ensure Patient Safety First
Confirm the SureSigns VM monitor is not the only active source of oxygen saturation monitoring before disconnecting sensors or cables.
If SpO2 monitoring is clinically required, have staff move the patient to another working monitor or use an approved alternate monitoring method first.
Expected outcome: Patient oxygenation monitoring is maintained safely during troubleshooting.
Confirm the Exact SpO2 Complaint
Ask clinical staff what they observed. Determine whether the issue is:
- No SpO2 reading
- Dashed or blank SpO2 value
- Sensor not detected
- Intermittent SpO2 dropout
- Poor pleth waveform
- Inaccurate or unstable reading
- Alarm or message related to SpO2 sensor, cable, or signal quality
Expected outcome: The issue is narrowed to patient condition, sensor placement, cable failure, accessory compatibility, connector issue, or monitor hardware.
Check the Patient and Sensor Site When Safe
Confirm the sensor is placed correctly and the site has adequate perfusion. Check for cold extremities, excessive motion, nail polish, artificial nails, poor circulation, bright ambient light, or improper sensor size.
Expected outcome: Patient-related signal problems are identified before replacing equipment.
Inspect the SpO2 Sensor
Check the sensor for cracked housing, damaged emitter/detector area, exposed wiring, loose strain relief, contamination, fluid intrusion, or worn adhesive if using a disposable sensor.
Expected outcome: A visibly damaged or contaminated sensor is removed from use and replaced.
Verify Proper Sensor Application
Reapply the sensor according to normal clinical use, ensuring the emitter and detector are aligned and the sensor is not too loose or too tight.
Expected outcome: A stable SpO2 value and pleth waveform return. If resolved, stop troubleshooting.
Check the SpO2 Extension Cable, If Used
Inspect the extension cable for bent pins, cracked connectors, intermittent strain relief, cuts, kinks, or loose locking connection. Reseat both ends firmly.
Expected outcome: A loose or damaged cable connection is corrected. If SpO2 returns, stop troubleshooting.
Swap the SpO2 Sensor With a Known-Good Sensor
Connect a compatible known-good Philips-approved SpO2 sensor to the same monitor and test on a simulator or appropriate test subject when safe.
Expected outcome: If the known-good sensor works, the original sensor is defective or incompatible and should be replaced.
Swap the Extension Cable With a Known-Good Cable
If the problem remains after replacing the sensor, test with a known-good compatible SpO2 extension cable.
Expected outcome: If the issue clears, replace the failed cable and return the monitor to service after verification.
Inspect the Monitor SpO2 Connector
Look at the SpO2 input port for bent pins, debris, cracked plastic, looseness, liquid residue, or signs of physical damage. Do not force a connector into the port.
Expected outcome: Connector damage or contamination is identified. If the port is damaged, remove the monitor from service.
Check Whether the Failure Follows the Accessory or the Monitor
Test the suspect sensor and cable on another compatible SureSigns VM monitor, if available. Then test known-good accessories on the suspect monitor.
Expected outcome: The failure is isolated to the sensor, cable, or monitor SpO2 input path.
Review SpO2 Settings and Display Configuration
Confirm SpO2 is enabled and being displayed as an active parameter. Check that the parameter has not been hidden, disabled, or affected by an incorrect profile or configuration.
Expected outcome: A configuration issue is corrected without replacing hardware.
Check for Repeated Dropout During Movement
Gently move the cable near the sensor end, extension connection, and monitor connector while observing the SpO2 reading and pleth waveform. Do not perform this on an active patient.
Expected outcome: Intermittent dropout during cable movement suggests cable or connector failure.
Power Cycle Only When Clinically Safe
If the monitor is not actively supporting patient care, power cycle the device and reconnect a known-good SpO2 sensor and cable.
Expected outcome: Temporary software or recognition issues clear. If resolved, verify stable operation before return to service.
Perform a Functional Check
Use a compatible SpO2 simulator or approved test method to confirm the monitor detects the sensor, displays SpO2, and maintains a stable waveform or numeric reading.
Expected outcome: The SureSigns VM passes a basic SpO2 functional check with known-good accessories.
If the Problem Persists
If the SpO2 issue remains after checking sensor placement, patient factors, accessory condition, cable integrity, connector seating, compatible known-good accessories, settings, and basic functional operation, common external causes have been ruled out.
The device should be:
- Removed from service
- Labeled Out of Service
- Sent for repair or bench evaluation
At that point, the issue may involve the monitor SpO2 input connector, internal acquisition circuitry, parameter board, or related internal hardware. Knowing when to stop is proper troubleshooting.
Clinical Use Tip
Do not troubleshoot SpO2 sensor or cable issues on an active patient if it interrupts required monitoring. Move the patient to another working monitor or use an approved alternate monitoring method first.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Clinical staff reported that the Philips SureSigns VM monitor would not display an SpO2 reading and showed intermittent sensor recognition."
Cause
What was observed during troubleshooting.
Example:
"Troubleshooting found the SpO2 extension cable had an intermittent connection when flexed near the monitor-side connector."
Resolution
What action was taken.
Example:
"Replaced the SpO2 extension cable, verified stable SpO2 reading with a known-good sensor, and returned the monitor to service."
Helpful Details to Include (If Known)
- Patient was moved to alternate monitoring before troubleshooting
- Exact SpO2 message or alarm observed
- SpO2 value blank, dashed, unstable, or intermittent
- Pleth waveform present, poor, or absent
- Sensor type tested
- Extension cable swapped
- Known-good sensor tested
- Known-good cable tested
- Monitor SpO2 port condition
- Whether issue followed the sensor, cable, or monitor
- Simulator or functional test result
- Environmental factors such as motion, cold extremities, bright ambient light, nail polish, artificial nails, or poor circulation
- Indicator lights, sensor recognition behavior, or displayed SpO2 status
- Final device status
Final Thought
SpO2 failures should be approached logically and safely. Start with patient condition, sensor placement, cable condition, accessory compatibility, and connector seating before suspecting internal monitor failure. Clear CCR documentation supports patient safety, repair decisions, and future troubleshooting.
That is successful troubleshooting.