Drager Primus

Touchscreen or Display Errors

On this page

Asset Type

Ventilator

Manufacturer

Drager

Model

Primus

What This Guide Helps With

This guide assists Clinical Engineering in troubleshooting Drager Primus ventilators that exhibit touchscreen or display errors. Display issues can prevent the user from seeing ventilator settings, alarms, or patient data, potentially affecting patient care. Most causes are external or easily verifiable before assuming internal electronic failure.

Step-by-Step Troubleshooting

Ensure Patient Safety First

Never attempt touchscreen troubleshooting on an actively ventilated patient. Move the patient to another ventilator before testing or powering off the device.

Check power connection

Verify battery status

Inspect the touchscreen surface

Check for visible damage

Perform a soft reboot

Check ventilator firmware and settings

Swap external peripherals

If the Problem Persists

External and software-related causes have been ruled out. Device should be:

Knowing when to escalate prevents further risk and preserves patient safety.

Clinical Use Tip

Never attempt touchscreen troubleshooting on an actively ventilated patient. Move the patient to another ventilator before testing or powering off the device. Ensure patient safety is maintained at all times.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
“Touchscreen unresponsive and display shows flickering or blank screen.”

Cause

What was observed during troubleshooting.

Example:
Observed that the ventilator operates normally on power cycle with no peripheral connections, but display fails intermittently. Cleaning and soft reboot did not correct the issue.

Resolution

What action was taken.

Example:
Device removed from clinical service, labeled Out of Service, and sent to biomedical engineering bench for display module evaluation or replacement.

Helpful Details to Include

Final Thought

Patient safety and logical, stepwise troubleshooting are paramount. Start with simple external checks, document every action with CCR, and escalate to repair when internal failure is suspected. Clear documentation supports safe, efficient operations and reduces repeat issues.

That is successful troubleshooting.

Related Guides

Was this guide helpful?

Don't see a guide you need?

Suggest a Guide