7 04/2011, version 1.0
cobas s 201 system
1.6.2 Aborting a pooling run after a control pipetting error locks the SK24 rack
A Controls pipetting error dialog box is displayed if a control pipetting error occurs, as expected. If
the operator aborts the pooling run, instead of following the prompts in the dialog box, the run is
successfully aborted and the associated donor samples can be retested. However, the SK24 rack
associated with the failed control(s) is not released and cannot be reused.
To avoid the problem, the operator should follow the onscreen instructions. In the event that the
anomaly occurs, the laboratory administrator should contact Roche Service for a replacement SK24
rack or relabel the SK24 rack ID with new sticker marked with a new barcode ID.
1.6.3 Plates with barcode reading errors are ignored
If more than one Deep Well Plate is loaded on a plate carrier, and the barcode labels for all the
plates are unreadable, the carrier is ejected, and the operator is prompted to manually enter the
barcode for the plate in position one. The rest of the plates are ignored. In general, the operator is
only prompted to manually enter barcodes for an unreadable plate if a readable plate follows it.
The operator should verify that the correct number of plates is recognized by the pipettor. If there
are any plate barcode reading errors, a plate with a readable barcode should be loaded in the last
used position on the carrier.
1.6.4 Donor samples incorrectly scheduled for SP12 from IP
If an aspirate or a dispense error occurs during an SP12 pooling run from an Intermediate Plate, the
associated donor samples remain pending for SP12 from the Intermediate Plate, and the pooling
requests are not listed in the Required Pooling tab for the batch. The system should schedule the
donor samples for ResP1 from donor tubes, since the volume left in the IP well is not enough for a
second SP12 pooling run
The operator should change the pooling request for the affected donor samples from SP12 to ResP1
and then load the donor tubes for the Secondary Pooling run.
1.6.5 Donor samples can be retested in a Primary Pooling run for the same test
Donor samples tested in a one-step pooling run (PP1 or Short Run PP48) can be tested again in a
two-step pooling run (PP96 or PP480) for the same test. The first valid result is assigned to the
donor sample and transmitted to the LIS.
The operator should not retest donor samples in a Primary Pooling run for the same test.
1.6.6 IP remains pending for Batch Run if Pooling Manager disconnected from server
Proper error handling is performed during a PP480 Plate Run if a donor sample pipetting error
occurs, even if the Pooling Manager workstation is disconnected from the server. An Oracle error
displays at the end of the pooling run indicating the lost connection. Once the connection is
reestablished and the workstation rebooted, the IP is pending for a Batch Run but the donor sample
with the pipetting error is not scheduled for SP6. The IP remains pending for a Batch Run even after
it is successfully pipetted in a Batch Run. If the IP is loaded for another Batch Run, one Primary
Pool is prepared containing the 11 donor samples successfully pipetted into the well that would
have contained the donor sample with the pipetting error. These donor samples were already
included in a Primary Pool in the previous Batch Run. The IP is still pending for Batch Run. The
donor sample with the pipetting error is only scheduled for SP6 after the IP well is rejected.
To avoid this issue the operator should reject the IP well after the IP has been used in the first Batch
Run, and retest the affected donor samples in SP6.
For donors tested in more than one Primary Pool, the first valid result is assigned to the donor
sample and transmitted to the LIS.