On this page
Asset Type
Fluoroscopy / Interventional System
Manufacturer
Model
What This Guide Helps With
Identifies external causes of system boot or initialization failures, including power instability, network issues, and peripheral conflicts, ensuring safe and timely system readiness.
Step-by-Step Troubleshooting
Ensure Patient and Staff Safety
- Confirm no patient is on the table and staff are clear.
- Why: Prevents injury or interruption during troubleshooting.
Verify Main Power Supply
- Check that the system is connected to a reliable outlet and power is stable.
- Confirm the emergency power off (EPO) switch is disengaged.
- Expected Outcome: System receives proper voltage and ready for startup.
Check System Power Indicators
- Observe LEDs or display lights on the main console and generator cabinet.
- Why: Indicator lights help identify power-related faults.
- Expected Outcome: Normal power indicators (green) confirm power is present.
Restart the System Properly
- Perform a controlled power cycle using the main power switch.
- Expected Outcome: System attempts a full boot sequence without errors.
Inspect Peripheral Connections
- Verify all network cables, detectors, and control panels are securely connected.
- Why: Loose or disconnected peripherals can prevent initialization.
- Expected Outcome: No loose connections; boot proceeds past hardware detection.
Check Network Connectivity
- Ensure connection to the hospital network, PACS, and license servers.
- Expected Outcome: System communicates with essential services without timeout errors.
Review Recent Software or Configuration Changes
- Confirm no updates, patches, or configuration changes were applied recently.
- Why: Conflicting software or incomplete updates can prevent boot.
- Expected Outcome: System boots with default or known good configuration.
Escalate if Boot Fails
- If the system fails to initialize after these steps:
- Remove the device from service.
- Label “Out of Service.”
- Send for vendor support or bench evaluation.
- Why: Internal software or hardware fault likely; do not attempt board-level repair.
Clinical Use Tip
Never troubleshoot while a patient is on the table. Move the patient to a backup system first.
Document each step clearly in case of escalation.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"System fails to boot or initialize; displays error messages on startup."
Cause
What was observed during troubleshooting.
Example:
"Loose network and peripheral connections discovered during inspection."
Resolution
What action was taken.
Example:
"Secured connections, performed controlled power cycle, system successfully booted."
Helpful Details to Include (If Known)
- Outlet tested and verified stable
- Power indicators checked (LEDs)
- All network and detector cables secured
- System boot logs reviewed for errors
- Final device status: operational
Final Thought
Boot and initialization issues often stem from external factors like power, network, or connections. Prioritize patient safety, follow stepwise logic, and escalate appropriately. Thorough documentation supports safety and efficiency.
That is successful troubleshooting.