bioMerieux VITEK 2 Compact

Sample, Rack, or Carrier Is Not Detected

On this page

Asset Type

Microbiology Identification System

Manufacturer

bioMerieux

Model

VITEK 2 Compact

What This Guide Helps With

Use this guide when the system does not detect an expected sample, card, rack, carrier, or other externally handled loading item.

Step-by-Step Troubleshooting

1. Protect Testing Integrity

Do not continue processing a patient specimen if the analyzer cannot reliably identify or detect the required sample-loading component.

Have laboratory staff retain or redirect the specimen according to their validated workflow while Clinical Engineering evaluates the equipment.

Expected outcome: Patient testing is protected from misidentification, missed processing, or incorrect sample association.

2. Confirm What Is Not Being Detected

Determine exactly what laboratory staff mean by “not detected.” Establish whether the problem involves:

Record any displayed message exactly.

Expected outcome: The problem is narrowed to a specific item, position, or system-wide detection condition.

3. Inspect the Sample, Rack, or Carrier Externally

With the system in a safe state, inspect the affected item for:

Compare it with a known-good item when available.

Expected outcome: The item is intact, correctly assembled, clean, and suitable for use.

If replacing a damaged or improperly positioned external item restores detection, troubleshooting can stop after verification.

4. Verify Correct Loading and Positioning

Have trained laboratory personnel confirm the sample, rack, carrier, or card is being inserted and positioned according to the validated workflow.

Clinical Engineering should focus on whether the loading path, seating surfaces, and externally visible guides permit normal placement.

Do not force an item into position.

Expected outcome: The item seats normally and reaches its intended detection position.

5. Inspect the Loading Area

Inspect accessible loading areas for:

Use only approved cleaning methods and do not reach into moving mechanisms.

Expected outcome: The loading area is clean, unobstructed, and allows normal movement.

6. Compare With a Known-Good Item

When permitted by laboratory workflow, test a known-good rack, carrier, or equivalent loading item.

Observe whether the problem follows the original item or remains with the analyzer position.

Expected outcome: The comparison distinguishes an accessory problem from an analyzer-side detection problem.

If the known-good item is detected normally and the original item is confirmed defective or incompatible, the issue is resolved.

7. Check Whether the Problem Is Position-Specific

If multiple loading positions are available, determine whether detection failure occurs only at one location or across the entire system.

Do not continue repeated testing at a position that behaves inconsistently.

Expected outcome: The problem is identified as isolated to one position or affecting the system more broadly.

8. Verify System Status and Configuration

Confirm the analyzer is fully initialized and in the correct operational state for loading.

Verify that no operator-accessible workflow setting, pending action, or system state is preventing recognition.

Do not make unauthorized configuration or service-menu changes.

Expected outcome: The analyzer is in the correct state to detect the loaded item.

9. Perform Final Functional Verification

After correction, verify repeated normal detection using appropriate known-good materials without forcing or manipulating the loading mechanism.

Confirm normal identification and processing handoff before returning the affected function to use.

Expected outcome: Samples, racks, carriers, or equivalent items are detected consistently in normal operation.

If the Problem Persists

If external item condition, orientation, loading technique, obstructions, known-good substitutions, system status, and accessible configuration have been checked, common external causes have been ruled out.

The remaining problem may involve a detection sensor, mechanical transport condition, alignment issue, internal control problem, or service-level configuration issue.

The device should be:

Do not adjust internal sensors, alignments, or mechanisms without authorized procedures. Knowing when to stop external troubleshooting is proper troubleshooting.

Complete appropriate operational and laboratory verification before return to service.

Clinical Use Tip

Treat inconsistent sample detection as a testing-integrity problem, not merely an inconvenience; prevent any possibility of the wrong specimen being associated with a test.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"Laboratory staff reported that a carrier was repeatedly not detected when loaded into the bioMerieux VITEK 2 Compact."

Cause

What was observed during troubleshooting.

Example:
"Clinical Engineering found adhesive residue on the carrier preventing it from seating fully in the loading position."

Resolution

What action was taken.

Example:
"Removed the affected carrier from use, verified proper seating with a known-good carrier, confirmed consistent detection, and returned the analyzer for laboratory verification."

Helpful Details to Include (If Known)

Final Thought

Protect specimen identification first, inspect the external item and loading path, compare with known-good components, and escalate rather than disturbing internal detection hardware. Document the complete troubleshooting path clearly.

That is successful troubleshooting.

Related Guides

Was this guide helpful?

Don't see a guide you need?

Suggest a Guide