On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Use this guide when the operator workstation becomes unresponsive or loses communication with scanner components during normal operation.
Step-by-Step Troubleshooting
1. Protect the Patient and Stop the Examination
Do not continue scanning when the workstation cannot reliably control or display scanner status. Safely remove the patient if necessary and arrange alternate imaging for urgent cases. Expected outcome: Clinical care no longer depends on an unresponsive control workstation.
2. Confirm the Exact Failure
Determine whether the entire workstation is frozen, only one application is unresponsive, the display is blank, or communication with the gantry or scanner has been lost. Record visible messages before restarting anything. Expected outcome: The failure is categorized as workstation, display, application, or communication related.
3. Check Workstation Power and Display Connections
Verify workstation and monitor power, external video connections, and display input selection where applicable. Expected outcome: A simple display or external power issue is identified or ruled out.
4. Inspect Accessible Network and Communication Connections
Check accessible Ethernet and other external communication cables for looseness, damage, or accidental disconnection. Observe available normal link indicators where appropriate. Expected outcome: External communication connections are secure.
5. Determine Whether Other Scanner Components Are Responsive
Check whether the gantry, table, or other normal system interfaces show evidence of continued operation. Do not initiate scans while communication integrity is uncertain. Expected outcome: The scope of the communication failure is established.
6. Check for Broader Network or Infrastructure Problems
Determine whether other imaging systems or department workstations are experiencing simultaneous communication problems. Coordinate with IT or network support if a shared infrastructure issue is suspected. Expected outcome: A scanner-specific failure is distinguished from a broader infrastructure event.
7. Perform an Approved Workstation or System Restart
If the system is stable and patient care is not dependent on it, perform the approved normal restart sequence. Avoid forced or repeated power interruption unless directed by qualified service procedures. Expected outcome: Workstation responsiveness and scanner communication return to normal. If they do, proceed to verification and stop troubleshooting.
8. Verify Complete System Communication
Confirm the workstation recognizes the scanner, scanner status is current, gantry/table functions report normally, and an approved nonpatient workflow can be completed. Expected outcome: Workstation and scanner communication remain stable throughout functional testing.
9. Escalate Recurring Freezes or Communication Loss
If the condition recurs, the workstation cannot communicate after restart, or data integrity is uncertain, discontinue troubleshooting. Expected outcome: The system is removed from service and referred for appropriate workstation, network, or scanner service evaluation.
If the Problem Persists
External power, display connections, accessible communication cabling, general network conditions, and a normal restart have been checked. Remaining causes may involve workstation hardware, operating software, scanner communications, internal networking, storage, or another service-level subsystem.
The scanner should be:
- Removed from service
- Labeled Out of Service
- Sent for repair or service evaluation
- Evaluated using Siemens Healthineers documentation and approved diagnostic tools
- Repaired or configured only by qualified personnel
Before return to service, verify stable workstation operation, scanner communication, examination workflow, and data handling. Knowing when to stop external troubleshooting is proper troubleshooting.
Clinical Use Tip
A responsive gantry does not make the scanner safe to use if the operator workstation cannot reliably communicate with it.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"CT staff reported that the SOMATOM X.cite workstation became unresponsive and lost communication with the scanner."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering found an accessible network connection at the workstation was not fully seated."
Resolution
What action was taken.
Example:
"The connection was secured, normal communication returned, and workstation-to-scanner operation was verified with a nonpatient workflow."
Helpful Details to Include (If Known)
- Exact freeze or communication symptoms
- Displayed message
- Workstation power status
- Monitor status
- Network link indication
- Cable condition
- Whether other networked devices were affected
- Results after restart
- Whether communication remained stable
- Final scanner status
Final Thought
Separate workstation, display, cabling, and infrastructure problems before suspecting internal scanner failure, then verify stable end-to-end communication before returning the system to clinical use.
That is successful troubleshooting.