On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Identifies external causes of DICOM/PACS transfer failures such as network issues, configuration errors, or server availability preventing image transmission.
Step-by-Step Troubleshooting
Ensure Patient and Data Safety
- Confirm no active exam is in progress and all acquired images are saved locally.
- If needed, move patient workflow to another unit.
- Why: Prevents data loss and workflow disruption during troubleshooting.
Verify Network Connection Status
- Check network indicators on the acquisition workstation:
- Network icon status (connected vs disconnected)
- Link lights on Ethernet ports
- Expected Outcome:
- System shows active network connection.
- Why: Loss of network connectivity is the most common cause of DICOM transfer failure.
Inspect Ethernet and Network Cabling
- Check all visible network cables between:
- Workstation and wall port
- System cabinets and switches
- Reseat cables and inspect for damage.
- Expected Outcome:
- Secure connections restore communication if cabling was loose.
- Why: Physical layer issues often cause intermittent or complete transfer failures.
Test Network Port / Wall Connection
- If possible, connect to a known working network port or test the port using another device (laptop).
- Expected Outcome:
- Verified active network port.
- Why: Rules out facility network drop or switch port failure.
Confirm PACS Connectivity and Availability
- Check if other modalities can send images to PACS.
- Contact IT or PACS admin if needed.
- Expected Outcome:
- PACS is reachable and accepting studies.
- Why: If PACS is down or rejecting studies, the issue is not with the modality.
Verify DICOM Configuration Settings
- Review DICOM settings on the workstation:
- AE Title
- IP address
- Port number
- Destination configuration
- Compare against known correct configuration.
- Expected Outcome:
- Settings match PACS configuration.
- Why: Incorrect configuration prevents successful association with PACS.
Attempt Manual Resend of Images
- Select a stored study and manually resend to PACS.
- Expected Outcome:
- Successful transmission confirms restored communication.
- Why: Verifies whether the issue is persistent or intermittent.
Check for Error Messages or Queue Backlog
- Review system message logs or DICOM queue:
- Stuck or failed studies
- Repeated transmission errors
- Clear or retry failed jobs if appropriate.
- Expected Outcome:
- Queue clears and studies transmit successfully.
- Why: Backlogged or failed jobs can block new transmissions.
Perform a Controlled System Restart
- Shut down the system properly, wait 2–3 minutes, and power back on.
- Expected Outcome:
- Temporary communication or software issues are resolved.
- Why: Restart resets network services and DICOM processes.
If the Problem Persists
If all network connections, configuration settings, and PACS availability have been verified, the issue is likely internal (software, interface board, or system integration fault).
Remove the system from service, label it Out of Service, and escalate for vendor support or bench evaluation.
Knowing when to stop prevents unnecessary risk and wasted troubleshooting time.
Clinical Use Tip
Do not troubleshoot during an active patient exam. Always ensure studies are saved locally before attempting network or system changes to prevent data loss.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Mammography unit unable to send images to PACS; studies stuck in queue."
Cause
What was observed during troubleshooting.
Example:
"Loose Ethernet connection at workstation causing intermittent network loss."
Resolution
What action was taken.
Example:
"Reseated network cable, verified connectivity, and successfully resent queued studies."
Helpful Details to Include (If Known)
- Network outlet tested
- Ethernet cables reseated or replaced
- PACS availability confirmed
- DICOM settings verified
- Error messages or codes observed
- Transfer queue status
- Final system status (operational or removed from service)
Final Thought
DICOM transfer failures are most often caused by simple external issues like network connectivity or configuration mismatches. A structured approach ensures patient data is protected while quickly isolating the root cause. Escalation is appropriate once external factors are ruled out, reinforcing safe and efficient troubleshooting practices.
That is successful troubleshooting.