DOI 10.1371/journal.pntd.0003738
Impact of the use of a rapid diagnostic test for visceral leishmaniasis on clinical practice in Ethiopia: a retrospective study.
Аннотация
BACKGROUND
Diagnostic guidelines for Visceral Leishmaniasis (VL) in the East African region are complex. Patients meeting the VL clinical case definition should be tested by rK39 rapid diagnostic test (RDT) followed by the Direct Agglutination Test (DAT) or tissue aspiration if RDT-negative. Otherwise, RDT-positive patients should be started on VL treatment. We evaluated how this guideline is adhered to by assessing the routine clinical practice in a university hospital in North-West Ethiopia.
METHODS
Retrospective record analysis was done for all patients who had an rK39-RDT done at University of Gondar (UoG) Hospital between June 2012 and June 2013. We described the diagnostic work-up performed and the proportion initiated on VL treatment by test result.
RESULTS/FINDINGS: From a total of 928 patients tested, 308 (33.2%) were rK39 RDT-positive. Spleen or bone marrow aspiration was done for 237 (77.2%) RDT-positive patients. Of these, 165 were confirmed parasitologically, yielding a positive predictive value of 69.6%. Only 126 (20.3%) of the 620 patients with a negative rK39 test underwent further testing by tissue aspiration, of which 22 (17.5%) were also parasitology positive. HIV test results were available for 570 (61.4%) patients and 36 (6.3%) were HIV-infected. Of the 187 parasitologically confirmed patients, 182 (97.3%) were started on VL treatment.
CONCLUSIONS/DISCUSSION: A negative rK39 test was often not followed by further testing and a positive rK39 test result was followed by tissue aspiration in three out of four cases. Further research is required to understand why the diagnostic work-up did not comply with the guidelines, including evaluating adherence to the VL clinical case definition and quality of rK39-RDT testing.
Предметные рубрики MeSH
Подготовка и перевод публикации
Обработка статьи · этапы, ошибки и управление
Ошибки и ограничения
История · было → стало
Состояние обновляется каждые 5 секунд, пока блок открыт. Процент показывается только там, где известен объём работы. Пауза останавливает продолжение этапа; текущий запрос к источнику может завершиться.
Тип публикации указан по данным источника. Уровень доказательности автоматически не присваивается.