Glucose Repeat Rules in Telcor

Hi Cindy, 
We recently made a change in Telcor that added the Repeat Configuration. We have the hold and repeat timeframe both for 5 minutes. The percent variation I believe is defaulted by Telcor and that is at 15%.
Our settings are:
Record 1 <=% variation: Send; confirm by repeat
Record 2 <=% variation Don't send;  repeat
Record 1 > % variation Exception; discrepant 
Record 2 > % variation Send; discrepant repeat

Our uses add a note on the glucometer and this helps us understand why a repeat was done. 

I would review Telcor's manual for more detail. It helped me understand the logic better for when the samples lands in the Results ExceptionQ.  

Thanks Jessica,
We have had repeat rules set for many years, just curious what variance others were using.  

This topic comes up from time to time.  Considering that most of us in the POCC role are or were laboratorians, I understand why the Telcor rule makes sense regarding what result is ultimately sent to the chart based on common sense rules around the repeat testing.  Many years ago however, the point was made that from our vantage point as POCCs, we in fact do not know truly what result the clinical staff has used.  So, repeat rules in the middleware/LIS are actually manipulating data away from the chart that the person performing the test had access to and may have indeed treated the patient on, even if it did not make medical sense.  All that to say, we removed any and all repeat rules in the middleware so that the patient chart actually matches the values the clinical staff had access to and could have acted on.  In any legal case where the patient medical record is expected to represent what actually happened, including all lab values, we thought this the safest route.  We do have a means set up on the device where the staff can tag the result as unreportable and we train them on using that, but that is very different from us deciding a result is unreportable based on repeat rules.