On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Use this guide when expected results are delayed, absent, unexpectedly inconsistent, or do not follow the normal sample-to-result workflow.
Step-by-Step Troubleshooting
1. Protect Patient Care and Confirm the Exact Result Problem
Do not release a questionable result or wait indefinitely on an analyzer when patient care depends on timely testing.
Identify whether the result is:
- Still processing
- Completed locally but missing from the LIS
- Never generated
- Flagged or held
- Unexpectedly different from prior or repeat results
- Associated with the wrong or uncertain sample identity
If result integrity is uncertain, involve laboratory personnel and use an alternate validated testing path as appropriate.
Expected outcome: The issue is categorized as processing delay, missing transmission, absent result, or questionable analytical result.
2. Confirm the Correct Sample and Order
Verify:
- Sample ID
- Requested assay
- Rack or carrier position
- Order received by the analyzer
- No duplicate or mismatched sample identification
- Correct patient/order association within the normal workflow
Expected outcome: The analyzer is working on the intended specimen and test. If the problem was an order or identification mismatch, correct it through the approved laboratory process and verify the result pathway.
3. Check Analyzer and Sample Status
Determine where the specimen currently resides in the workflow.
Look for:
- Waiting
- In process
- Completed
- Held
- Aborted
- Rerun pending
- Sample not detected
- Reagent, calibration, or consumable condition preventing completion
Expected outcome: The sample's processing state is known and any external condition delaying it is identified.
4. Verify Reagent, Calibration, and QC Readiness
For the affected assay, confirm:
- Required reagent is recognized
- Calibration status is acceptable
- Required QC is acceptable
- No assay-specific condition is preventing release or processing
Do not bypass an assay hold caused by unresolved calibration or QC.
Expected outcome: The assay is properly qualified for testing. If correcting an identified reagent, calibration, or QC condition restores normal processing, troubleshooting can stop after verification.
5. Check for Sample-Handling Problems
Review whether the affected specimen experienced:
- Barcode failure
- Rack detection problem
- Aspiration error
- Clot or bubble condition
- Insufficient volume
- Probe or pipettor fault
Inspect the sample and rack as appropriate.
Expected outcome: Sample handling is either confirmed normal or a specific cause of the delay is identified and corrected.
6. Distinguish Analyzer Result Generation From LIS Transmission
If the result appears correctly on the analyzer but not in the LIS, treat the problem as a communication or interface issue rather than an analytical failure.
Check for:
- Pending transmission
- Interface disconnected
- Network problem
- Middleware or LIS interruption
Expected outcome: Missing-result issues are correctly separated into analyzer-generation versus result-transmission problems.
7. Investigate Inconsistent Results Safely
For an unexpectedly inconsistent result, do not assume the analyzer is faulty based on one comparison.
Work with laboratory personnel to review:
- Sample integrity
- Correct patient identification
- Adequate volume
- Reagent and calibration status
- QC performance
- Whether other samples on the same assay are behaving normally
- Whether the result is reproducibly inconsistent using the laboratory's approved process
Clinical Engineering should not make clinical interpretation decisions.
Expected outcome: The inconsistency is traced to a sample, assay, QC, or analyzer-level pattern rather than speculation.
8. Check for Broader Analyzer Delays
Determine whether:
- One assay is delayed
- One sample is delayed
- All testing is slow
- Multiple racks are waiting
- A fluidics, consumable, waste, communication, or processing condition is active
Expected outcome: The problem is categorized as isolated or system-wide.
9. Verify the Complete Workflow After Correction
Using appropriate laboratory-approved material, verify:
- Sample is detected
- Order is recognized
- Assay begins
- Processing completes
- Result is generated
- Result transfers to the intended destination
- Required QC remains acceptable
Expected outcome: The complete sample-to-result pathway is reliable. Troubleshooting can stop.
10. Escalate Persistent Missing or Inconsistent Results
If sample identification, handling, reagent, calibration, QC, processing status, and communication have all been verified but results remain unreliable, remove the affected assay or analyzer from service.
Do not attempt internal detector adjustment, assay parameter changes, or restricted service calibration.
Expected outcome: Continued use of an unreliable analytical pathway is prevented and qualified support is engaged.
If the Problem Persists
If sample identity, sample condition, reagent availability, calibration, QC, analyzer status, and LIS communication have been verified, common external causes have been ruled out.
Possible remaining categories include internal measurement performance, fluidics, software processing, database or interface behavior, assay configuration, detector performance, or another service-level problem.
The affected analyzer or assay should be:
- Removed from service
- Labeled Out of Service when appropriate
- Sent for repair or qualified technical evaluation
- Evaluated using Siemens Healthineers documentation and approved test equipment
- Repaired or configured only by qualified personnel
Before return to service, verify the full sample-to-result workflow and complete laboratory-required QC.
Knowing when to stop external troubleshooting is proper troubleshooting.
Clinical Use Tip
For a missing result, trace the specimen from identification through processing and transmission; never assume “no result in the LIS” means the analyzer failed analytically.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Laboratory staff reported that an Atellica IM 1600 result was complete on the analyzer but remained missing from the LIS."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering found the analyzer was processing normally but its network communication had been interrupted."
Resolution
What action was taken.
Example:
"Network communication was restored and an approved test confirmed successful result transmission from the analyzer to the LIS."
Helpful Details to Include (If Known)
- Sample ID and assay affected
- Whether the result existed locally
- Analyzer sample status
- Reagent status
- Calibration and QC status
- Aspiration or sample-handling events
- Barcode and order status
- LIS/interface status
- Whether other samples or assays were affected
- End-to-end test result
- Final analyzer status
Final Thought
Delayed, missing, and inconsistent results require tracing the complete analytical workflow rather than assuming an internal instrument failure. Protect patient-result integrity, verify every external dependency, and escalate when reliable performance cannot be demonstrated.
That is successful troubleshooting.