Periodic shifts in viral load increase risk of spillover from bats
Bibliographic record
Abstract
Abstract Prediction and management of zoonotic pathogen spillover requires an understanding of infection dynamics within reservoir host populations. Transmission risk is often assessed using prevalence of infected hosts, with infection status based on the presence of genomic material. However, detection of viral genomic material alone does not necessarily indicate the presence of infectious virus, which could decouple prevalence from transmission risk. We undertook a multi-faceted investigation of Hendra virus shedding in Pteropus bats, combining insights from virus isolation, viral load proxies, viral prevalence, and longitudinal patterns of shedding, from 6,151 samples. In addition to seasonal and interannual fluctuation in prevalence, we found evidence for periodic shifts in the distribution of viral loads. The proportion of bats shedding high viral loads was higher during peak prevalence periods during which spillover events were observed, and lower during non-peak periods when there were no spillovers. We suggest that prolonged periods of low viral load and low prevalence reflect prolonged shedding of non-infectious RNA, or viral loads that are insufficient or unlikely to overcome dose barriers to spillover infection. These findings show that incorporating viral load (or proxies of viral load) into longitudinal studies of virus excretion will better inform predictions of spillover risk than prevalence alone. Significance statement We present a comprehensive analysis of a high-profile bat-virus system (Hendra virus in Australian flying-foxes) to demonstrate that both prevalence and viral loads can shift systematically over time, resulting in concentrated periods of increased spillover risk when prevalence and viral loads are high. We further suggest that prolonged periods of low-prevalence, low-load shedding may not reflect excretion of infectious virus, resolving the outstanding puzzle of why spillovers have not been observed during periods of low off-season prevalence in subtropical Australia, or more frequently in tropical Australia despite consistent low-prevalence shedding. The consideration of viral loads (or proxies of viral load) along with prevalence may improve risk inference from longitudinal surveys of zoonotic viruses across wildlife reservoir hosts.
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 distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.001 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.000 | 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 teacher head, 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".