Puritan Bennett 980

Touchscreen or GUI Unresponsive

On this page

Asset Type

Ventilator

Manufacturer

Puritan Bennett

Model

980

What This Guide Helps With

Troubleshooting a frozen, blank, inaccurate, intermittently responsive, or completely unresponsive GUI caused by contamination, software state, power, connections, or display failure.

Step-by-Step Troubleshooting

1. Ensure Patient Safety First

Do not troubleshoot an unresponsive touchscreen or GUI while the Puritan Bennett 980 is actively supporting a patient.

Expected outcome: The patient is safely supported without relying on a ventilator whose settings cannot be reliably viewed or changed.

Continue Clinical Engineering troubleshooting only after the affected PB980 has been removed from patient use.

2. Confirm the Exact GUI Failure

Determine whether the problem involves:

Observe the separate status display on the breath delivery unit for power, ventilation, alarm, or fault information. The PB980 includes this additional display as a redundant indication of ventilator operation.

Expected outcome: The failure is clearly identified as a display, touchscreen-input, startup, or complete ventilator problem.

3. Check for Screen Contamination or Physical Interference

Inspect the touchscreen for:

Power the ventilator off before cleaning. Clean the screen only with products and methods approved by the manufacturer and facility policy. Do not spray liquid directly onto the GUI.

Allow the screen to dry fully before testing.

Expected outcome: The display surface is clean, dry, unobstructed, and free from visible damage.

If normal touch operation returns, complete an operational verification and stop troubleshooting.

4. Verify That the GUI Is Not Locked or Awaiting Confirmation

Review the displayed screen for:

Attempt to operate several different on-screen controls rather than repeatedly pressing one location.

Expected outcome: A screen lock, open prompt, or software-navigation condition is either identified and cleared or ruled out.

If the GUI responds normally afterward, verify all critical controls and stop troubleshooting.

5. Check External Power and Power Indicators

Verify:

Test the outlet with an approved electrical tester or known-good device when permitted.

A blank GUI accompanied by loss of all ventilator indicators suggests a broader power problem rather than an isolated touchscreen failure.

Expected outcome: Stable external power is confirmed, and the issue is isolated to the GUI or touchscreen when other ventilator indicators remain operational.

6. Inspect the GUI Assembly and External Connections

With the ventilator powered off and disconnected from the patient:

Expected outcome: The GUI mounting and externally accessible connections are secure and undamaged.

If a loose external connection is found and can be safely corrected without internal disassembly, secure it and retest the ventilator.

7. Perform a Controlled Restart

Only after the ventilator has been removed from patient service:

Do not repeatedly cycle power if the GUI continues freezing or restarting. Repeated restarts can obscure an intermittent fault without correcting its cause.

Expected outcome: The GUI completes startup, displays information correctly, and responds consistently to touch.

If the restart restores operation, continue with functional verification before returning the ventilator to service.

8. Check for Startup Errors, Alarms, or Diagnostic Information

Record all displayed or status-screen information, including:

Photograph or transcribe the information according to facility policy before restarting the ventilator again.

Expected outcome: Available fault information is preserved for repair evaluation and vendor support.

9. Test the Entire Touchscreen

When the GUI is responsive, test controls across multiple areas of the screen:

Watch for:

Do not rely on a touchscreen that works only in certain areas.

Expected outcome: The full active touchscreen area responds accurately and consistently.

If any dead zone or inaccurate response remains, remove the ventilator from service.

10. Remove External Accessories That May Affect Operation

Disconnect nonessential external accessories one at a time while the ventilator is powered off, such as:

Restart and retest after removing questionable accessories.

Do not disconnect required gas or breathing-system components during a formal performance test.

Expected outcome: An external accessory or communication connection is either identified as the cause or ruled out.

If the GUI operates normally after an accessory is removed, inspect or replace that accessory and document the finding.

11. Complete an Operational Verification

Before returning the PB980 to clinical use:

The manufacturer provides the PB980 operator’s manual and supporting reference materials as the primary instructions for operation and verification.

Expected outcome: The ventilator completes required testing with a stable, accurate, and fully responsive GUI.

If the issue was resolved but cannot be confidently duplicated or verified, keep the ventilator out of service for further observation or bench evaluation.

If the Problem Persists

If the GUI remains blank, frozen, inaccurate, intermittently responsive, or unable to complete startup after external causes have been ruled out, the problem is likely internal.

Possible internal causes may involve the touchscreen assembly, GUI electronics, power distribution, communication path, software, processor, or breath delivery unit interface. Internal diagnosis should follow the current manufacturer service documentation and facility authorization requirements.

The ventilator should be:

Do not return the ventilator to clinical use solely because the touchscreen begins responding temporarily. Knowing when to stop and escalate is proper troubleshooting.

Clinical Use Tip

Never troubleshoot an unreliable GUI while the PB980 is connected to an active patient. Move the patient to another verified ventilator before restarting, cleaning, disconnecting accessories, or evaluating controls.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"Respiratory therapy reported that the Puritan Bennett 980 GUI displayed ventilation information but did not respond to touchscreen selections."

Cause

What was observed during troubleshooting.

Example:
"Touchscreen remained unresponsive after cleaning, verifying AC power, inspecting accessible GUI connections, removing external accessories, and performing a controlled restart."

Resolution

What action was taken.

Example:
"Ventilator was removed from service, labeled Out of Service, and routed for bench evaluation of the GUI and communication hardware."

Helpful Details to Include (If Known)

Final Thought

A PB980 with unreliable controls presents a serious patient-safety risk even when ventilation appears to continue. External-first troubleshooting, controlled testing, timely escalation, and complete CCR documentation protect both patients and the repair process.

That is successful troubleshooting.

Related Guides

Was this guide helpful?

Don't see a guide you need?

Suggest a Guide