Fotemustine

From Glioblastoma Treatments
Revision as of 21:45, 30 March 2024 by Lazy (talk | contribs) (Created page with "{{TreatmentInfo |drug_name=Fotemustine |FDA_approval=Available in Europe, not FDA-approved in the United States for GBM |used_for=Recurrent Glioblastoma Multiforme (GBM) after the standard Stupp protocol treatment |clinical_trial_phase=Varied, with multiple studies evaluating efficacy and optimal scheduling |common_side_effects=Not specified, typical of nitrosoureas may include myelosuppression, nausea, and liver enzyme elevation |OS_without=Not specified |OS_with=Not sp...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search
Property Information
Drug Name Fotemustine
FDA Approval Available in Europe, not FDA-approved in the United States for GBM
Used for Recurrent Glioblastoma Multiforme (GBM) after the standard Stupp protocol treatment
Clinical Trial Phase Varied, with multiple studies evaluating efficacy and optimal scheduling
Clinical Trial Explanation Not specified
Common Side Effects Not specified, typical of nitrosoureas may include myelosuppression, nausea, and liver enzyme elevation
OS without Not specified
OS with Not specified; however, survival six months after recurrence was used as a primary measure in comparative studies with Avastin
PFS without Not applicable
PFS with Ranges from 26 to 44% with different schedules; 61% PFS-6 with the best results obtained using a specific dosing schedule
Usefulness Rating Based on available data, potentially highly useful in specific dosing schedules
Usefulness Explanation Fotemustine has shown promising results in patients with recurrent GBM, especially when administered every two weeks for five consecutive treatments at a dose of 80 mg/sq.-meter followed by maintenance therapy every four weeks. This regimen resulted in a PFS-6 value of 61% and a median time to progression of 6.7 months, indicating potential as an effective treatment option in this setting.Property "Has Usefulness Explanation" (as page type) with input value "Fotemustine has shown promising results in patients with recurrent GBM, especially when administered every two weeks for five consecutive treatments at a dose of 80 mg/sq.-meter followed by maintenance therapy every four weeks. This regimen resulted in a PFS-6 value of 61% and a median time to progression of 6.7 months, indicating potential as an effective treatment option in this setting." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
Toxicity Level 3
Toxicity Explanation While specific common side effects were not detailed, nitrosoureas typically present with myelosuppression, nausea, and potential for liver enzyme elevation. The toxicity profile necessitates careful monitoring and management, similar to other agents in its class.



From Ben Williams Book: Fotemustine represents a newer addition to the nitrosourea family of chemotherapeutics, showing efficacy in treating recurrent GBM post-Stupp protocol. Its unique dosing schedule, which has yielded higher PFS-6 values, suggests fotemustine as a viable option for patients who have failed initial treatments. Continued research and direct comparisons, such as those conducted in Italian studies, further support its role in the treatment landscape for GBM, albeit with a need for careful consideration of toxicity management.Property "Has original text" (as page type) with input value "Fotemustine represents a newer addition to the nitrosourea family of chemotherapeutics, showing efficacy in treating recurrent GBM post-Stupp protocol. Its unique dosing schedule, which has yielded higher PFS-6 values, suggests fotemustine as a viable option for patients who have failed initial treatments. Continued research and direct comparisons, such as those conducted in Italian studies, further support its role in the treatment landscape for GBM, albeit with a need for careful consideration of toxicity management." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.

Loading comments...