Philips Brilliance Series

Image Artifacts or Reconstruction Issues

On this page

Asset Type

CT Scanner

Manufacturer

Philips

Model

Brilliance Series

What This Guide Helps With

Image artifacts, poor reconstruction, or distorted CT images caused by setup, patient positioning, calibration, accessory, or system issues.

Step-by-Step Troubleshooting

Ensure Patient Safety First

Confirm the patient is stable and the scan is not being repeated unnecessarily.

Action:

Expected: Patient exposure is minimized and clinical care continues safely.

Verify the Reported Image Problem

Review the reported artifact or reconstruction issue with the technologist or radiologist.

Action:

Expected: The issue is narrowed to acquisition, reconstruction, display, or transfer.

Why it matters: CT image problems can come from patient motion, positioning, metal, protocol selection, detector calibration, reconstruction software, or PACS transfer.

Check for Patient Motion or External Causes

Motion and external objects are common causes of poor CT image quality.

Action:

Expected: Artifact is explained by motion or external objects if only one patient or one study was affected.

If this resolves the issue, document the cause and stop troubleshooting.

Confirm Patient Positioning and Scan Centering

Incorrect positioning can cause shading, truncation, or reconstruction problems.

Action:

Expected: Patient and anatomy are properly centered within the selected field of view.

Why it matters: CT reconstruction depends on accurate geometry and complete projection data.

Review Protocol and Reconstruction Selection

Incorrect protocol or reconstruction settings can create images that appear abnormal even when the scanner is functioning normally.

Action:

Expected: Protocol and reconstruction settings match the intended clinical exam.

If protocol selection caused the issue, correct the protocol use and stop troubleshooting.

Check Recent Changes or Software Behavior

Determine whether the issue began after a configuration, network, or software change.

Action:

Expected: Temporary software or reconstruction queue issues clear after safe restart or job management.

Inspect Accessories and Table-Related Causes

Objects in the imaging path can create artifacts.

Action:

Expected: No accessory or table item is causing attenuation or streak artifact.

Check Gantry, Bore, and Visible Obstructions

Visible contamination or obstruction can affect image quality.

Action:

Expected: Gantry area is clean, intact, and free of visible obstruction.

Perform Approved Quality Control or Phantom Check

Use the site-approved CT QC process to determine whether the artifact is reproducible without a patient.

Action:

Expected: QC passes and images are free of artifacts.

If QC fails or the artifact appears on phantom images, remove the scanner from clinical use and escalate.

Check Reconstruction Console and Storage Status

Reconstruction issues may occur if the system cannot process or store image data correctly.

Action:

Expected: Reconstruction completes normally and images are available locally before transfer.

Why it matters: A PACS or network issue can look like a reconstruction issue if images are missing, delayed, or incomplete.

Verify Network and PACS Transfer Separately

If reconstructed images look correct locally but wrong or incomplete in PACS, troubleshoot the image transfer path.

Action:

Expected: The scanner reconstruction is confirmed separate from PACS transfer or display issues.

Review System Messages and Error Logs at the Operator Level

Check for visible system messages without performing internal service procedures.

Action:

Expected: Any system fault information is captured for service evaluation.

If the Problem Persists

If image artifacts or reconstruction issues continue after patient motion, positioning, accessories, protocol selection, QC, reconstruction console status, and PACS transfer have been checked, the likely cause is internal or service-level.

Possible internal causes may include detector calibration failure, data acquisition fault, reconstruction hardware/software failure, tube or generator instability, gantry alignment issue, or system storage failure.

The device should be removed from service if image quality may affect diagnosis, labeled Out of Service, escalated to Philips service, imaging service, or qualified CT repair support, and held from patient use until image quality and reconstruction performance are verified.

Knowing when to stop is proper troubleshooting. CT image quality issues can affect diagnosis and patient dose, so continued clinical use should not be allowed when image integrity is uncertain.

Clinical Use Tip

Do not troubleshoot image artifact problems by repeatedly scanning patients. Use phantom testing, approved QC workflows, prior images, and local image review whenever possible to reduce unnecessary radiation exposure.

Do not troubleshoot on an active patient. Move the patient to a backup scanner first when imaging must continue, and protect therapy or care continuity by coordinating with CT staff and the radiologist.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"CT staff reported streak artifacts and incomplete reconstructed image series on a Philips Brilliance CT scan."

Cause

What was observed during troubleshooting.

Example:
"Patient motion and external objects were ruled out, protocol settings were verified, and phantom QC reproduced image artifacts."

Resolution

What action was taken.

Example:
"Scanner was removed from service, labeled Out of Service, and escalated to Philips service for detector/reconstruction system evaluation."

Helpful Details to Include (If Known)

Final Thought

CT image artifacts and reconstruction problems should be approached logically and safely. Rule out patient motion, positioning, protocol selection, accessories, and PACS transfer before assuming scanner failure. If QC fails or image integrity is uncertain, remove the system from service and document the findings clearly.

That is successful troubleshooting.

Related Guides

Was this guide helpful?

Don't see a guide you need?

Suggest a Guide