On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Failure to send images to PACS, DICOM transfer errors, network disconnects, or studies not appearing in the archive.
Step-by-Step Troubleshooting
Ensure Patient Safety First
- Do not delay patient care while troubleshooting.
- Use an alternate ultrasound system if image export is required immediately.
Expected: Patient care continues without interruption
Why it matters: Export issues should never impact clinical workflow or diagnosis
Verify the Reported Issue
- Attempt to send a test image or study to PACS.
- Observe:
- Error messages on screen
- “Send failed” or timeout messages
- No confirmation of successful transfer
Expected: Issue is reproducible
Why it matters: Confirms this is a true communication failure, not user workflow error
Check Network Cable Connection
- Inspect the Ethernet cable at the rear of the system and wall port.
- Ensure cable is fully seated
- Look for link/activity lights on the port
Expected: Solid or blinking network lights
Why it matters: Loose or disconnected cables are a common cause of DICOM failure
Verify Network Connectivity
- Check system network status in settings.
- Confirm IP address is present (not 0.0.0.0)
- Verify connection to hospital network
- If possible:
- Ping PACS server (if available in system tools)
Expected: Valid IP address and network connection
Why it matters: No network = no DICOM communication
Confirm DICOM Configuration Settings
- Navigate to DICOM settings and verify:
- AE Title (matches PACS)
- IP address of PACS server
- Port number
- Device name
Expected: All values match hospital PACS configuration
Why it matters: Incorrect configuration is one of the most common causes of failed exports
Perform a Test Send
- Send a test study or image to PACS.
- Monitor for success confirmation
- Check PACS workstation to confirm receipt
Expected: Study appears in PACS
Why it matters: Confirms end-to-end communication is working
Check for Network Restrictions
- Verify with IT or networking team:
- No recent network changes
- VLAN or port restrictions
- Firewall blocking DICOM port
Expected: No network-level blocks
Why it matters: Even correctly configured systems will fail if blocked by network security
Restart the System
- Power down the ultrasound system completely, wait 30 seconds, and restart.
Expected: Temporary communication issues may resolve
Why it matters: Clears software/network stack issues
Try Alternate Network Port
- Plug the system into a known working network port.
Expected: Successful connection and transfer
Why it matters: Rules out faulty wall ports or switch issues
If the Problem Persists
If all external connections, network settings, and configuration have been verified, the issue is likely internal (network interface hardware or system software).
Remove the device from service, label it Out of Service, and send for repair or further bench evaluation.
Knowing when to stop prevents unnecessary downtime and protects system integrity.
Clinical Use Tip
Always confirm images have successfully reached PACS before ending the exam. Do not troubleshoot on an active patient. Move the patient to a backup device first to ensure therapy continuity.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Ultrasound unable to send studies to PACS; export failing."
Cause
What was observed during troubleshooting.
Example:
"Incorrect DICOM AE Title configured, preventing communication with PACS server."
Resolution
What action was taken.
Example:
"Corrected AE Title and verified successful test transmission to PACS."
Helpful Details to Include (If Known)
- Network cable checked and reseated
- IP address verified
- DICOM settings reviewed (AE Title, IP, port)
- Test send results
- PACS confirmation
- Alternate port tested
- Final device status
Final Thought
DICOM failures are most often caused by configuration or network issues, not hardware failure. A structured approach—starting with connections and settings—ensures safe, efficient resolution while minimizing downtime. Proper escalation and documentation support long-term system reliability.
That is successful troubleshooting.