On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshoots tissue-container, basket, carrier, loading, positioning, or detection conditions that prevent the processor from recognizing a properly loaded processing setup.
Step-by-Step Troubleshooting
1. Protect Specimens Before Troubleshooting
If tissue specimens are involved, have laboratory staff secure them according to laboratory handling procedures before manipulating baskets, containers, or processor loading areas.
Do not repeatedly start processing attempts while specimen location or loading status is uncertain.
Expected outcome: Specimens remain accounted for and protected while the detection problem is investigated.
2. Confirm What Is Actually Not Being Detected
Determine what staff mean by “sample, rack, or carrier not detected.” On a tissue processor, the complaint may involve a specimen basket, processing container, loading position, retort-related readiness condition, or another component required before processing can begin.
Record the exact displayed message if one is present.
Expected outcome: The specific item or loading condition associated with the complaint is identified.
3. Inspect the Basket or Carrier Externally
Check the applicable basket, carrier, lid, container, or other removable processing component for damage, deformation, contamination, incorrect assembly, or an object preventing normal seating.
Do not modify the component to force acceptance.
Expected outcome: The removable component is intact, clean enough for normal engagement, and correctly assembled.
4. Verify Correct Positioning
Have qualified laboratory staff confirm that the basket or carrier is installed in the intended orientation and fully seated.
Look for obvious obstructions, tissue debris, paraffin, residue, or other material preventing complete positioning.
Expected outcome: The component sits fully and correctly in its intended position. If proper seating restores detection, troubleshooting can stop after verification.
5. Inspect Accessible Detection Areas
With the processor in a safe condition, visually inspect accessible areas associated with component detection for contamination, obstruction, or damage.
Clean only external or routinely accessible surfaces using approved laboratory/device procedures. Do not disassemble sensors or internal mechanisms.
Expected outcome: Accessible detection surfaces are unobstructed and undamaged.
6. Compare With a Known-Good Component
If another compatible basket, carrier, or removable component is available and laboratory workflow allows, substitute a known-good item.
If the known-good component is detected normally, inspect the original accessory more closely and remove it from use if damaged.
Expected outcome: The comparison identifies whether the condition follows the removable component or remains with the processor.
7. Check Related Covers, Lids, and Accessible Interlocks
Confirm that accessible covers, lids, and doors associated with normal processing are fully closed and correctly positioned.
Do not defeat or bypass safety interlocks.
Expected outcome: All required external closures are properly engaged and the processor recognizes the loading condition.
8. Restart Only if Appropriate
If no specimens are at risk and laboratory staff approve, perform a normal restart to clear a temporary state or communication condition.
Do not repeatedly restart the system if the same detection failure returns.
Expected outcome: The system initializes normally and detects the correctly installed component. If so, troubleshooting can stop after final verification.
9. Perform Final Functional Verification
Confirm that the processor consistently recognizes the basket, carrier, or applicable loading condition and reaches the expected ready state without requiring force or repeated repositioning.
Expected outcome: The component is reliably detected and the processor is ready for normal use.
If the Problem Persists
If correct loading, component condition, seating, accessible detection areas, covers, interlocks, and known-good substitution have been checked and the problem remains, common external causes have been ruled out.
The remaining cause may involve an internal position sensor, interlock, alignment mechanism, control circuit, internal communication path, or service-level configuration condition.
The device should be:
- Removed from service if reliable detection cannot be established.
- Labeled Out of Service.
- Sent for repair or qualified bench/service evaluation.
- Evaluated using appropriate Sakura Finetek documentation and approved test equipment.
- Repaired or configured only by qualified personnel.
Do not bypass detection or safety mechanisms to allow processing. Complete applicable functional verification before returning the processor to service.
Knowing when to stop external troubleshooting is proper troubleshooting.
Clinical Use Tip
Never begin a processing cycle unless the specimen basket or required loading component is positively and consistently recognized by the processor.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Laboratory staff reported that the processor would not recognize the loaded tissue basket."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering found residue preventing the removable basket assembly from seating completely."
Resolution
What action was taken.
Example:
"The accessible seating area was cleaned according to approved procedures, the basket was reinstalled, reliable detection was verified, and the processor was returned to service."
Helpful Details to Include (If Known)
- Exact displayed message
- Component that was not detected
- Specimen status
- Basket or carrier condition
- Orientation and seating observed
- Visible residue or obstruction
- Known-good component substitution results
- Cover or lid condition
- Results after restart
- Final device status
Final Thought
Protect specimens, confirm exactly what is not being recognized, verify removable components and positioning before suspecting internal detection hardware, and escalate any unreliable detection condition with clear documentation.
That is successful troubleshooting.