Clinitek Status + QC Lockout

We don't use microalbumin on our Clinitek Status+ devices, however, I'm interested to know how you get the QC lockout function to work in the Clinitek Status+ for the urine dipsticks. We have 20 of these devices across our organization and use Telcor QML as our Middleware. QML doesn't have a way of sending the QC expected ranges to the devices, so the only way we can utilize QC lockout is to manually program the QC ranges into each individual device. There is no way we could do that! So instead we have to program our devices with very broad QC ranges, which unfortunately makes the device think QC passes almost every time. But we have it set that the operator has to verify QC results and we have them write down QC results onto a QC logsheet (which we review each month). This makes it super difficult for staff to understand that they cannot trust the "QC Pass" result that the Clinitek gives them. Its frustrating to us for sure! 

We use the Siemens RapidComm application to send lot# information to the Cliniteks.  It also allows us to review QC data electronically.  There are 2 HUGE flaws in the Cliniteks:  1) only one lot can be programmed into each device for each level of QC, 2) the operators are not prevented from entering/running other lots. This means that results may PASS, but review of the data shows that it's corrupted (the lot# they actually ran is not the lot# programmed into the meter).

We are embedding superusers at each of our practices, and providing them with the instructions to review the package inserts when changing lots and update the instrument with the new acceptable ranges. Initial programming was done by POCT staff. 

I completely agree with the Clinitek flaws. It's frustrating that there haven't been any improvements made!