On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Identifies external causes of reconstruction delays or PACS transfer failures including network issues, storage limits, workflow interruptions, or system communication problems.
Step-by-Step Troubleshooting
Ensure Patient Safety First
- Confirm no active exam is in progress and all acquired images are saved locally.
- If needed, move workflow to another unit.
Expected Outcome:
No risk of data loss or patient care disruption.
Check Reconstruction Status and Queue
- Review the system for studies stuck in reconstruction or processing.
- Look for error messages or stalled progress indicators.
Expected Outcome:
Images complete reconstruction or display a clear error.
Why:
Backlogged or stalled reconstruction prevents images from being sent to PACS.
Verify Available System Storage
- Check workstation storage capacity.
Expected Outcome:
At least 10–15% free disk space available.
Why:
Insufficient storage can stop both reconstruction and DICOM export processes.
Confirm Network Connectivity
- Check network status on the workstation:
- Network icon connected
- Ethernet link lights active
- Ability to access hospital network (if applicable)
Expected Outcome:
Stable network connection is present.
Why:
DICOM transfer requires active network communication.
Inspect Network Cabling and Ports
- Check all visible Ethernet connections between:
- Workstation and wall port
- System cabinets and switches
- Reseat cables and inspect for damage.
Expected Outcome:
Secure connections restore communication if cabling was loose.
Why:
Loose or damaged cables commonly cause intermittent transfer failures.
Verify DICOM Destination Configuration
- Confirm correct PACS destination settings:
- AE Title
- IP address
- Port number
- Ensure no recent changes were made.
Expected Outcome:
Correct configuration allows successful communication with PACS.
Why:
Incorrect DICOM settings prevent image routing even if the network is active.
Check for PACS or Server Availability Issues
- Confirm PACS system is operational by:
- Checking with IT or radiology
- Verifying other modalities can send images
Expected Outcome:
If PACS is down, issue is external to the modality.
Why:
System may be functioning correctly but unable to send to an unavailable destination.
Restart DICOM/Acquisition Services or Workstation
- If allowed by policy, restart the acquisition workstation or relevant services.
Expected Outcome:
System clears stalled processes and resumes reconstruction/transfer.
Why:
Software processes can hang and require a restart to recover.
Attempt Manual Resend of Studies
- Select affected studies and attempt manual DICOM resend.
Expected Outcome:
Images successfully transmit to PACS.
Why:
Confirms whether the issue was temporary or persistent.
If the Problem Persists
If reconstruction failures or DICOM transfer issues continue after verifying storage, network, configuration, and PACS availability, the issue is likely internal (software corruption, database issues, or system communication faults).
Remove the system from service, label it Out of Service, and escalate for vendor service or advanced bench evaluation.
Knowing when to stop prevents data loss and workflow disruption.
Clinical Use Tip
Do not troubleshoot during an active patient exam. Ensure all images are safely stored or backed up before performing restarts or system checks.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Images not reconstructing and failing to send to PACS from Hologic Dimensions system."
Cause
What was observed during troubleshooting.
Example:
"Network cable partially disconnected causing intermittent communication failure."
Resolution
What action was taken.
Example:
"Reseated Ethernet connection and verified successful reconstruction and PACS transfer."
Helpful Details to Include (If Known)
- Network status confirmed (connected/disconnected)
- Storage capacity level
- Error messages observed
- Reconstruction queue behavior
- PACS availability status
- Cables reseated or swapped
- Manual resend results
- Final system status
Final Thought
Effective troubleshooting starts with protecting patient data and workflow, then systematically verifying storage, network, and configuration before escalation. Proper documentation ensures repeat issues are resolved faster and more accurately.
That is successful troubleshooting.