On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
This guide assists Clinical Engineering in troubleshooting situations where the Nellcor PM100N does not detect the SpO₂ sensor or displays intermittent or unstable readings. These issues are commonly caused by external factors such as sensor condition, cable connections, or patient-related variables before indicating internal hardware failure.
Step-by-Step Troubleshooting
Ensure Patient Safety First
- Do not troubleshoot on an active patient.
- Ensure the patient is moved to a functioning monitor before proceeding.
Verify the sensor is properly connected
- Ensure the SpO₂ sensor is fully seated in the monitor’s sensor port.
- A loose or partially inserted connector is a common cause of “sensor not detected” errors.
Inspect the sensor cable and connector
- Check for visible damage such as fraying, bent pins, or cracked connectors.
- Damaged sensors or cables can cause intermittent readings or failure to detect.
Try a known-good sensor
- Swap the sensor with a confirmed working SpO₂ sensor.
- This helps quickly determine if the issue is with the sensor or the monitor.
Check compatibility of the sensor
- Confirm that the sensor being used is compatible with the Nellcor PM100N.
- Using incorrect or non-approved sensors can result in detection errors.
Inspect the sensor port on the monitor
- Look for debris, bent pins, or damage inside the port.
- A contaminated or damaged port can interrupt communication with the sensor.
Ensure proper sensor placement on the patient (if applicable)
- Verify correct placement (finger, toe, etc.) with adequate perfusion.
- Poor placement or low perfusion can cause intermittent or inaccurate readings.
Check for motion artifact or environmental interference
- Excessive patient movement, vibration, or strong ambient light (e.g., surgical lights) can disrupt signal detection and cause unstable readings.
Confirm adequate patient perfusion
- Cold extremities, hypotension, or vasoconstriction can lead to weak signals.
- Try repositioning the sensor to a better-perfused site.
Power cycle the device
- Turn the monitor off, wait a few seconds, and power it back on.
- This can clear temporary communication faults.
Check for error messages or alarm indicators
- Note any specific alarms or messages related to sensor failure, as they may guide further action or indicate internal faults.
If the Problem Persists
If the sensor and cable have been verified as functional and all external causes have been ruled out, the issue is likely due to an internal fault such as a defective sensor port or signal processing failure.
- Removed from service
- Labeled Out of Service
- Sent for repair or bench evaluation
Recognizing when the issue is no longer external is an important part of proper troubleshooting.
Clinical Use Tip
Do not troubleshoot SpO₂ sensor issues on an active patient. Always transfer the patient to a functioning monitor before performing troubleshooting steps to ensure continuous monitoring and patient safety.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
“Unit not detecting SpO₂ sensor or showing intermittent readings during use.”
Cause
What was observed during troubleshooting.
Example:
“Failed SpO₂ sensor cable identified during troubleshooting (issue resolved when swapped with known-good sensor).”
Resolution
What action was taken.
Example:
“Replaced faulty SpO₂ sensor and verified proper operation.”
Helpful Details to Include
- Sensor swapped with known-good unit
- Port inspected for debris or damage
- Cable condition verified
- Alarm messages observed
- Patient factors (motion, perfusion) considered
- Power cycle performed
- Final device status (returned to service or sent for repair)
Final Thought
Effective troubleshooting of SpO₂ detection issues starts with simple, external checks such as sensors, cables, and patient conditions. Many problems can be resolved quickly without invasive action. When those factors are ruled out, escalating appropriately protects both patient safety and equipment reliability. Clear documentation ensures continuity and accountability.
That is successful troubleshooting.