On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
This guide assists Clinical Engineering in troubleshooting situations where the Philips EPIQ Series ultrasound system cannot export images to the PACS or experiences network connectivity failures. Common presentations include:
- Failed or delayed image transfers to PACS
- Error messages indicating network timeout or export failure
- System cannot reach network servers or DICOM nodes
The guide focuses on external, verifiable network issues before considering internal system faults.
Step-by-Step Troubleshooting
Verify network connectivity
- Check the network cable is securely connected to the system.
- Confirm link lights on the Ethernet port are active.
- Ping the PACS server from a networked workstation to confirm it is online.
- Why: Ensures the device can physically communicate on the network.
Check system network configuration
- Confirm IP address, subnet mask, and gateway are correctly configured on the ultrasound system.
- Ensure no IP conflicts exist with other devices on the network.
- Why: Incorrect network settings prevent communication with PACS.
Test DICOM settings
- Verify the PACS AE Title, IP address, and port on the EPIQ match the server’s configuration.
- Confirm DICOM export is enabled and the destination node is active.
- Why: Mismatched DICOM settings are a common cause of failed image transfers.
Check firewall or security settings
- Confirm the hospital network allows traffic between the EPIQ system and PACS server.
- Ensure no recent firewall or security changes are blocking DICOM ports (typically 104 or configured port).
- Why: Network security can block data transfer even if cabling and IPs are correct.
Restart network components
- Restart the EPIQ system and any local switches or routers if possible.
- Why: Resets any temporary network issues without affecting patient data.
Test with a manual export
- Attempt to send a single study to PACS manually to verify functionality.
- Check if error persists or is intermittent.
If the Problem Persists
Common external causes have been ruled out. The issue may be internal to the EPIQ system or related to PACS server compatibility.
- Remove the system from clinical service temporarily.
- Label as Out of Service.
- Escalate to Philips service or your hospital’s PACS support team for bench evaluation.
Clinical Use Tip
- Do not attempt troubleshooting on an active patient exam. Move the patient to another system if available.
- Always verify patient data integrity before and after network or PACS troubleshooting.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
“Unable to export images to PACS; system reports network timeout errors.”
Cause
What was observed during troubleshooting.
Example:
“Network cable verified, DICOM settings checked, PACS server reachable from other workstations. Error persists on system export.”
Resolution
What action was taken.
Example:
“System removed from service and labeled Out of Service. Issue escalated to Philips service and PACS team for evaluation.”
Helpful Details to Include
- Date and time of failed exports
- Specific error messages displayed
- Network tests performed (ping results, cable swaps)
- DICOM configuration settings verified
Final Thought
Network and PACS export failures require careful, methodical troubleshooting to ensure patient data is secure and imaging workflow is uninterrupted. Document all checks, escalate appropriately, and maintain patient safety at all times.
That is successful troubleshooting.