Determining human immunodeficiency virus coreceptor use in a clinical setting: degree of correlation between two phenotypic assays and a bioinformatic model.

Abstract:

Two recombinant phenotypic assays for human immunodeficiency virus ...
Two recombinant phenotypic assays for human immunodeficiency virus (HIV) coreceptor usage and an HIV envelope genotypic predictor were employed on a set of clinically derived HIV type 1 (HIV-1) samples in order to evaluate the concordance between measures. Previously genotyped HIV-1 samples derived from antiretroviral-naive individuals were tested for coreceptor usage using two independent phenotyping methods. Phenotypes were determined by validated recombinant assays that incorporate either an approximately 2,500-bp ("Trofile" assay) or an approximately 900-bp (TRT assay) fragment of the HIV envelope gp120. Population-based HIV envelope V3 loop sequences ( approximately 105 bp) were derived by automated sequence analysis. Genotypic coreceptor predictions were performed using a support vector machine model trained on a separate genotype-Trofile phenotype data set. HIV coreceptor usage was obtained from both phenotypic assays for 74 samples, with an overall 85.1% concordance. There was no evidence of a difference in sensitivity between the two phenotypic assays. A bioinformatic algorithm based on a support vector machine using HIV V3 genotype data was able to achieve 86.5% and 79.7% concordance with the Trofile and TRT assays, respectively, approaching the degree of agreement between the two phenotype assays. In most cases, the phenotype assays and the bioinformatic approach gave similar results. However, in cases where there were differences in the tropism results, it was not clear which of the assays was "correct." X4 (CXCR4-using) minority species in clinically derived samples likely complicate the interpretation of both phenotypic and genotypic assessments of HIV tropism.

Polymerases:

Topics:

Status:

new topics/pols set partial results complete validated

Results:

No results available for this paper.

Entry validated by:

Using Polbase tables:

Sorting:

Tables may be sorted by clicking on any of the column titles. A second click reverses the sort order. <Ctrl> + click on the column titles to sort by more than one column (e.g. family then name).

Filtering:

It is also possible to filter the table by typing into the search box above the table. This will instantly hide lines from the table that do not contain your search text.