Philips Azurion

Asset Type

Fluoroscopy / Interventional System

Manufacturer

Philips

Model

Azurion

What This Guide Helps With

Identifies external causes of DICOM/PACS transfer failures, including network connectivity, server access, and configuration issues, ensuring timely image availability for patient care.

Step-by-Step Troubleshooting

Ensure Patient and Staff Safety

• Confirm no patient is actively undergoing a procedure.
• Why: Prevents interruption of patient care and avoids accidental system interaction.

Check Network Connections

• Verify Ethernet cables are securely connected to the Azurion and network switches.
• Expected outcome: No loose or disconnected cables.

Confirm Network Activity

• Check the system’s network status indicators and test ping to the PACS server.
• Expected outcome: Successful response from the server confirms network reachability.

Verify PACS Server Availability

• Confirm PACS server is powered on and accessible from other systems.
• Why: System cannot transfer images if the server is offline.

Check DICOM Configuration Settings

• Validate AE Titles, IP addresses, and ports match PACS server requirements.
• Expected outcome: Correct configuration ensures proper communication.

Inspect Firewall or Security Settings

• Confirm firewalls or security appliances are not blocking DICOM ports.
• Why: Blocked ports prevent image transfer.

Review System Logs

• Check Azurion event logs for error codes or failed transfer entries.
• Expected outcome: Identifies specific network or configuration errors for escalation.

Test with Alternate Server or Workstation

• Attempt to transfer a test image to another PACS or workstation.
• Why: Confirms if issue is system-specific or network/server related.

If the Problem Persists

External causes have been ruled out; issue is likely internal or requires PACS/server support.

• Remove the Azurion from service for non-critical procedures if possible.
• Label Out of Service.
• Escalate to Philips service or network/PACS team for further evaluation.

Clinical Use Tip

Do not troubleshoot during an active procedure. Move the patient to another available system first.

Only perform network checks when patient safety is ensured.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"Images are not transferring to PACS from the Azurion."

Cause

What was observed during troubleshooting.

Example:
Network connectivity verified; DICOM configuration and server availability confirmed.

Resolution

What action was taken.

Example:
Network ports and PACS settings verified; issue escalated to service team for internal troubleshooting.

Helpful Details to Include (If Known)

• Network cables tested
• PACS server reachable
• DICOM AE Titles/IPs verified
• Firewall/port settings checked
• System logs reviewed
• Test transfer attempted
• Current device status: Out of Service if escalated

Final Thought

Patient safety and workflow continuity must guide troubleshooting. Systematic checks of connections, configurations, and server status prevent unnecessary downtime. Proper documentation and escalation ensure accountability and resolution.

That is successful troubleshooting.