Siemens Healthineers Biograph Vision

Detector or Acquisition Hardware Is Not Ready

On this page

Asset Type

PET / CT System

Manufacturer

Siemens Healthineers

Model

Biograph Vision

What This Guide Helps With

Use this guide when PET or CT acquisition hardware remains unavailable, not ready, or fails initialization because of startup, connection, environmental, or subsystem-readiness conditions.

Step-by-Step Troubleshooting

1. Protect the Patient and Stop Clinical Acquisition Attempts

Do not continue attempting patient scans when required detector or acquisition hardware is not ready.

Move the patient to a safe condition and arrange alternate imaging when clinically necessary.

Expected outcome: No patient examination depends on unreliable acquisition hardware.

If acquisition readiness cannot be established, the system remains out of clinical use.

2. Confirm the Exact Not-Ready Condition

Identify:

Expected outcome: The affected acquisition subsystem and sequence of events are documented.

If the subsystem transitions normally to ready and remains stable during verification, proceed to final functional testing.

3. Verify Complete System Startup

Confirm that the Biograph Vision has completed its normal startup sequence and that no other major system subsystem remains offline.

A detector or acquisition-not-ready indication may be secondary to incomplete system initialization.

Expected outcome: The scanner, workstation, and required supporting subsystems have completed normal startup.

If waiting for a legitimate startup sequence to complete resolves the condition and the system remains stable, verify operation and stop.

4. Inspect Accessible External Connections

Check accessible external cables and connectors related to operator consoles, acquisition peripherals, or externally connected system components.

Look for:

Do not open detector electronics, gantry covers, or internal equipment cabinets.

Expected outcome: Accessible external acquisition-related connections are secure and undamaged.

If restoring an obvious external connection returns the subsystem to ready, complete final verification and stop.

5. Check Environmental Conditions

Confirm that the equipment room and scanner environment do not show obvious signs of:

Detector and acquisition systems may remain inhibited if environmental conditions are not acceptable.

Expected outcome: No external environmental condition is preventing acquisition readiness.

If environmental restoration returns the hardware to a stable ready state, verify operation and stop.

6. Review System Status Without Changing Service Configuration

Use normal operator-accessible status information to identify whether another subsystem or prerequisite is preventing readiness.

Do not:

Expected outcome: Any operator-visible prerequisite or related fault is identified without altering protected settings.

If correcting a normal operating-state issue restores acquisition readiness, verify the system and stop.

7. Perform One Controlled Restart if Appropriate

If no hazard exists and the system can be shut down normally, perform one approved controlled restart.

Avoid repeated power cycling if the same acquisition hardware remains unavailable.

Expected outcome: All required detector and acquisition subsystems initialize and report ready after startup.

If readiness is restored and remains stable, proceed to final verification and stop.

8. Verify Consistent Ready State

Allow the system to remain in its normal ready condition and confirm that the affected subsystem does not immediately drop offline or return to not-ready status.

Expected outcome: The acquisition subsystem remains stable and ready without recurring faults.

If readiness is intermittent, remove the system from service and escalate even if it temporarily recovers.

9. Perform Final Functional Verification

Before release, confirm:

Expected outcome: Acquisition hardware is stable, ready, and passes required verification.

If all checks pass, troubleshooting is complete.

10. Escalate Persistent Acquisition Hardware Faults

If detector or acquisition hardware remains unavailable after startup, environmental, connection, and normal system-state checks, stop external troubleshooting.

Expected outcome: The system is removed from clinical service and referred for qualified technical evaluation.

If the Problem Persists

Common external causes have been ruled out. Remaining possibilities may involve internal detector electronics, acquisition controllers, timing or synchronization systems, internal communication, internal power distribution, cooling, calibration data, or another service-level condition.

The device should be:

Do not open detector assemblies or attempt board-level diagnosis.

Return to clinical use only after acquisition readiness, required quality checks, and appropriate functional verification have passed.

Knowing when to stop external troubleshooting and escalate is proper troubleshooting.

Clinical Use Tip

A detector that briefly returns to ready but repeatedly drops offline should not be considered reliable enough for patient imaging.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"Clinical staff reported that the Biograph Vision remained unavailable for scanning because the acquisition subsystem would not reach ready status."

Cause

What was observed during troubleshooting.

Example:
"Clinical Engineering found an accessible external communication cable loose following nearby equipment service."

Resolution

What action was taken.

Example:
"Clinical Engineering secured the connection, restarted the system normally, verified stable acquisition readiness, and completed functional verification before return to service."

Helpful Details to Include (If Known)

Final Thought

Protect the patient, confirm complete startup and simple external causes first, avoid assuming an internal detector failure prematurely, and escalate any acquisition subsystem that cannot demonstrate stable readiness.

That is successful troubleshooting.

Related Guides

Was this guide helpful?

Don't see a guide you need?

Suggest a Guide