On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
This guide addresses situations where the GE Carestation 600 touchscreen or software:
- Does not respond to user input (touchscreen unresponsive)
- Responds intermittently or with delays
- Shows frozen screens, error messages, or unexpected reboots
- Exhibits software glitches affecting workflow
The guide focuses on external, easily verifiable issues first—such as power, connections, and software resets—before considering internal hardware or software failures.
Step-by-Step Troubleshooting
Verify Power and Battery Backup
- Ensure the machine is plugged into a properly functioning outlet. Test the outlet if necessary.
- Check the UPS or battery backup (if applicable) for sufficient charge.
- Why: Touchscreen and software errors can be caused by unstable power.
Inspect Cables and Connections
- Confirm all external cables (power, network, USB devices) are firmly seated.
- Remove any recently added peripherals that could interfere with the touchscreen.
- Why: Loose connections can cause system freezes or touchscreen errors.
Perform a Soft Reboot
- Use the machine’s standard restart procedure (via the touchscreen menu or power button).
- Wait for the system to fully reboot and check touchscreen response.
- Why: Temporary software glitches are often resolved with a controlled reboot.
Check for System Alerts or Error Messages
- Review the error logs or alerts displayed on the monitor.
- Record any recurring messages for documentation.
- Why: Persistent errors may indicate a software or module problem.
Test Touchscreen Responsiveness
- Perform simple touch tests across the display to identify unresponsive areas.
- Note if the problem is localized (single area) or affects the entire screen.
- Why: This can distinguish between calibration issues, software, or hardware faults.
Run Self-Diagnostics (if available)
- Access the machine’s diagnostic menu and run any touchscreen or software checks.
- Follow on-screen recommendations for minor software resets or calibrations.
- Why: Self-diagnostics can confirm whether the issue is software or touchscreen hardware.
Review Recent Updates or Configuration Changes
- Determine if any software updates, patches, or configuration changes were applied recently.
- Roll back changes if feasible to test system stability.
- Why: Software errors often coincide with recent updates.
If the Problem Persists
External causes have likely been ruled out.
The touchscreen, software module, or internal electronics may be faulty.
- Remove the anesthesia machine from service
- Label as Out of Service
- Schedule a service call with GE Healthcare or authorized biomedical repair
Stopping here avoids patient risk and follows proper troubleshooting procedure.
Clinical Use Tip
- Do not troubleshoot on an active patient—always move the patient to a functional anesthesia machine first.
- Document any errors and temporary actions in the patient record if needed.
- Troubleshoot only when safe, ensuring the OR workflow is not compromised.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
“Touchscreen unresponsive and software freezes intermittently during cases.”
Cause
What was observed during troubleshooting.
Example:
“No loose cables, power stable, soft reboot and diagnostics performed; issue persists.”
Resolution
What action was taken.
Example:
“Machine removed from service, labeled Out of Service, GE Healthcare service scheduled.”
Helpful Details to Include
- Outlet tested and verified
- UPS/battery backup status
- Error messages captured
- Areas of touchscreen unresponsiveness
- Any recent software updates or configuration changes
- Final device status (Out of Service)
Final Thought
Patient safety must always take priority over troubleshooting convenience. Logical, stepwise checks can rule out external issues, but knowing when to escalate to service prevents risk. Accurate documentation of observed issues ensures continuity and accountability in clinical engineering practice.
That is successful troubleshooting.