On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Addresses failures sending studies to PACS or network due to configuration, connectivity, or software issues before assuming hardware failure.
Step-by-Step Troubleshooting
Ensure Patient Safety
- Confirm no patient depends on immediate image transfer. Move the patient to another system if urgent imaging is required.
Check Network Connectivity
- Verify the system is connected to the hospital network (LAN/Wi-Fi).
- Check cable integrity and switch ports.
- Expected outcome: Network link light active; system can ping hospital servers.
Verify PACS/DICOM Configuration
- Ensure AE Title, IP address, and port match the PACS server settings.
- Check for recent changes in PACS or network policies.
- Expected outcome: Configuration matches PACS, no typos or mismatches.
Test DICOM Communication
- Use the system’s DICOM test tool to verify connectivity to the PACS server.
- Expected outcome: Successful connection test; if failed, note error code.
Check System Software Status
- Ensure the ultrasound software is up to date.
- Restart the system to clear temporary software locks or network glitches.
- Expected outcome: System restarts cleanly, connectivity restored.
Review Firewall or Security Settings
- Confirm network firewalls or antivirus are not blocking DICOM ports (typically 104, 105, or configured custom port).
- Expected outcome: DICOM traffic allowed through the network.
Try Alternate PACS Node
- If available, configure export to a different PACS node or workstation.
- Expected outcome: If export works, original PACS server settings or network path may be the issue.
If the Problem Persists
External network and configuration issues have been ruled out. Likely internal system software fault or network interface hardware problem.
- Remove the system from service.
- Label Out of Service.
- Send for repair or vendor bench evaluation.
Knowing when to escalate prevents patient safety risk and wasted troubleshooting time.
Clinical Use Tip
Do not attempt to export studies while the patient is actively being scanned.
Ensure all urgent imaging is completed on a functional system before troubleshooting network issues.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"PACS export fails; images not appearing on server."
Cause
What was observed during troubleshooting.
Example:
"Network configuration mismatch and temporary software lock detected."
Resolution
What action was taken.
Example:
"Verified network connection, corrected PACS settings, restarted system; successful export confirmed."
Helpful Details to Include (If Known)
- Network cable tested and swapped.
- Indicator lights on network port observed.
- DICOM test tool results logged.
- Firewall/port checks performed.
- Final device status: Export verified functional.
Final Thought
Logical troubleshooting protects patients and reduces downtime. Start with basic connectivity and configuration checks before assuming internal failure. Proper CCR documentation ensures clear records for ongoing support.
That is successful troubleshooting.