Canon Aquilion Series

Detector Calibration or Image Artifacts

On this page

Asset Type

CT Scanner

Manufacturer

Canon

Model

Aquilion Series

What This Guide Helps With

Image artifacts, calibration failures, ring artifacts, streaking, shading, or inconsistent CT image quality caused by setup, calibration, or detector-related issues.

Step-by-Step Troubleshooting

1. Ensure Patient Safety First

Do not troubleshoot image quality issues during an active patient scan unless the scan has been safely stopped by clinical staff.

Action:

Expected outcome:
No patient is scanned on a system producing questionable or unreliable images.

2. Verify the Reported Artifact or Calibration Issue

Confirm exactly what the user is seeing before assuming detector failure.

Action:

Expected outcome:
The problem is clearly defined and repeatable, or isolated to a specific scan condition.

Why it matters:
Some artifacts are caused by patient positioning, metal, contrast, protocol settings, or reconstruction choices rather than detector hardware.

3. Remove Patient-Related and External Causes First

Artifacts may be caused by items in the scan field.

Action:

Expected outcome:
Artifacts caused by external objects or patient setup are identified and corrected.

If this resolves the issue, document the finding and return the scanner to service after image quality is confirmed.

4. Check Scan Protocol and Reconstruction Settings

Incorrect protocol or reconstruction choices can mimic system image problems.

Action:

Expected outcome:
If the issue is protocol-specific, clinical applications or CT leadership should review the protocol before equipment repair is pursued.

Why it matters:
Clinical Engineering should rule out setup and configuration issues before escalating to detector or reconstruction hardware concerns.

5. Check System Readiness and Error Messages

Detector calibration issues may be accompanied by system warnings or failed readiness checks.

Action:

Expected outcome:
Any system-generated fault is captured accurately for service documentation.

6. Confirm Gantry and Bore Are Clear

Objects inside the gantry opening can affect image quality or interfere with calibration scans.

Action:

Expected outcome:
The scan field is clear and free of external causes.

7. Verify Environmental Conditions

CT detector calibration can be affected by temperature instability or room environmental changes.

Action:

Expected outcome:
Environmental causes are ruled out or corrected before deeper troubleshooting.

Why it matters:
Detector systems and image calibration depend on stable environmental conditions.

8. Perform a Proper System Restart if Appropriate

Temporary software or reconstruction issues may clear after a controlled restart.

Action:

Expected outcome:
If the artifact was caused by a temporary software or communication issue, the scanner returns to normal operation.

If this resolves the issue, perform image verification before returning to service.

9. Run User-Accessible Calibration or Air Calibration Only if Allowed

Calibration should only be performed if it is part of normal operator-accessible workflow or approved Clinical Engineering procedure.

Action:

Expected outcome:
Calibration completes successfully and image quality returns to normal, or the failure is confirmed for escalation.

Why it matters:
Failed calibration after external causes are ruled out may indicate detector, DAS, reconstruction, temperature, or calibration data issues.

10. Perform Phantom or Image Quality Verification

Before returning the scanner to service, image quality should be verified.

Action:

Expected outcome:
Images are clinically acceptable and artifacts are not reproducible.

If artifacts remain, remove the scanner from service.

11. Identify Artifact Pattern for Escalation

The artifact pattern can help determine the likely area of concern.

Action:

Expected outcome:
The service vendor or imaging specialist receives useful detail instead of a vague “bad image” complaint.

12. Check for Recent Service, Updates, or Events

Recent changes often explain image quality problems.

Action:

Expected outcome:
A possible trigger is identified and included in the repair escalation.

If the Problem Persists

If image artifacts remain after patient setup, external objects, protocol settings, room conditions, restart, and approved calibration checks have been ruled out, the issue is likely internal.

The scanner should be:

Possible internal causes may include detector calibration data failure, detector module issue, DAS communication problem, reconstruction system issue, thermal instability, or other service-level fault.

Knowing when to stop is proper troubleshooting. CT image quality problems can affect diagnosis, so do not continue scanning patients if artifact behavior is unresolved.

Clinical Use Tip

Do not troubleshoot detector artifacts on an active patient. If image quality is questionable, stop clinical use, move the patient to another scanner if available, and verify image quality with approved testing before returning the system to service.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"CT staff reported ring artifacts and failed detector calibration on the Canon Aquilion Series CT scanner during morning startup."

Cause

What was observed during troubleshooting.

Example:
"External scan field, patient setup, room conditions, protocol selection, and system restart were checked; artifact persisted during phantom verification."

Resolution

What action was taken.

Example:
"Scanner was removed from service, labeled Out of Service, and escalated to Canon service for detector calibration and image quality evaluation."

Helpful Details to Include (If Known)

Final Thought

Detector calibration and image artifact troubleshooting must stay patient-safety focused. Start with visible, external, and setup-related causes before assuming internal detector failure. If artifacts remain after basic checks and approved calibration steps, remove the scanner from service and escalate with clear documentation.

That is successful troubleshooting.

Related Guides

Was this guide helpful?

Don't see a guide you need?

Suggest a Guide