cobas taqman mtb test definition file v3.0 for use with amplilink 3.3 의 안전성 경고

Safety alert

2012-12-12

2012-12-12

Hong Kong

DH

https://www.mdco.gov.hk/english/safety/recalls/recalls_20121212a.html

Medical device safety alert: roche cobas taqman mtb test definition file v3.0 for use with amplilink 3.3 medical device manufacturer, roche limited has issued a medical device safety alert concerning cobas taqman mtb test definition file v3.0 for use with amplilink 3.3 (material number 04803531190, all lots). a recent investigation into the affected product revealed that the ct cutoff value has been set at 48 rather than the correct value of 50. when using the cobas taqman mtb test definition file v3.0 with amplilink 3.3, there is a rare circumstance that ct values of patient samples may fall in the range of 48 to 50. results falling within this range would have been considered as negatives. the frequency of results with ct value between 48 and 50 is rare. previous data generated indicates that 0.7% of samples fall in the ct range of 48 to 50. the frequency of the failure mode is estimated to be low and any subsequent health consequences is remote. in addition, ct value within this range indicates the presence of very low titre of mtb dna and it is expected that such sample would generate a negative smear test result. management of such patient will depend on the result of bacterial culture in conjunction with other clinical and laboratory tests. therefore the risk of causing adverse health consequence is remote and review of previously generated results is not indicated. an updated ce-ivd tdf, v3.1 with the correct ct cutoff value of 50 will be released in the near future. as an interim measure, the manufacturer recommends users to review all ct values after each run. in the unlikely event that samples with ct values in the range of 48 to 50 are generated, these results should be reported as positive. according to the local supplier, the affected products were distributed in hong kong. if you are in possession of the affected product, please contact your supplier for necessary actions. posted on 12 december 2012.