HIV-Associated Diffuse Large B-Cell Lymphoma Shows Different Genomic Patterns between EBV-Positive and EBV-Negative Tumors
Notice bibliographique
Résumé
Introduction: HIV-associated diffuse large B-cell lymphoma (HIV-DLBCL) is a significant complication in HIV-positive individuals, presenting unique clinical challenges and a poorer prognosis compared to patients with de novo DLBCL. Epstein-Barr Virus (EBV) status is a critical factor influencing the pathogenesis, clinical behavior, and therapeutic responses in these lymphomas. Plasmablastic lymphomas (PBL) have shared some overlapping genomic abnormalities with HIV-DLBCL including MYC rearrangements. This study aims to elucidate the differences in the genetic profiles and pathway activations between EBV(+) and EBV(-) HIV-DLBCL through comprehensive genomic profiling. Methods: Cases of DLBCL were identified in patients living with HIV from a multi-institute cooperative group. Cases of Burkitt lymphoma and PBL were excluded. We performed whole exome sequencing (WES) on 106 tumors of HIV-DLBCL and RNA sequencing on 39 tumors and mapped the reads to hg38 reference genome using BWA and STAR, respectively. EBV status of cases was determined by in situ hybridization and/or reads mapped on EBV genome in sequencing data. Somatic mutations were identified using variant callers (Strelka2, Mutect2) with WES data. For those mutated genes in COSMIC, allele frequency cutoff was set at 0.03. Mutations with an artifact score larger than 0.7 in SOBDetector and those located in segmental duplications were further removed. They were annotated with Ensembl Variant Effect Predictor, manually checked, and plotted with maftools. RNAseq read counts aligned to each gene were obtained by featureCounts and DEseq2 was used for differential expression (DE) analysis between EBV positive and negative groups. Pathway analysis with the DE genes was performed using GSEA. FISH analysis was performed using MYC, BCL2, and BCL6 break-apart probes. Results: There were 41 cases of EBV(+) HIV-DLBCL and 65 cases of EBV(-) HIV-DLBCL. FISH of EBV(+) HIV-DLBCL identified 42% (3/7) with MYC rearrangement (MYCr), none with BCL2 rearrangements (BCL2r) (0/6), and 33% (2/6) positive for BCL6 rearrangement (BCL6r) with 1 tumor having a MYCr/BCL6r. For EBV(-) HIV-DLBCL, there were 35% with a MYCr (6/17), 18% with BCL2r (2/11), and 27% with a BCL6r (3/11) with 2 tumors with MYCr/BCL6r, and 1 tumor with MYCr/BCL2r/BCL6r. The most frequent mutations seen in EBV(+) HIV-DLBCL were STAT3 (32%), DDX3X (22%), and TP53 (15%). For EBV(-) HIV-DLBCL, the most frequent mutations were KMT2D (25%), TP53 (23%), GNA13 (22%), and TET2 (22%). Pathways that were most commonly associated with EBV(+) HIV-DLBCL were JAK/STAT (42%) (STAT3, JAK1) and NF-kB (39%)(DDX3X, TNFAIP3) while EBV(-) HIV-DLBCL was associated with epigenetic modifiers (62%)(KMT2D, TET2, EP300), JAK/STAT (45%)(SOCS1, JAK3) and PI3K/mTOR (40%)(GNA13, MTOR). Significant disparities between EBV(+) and EBV(-) were KMT2D (24% vs 50%, P=0.0025), TET2 (10% vs 26%, P=0.008), SOCS1 (29% vs 39%, P=0.04), DDX3X (15% vs 5%, P=0.03), and GNA13 (5% vs 24%, P=0.001). RAS mutations (KRAS, NRAS) were infrequent in HIV-DLBCL (EBV(+), 12%; EBV(-), 6%), in contrast to prior studies of PBL. Gene expression profiling showed enrichment of MYC targets, oxidative phosphorylation, and the mTORC pathway in EBV(+) as compared to EBV(-) HIV-DLBCL. Conclusion: EBV(+) HIV-DLBCL show a distinct mutational profile compared to EBV(-) HIV-DLBCL, with EBV(+) cases showing frequent mutations with STAT3 and DDX3X in contrast to EBV(-) cases with frequent mutations associated with epigenetic modification pathways (KMT2D, TET2). These genetic profiles underscore the need for tailored therapeutic approaches depending on EBV status. Although the analysis is limited and requires confirmation in a larger cohort, this is the largest study at present evaluating these tumors.
Récupéré en direct depuis OpenAlex et désinversé. Les résumés ne sont pas conservés dans cette base de données : les index inversés représentent 8,6 Go des 9,3 Go de texte de la base, et le serveur dispose de 13 Go libres.
Comment cette classification a été obtenuedéplier
Prédiction machine sur la base complète
Imitation des enseignantsNi prévalence calibrée, ni vérité terrain. Validation humaine à venir. Le volet Gemma est une étiquette directe du modèle pour chaque travail de la base, lue sur la notice réduite au titre. Le volet Codex est un classifieur appris des 10 348 étiquettes directes de Codex et calibré sur les taux pondérés de l'échantillon; les champs sans appui suffisant ne portent aucun appel Codex. Le mode candidate est l'union des deux volets; le consensus est leur intersection. Ces sorties portent le statut machine_predicted_unvalidated et ne sont pas des étiquettes humaines.
Scores du classifieur distillé par catégorie (deux têtes)
| Catégorie | Codex | Gemma |
|---|---|---|
| Métarecherche | 0,000 | 0,000 |
| Méta-épidémiologie (sens strict) | 0,000 | 0,000 |
| Méta-épidémiologie (sens large) | 0,000 | 0,000 |
| Bibliométrie | 0,001 | 0,001 |
| Études des sciences et des technologies | 0,000 | 0,000 |
| Communication savante | 0,000 | 0,000 |
| Science ouverte | 0,000 | 0,000 |
| Intégrité de la recherche | 0,000 | 0,000 |
| Charge utile insuffisante (le modèle a refusé de juger) | 0,003 | 0,001 |
Scores machine (provisoires)
Les deux têtes enseignantes du modèle étudiant, lues sur ce travail. Un score ordonne la base pour la relecture; il n'affirme jamais une catégorie, et le statut de validation accompagne chaque rangée tel quel.
Scores de référence d'un modèle non mature (critères de maturité non atteints, 7 itérations). Un score ordonne; il n'affirme jamais une catégorie.
score_only:v0-immature-baseline · tel quel depuis la passe de notation : score_only signifie que le nombre peut ordonner les travaux, et qu'aucune étiquette de catégorie n'en découleClassification
machine, non validéePrédiction automatique; un appel candidat d’une seule source (Gemma direct ou Codex distillé), pas un consensus.
Le détail, modèle par modèle et score par score, se trouve en fin de page sous « Comment cette classification a été obtenue ».