Rapid Infusion Rituximab in Combination with Steroid Containing Chemotherapy Can Be Given Safely and Substantially Reduces Resource Utilization.
Notice bibliographique
Résumé
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.
Récupéré en direct depuis OpenAlex et désinversé. Les résumés ne sont pas conservés dans cette base de données : les index inversés représentent 8,6 Go des 9,3 Go de texte de la base, et le serveur dispose de 13 Go libres.
Comment cette classification a été obtenuedéplier
Prédiction machine sur la base complète
Imitation des enseignantsNi prévalence calibrée, ni vérité terrain. Validation humaine à venir. Le volet Gemma est une étiquette directe du modèle pour chaque travail de la base, lue sur la notice réduite au titre. Le volet Codex est un classifieur appris des 10 348 étiquettes directes de Codex et calibré sur les taux pondérés de l'échantillon; les champs sans appui suffisant ne portent aucun appel Codex. Le mode candidate est l'union des deux volets; le consensus est leur intersection. Ces sorties portent le statut machine_predicted_unvalidated et ne sont pas des étiquettes humaines.
Scores du classifieur distillé par catégorie (deux têtes)
| Catégorie | Codex | Gemma |
|---|---|---|
| Métarecherche | 0,000 | 0,001 |
| Méta-épidémiologie (sens strict) | 0,000 | 0,000 |
| Méta-épidémiologie (sens large) | 0,000 | 0,000 |
| Bibliométrie | 0,000 | 0,000 |
| Études des sciences et des technologies | 0,000 | 0,000 |
| Communication savante | 0,000 | 0,000 |
| Science ouverte | 0,000 | 0,000 |
| Intégrité de la recherche | 0,000 | 0,000 |
| Charge utile insuffisante (le modèle a refusé de juger) | 0,003 | 0,001 |
Scores machine (provisoires)
Les deux têtes enseignantes du modèle étudiant, lues sur ce travail. Un score ordonne la base pour la relecture; il n'affirme jamais une catégorie, et le statut de validation accompagne chaque rangée tel quel.
Scores de référence d'un modèle non mature (critères de maturité non atteints, 7 itérations). Un score ordonne; il n'affirme jamais une catégorie.
score_only:v0-immature-baseline · tel quel depuis la passe de notation : score_only signifie que le nombre peut ordonner les travaux, et qu'aucune étiquette de catégorie n'en découleClassification
machine, non validéePrédiction automatique; un appel candidat d’une seule source (Gemma direct ou Codex distillé), pas un consensus.
Le détail, modèle par modèle et score par score, se trouve en fin de page sous « Comment cette classification a été obtenue ».