On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
This guide assists Clinical Engineering in troubleshooting a GE Healthcare OEC 9900 Series C-Arm that is unable to communicate with PACS or networked imaging systems. Symptoms may include:
- Images not appearing on PACS
- Network error messages on the console
- Failure to send or receive DICOM images
The guide focuses on external and verifiable network issues first, before assuming internal device failure.
Step-by-Step Troubleshooting
Verify Network Connectivity
- Check that the C-Arm is physically connected to the network via Ethernet or Wi-Fi.
- Confirm link lights on network ports are active.
- Reason: A disconnected or faulty network cable is the most common cause of communication failure.
Check IP Configuration
- Access the device’s network settings to confirm IP address, subnet mask, gateway, and DNS are correctly configured.
- Reason: Incorrect IP settings prevent PACS communication.
Ping PACS / Server
- From the C-Arm or connected workstation, ping the PACS server to verify network reachability.
- Reason: Confirms that the device can reach the destination server.
Verify PACS Server Status
- Confirm the PACS server is online, reachable, and accepting incoming connections.
- Reason: The problem may originate on the server side rather than the C-Arm.
Check Firewall / Port Settings
- Ensure the necessary DICOM ports (usually 104 or configured ports) are open between the C-Arm and PACS server.
- Reason: Firewalls can block DICOM communication.
Test DICOM AE Titles and Settings
- Confirm the C-Arm AE Title, PACS AE Title, and port numbers match the PACS configuration.
- Reason: Mismatched AE Titles prevent successful image transfer.
Restart Network Equipment
- Power cycle network switches, routers, or access points if connectivity is uncertain.
- Reason: Temporary network glitches can disrupt communication.
If the Problem Persists
External network checks have been ruled out.
The device may have an internal network interface failure or corrupted network settings.
- Remove device from service.
- Label “Out of Service – Network Issue.”
- Escalate to GE service or in-house bench evaluation.
Knowing when to stop prevents unnecessary downtime and ensures patient safety.
Clinical Use Tip
- Do not attempt to troubleshoot network failures while the device is actively imaging a patient.
- Move the patient to another operational C-Arm if possible.
- Ensure troubleshooting occurs in a safe, controlled environment.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
“C-Arm unable to send images to PACS; error displayed on console.”
Cause
What was observed during troubleshooting.
Example:
“Device could not communicate with PACS server; network link and IP settings verified. Server reachable via other devices.”
Resolution
What action was taken.
Example:
“Device removed from service and labeled out of service. Escalated to GE service for network interface evaluation.”
Helpful Details to Include
- Network cable tested and swapped
- Link lights observed
- IP configuration verified
- Ping and connectivity tests results
- PACS AE titles and ports checked
- Network switch or firewall changes noted
Final Thought
Patient safety and logical troubleshooting are paramount. Start with simple network checks, document all observations, and escalate when internal issues are suspected. Proper CCR documentation ensures continuity and accountability.
That is successful troubleshooting.