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 DICOM or network communication failures preventing image transfer, including connectivity, configuration, and server availability issues.

Step-by-Step Troubleshooting

Ensure Patient Safety First

• Confirm no active procedure is in progress.
• Why: Prevents disruption of patient care and avoids loss of critical imaging data.

Verify System Network Status

• Check network indicators on the workstation and system cabinets.
• Look for disconnected status, warning icons, or loss of link lights.
• Expected Outcome: Active network connection with normal indicators.
• Why: Confirms whether the system is physically connected to the network.

Inspect Ethernet and Network Cabling

• Check all visible network cables between:
• Workstation
• System cabinets
• Wall/network ports
• Look for loose, damaged, or unplugged cables. Reseat connections.
• Expected Outcome: Secure connections restore communication if cabling was the issue.

Test Network Port / Wall Connection

• If possible, move the system connection to a known working network port or test the port with another device.
• Expected Outcome: Verified live network port.
• Why: Rules out infrastructure or wall port failure.

Confirm PACS / Server Availability

• Verify that the PACS or DICOM server is:
• Powered on
• Reachable from other hospital systems
• Expected Outcome: Other modalities can send images successfully.
• Why: If PACS is down, the issue is not with the Optima system.

Check DICOM Configuration Settings

• Review system configuration for:
• AE Title
• IP address
• Port number
• Compare with PACS configuration.
• Expected Outcome: Matching configuration allows successful communication.
• Why: Mismatched settings are a common cause of transfer failure.

Attempt a DICOM Send Test

• Send a test image or study to PACS.
• Observe for:
• Immediate failure
• Delayed queue buildup
• Error messages
• Expected Outcome: Successful transfer confirms system functionality.
• Why: Helps determine if issue is persistent or intermittent.

Review Error Messages and Logs (User-Level)

• Check for visible DICOM or network-related errors on the workstation.
• Note any recurring codes or communication timeouts.
• Expected Outcome: Error pattern may indicate configuration vs. connectivity issue.

Restart the Workstation and Network Interfaces

• Perform a controlled system restart.
• If accessible, reboot network switch or interface (with IT coordination).
• Expected Outcome: Temporary communication faults may clear after restart.
• Why: Resets network services and clears software-related issues.

Check for Network Changes or IT Work

• Confirm with IT if there have been:
• IP changes
• VLAN changes
• Firewall updates
• Expected Outcome: Identification of recent changes that could block communication.
• Why: Network configuration changes frequently cause sudden failures.

If the Problem Persists

If all external network, cabling, PACS availability, and configuration issues have been ruled out, the problem is likely internal (network interface hardware or system software).

Remove the system from service if clinically necessary, label it Out of Service, and escalate for vendor support or advanced diagnostics.

Clinical Use Tip

Always transition the patient to a functioning system before troubleshooting. Do not delay image transfer during active procedures.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"Staff reported images not transferring to PACS from Optima IGS system."

Cause

What was observed during troubleshooting.

Example:
"Loose Ethernet connection at workstation network port causing intermittent communication failure."

Resolution

What action was taken.

Example:
"Reseated network cable, verified link lights, and confirmed successful DICOM image transfer to PACS."

Helpful Details to Include (If Known)

• Network port tested and verified
• Cables reseated or replaced
• PACS server status confirmed
• Error messages observed
• DICOM send test results
• System restarted
• Final transfer status confirmed

Final Thought

DICOM failures are often caused by simple network or configuration issues. A structured approach—starting with connections and server availability—prevents unnecessary escalation. Always prioritize patient workflow and document findings clearly to support long-term reliability.

That is successful troubleshooting.