Drager Apollo Anesthesia Machine

Touchscreen or Control Knob Failure

On this page

Asset Type

Anesthesia Machine

Manufacturer

Drager

Model

Apollo

What This Guide Helps With

This guide addresses situations where the Apollo anesthesia machine:

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

Inspect Touchscreen and Knobs for Physical Obstructions

Reboot the Machine

Check for External Device Interference

Verify Software Version and Recent Updates

Calibrate Touchscreen (If Available in Menu)

Observe Behavior with Minimal Configuration

If the Problem Persists

External checks have been exhausted.

Likely causes: internal touchscreen digitizer failure, control knob encoder malfunction, or mainboard issue.

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

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.

Related Guides

Was this guide helpful?

Don't see a guide you need?

Suggest a Guide