Asset Type

Ultrasound System

Manufacturer

Canon

Model

Aplio Series

What This Guide Helps With

Addresses failed study transfers to PACS caused by network, configuration, or software issues before assuming internal system or hardware failure.

Step-by-Step Troubleshooting

1. Ensure Patient Safety

• Confirm no patient requires immediate imaging.
• Move any patient needing urgent imaging to another system.

2. Verify Network Connectivity

• Check that the ultrasound system is properly connected to the hospital network.
• Look for link/activity lights on network ports or Wi-Fi indicators.
• Expected outcome: Active network connection indicated; if not, resolve network issue first.

3. Test PACS Server Accessibility

• Ping or traceroute the PACS server from the system’s network interface.
• Confirm PACS server IP and hostname are reachable.
• Expected outcome: Successful response; failures indicate network routing or firewall issue.

4. Confirm DICOM Configuration

• Check AE Title, PACS IP, and port settings in the Aplio system.
• Ensure they match the PACS configuration.
• Expected outcome: Correct configuration; incorrect settings must be updated.

5. Examine Recent Study Logs

• Access the system’s DICOM log for failed transfer attempts.
• Note any error codes or messages (e.g., AE Title mismatch, timeout).
• Expected outcome: Identify whether failure is system-side or PACS-side.

6. Retry Transfer

• Select a test image or study and manually retry sending to PACS.
• Expected outcome: Successful transfer confirms issue was temporary; failure requires escalation.

7. Swap or Test Network Cables

• If on wired connection, try an alternate CAT6 cable and port.
• Expected outcome: Resolves connectivity issues caused by damaged cables.

8. Restart Ultrasound System

• Reboot the system to refresh network services.
• Expected outcome: Transfer may succeed if the issue was software-related.

If the Problem Persists

External causes (network, configuration, cables, software) have been ruled out.

Remove the device from service.

Label as Out of Service and send for vendor repair or internal bench evaluation.

Knowing when to stop is proper troubleshooting and prevents patient risk.

Clinical Use Tip

Never troubleshoot DICOM transfer while a patient is actively being scanned.

Use a test study to validate fixes instead of patient data.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"Studies fail to transfer to PACS; users report “Transfer Failed” errors."

Cause

What was observed during troubleshooting.

Example:
"Network configuration mismatch identified; PACS unreachable from system."

Resolution

What action was taken.

Example:
"Corrected AE Title, IP, and port settings; verified successful transfer to PACS."

Helpful Details to Include

• Network port activity and link lights
• Error codes from DICOM logs
• Manual transfer attempts
• System software version
• Final status of test study transfer

Final Thought

Logical, stepwise troubleshooting ensures patient safety and prevents unnecessary vendor escalation. Always verify external network and software causes before assuming internal failure, and document actions clearly for compliance and continuity.

That is successful troubleshooting.