Why the study?
While VEGFR-TKIs are known to cause adverse events like cardiotoxicity and haematotoxicity, their impact on liver injury remains understudied.
Are VEGFR-TKIs associated with liver injury in patients reported in the FAERS database?
Are VEGFR-TKIs associated with liver injury in patients reported in the FAERS database?
VEGFR-TKIs are associated with significant liver injury, highlighting the need for close monitoring to mitigate risks of hospitalization and early mortality.
Answers are grounded in this paper and cite their sources.
FAERS signals link VEGFR-TKIs to liver injury; leaves open causality and optimal monitoring in prospective studies.
BACKGROUND: While vascular endothelial growth factor tyrosine kinase inhibitors (VEGFR-TKIs) are known to cause adverse events like cardiotoxicity and haematotoxicity, their impact on liver injury remains understudied. This study evaluates the association between VEGFR-TKIs and liver injury using data from the FDA Adverse Event Reporting System (FAERS) database from 2006 to 2024. RESEARCH DESIGN AND METHODS: Nine VEGFR-TKIs (Axitinib, Vandetanib, Cabozantinib, Lenvatinib, Pazopanib, Ponatinib, Regorafenib, Sunitinib, Sorafenib) were analyzed. Disproportionality and Bayesian analyses identified cases of VEGFR-TKI-induced liver injury, assessing onset time, mortality, and hospitalization rates. RESULTS: 8,619 cases of liver injury were identified. Pazopanib had the highest association with liver injury (reporting odds ratio 3.9). The median onset of liver injury was 21 days. Mortality was 28.5%, with Sorafenib linked to the highest mortality (48.6%). Lenvatinib had the highest hospitalization rate (56%). CONCLUSION: VEGFR-TKIs are associated with liver injury. Close monitoring is required to mitigate the risks of hospitalization and early mortality during treatment.
No takes yet. Share an insight, caveat, or question.
Wang et al. (2025) studied this question.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: