|
The customer states there is an issue with the cobas infinity software that allows test results to validated and released before the system performs corresponding quality control evaluation.Consequently, patient results will not be linked with quality control results and will have a status indicating that quality control results are pending.The customer set up the triggering of a rule in the cobas infinity system to "after result evaluation", which means that the rule is to be triggered only after quality control, average of normals, and serum indices have been evaluated for sample test results.When using the "after result evaluation" setting, it was found that rules would be triggered in the cobas infinity system before the quality control evaluation of some tests performed for a sample.The customer expected individual test results for a patient sample to be validated only after the quality control evaluation has been performed, but this was not the case.The cobas infinity would trigger the rule for all tests with results belonging to the test group assigned to the rule.When this occurs, the rule would be triggered for some sample test results even if quality controls for that test have not been evaluated.
|
|
Cobas infinity allows the creation of customized rules.The rules are configurations of conditions and actions related to orders, tests, tubes, or instruments.Thus, if certain conditions are met, the software automatically triggers the corresponding actions.One of the available actions in the cobas infinity rule engine is the test result validation.In this case, it is alleged that some tests have been validated before the system performs the corresponding qc evaluation and, consequently, the patient results are not linked with qc results and they still have a flag of qcps (qc pending status).During the investigation, it was found that the customer is validating using the rule engine feature using the trigger mode after result evaluation - after qc, average of normals (aon) and serum index (si) evaluation.According to product labeling, this trigger mode will be launched when all the results are evaluated first by qc, aon and si and then the configured rule, and therefore on the rule condition, it was not configured to check if the qc is still pending to be evaluated.However, the expected way this trigger mode works is that any test evaluated by qc, aon and si will trigger the rule configured as after result evaluation.This rule, as indicated in labeling, will evaluate the rule conditions for each test.As the rule conditions are not checking if the qc is already evaluated for the specific test result, it may happen in some situations that the rule is executed for a test with the qc still pending.There is the following warning in product labeling: do not validate tests or results with rule engine rules as unexpected system behavior can occur, it is acceptable to do so only when qc flags do not have to be taken into account for the test to be validated.Product labeling also states: if you configure a rule to validate results, it can happen that aon or qc results are not correctly associated to the patient results.Therefore, the rule engine configured with the action validation while using the qc status on the conditions fields is considered off-label use.The documentation that contributed to the customer's misunderstanding of how the rule trigger mode after result evaluation" was working has been considered a product labeling issue.
|