On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Image reconstruction failures, delayed image availability, processing errors, or missing CT images after scan acquisition.
Step-by-Step Troubleshooting
1. Ensure Patient Safety First
Confirm the patient is no longer dependent on the affected scan session before troubleshooting.
Action:
- Stop additional scanning until image availability is confirmed
- Notify CT staff that images may not be available for diagnosis
- If urgent imaging is needed, move the patient to another CT scanner if available
- Do not repeat radiation exposure until acquisition status and image availability are reviewed
Expected: Patient care continues safely without unnecessary repeat exposure.
2. Verify the Reported Failure
Confirm exactly what failed.
Action:
- Ask CT staff whether the scan acquired normally
- Determine whether the issue is reconstruction failure, delayed reconstruction, frozen processing, missing images, or PACS transfer failure
- Check whether raw data is still present
- Confirm whether the problem affects one patient, one protocol, or all exams
Expected: The failure type is clearly identified before deeper troubleshooting begins.
Why it matters: A PACS transfer issue can look like reconstruction failure, but the troubleshooting path is different.
3. Check the Operator Console Status
Inspect the CT operator console for visible errors or abnormal behavior.
Action:
- Look for reconstruction queue errors
- Check if the console is frozen, slow, or unresponsive
- Confirm whether other applications are running normally
- Note any displayed error codes or messages exactly as shown
Expected: Console is responsive and reconstruction queue status can be reviewed.
If the console is frozen or unresponsive, proceed with safe restart steps only after confirming no active scan or reconstruction is in progress.
4. Confirm the Scan Data Was Acquired
Make sure the issue is not failed acquisition.
Action:
- Review the completed exam list
- Confirm scan series are listed
- Check whether scout/localizer and axial/helical data exist
- Verify that the correct patient and accession were selected
Expected: Acquired scan data is present and associated with the correct exam.
If no scan data exists, the issue may be acquisition-related rather than reconstruction-related.
5. Check Reconstruction Queue or Pending Jobs
Review whether reconstruction jobs are stuck, paused, failed, or backed up.
Action:
- Open the reconstruction or processing queue
- Look for pending, failed, or incomplete recon jobs
- Confirm whether multiple studies are waiting to process
- Check if one specific series is blocking the queue
Expected: Reconstruction jobs are either actively processing or show a clear failure state.
If one job is stuck and others are waiting behind it, document the affected exam and escalate before deleting or altering data.
6. Verify Protocol and Reconstruction Settings
Confirm that the selected protocol and recon parameters are valid.
Action:
- Review slice thickness, kernel, field of view, recon range, and image series settings
- Compare to a known working protocol if available
- Check whether the failure occurred after protocol editing
- Ask whether this protocol recently changed
Expected: Reconstruction settings are valid and consistent with normal department workflow.
Why it matters: Invalid or unusual recon parameters can cause processing errors even when the scan acquisition was successful.
7. Check Storage Capacity
Low storage can prevent reconstruction or image processing from completing.
Action:
- Check local console storage status if accessible
- Review whether the system reports low disk space
- Confirm whether older completed exams are being archived properly
- Do not delete studies unless following site policy and confirming data is safely archived
Expected: Adequate storage is available for reconstruction and temporary processing.
If storage is full or near full, stop scanning and escalate for controlled data management.
8. Check Network and PACS Separation
Determine whether images failed to reconstruct or simply failed to send.
Action:
- Check whether images are visible locally on the CT console
- Confirm whether images are missing only in PACS
- Test DICOM send status if available
- Check destination status for PACS, archive, or workstation
Expected: Locally reconstructed images are viewable before blaming reconstruction.
If images are present locally but absent in PACS, troubleshoot as a DICOM/network transfer issue, not a reconstruction failure.
9. Attempt a Safe Reprocess or Manual Reconstruction
If raw data is present and the system allows it, attempt reconstruction again using normal operator-level tools.
Action:
- Select the affected raw data or series
- Re-run reconstruction using the original or known-good parameters
- Monitor whether processing completes
- Confirm image series appears locally afterward
Expected: Images reconstruct successfully and become available for review.
If successful, verify image transfer to PACS and stop.
10. Restart the Affected Application or Console if Safe
If reconstruction remains stuck and no active scan is running, a controlled restart may clear a software processing fault.
Action:
- Confirm no patient is being scanned
- Confirm no active reconstruction job should be interrupted
- Follow site-approved shutdown or restart process
- Restart the console or reconstruction application
- Recheck the affected exam and reconstruction queue
Expected: Console returns to normal operation and reconstruction can be retried.
Do not hard power-cycle CT system components unless directed by service procedure or qualified support.
11. Test With a Non-Patient or Phantom Workflow if Available
After patient impact is controlled, verify whether the issue is repeatable.
Action:
- Use a site-approved phantom or test workflow if available
- Run a simple scan and reconstruction
- Confirm local image generation and PACS transfer
- Document whether the issue affects all reconstructions or only one exam/protocol
Expected: Test reconstruction completes normally.
If test reconstructions fail, the issue is likely system-level.
12. Check for Environmental or System Clues
Look for signs of workstation or server instability.
Action:
- Listen for abnormal workstation fan noise
- Check for excessive heat around console cabinets
- Note slow response, freezing, or repeated software errors
- Check for recent power events or IT/network downtime
Expected: No obvious external environmental or power-related cause is present.
Why it matters: Reconstruction can fail due to workstation performance, storage, network, or server-side processing problems.
If the Problem Persists
If reconstruction or image processing still fails after patient safety, acquisition status, queue status, storage, protocol settings, network separation, and environmental or power-related causes have been checked, the issue is likely internal to the CT reconstruction workstation, image processing software, storage system, or system communication pathway.
The CT scanner should be removed from clinical use if images cannot be reliably reconstructed, labeled Out of Service, escalated to GE service, qualified imaging service, or internal imaging support, and evaluated before being returned to patient scanning.
Knowing when to stop is proper troubleshooting. Do not continue scanning patients if image reconstruction reliability is uncertain.
Clinical Use Tip
Do not troubleshoot reconstruction or image processing failures on an active patient. Move the patient to a backup CT scanner or alternate imaging pathway first if imaging is urgent and therapy or clinical decision-making depends on timely image availability.
Do not repeat a CT scan only because images are missing from PACS. First confirm whether the images exist locally, whether raw data is available, and whether reconstruction or transfer failed. This helps prevent unnecessary radiation exposure and supports continuity of care.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"CT staff reported that a GE Revolution Series CT exam completed acquisition, but reconstructed images were not available for review."
Cause
What was observed during troubleshooting.
Example:
"Troubleshooting found the raw scan data present, but the reconstruction queue was stalled and no completed image series was generated."
Resolution
What action was taken.
Example:
"Confirmed patient was no longer on the scanner, checked local image availability, verified storage and queue status, attempted safe reprocessing, and removed the CT scanner from service for GE imaging service evaluation."
Helpful Details to Include (If Known)
- Exact reconstruction error message or code
- Alarm behavior or displayed processing alerts
- Accessories swapped or removed during evaluation
- Power behavior, restart behavior, or recent power events
- Environmental factors such as heat, console cabinet airflow, or workstation fan noise
- Indicator lights, console messages, queue status, or workstation status
- Whether raw data was present
- Whether images were visible locally
- Whether images were missing only from PACS
- Affected patient exam or accession number, following privacy policy
- Whether one protocol or all protocols were affected
- Storage status if available
- Any recent protocol, software, or network changes
- Whether console was frozen, slow, or responsive
- Whether a restart or reprocess was attempted
- Final device status
Final Thought
Reconstruction failures require careful separation of acquisition, processing, storage, and image transfer problems. Clinical Engineering should protect the patient first, avoid unnecessary repeat exposure, verify the simplest external causes, and escalate when image availability cannot be trusted.
That is successful troubleshooting.