On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Addresses unresponsive display adjustment caused by locked controls, touchscreen or key problems, software state, configuration, or display failure.
Step-by-Step Troubleshooting
1. Protect the Patient and Confirm Display Usability
Do not use the GlideScope for airway management if the display cannot be viewed adequately in the clinical environment. Provide another verified visualization device before troubleshooting.
If the screen is excessively dark, unstable, or unreadable, remove the system from active use.
Expected outcome: Patient care continues with a clearly visible, reliable display.
2. Confirm the Exact Adjustment Problem
Determine whether brightness cannot be increased, cannot be decreased, returns to a previous level, or whether all display controls are unresponsive. Ask whether the issue affects touchscreen controls, physical keys, or both.
Reproduce the complaint away from patient care.
Expected outcome: The affected control and display behavior are identified.
3. Verify Normal Startup and System Responsiveness
Power-cycle the monitor using the normal operator control. Confirm it reaches the standard operating screen and that other menus or functions respond.
Do not repeatedly interrupt startup if the unit is in a boot loop or update state.
Expected outcome: The system starts normally and responds to basic controls. If the entire system is frozen, follow software-freeze troubleshooting instead.
4. Clean and Inspect the Touchscreen or Keys
Check for gloves, moisture, disinfectant residue, protective film, labels, or physical obstruction affecting the controls. Clean and dry the external control surfaces using approved methods.
Inspect buttons for sticking, damage, or incomplete travel.
Expected outcome: Controls are clean, dry, and mechanically unobstructed.
5. Confirm the Correct Adjustment Method
Navigate through the normal user-accessible display controls for the specific GlideScope configuration. Verify that the technician is adjusting brightness rather than another image parameter.
Do not enter unauthorized service menus or change restricted configuration settings.
Expected outcome: The correct control is selected and the displayed setting changes normally. If adjustment is restored, complete final verification and stop troubleshooting.
6. Check for Control Lock or Restricted Profile
Determine whether a user-accessible lock, clinical profile, or facility configuration limits display changes. Compare with another identical verified system if available.
Do not bypass passwords or alter protected settings without authorization.
Expected outcome: Any authorized control restriction is identified and corrected through the approved process.
7. Test Under Different Ambient Lighting
Move the monitor away from direct overhead lighting, sunlight, or strong reflections. Confirm that apparent brightness problems are not caused by glare or viewing angle.
Adjust the monitor position and cart height as appropriate.
Expected outcome: The screen remains readable in a normal clinical environment.
8. Compare Touchscreen and Physical Controls
If the system provides more than one user input method, test each approved method. Determine whether only one control path fails.
Expected outcome: The issue is isolated to the touchscreen, a physical control, or the display-setting function itself.
9. Compare With a Known-Good System
Use another verified GlideScope of the same configuration to compare menu behavior, available settings, and visible brightness range.
Do not copy configuration files or settings unless authorized.
Expected outcome: The suspect unit’s behavior is confirmed as abnormal rather than a normal model limitation.
10. Perform Final Functional Verification
Verify the setting changes through its available range, remains at the selected level after normal navigation or restart when designed to do so, and leaves the live image and menus clearly visible.
Check other basic controls and live video before return to service.
Expected outcome: Brightness and display settings respond reliably. The system may return to service after all required checks pass.
If the Problem Persists
External contamination, user-accessible controls, normal configuration, ambient lighting, and control methods have been evaluated. The remaining cause may involve the touchscreen, keypad, display controller, software, restricted configuration, backlight, or internal display assembly.
Remove the system from service, label it Out of Service, and send it for qualified repair or bench evaluation using the applicable manufacturer documentation and approved test equipment. Do not open the display or enter unauthorized service modes.
Return-to-service testing must verify readable display output, reliable control response, live-image visibility, and normal startup. Knowing when to stop protects against returning a visually unreliable airway device to service.
Clinical Use Tip
Confirm display visibility from the operator’s expected position before airway instrumentation begins.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Clinical staff reported that the GlideScope screen brightness would not increase using the touchscreen control."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering found dried disinfectant residue on the touchscreen that prevented reliable input."
Resolution
What action was taken.
Example:
"Clinical Engineering cleaned and dried the touchscreen according to approved procedures and verified repeated brightness adjustment and a clear live image."
Helpful Details to Include (If Known)
- Brightness or setting affected
- Touchscreen or physical-key response
- Startup behavior
- Control lock or profile observed
- Ambient lighting and glare
- Surface contamination
- Comparison-unit results
- Setting behavior after restart
- Live-image visibility
- Final device status
Final Thought
Ensure the display is clinically usable, verify simple control and environmental causes before assuming display failure, avoid unauthorized configuration changes, and document the final verified condition.
That is successful troubleshooting.