Asset Type

C-Arm

Manufacturer

GE Healthcare

Model

OEC 9800

What This Guide Helps With

This guide assists Clinical Engineering in troubleshooting a GE Healthcare OEC 9800 C-Arm that is unable to send images to a PACS server or other DICOM destinations. Symptoms may include images not appearing in PACS, error messages related to DICOM transfer, or failure to complete image export after acquisition. The focus is on verifying external and network-related causes before considering internal device faults.

Step-by-Step Troubleshooting

Confirm device status and acquisition

• Ensure the C-Arm has successfully captured images and that they appear on the local monitor.
• Reason: If images are not acquired correctly, DICOM transfer will fail.

Check network connections

• Verify Ethernet or fiber connections from the C-Arm to the network switch.
• Confirm cables are securely plugged in and undamaged.
• Reason: Loose or damaged cables are a common cause of transfer failure.

Verify IP configuration

• Confirm the C-Arm has a valid IP address on the hospital network.
• Check subnet mask, gateway, and PACS server address settings.
• Reason: Misconfigured IP or network settings prevent DICOM communication.

Ping PACS server

• From the C-Arm or connected workstation, attempt to ping the PACS server.
• Reason: Confirms network reachability; failure indicates network or firewall issues.

Check PACS server status

• Confirm the PACS server is online and accepting DICOM connections.
• Reason: Server downtime can mimic device issues.

Verify AE Titles and ports

• Ensure the C-Arm’s DICOM AE Title matches the PACS configuration.
• Confirm the DICOM port is correct and not blocked by firewall.
• Reason: Mismatched AE Titles or blocked ports prevent successful DICOM transfer.

Restart network interfaces

• Power-cycle the C-Arm’s network interface or restart the device if safe.
• Reason: Temporary network glitches can be resolved by a restart.

Check DICOM logs

• Access DICOM logs on the C-Arm to identify errors during transfer.
• Reason: Logs provide error codes to help isolate the cause.

If the Problem Persists

If all external network checks and PACS configuration are verified and transfer still fails:

• Remove the device from service.
• Label it “Out of Service.”
• Escalate to internal repair or vendor support for potential network interface board or DICOM software fault.
• Reason: Continuing to troubleshoot internally without proper expertise may risk patient safety or device integrity.

Clinical Use Tip

• Never troubleshoot DICOM transfers while the C-Arm is in active use on a patient.
• Move the patient to another imaging system first.
• Only perform network and device checks when the system is idle and safe to test.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
“PACS transfer failed; images not reaching server.”

Cause

What was observed during troubleshooting.

Example:
“Network cable found loose; device could not communicate with PACS server.”

Resolution

What action was taken.

Example:
“Secured cable, verified network connection, restarted C-Arm, successfully completed DICOM transfer test.”

Helpful Details to Include

• Cable tested/li>
• Network switch port verified
• IP address and AE Title confirmed
• Firewall or port block checked
• Final device status: Transfer successful or device labeled OOS if unresolved

Final Thought

Patient safety and proper escalation are paramount. Troubleshooting DICOM issues requires a methodical approach, starting with network and configuration checks before assuming internal failure. Accurate CCR documentation ensures the issue is tracked and resolved efficiently.

That is successful troubleshooting.