Philips Allura Xper

Asset Type

Fluoroscopy / Interventional System

Manufacturer

Philips

Model

Allura Xper

What This Guide Helps With

Identifies external causes of DICOM or PACS transfer failure, including network issues, server connectivity, or configuration errors, ensuring timely image availability for patient care.

Step-by-Step Troubleshooting

Ensure Patient and Staff Safety

• Confirm no patient is actively undergoing a procedure while troubleshooting network or system issues.
• Why: Prevents disruption to live imaging and ensures staff are clear of equipment.

Check System Power and Status

• Verify the Allura Xper is powered on with normal system boot indicators.
• Expected Outcome: System is ready; no error lights or boot failures.
• Why: A device not fully booted cannot communicate with PACS.

Verify Network Connections

• Inspect Ethernet cables, switches, and wall ports for secure connections.
• Test network link lights or use a network tester if available.
• Expected Outcome: Active network link with stable connectivity.
• Why: DICOM relies on a stable network to reach PACS servers.

Ping PACS / DICOM Server

• From the Allura console or associated workstation, ping the PACS server IP.
• Expected Outcome: Successful response indicates network and server reachability.
• Why: Confirms that the server is accessible and routing is correct.

Check DICOM Configuration

• Verify AE titles, IP addresses, and ports match PACS server settings.
• Ensure DICOM service is enabled on both the Allura system and PACS.
• Expected Outcome: Properly configured DICOM connection.
• Why: Misconfigured AE titles or addresses are common causes of transfer failure.

Inspect PACS Server and Storage

• Confirm server is operational, has storage space, and is not rejecting incoming studies.
• Expected Outcome: PACS server accepts new studies.
• Why: Transfer can fail if the server is offline or full.

Test with a Small Study

• Send a test image or study to PACS to verify functionality.
• Expected Outcome: Test study successfully received in PACS.
• Why: Confirms transfer capability without involving live patient procedures.

If the Problem Persists

Common external causes have been ruled out.

Remove Allura Xper from clinical service.

Label Out of Service and escalate to Philips service for bench evaluation.

Why: Avoids risk to patient care and prevents further network errors.

Clinical Use Tip

Always move active patients to another operational system if transfer issues arise during a procedure.

Troubleshoot only when safe and non-critical.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"Cath lab staff reported failure to send images to PACS from Allura Xper."

Cause

What was observed during troubleshooting.

Example:
"Network misconfiguration and unreachable PACS server."

Resolution

What action was taken.

Example:
"Verified cables, corrected DICOM settings, and confirmed successful test transfer."

Helpful Details to Include (If Known)

• Network switch port tested
• Cables swapped
• PACS server status verified
• Test study transfer successful
• No abnormal lights or alarms on Allura Xper

Final Thought

Logical, stepwise troubleshooting preserves patient safety, identifies network or configuration issues, and ensures proper escalation when needed. Thorough documentation aids continuity of care and regulatory compliance.

That is successful troubleshooting.