Asset Type

Ultrasound System

Manufacturer

Mindray

Model

DC Series (Ultrasound System)

What This Guide Helps With

Identifies common external causes of DICOM/network export failures, including network connectivity, PACS settings, IP configuration, and cable issues.

Step-by-Step Troubleshooting

Ensure Patient Safety First

• Confirm no patient is actively connected or being scanned.
• Expected outcome: Safe environment for troubleshooting network issues.

Verify Network Connectivity

• Check that the ultrasound system is connected to the hospital network.
• Verify Ethernet cable is securely attached and undamaged.
• Test connection with another network device on the same port.
• Expected outcome: System shows network link active; no visible cable damage.

Confirm IP and DICOM Settings

• Check that the system has a valid IP address, subnet mask, and gateway.
• Verify PACS server IP, AE Title, and port are correctly configured.
• Confirm DICOM transfer settings match hospital PACS requirements.
• Expected outcome: IP configuration correct; system ready to communicate with PACS.

Ping the PACS Server

• From the ultrasound system, attempt to ping the PACS server.
• If ping fails, confirm network path and firewall rules.
• Expected outcome: Successful ping confirms network route to PACS.

Test with Another PACS Node

• If available, try exporting to an alternate PACS node or DICOM storage server.
• Expected outcome: Successful export indicates original PACS server or AE Title may have issues.

Review System Logs / Error Messages

• Check DICOM or network logs for specific error codes.
• Document any recurring errors for escalation.
• Expected outcome: Identifiable error messages that may guide further action.

If the Problem Persists

External causes (network, cables, configuration) have been ruled out. Remove the system from service, label as Out of Service, and send for vendor repair or bench evaluation. Stopping here ensures patient safety and proper troubleshooting protocol.

Clinical Use Tip

Do not attempt imaging or exports during troubleshooting. Move patients to another operational system to prevent delays or data loss.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"System unable to send studies to PACS."

Cause

What was observed during troubleshooting.

Example:
"Network configuration mismatch and PACS connectivity errors observed."

Resolution

What action was taken.

Example:
"Verified cables and network, updated IP and AE Title settings; attempted test export. System sent for further evaluation due to persistent transfer failures."

Helpful Details to Include (If Known)

• Outlet and network port tested
• Ethernet cable replaced/swapped
• DICOM AE Titles verified
• Error logs captured
• Final device status: Out of Service for repair

Final Thought

Logical, stepwise troubleshooting ensures network and configuration issues are addressed first, minimizing unnecessary repairs. Documenting each step supports patient safety and smooth escalation to vendor repair when needed.

That is successful troubleshooting.