On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshoots missing SpO2 detection caused by loose connections, damaged sensors or cables, incompatible accessories, configuration, or module communication problems.
Step-by-Step Troubleshooting
1. Protect the Patient and Provide Alternate Monitoring
Do not troubleshoot an unreliable SpO2 monitoring function while a patient depends on it. If oxygen saturation monitoring is required, place the patient on another verified pulse oximeter or monitoring system before disconnecting accessories or restarting equipment.
Confirm ventilation remains unaffected.
Expected outcome: The patient has uninterrupted respiratory support and reliable alternate SpO2 monitoring. Continue only after patient safety is protected.
2. Confirm the Exact Detection Problem
Determine whether:
- The SpO2 parameter is completely absent
- The module is not recognized
- The sensor is not detected
- The parameter appears but no patient signal is obtained
- Detection is intermittent
- The issue began after an accessory change
Record the exact displayed message or parameter status.
Expected outcome: The problem is clearly identified as module detection, sensor detection, or signal acquisition. If the parameter returns and remains stable during verification, troubleshooting can stop.
3. Inspect the External SpO2 Connections
Inspect all accessible connections from the ventilator or SpO2 module through the patient cable and sensor.
Look for:
- Partially inserted connectors
- Bent or damaged contacts
- Fluid contamination
- Broken latching features
- Cable strain
- Cuts or crushing
- Loose intermediate connections
Reseat each connection normally.
Expected outcome: All components are securely connected and undamaged. If reseating restores detection and stable measurement, verify operation and stop troubleshooting.
4. Verify Accessory Compatibility
Confirm the SpO2 module, patient cable, extension cable, and sensor are compatible with the Hamilton T1 configuration in use.
Avoid mixing visually similar but unsupported components.
Expected outcome: All installed components are appropriate for the ventilator and SpO2 technology in use. If an incompatible accessory is identified and replaced, normal detection returns.
5. Inspect the SpO2 Sensor
Inspect the sensor for:
- Damage to the optical surfaces
- Cracked housing
- Contamination
- Broken cable
- Damaged connector
- Excessive wear
If clinically appropriate, ensure the sensor is positioned correctly and not obstructed by materials that interfere with measurement.
Expected outcome: The sensor is intact and suitable for use. If a damaged sensor is replaced and the parameter operates normally, troubleshooting can stop.
6. Substitute a Known-Good Sensor
Connect a known-good compatible SpO2 sensor to the existing cable or module.
This helps determine whether the failure is isolated to the sensor.
Expected outcome: The known-good sensor is detected and produces a stable reading under appropriate test conditions. If so, remove the original sensor from use.
7. Substitute the Patient or Extension Cable
If a separate SpO2 patient cable or extension cable is used, replace it with a known-good compatible cable.
Flex the cable only through normal handling; do not aggressively manipulate damaged wiring to reproduce an intermittent condition.
Expected outcome: Detection remains stable with the known-good cable. If the issue is corrected, replace the faulty cable and stop troubleshooting after verification.
8. Inspect and Reseat the SpO2 Module if Externally Accessible
If the T1 configuration uses a removable external module or interface, verify that it is fully seated and its connection is clean and undamaged.
Do not open the ventilator or module housing.
Expected outcome: The module is securely connected and recognized. If normal operation returns after reseating, perform final verification and troubleshooting can stop.
9. Verify SpO2 Configuration
Confirm that SpO2 monitoring is enabled and available in the current ventilator configuration.
Do not modify restricted parameters, licensing, or service-level configuration without authorization and appropriate documentation.
Expected outcome: SpO2 monitoring is enabled and appropriately configured. If an approved configuration correction restores detection, verify operation and document the change.
10. Restart Only When Clinically Safe
If patient care has been transferred and normal operating procedures permit, perform a controlled ventilator restart to determine whether the module is recognized during startup.
Do not reboot a ventilator supporting a patient merely to test an accessory.
Expected outcome: The ventilator completes startup and detects the SpO2 hardware normally. If detection remains stable, continue to final verification.
11. Compare With Known-Good Hardware
When available, test the suspect SpO2 module and accessories on another compatible known-good system, or test a known-good module on the affected T1.
Use only approved combinations.
Expected outcome: Testing identifies whether the fault follows an accessory or remains with the ventilator. If the fault follows an accessory, remove that accessory from service.
12. Perform Final Functional Verification
After correction:
- Confirm the SpO2 module is detected
- Confirm the sensor is recognized
- Verify a stable saturation reading using an appropriate test method
- Confirm pulse rate information if applicable
- Verify associated alarms
- Check that the connection remains stable during normal handling
Expected outcome: SpO2 monitoring remains recognized and functional without intermittent loss. The ventilator may be returned to service after required testing passes.
13. Escalate if Detection Still Fails
If known-good compatible sensors, cables, and external module hardware are not detected, stop external troubleshooting.
Expected outcome: The ventilator is removed from service rather than returned with an unresolved monitoring interface problem.
If the Problem Persists
Common external causes involving loose connections, sensors, patient cables, module seating, accessory compatibility, and user-accessible configuration have been ruled out.
The remaining problem may involve the SpO2 interface, module electronics, internal communication, connector hardware, configuration, or another service-level issue.
The ventilator should be:
- Removed from service
- Labeled Out of Service
- Sent for repair or bench evaluation
- Evaluated using appropriate Hamilton documentation and approved test equipment
- Repaired or configured only by qualified personnel
Complete applicable functional testing, alarm testing, and return-to-service verification after repair.
Knowing when to stop external troubleshooting is proper troubleshooting.
Clinical Use Tip
Use a separate verified pulse oximeter whenever the ventilator's integrated SpO2 measurement is unavailable or unreliable during patient care.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Respiratory Therapy reported that the Hamilton T1 did not recognize the connected SpO2 sensor."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering found that the SpO2 patient cable had an intermittent connector and failed comparison with a known-good cable."
Resolution
What action was taken.
Example:
"Replaced the defective cable, verified sensor detection, stable SpO2 measurement, and alarm operation, and returned the ventilator to service."
Helpful Details to Include (If Known)
- Exact SpO2 status or message
- Whether the module was recognized
- Sensor type and condition
- Patient cable condition
- Extension cable condition
- Known-good sensor result
- Known-good cable result
- Module reseating result
- Configuration observed
- Whether detection survived restart
- Alarm verification result
- Final device status
Final Thought
Maintain continuous patient monitoring, then isolate the problem through the sensor, cables, module connection, compatibility, and configuration before assuming an internal failure. Verify stable detection and alarms after correction, and escalate when external causes have been exhausted.
That is successful troubleshooting.