Gastrointestinal ulceration as a possible side effect of bevacizumab which may herald perforation.
Publication year
2008Source
Investigational New Drugs, 26, 4, (2008), pp. 393-7ISSN
Publication type
Article / Letter to editor
Display more detailsDisplay less details
Organization
Medical Oncology
Pathology
Neurology
Journal title
Investigational New Drugs
Volume
vol. 26
Issue
iss. 4
Page start
p. 393
Page end
p. 7
Subject
NCMLS 1: Immunity, infection and tissue repair; NCMLS 2: Immune Regulation; NCMLS 6: Genetics and epigenetic pathways of disease; ONCOL 1: Hereditary cancer and cancer-related syndromes; ONCOL 2: Age-related aspects of cancer; ONCOL 3: Translational research; UMCN 1.2: Molecular diagnosis, prognosis and monitoring; UMCN 1.3: Tumor microenvironment; UMCN 1.5: Interventional oncologyAbstract
Chemotherapy plus bevacizumab is currently considered as the standard 1st line treatment of advanced colorectal cancer (ACC). Whereas GI perforation is a known side effect of bevacizumab, the development of GI ulcers has not been reported. We identified 18 patients with ACC who participated in a phase III multicentre trial which included chemotherapy and bevacizumab, who developed a GI ulcer (n = 6), perforation (n = 8) or both (n = 4). The risk of developing a symptomatic GI ulcer or perforation was 1.3% and 1.6%, respectively. Central review of the histology specimens showed ulceration and/or granulation tissue with neovascularisation. The majority (89%) of events developed early during treatment. Given these observations, as well as the relationship between VEGF and mucosal injury healing, we suggest that GI ulcers may occur as a side effect of treatment with bevacizumab and may herald perforation.
This item appears in the following Collection(s)
- Academic publications [238441]
- Electronic publications [122544]
- Faculty of Medical Sciences [90373]
- Open Access publications [97535]
Upload full text
Use your RU credentials (u/z-number and password) to log in with SURFconext to upload a file for processing by the repository team.