GE Healthcare Optima IGS Series

Asset Type

Fluoroscopy / Interventional System

Manufacturer

GE Healthcare

Model

Optima IGS Series

What This Guide Helps With

Identifies external causes of software startup failures or application crashes, including power, peripherals, network, and workstation-related issues.

Step-by-Step Troubleshooting

Ensure Patient Safety First

• Confirm no patient is on the table and no procedure is in progress.
• Why: Prevents interruption of care and avoids unsafe system behavior during troubleshooting.

Observe Boot and Error Behavior

• Restart the system and watch closely:
• Does it fail during OS load, application launch, or post-login?
• Note any error messages or freeze points.
• Expected Outcome: Identifying failure stage helps isolate workstation vs system issue.

Verify System Power Stability

• Check power to all major components:
• Workstation
• Monitors
• System cabinets
• Inspect breakers, UPS (if present), and power indicators.
• Expected Outcome: Stable power with no flickering or unexpected restarts.
• Why: Power instability commonly causes crashes or incomplete initialization.

Check Peripheral and External Device Connections

• Inspect all connected devices:
• Keyboard and mouse
• USB devices (remove non-essential devices)
• Monitors and video cables
• Expected Outcome: System stabilizes after removing problematic peripherals.
• Why: Faulty or conflicting peripherals can interrupt software loading.

Inspect Network Connectivity

• Verify Ethernet connections to:
• Workstation
• System network switches
• Check link lights and connection status.
• Expected Outcome: Active network connection.
• Why: Some applications depend on network services during initialization and may crash if unavailable.

Confirm Server / System Dependencies Are Available

• Verify availability of:
• PACS / DICOM servers
• Domain/network authentication (if applicable)
• Test access from another device if possible.
• Expected Outcome: External systems are reachable and operational.
• Why: Missing dependencies can cause application failures or timeouts.

Restart the Workstation Independently (If Applicable)

• If the system allows, reboot only the workstation/application host.
• Expected Outcome: Clean restart may resolve temporary software faults.
• Why: Clears memory-related issues and hung processes.

Check Disk Space and Basic System Health Indicators

• Look for warnings such as:
• Low disk space
• System alerts on startup
• Slow or unresponsive behavior
• Expected Outcome: No critical system warnings.
• Why: Insufficient resources can prevent proper application loading.

Review Error Logs or On-Screen Alerts (If Accessible)

• Check for visible logs or error codes presented on the console.
• Document exact messages.
• Expected Outcome: Error details help determine if issue is software or hardware-related.

Perform Full System Power Cycle

• Shut down the system properly, wait 1–2 minutes, then restart all components.
• Expected Outcome: System initializes normally after clean restart.
• Why: Resets communication between subsystems and clears transient faults.

If the Problem Persists

If all external causes have been ruled out, the issue is likely internal (software corruption, workstation failure, or system component fault).

Remove the system from service

Label as Out of Service

Escalate for vendor support or advanced bench evaluation

Knowing when to stop prevents unnecessary risk and reflects proper troubleshooting practice.

Clinical Use Tip

Never troubleshoot software or restart the system during an active case. Always move the patient to a functioning room before attempting recovery.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"System application crashes during startup and fails to reach ready state."

Cause

What was observed during troubleshooting.

Example:
"External checks completed; no power, network, or peripheral issues found—likely workstation/software fault."

Resolution

What action was taken.

Example:
"System removed from service and escalated to vendor for software recovery."

Helpful Details to Include (If Known)

• Boot stage where failure occurs
• Exact error messages or codes
• Network status confirmed
• Peripherals removed/tested
• Power stability verified
• Any unusual sounds, freezing, or lag
• Final system status (operational vs out of service)

Final Thought

Software issues often appear complex, but many originate from simple external causes like power instability, peripherals, or network dependencies. A structured approach ensures patient safety, avoids unnecessary escalation, and supports accurate documentation when escalation is required.

That is successful troubleshooting.