On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshoots unresponsive controls caused by startup state, contamination, obstruction, connection, software lockup, external accessories, or control-panel faults.
Step-by-Step Troubleshooting
1. Protect the Patient From Loss of Control or Alarm Access
Do not troubleshoot an unresponsive user interface while an infant depends on the OmniBed for thermal control, oxygen support, alarms, or other active functions.
Transfer the infant to another verified device if critical controls or displayed information cannot be reliably accessed.
Expected outcome: Patient care no longer depends on an unreliable user interface.
2. Confirm Which Interface Function Is Affected
Determine whether the problem involves:
- Entire display blank
- Display visible but touchscreen does not respond
- Only one touch region fails
- Encoder does not turn or select
- Keypad button does not respond
- Controls respond intermittently
- Interface freezes after startup
- Unit continues operating despite loss of control input
Expected outcome: The failed control or display function is clearly identified.
3. Verify Basic Power and Startup Status
Confirm the OmniBed has reliable AC power and completes its normal startup sequence.
If the screen is blank, distinguish between a complete power failure and a display-only problem by observing other indicators, sounds, or equipment activity.
Expected outcome: The issue is isolated to the interface rather than the entire power system.
4. Inspect the Touchscreen and Controls Externally
Check for:
- Fluid or cleaning residue
- Adhesive film
- Gloves or objects pressing against the screen
- Physical cracks
- Impact damage
- Stuck buttons
- Debris around the encoder
- Loose external trim
Clean only according to approved equipment-cleaning practices.
Expected outcome: The controls are unobstructed, clean, and physically intact. If cleaning or removing an obstruction restores reliable operation, troubleshooting can stop after verification.
5. Check for Continuous Accidental Input
Ensure no accessory, cable, linen, or stored item is contacting a touchscreen region, button, or encoder.
Continuous unintended contact may make normal input appear unresponsive.
Expected outcome: No external object is interfering with control input.
6. Perform a Controlled Restart
With no patient dependent on the device, shut down and restart the OmniBed using the normal authorized procedure.
Observe whether the interface becomes responsive and whether the freeze returns.
Do not repeatedly power-cycle a device that shows signs of electrical failure, overheating, or corrupted startup behavior.
Expected outcome: The display and controls initialize normally and remain responsive.
7. Remove Nonessential External Connections
Disconnect nonessential external communication or accessory connections that can safely be removed, then restart and retest the interface.
Reconnect devices individually if normal operation returns.
Expected outcome: An external accessory or communication connection is either ruled out or identified as contributing to the problem.
8. Test All Normal Interface Functions
If responsiveness returns, test the touchscreen across its normal accessible regions and verify the encoder, keypad, visual display, and applicable audible feedback.
Do not access restricted service menus merely to test the screen.
Expected outcome: All normal control inputs respond consistently without missed, repeated, or unintended selections.
9. Verify Critical Functions Before Return to Service
Confirm that the interface can reliably display and adjust the normal operational functions required for patient care and that alarm information remains visible and accessible.
A control panel that fails intermittently should not be returned to service simply because it works after one restart.
Expected outcome: Display and controls remain stable through repeated normal operation. Troubleshooting can stop.
If the Problem Persists
If power, contamination, obstructions, restart behavior, and external connections have been ruled out, the problem may involve the touchscreen assembly, encoder or keypad hardware, display electronics, internal communication, processor, software, wiring, or another service-level control fault.
The OmniBed should be:
- Removed from service
- Labeled Out of Service
- Sent for repair or bench evaluation
- Evaluated using current GE Healthcare service documentation and approved test equipment
- Repaired or configured only by qualified personnel
Do not use an incubator with intermittent access to critical controls or alarm information. Complete full interface, alarm, thermal-control, and applicable functional testing before return to service.
Knowing when to stop external troubleshooting and escalate is proper troubleshooting.
Clinical Use Tip
An OmniBed that continues heating does not remain clinically reliable if staff cannot consistently view or change controls and respond to alarms.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"NICU staff reported that several areas of the OmniBed touchscreen did not respond to touch."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering found dried cleaning residue across the touchscreen surface that interfered with reliable touch input."
Resolution
What action was taken.
Example:
"Cleaned the display using the approved cleaning method, verified consistent touchscreen, encoder, and keypad response, and completed functional testing before return to service."
Helpful Details to Include (If Known)
- Display on or blank
- Touchscreen region affected
- Encoder response
- Keypad response
- Physical or liquid damage
- Cleaning residue or obstruction
- Startup behavior
- Result after controlled restart
- External accessories connected
- Intermittent versus continuous failure
- Alarm display and control response
- Final device status
- Display on or blank
- Touchscreen region affected
- Encoder response
- Keypad response
- Physical or liquid damage
- Cleaning residue or obstruction
- Startup behavior
- Result after controlled restart
- External accessories connected
- Intermittent versus continuous failure
- Alarm display and control response
- Final device status
Final Thought
Separate a true interface failure from basic power, contamination, external interference, or a temporary startup problem before assuming internal electronics are defective. Because the interface provides access to critical neonatal controls and alarms, any unreliable input system requires appropriate escalation and documented verification.
That is successful troubleshooting.