On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
This guide addresses situations where the Apollo anesthesia machine:
- Touchscreen does not respond to touch inputs
- Control knobs fail to change settings or respond intermittently
- Navigation through menus is erratic or unresponsive
The guide focuses on external checks, user interface verification, and logical troubleshooting steps before assuming internal module or display failure.
Step-by-Step Troubleshooting
Confirm AC Power and Battery Status
- Verify the machine is connected to a reliable AC outlet.
- Check the battery charge level; a low battery can cause UI response issues.
- Why: Ensures the device has stable power; erratic touch or knob behavior can occur with insufficient power.
Inspect Touchscreen and Knobs for Physical Obstructions
- Check for protective films, debris, or liquids on the touchscreen surface.
- Rotate each control knob fully to ensure it moves freely without sticking.
- Why: Physical interference is a common, easily fixable cause of unresponsiveness.
Reboot the Machine
- Perform a proper shutdown and power-on cycle following Apollo startup procedure.
- Observe if touchscreen and knobs respond during POST (Power-On Self-Test).
- Why: Software glitches can temporarily disable user interface inputs.
Check for External Device Interference
- Remove USB drives, external monitors, or accessory modules connected to the Apollo.
- Why: Some connected peripherals can cause touchscreen or control knob conflicts.
Verify Software Version and Recent Updates
- Check the software version displayed on startup.
- Note any recent software updates that may correlate with the failure.
- Why: Certain firmware issues may affect UI responsiveness and may require manufacturer intervention.
Calibrate Touchscreen (If Available in Menu)
- Navigate to the calibration option (if responsive).
- Follow on-screen instructions to recalibrate.
- Why: Miscalibrated touchscreens can appear unresponsive even when functional.
Observe Behavior with Minimal Configuration
- Disconnect nonessential modules (e.g., monitoring interfaces) and restart.
- Test touchscreen and knobs.
- Why: Confirms whether the failure is isolated or caused by a module/software conflict.
If the Problem Persists
External checks have been exhausted.
Likely causes: internal touchscreen digitizer failure, control knob encoder malfunction, or mainboard issue.
- Remove machine from service.
- Label as “Out of Service.”
- Send for repair or bench evaluation.
Note: Stopping here is proper Clinical Engineering practice—further disassembly without service authorization may void warranty or compromise patient safety.
Clinical Use Tip
Never attempt to troubleshoot UI issues while a patient is on the machine.
Move the patient to an alternate anesthesia machine first.
Only interact with the unresponsive Apollo when it is safe to do so.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
“Touchscreen and control knobs are unresponsive during anesthesia setup.”
Cause
What was observed during troubleshooting.
Example:
“After verifying power, removing obstructions, and rebooting, touchscreen and knobs remained unresponsive.”
Resolution
What action was taken.
Example:
“Device removed from service, labeled Out of Service, and sent for manufacturer repair evaluation.”
Helpful Details to Include
- AC outlet tested and confirmed stable
- Battery charge level recorded
- Observed any screen flicker or partial responsiveness
- Noted control knob stiffness or lack of detent feedback
- Device final status before removal from service
Final Thought
Patient safety and proper escalation are paramount. Logical troubleshooting protects both patients and equipment. Always document actions clearly and escalate when external checks cannot resolve the issue.
That is successful troubleshooting.