On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshoot unstable or missing SpO2 readings despite sensor detection, including probe, cable, positioning, perfusion, and compatibility problems.
Step-by-Step Troubleshooting
1. Ensure Patient Safety and Monitoring Continuity
- Confirm whether the patient requires continuous oxygen saturation monitoring.
- Arrange another verified SpO2 monitor if the B40 reading is absent or unreliable.
- Do not use an unstable SpO2 value to make clinical decisions.
- Perform technical verification using approved test equipment.
Expected outcome: Reliable oxygen saturation monitoring remains available throughout troubleshooting.
2. Confirm the SpO2 Symptom
- Determine whether the monitor detects the sensor but displays no value, an unstable value, or an unreliable pulse rate.
- Record displayed messages and waveform behavior.
- Identify the installed SpO2 technology and sensor type.
- Determine whether the issue affects one sensor or multiple sensors.
Expected outcome: The failure is clearly defined and the installed sensor system is identified.
3. Inspect the SpO2 Sensor
- Examine the sensor for damaged wiring, cracked housings, contamination, or damaged optical surfaces.
- Verify that the sensor is approved for the installed SpO2 technology.
- Check whether a reusable or disposable sensor is appropriate for the application.
- Replace a damaged or questionable sensor.
Expected outcome: The sensor is physically intact and compatible with the monitor.
4. Verify Sensor Positioning and Clinical Conditions
- Coordinate with clinical staff to confirm correct sensor placement.
- Check for excessive movement, poor contact, ambient light interference, or inappropriate sensor size.
- Consider whether low peripheral perfusion or other clinical conditions could affect signal acquisition.
- Do not interpret a technical test as a clinical assessment of the patient.
Expected outcome: Sensor placement and external signal conditions are appropriate.
5. Inspect the Extension Cable and Connections
- Check the sensor extension cable, if installed, for damage.
- Verify secure connections between the sensor, cable, and monitor or parameter module.
- Inspect accessible connectors for contamination or bent contacts.
- Substitute a known-good compatible cable.
Expected outcome: The external signal path is secure and undamaged.
6. Confirm Sensor Technology Compatibility
- Verify that the sensor and extension cable match the installed SpO2 module technology.
- Do not interchange sensors intended for different technologies unless explicitly approved.
- Check any accessible parameter configuration relevant to the installed module.
- Avoid unauthorized service-level changes.
Expected outcome: All SpO2 components are compatible and correctly configured.
7. Compare With Known-Good Accessories
- Install a known-good approved sensor.
- Repeat the test using a known-good extension cable if applicable.
- Compare the original and substitute accessories under the same controlled conditions.
- Remove any identified defective accessory from circulation.
Expected outcome: Accessory-related signal problems are isolated. If reliable operation returns and verification passes, troubleshooting can stop.
8. Perform Approved SpO2 Functional Testing
- Use a compatible SpO2 simulator or manufacturer-approved functional test method.
- Confirm that the test equipment supports the installed SpO2 technology.
- Verify displayed saturation and pulse-rate behavior against the applicable test method.
- Recognize that some functional testers verify signal processing but do not establish full clinical accuracy.
Expected outcome: The monitor responds correctly to the approved SpO2 test conditions.
9. Verify Alarms and Final Operation
- Test applicable SpO2 and pulse-rate alarms using approved procedures.
- Confirm that the plethysmographic waveform is stable during the functional test.
- Verify appropriate alarm annunciation.
- Document the final test results.
Expected outcome: SpO2 acquisition and applicable alarms operate reliably. If all required checks pass, troubleshooting can stop.
If the Problem Persists
External sensors, cables, compatibility, positioning, and test conditions have been evaluated. Remaining possibilities include SpO2 module electronics, optical signal processing, internal connections, or software-related faults.
Remove the B40 from service, label it Out of Service, and send it for repair or bench evaluation. Qualified personnel should use appropriate manufacturer documentation and approved SpO2 testing equipment. Only qualified personnel should repair or configure internal components.
Complete applicable SpO2 functional and alarm verification before return to service. Stopping external troubleshooting when no verified cause remains is appropriate troubleshooting.
Clinical Use Tip
A detected SpO2 sensor does not guarantee a valid saturation measurement. Confirm waveform quality and pulse-rate agreement with an independent clinical assessment when appropriate.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Clinical staff reported that the B40 recognized the SpO2 sensor but displayed an intermittent saturation value."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering identified a damaged SpO2 extension cable that interrupted reliable signal acquisition."
Resolution
What action was taken.
Example:
"Replaced the extension cable with an approved compatible accessory and verified stable simulated SpO2, pulse-rate display, and alarm operation."
Helpful Details to Include (If Known)
- Installed SpO2 technology
- Sensor model and type
- Displayed error or status message
- Plethysmographic waveform behavior
- Sensor and cable condition
- Positioning and environmental observations
- Known-good substitutions
- Functional tester compatibility
- Pulse-rate and saturation test results
- Alarm verification
Final Thought
Reliable SpO2 monitoring requires more than sensor recognition. Protect the patient, evaluate compatible accessories and signal conditions, and use approved functional testing before suspecting module failure. Escalate unresolved problems and document the complete troubleshooting sequence.
That is successful troubleshooting.