Splenic rupture or infarction associated with Epstein-Barr virus infectious mononucleosis: a systematic literature review
Bibliographic record
Abstract
BACKGROUND: Epstein-Barr virus (EBV), also known as human herpesvirus 4, is one of the most common pathogenic viruses in humans. EBV mononucleosis always involves the spleen and as such it predisposes to splenic rupture, often without a trauma, and splenic infarction. Nowadays the goal of management is to preserve the spleen, thereby eliminating the risk of post-splenectomy infections. METHODS: To characterise these complications and their management, we performed a systematic review (PROSPERO CRD42022370268) following PRISMA guidelines in three databases: Excerpta Medica, the United States National Library of Medicine, and Web of Science. Articles listed in Google Scholar were also considered. Eligible articles were those describing splenic rupture or infarction in subjects with Epstein-Barr virus mononucleosis. RESULTS: In the literature, we found 171 articles published since 1970, documenting 186 cases with splenic rupture and 29 with infarction. Both conditions predominantly occurred in males, 60% and 70% respectively. Splenic rupture was preceded by a trauma in 17 (9.1%) cases. Approximately 80% (n = 139) of cases occurred within three weeks of the onset of mononucleosis symptoms. A correlation was found between the World Society of Emergency Surgery splenic rupture score, which was retrospectively calculated, and surgical management: splenectomy in 84% (n = 44) of cases with a severe score and in 58% (n = 70) of cases with a moderate or minor score (p = 0.001). The mortality rate of splenic rupture was 4.8% (n = 9). In splenic infarction, an underlying haematological condition was observed in 21% (n = 6) of cases. The treatment of splenic infarction was always conservative without any fatal outcomes. CONCLUSIONS: Similarly to traumatic splenic rupture, splenic preservation is increasingly common in the management of mononucleosis-associated cases as well. This complication is still occasionally fatal. Splenic infarction often occurs in subjects with a pre-existing haematological condition.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.004 | 0.020 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.006 | 0.004 |
| Bibliometrics | 0.014 | 0.016 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.002 | 0.002 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.002 | 0.001 |
| Insufficient payload (model declined to judge) | 0.004 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".