Rapid Infusion Rituximab in Combination with Steroid Containing Chemotherapy Can Be Given Safely and Substantially Reduces Resource Utilization.
Bibliographic record
Abstract
Abstract Background Administration of rituximab, a chimeric anti-CD20 monoclonal antibody, can be associated with substantial infusion-related toxicity, including hypersensitivity reactions causing fever, rash, cardiovascular and respiratory compromise and rarely a fatal cytokine release syndrome. The risk of grade 3/4 infusion reactions is greatest with the first infusion (7%), and lower for all subsequent infusions (2% for fourth infusion). To minimize the risk of reaction, strict guidelines for administration have been developed, requiring lengthy infusion times (average 5–6 h for first infusion and 3–4 h for remaining infusions). As more patients are now receiving rituximab in combination with steroid containing chemotherapy regimens, the risk of reaction may be lower and the need for lengthy infusion unnecessary. Methods In March 2004, we began a pilot study investigating the safety of a rapid infusion rituximab schedule for all patients with non-Hodgkin’s lymphoma receiving rituximab in combination with CHOP or CVP chemotherapy. The schedule of administration for cycle 1 of therapy was unaltered and delivered according to the product monograph. All further cycles were administered the same day of chemotherapy, over a total infusion time of 90 minutes (20% of the dose in the first 30 min then the remaining 80% over 60 min; total dose delivered in 250 mL). Patients took their daily prednisone dose prior to receiving rituximab. Safety information was monitored prospectively using an infusion monitoring record. Results 67 patients have been treated for a total of 163 infusions (median infusions per patient: 2). Patient characteristics are as follows: median age, 64 y (range 21–90); 67% male; 66% stage III/IV; PS > 1, 19%; IPI score high/high-intermediate, 36%. Histology: 42 DLBCL, 6 follicular, 8 transformed, 4 mantle cell, 7 other. No patients had increased numbers of circulating lymphocytes. Chemotherapy regimen: 57 CHOP, 9 CVP, 1 other. The 90-minute rituximab infusion schedule was extremely well tolerated with no grade 3/4 adverse infusion related events observed. One patient developed mild transient asymptomatic hypotension, BP 97/71, grade 1 toxicity, which was managed with a 30-minute infusion delay. Four patients (6%) had an adverse event with their first cycle (administered at the standard rate) and subsequently tolerated the rapid infusion schedule without event. Five patients did not receive steroids with their treatment due to a prior history of hepatitis exposure and none of these patients developed an adverse event with the rapid infusion. The overall rate of grade 3/4 infusion related reactions observed with the rapid infusion protocol was 0% (95% CI 0–0.044), which is at least as low as the expected rate following the standard infusion schedule. No increased incidence in minor reactions was noted. Introduction of this shortened infusion schedule has enabled us to cut rituximab infusion times in half, allowing more patients to be conveniently treated and ensuring that both chemotherapy and rituximab can be given in one rather than two days. Conclusion A rapid (90-minute) rituximab infusion schedule in combination with a steroid containing chemotherapy regimen is well tolerated and safe when administered from the second infusion onward. This shortened infusion schedule has resulted in a substantial reduction in resource utilization.
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.001 |
| 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.000 |
| Insufficient payload (model declined to judge) | 0.003 | 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".