On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Modules not detected, intermittent communication loss, missing parameters, or module error messages due to connection, compatibility, or external interface issues.
Step-by-Step Troubleshooting
Ensure Patient Safety First
- If the module is required for active monitoring (e.g., gases, hemodynamics), transition the patient to alternate monitoring before troubleshooting.
- Expected: Patient monitoring remains uninterrupted.
- Why it matters: Loss of module data can compromise clinical decision-making.
Verify the Reported Issue
- Confirm the module is not recognized or displaying communication errors.
- Observe:
- Is the module completely missing from the screen?
- Are values intermittent or frozen?
- Are specific error messages displayed?
- Expected: Issue is reproducible and clearly identified.
- Why it matters: Confirms a true communication issue vs user misunderstanding or configuration.
Check Module Seating and Physical Connection
- Inspect the module placement in the slot.
- Remove the module and reseat it firmly.
- Ensure it clicks fully into place.
- Try a different slot if available.
- Expected: Module is recognized after reseating.
- Why it matters: Poor physical connection is the most common cause of module communication failure.
Inspect Module and Slot Contacts
- Visually inspect both the module connector and slot interface.
- Look for bent or damaged pins, debris, or contamination.
- Expected: Clean, undamaged connectors.
- Why it matters: Physical damage prevents proper data communication.
Swap with a Known Good Module
- Insert a known working module into the same slot.
- If the new module works → original module is faulty.
- If the new module also fails → slot or monitor issue.
- Why it matters: Quickly isolates whether the problem is module-specific or system-related.
Test the Suspect Module in Another Monitor
- Place the original module into a known working S5 monitor.
- If it works → issue is with original monitor.
- If it fails again → module failure confirmed.
- Why it matters: Confirms root cause without internal disassembly.
Check Module Compatibility and Configuration
- Verify the module is supported by the system.
- Confirm correct module type for the monitor configuration.
- Ensure no software mismatch or unsupported module type.
- Expected: Module is compatible with system configuration.
- Why it matters: Some modules may not be recognized if incompatible or improperly configured.
Reboot the Monitor
- Power cycle the monitor completely.
- Turn off the unit.
- Disconnect from AC power briefly if needed.
- Restart and allow full boot.
- Expected: Module is recognized after reboot.
- Why it matters: Clears temporary communication or initialization errors.
Check for Intermittent Behavior
- Gently observe if movement affects detection.
- Expected: No intermittent loss when module is stable.
- Why it matters: Intermittent detection often indicates worn connectors or internal slot issues.
If the Problem Persists
Common external causes have been ruled out. The issue is likely internal to the module interface, communication bus, or system board.
Remove the device from service, label it Out of Service, and send for repair or bench evaluation.
Clinical Use Tip
Do not troubleshoot module communication issues on an active patient. Always move the patient to another monitor before removing or reseating modules.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Gas module not recognized by S5 monitor; no readings displayed."
Cause
What was observed during troubleshooting.
Example:
"Faulty module identified after failing in multiple monitors."
Resolution
What action was taken.
Example:
"Removed module from service and sent for repair; replaced with working module."
Helpful Details to Include (If Known)
- Alarm behavior or module error messages
- Accessories or modules swapped during testing
- Power behavior during troubleshooting
- Environmental factors (movement, vibration)
- Indicator lights or slot detection behavior
- Final device status (working or removed from service)
Final Thought
Effective troubleshooting starts with simple connection checks and logical isolation. Patient safety comes first, and recognizing when a failure is internal is just as important as fixing external issues. Clear documentation ensures continuity and supports repair decisions.
That is successful troubleshooting.