Are multiple births at greater risk for RSV-related hospitalisation compared with singletons?
Bibliographic record
Abstract
Twins 34 weeks gestational age are being discharged from the neonatal unit for regular follow-up by their general practitioner. One of the twins required nasal continuous positive airway pressure for 3 days for mild respiratory distress syndrome. The mother asks, are my twins at high risk for respiratory syncytial virus (RSV) infection and related hospitalisation? Are multiple births ( population ) at greater risk for RSV-related hospitalisation ( outcome ) compared with singletons ( control )? An advanced modality search was conducted across available databases including PubMed, Google Scholar, Ovid Medline, Cochrane Library and Web of Science using the following keywords and Medical Subject Headings (MeSH) terms: Respiratory syncytial virus OR RSV AND Twins OR Triplets OR Multiple gestation OR Multiple birth. All relevant articles that comprised multiple birth neonates aged less than 2 years that were hospitalised with RSV infection were reviewed. Included articles were checked for references to additional relevant studies. Animal-based, non–English-language case reports, and studies prior to 1980 were excluded. The search yielded 466 articles, and after exclusions and consensus, a total of 15 articles were retained for analysis and the characteristics of 12 key studies1–12 are shown in table 1. View this table: Table 1 Summary of included studies (n=12) RSV is one of the most common causes of viral-related hospitalisation (RSVH) and mortality in the world, resulting in 31% hospital admissions among children aged less than 5 years, and an estimated 118 200 in and out of hospital deaths.13 It is estimated that 22% of global lower respiratory tract infection (LRTI) in children is due to RSV and 44% of RSVH occurs in those less than 2 months of age, with the highest mortality reported in children of very low birth weight <1500 g, and those who are immunocompromised or are infected with HIV.14 Well-established risk factors associated with RSV LRTI and RSVH include …
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.003 | 0.021 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.004 | 0.004 |
| Bibliometrics | 0.007 | 0.010 |
| Science and technology studies | 0.000 | 0.001 |
| Scholarly communication | 0.001 | 0.002 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.002 | 0.001 |
| Insufficient payload (model declined to judge) | 0.011 | 0.001 |
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".