Cyclophosphamide Facilitates Antitumor Efficacy against Subcutaneous Tumors following Intravenous Delivery of Reovirus
Bibliographic record
Abstract
PURPOSE: The purpose of the present study was to investigate whether it is possible to achieve truly systemic delivery of oncolytic reovirus, in immunocompetent hosts, using cyclophosphamide to overcome some of the barriers to effective intratumoral delivery and replication of i.v. injected virus. EXPERIMENTAL DESIGN: I.v. delivery of reovirus was combined with different regimens of i.p. administered cyclophosphamide in C57Bl/6 mice bearing established s.c. B16 tumors. Intratumoral viral replication, tumor size, and survival were measured along with levels of neutralizing antibody (NAb) in the blood. Finally, differential toxicities of the virus/cyclophosphamide regimens were monitored through viral replication in systemic organs, survival, and cardiac damage. RESULTS: Repeated i.v. injection of reovirus was poorly effective at seeding intratumoral viral replication/oncolysis. However, by combining i.v. virus with cyclophosphamide, viral titers of between 10(7) and 10(8) plaque-forming units per milligram were recovered from regressing tumors. Doses of cyclophosphamide that ablated NAb were associated with severe toxicities, characterized by viral replication in systemic organs--toxicities that are mirrored by repeated reovirus injections into B-cell knockout mice. Next, we restructured the dosing of cyclophosphamide and i.v. virus such that a dose of 3 mg cyclophosphamide was administered 24 h before reovirus injection, and this schedule was repeated every 6 days. Using this protocol, high levels of intratumoral viral access and replication ( approximately 10(7) plaque-forming units per milligram tumor) were maintained along with systemically protective levels of NAb and only very mild, non-life-threatening toxicity. CONCLUSION: NAb to oncolytic viruses play a dual role in the context of systemic viral delivery; on one hand, they hinder repeated administration of virus but on the other, they provide an important safety mechanism by which virus released from vigorous intratumoral replication is neutralized before it can disseminate and cause toxicity. These data support the use of cyclophosphamide to modulate, but not ablate, patient NAb, in development of carefully controlled clinical trials of the systemic administration of oncolytic viruses.
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.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.001 |
| Insufficient payload (model declined to judge) | 0.001 | 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".