Asset Type
CT Scanner
Manufacturer
Siemens Healthineers
Model
SOMATOM Series
What This Guide Helps With
This guide assists Clinical Engineering in troubleshooting situations where a Siemens Healthineers SOMATOM Series CT scanner fails to send images to a PACS server or other DICOM destinations. Symptoms may include images not appearing in PACS, failed DICOM transfers, or errors on the modality console. The focus is on external and verifiable issues before assuming internal hardware or software failure.
Step-by-Step Troubleshooting
Verify Network Connection
- Check that the CT scanner is connected to the hospital network (Ethernet port link lights are active).
- Confirm the network cable is fully seated and undamaged.
- Why it matters: DICOM transfer requires active network communication; loose cables or port issues are a common cause.
Ping the PACS Server
- From the CT console or service workstation, ping the PACS server IP.
- Confirm there is a response and note any packet loss.
- Why it matters: Ensures network reachability; no response indicates a network or firewall issue.
Check DICOM Configuration
- Verify AE Title, IP address, and port settings on the CT scanner match the PACS configuration.
- Confirm that DICOM destinations are enabled and active in the modality software.
- Why it matters: Incorrect AE Titles or ports prevent image transfer.
Verify PACS Availability
- Check that the PACS server is operational and not in maintenance mode.
- Confirm sufficient storage space and that it is not rejecting incoming connections.
Restart Modality Services (if permitted)
- Restart DICOM service or network interface on the CT console.
- Why it matters: Sometimes network services hang and restarting clears temporary faults.
Check for Software Updates or Error Logs
- Review CT console logs for DICOM-related error codes.
- Note any specific transfer errors (e.g., association rejected, connection timeout).
Swap Ports / Cables
- If using a wired connection, try an alternate network port and/or cable.
- Why it matters: Eliminates physical network faults.
If the Problem Persists
External network and configuration issues have been ruled out.
The issue may be internal to the CT system’s DICOM service or software stack.
Action:
- Remove the CT scanner from PACS transfer use.
- Label “Out of Service – DICOM Transfer Fault.”
- Escalate to Siemens Healthineers service or your internal repair team for bench evaluation.
Clinical Use Tip
- Do not attempt DICOM troubleshooting during a patient scan.
- If the scanner is needed for patient care, route the patient to another available CT scanner.
- Always ensure patient imaging is not delayed due to network troubleshooting.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
“CT images from SOMATOM Series are not appearing in PACS; transfer errors observed on the console.”
Cause
What was observed during troubleshooting.
Example:
“Network connection verified; AE Title and PACS IP correct; PACS operational; temporary DICOM service restart did not resolve issue.”
Resolution
What action was taken.
Example:
“Scanner labeled Out of Service; issue escalated to Siemens service for DICOM software evaluation.”
Helpful Details to Include
- Network cable and port tested
- PACS server availability verified
- DICOM AE Title and port settings confirmed
- Error messages from modality logged
- Final device status: Out of Service, pending repair
Final Thought
Patient safety is the top priority; ensure imaging continues on an alternate device. Clinical Engineering troubleshooting should follow a logical, stepwise approach, ruling out external and network issues before assuming internal failures. Proper CCR documentation ensures accountability and supports timely repair.
That is successful troubleshooting.