The genomic integration of HIV into cells results in long-term persistence of virally infected cell populations. This integration event acts as a heritable mark that can be tracked to monitor infected cells that persist over time. Previous reports have documented clonal expansion in people and have linked them to proto-oncogenes; however, their significance or contribution to the latent reservoir has remained unclear. Here, we demonstrate that a directed pattern of clonal expansion occurs in vivo, specifically in gene pathways important for viral replication and persistence. These biological processes include cellular division, transcriptional regulation, RNA processing, and posttranslational modification pathways. This indicates preferential expansion when integration events occur within genes or biological pathways beneficial for HIV replication and persistence. Additionally, these expansions occur quickly during unsuppressed viral replication in vivo, reinforcing the importance of early intervention for individuals to limit reservoir seeding of clonally expanded HIV-infected cells.
Kevin G. Haworth, Lauren E. Schefter, Zachary K. Norgaard, Christina Ironside, Jennifer E. Adair, Hans-Peter Kiem
Guidelines: The Editorial Board will only consider letters that we deem relevant and of interest to our readers. We will not post data that have not been subjected to peer review, nor will we post letters that are essentially a reiteration of another letter. We reserve the right to edit any letter for length, content, and clarity. Authors will be notified by e-mail if their letters were accepted. No appeals will be considered.
Specific requirements: All letters must be 400 words or fewer. You may enter the letter as plain text or HTML. The author's name and e-mail address are required, and will be posted with the letter. All possible conflicts of interest must be noted, even if they are not posted. If you wish to include a figure (keep in mind that non-peer-reviewed data will not be posted), please contact the editors directly at email@example.com.