Asset Type

Ultrasound System

Manufacturer

Fujifilm Sonosite

Model

X-Porte

What This Guide Helps With

Failed image export, studies not sending to PACS, or network communication issues related to connectivity, configuration, or external network dependencies.

Step-by-Step Troubleshooting

Ensure Patient Safety First

• Do not troubleshoot while the system is actively being used for patient care.
• Move to a backup ultrasound system if imaging/export is needed urgently.
• Expected: Prevents disruption to patient care and avoids data loss during active studies.

Verify the Reported Issue

• Attempt to send a study to PACS or DICOM destination.
• Note any error messages or failure behavior (e.g., timeout, rejection, no response).
• Expected: Export fails consistently or intermittently.
• Why it matters: Confirms this is a true system or network issue, not user error.

Check Network Connection (Physical Layer)

• Inspect the Ethernet cable connection at the X-Porte and wall port.
• Verify link lights are active on the network port.
• Try a known working network cable and port if available.
• Expected: Solid or blinking link/activity lights present.
• Why it matters: Physical connection issues are a common and easily missed cause.

Verify Network Connectivity on the System

• Access system network settings.
• Confirm IP address, subnet mask, and gateway are populated correctly.
• Check if IP is valid (not 0.0.0.0 or self-assigned 169.254.x.x).
• Restart network connection or reboot system if needed.
• Expected: Valid network configuration present.
• Why it matters: Incorrect or missing IP settings prevent communication with PACS.

Test Network Availability

• If available, use built-in network test tools (ping or connectivity test).
• Alternatively, confirm with IT that the network port is active.
• Expected: Successful communication with network resources.
• Why it matters: Confirms the issue is not due to upstream network failure.

Verify DICOM Configuration

• Check DICOM settings on the X-Porte:
• AE Title (local and remote)
• IP address of PACS server
• Port number
• Ensure these match PACS configuration exactly.
• Expected: Matching configuration between ultrasound and PACS.
• Why it matters: Even minor mismatches will cause silent failures or rejections.

Check for Recent Changes

• Ask if any recent updates occurred:
• Network changes
• PACS server updates
• Device relocation
• Expected: No unverified changes.
• Why it matters: Many DICOM failures are caused by changes outside the device.

Attempt Alternate Export Method

• If available, try exporting to:
• USB device
• Secondary DICOM destination
• Expected: Export works via alternate method.
• Why it matters: Helps isolate whether the issue is network-specific or system-wide.

Reboot the System

• Perform a full system shutdown and restart.
• Expected: Temporary communication issues may resolve.
• Why it matters: Clears software/network stack errors that can block exports.

If the Problem Persists

If all external causes (network connection, configuration, and PACS communication) have been ruled out, the issue is likely internal (software, network interface, or DICOM service failure).

Remove the system from service if export is critical. Label the device Out of Service and send for repair or further bench evaluation.

Knowing when to stop prevents unnecessary downtime and ensures proper escalation.

Clinical Use Tip

Always confirm image export functionality after moving or reconnecting an ultrasound system. Network changes are a common cause of silent DICOM failures.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"Ultrasound unable to send images to PACS; export attempts failing."

Cause

What was observed during troubleshooting.

Example:
"Incorrect DICOM destination IP configuration after network port change."

Resolution

What action was taken.

Example:
"Updated DICOM settings to correct PACS IP and verified successful image transmission."

Helpful Details to Include (If Known)

• Network port tested and active
• Ethernet cable swapped
• IP address verified
• DICOM AE Title/IP/Port confirmed
• Error messages observed (if any)
• Alternate export method tested
• System reboot performed
• Final device status (operational or removed from service)

Final Thought

DICOM and network issues are often external to the device, making structured troubleshooting critical. Always verify connectivity and configuration before suspecting internal failure. Proper escalation and clear documentation ensure continuity of patient care and efficient resolution.

That is successful troubleshooting.