Why the study?
What are the regulatory actions taken regarding the cardiovascular safety of selective COX-2 inhibitors?
What are the regulatory actions taken regarding the cardiovascular safety of selective COX-2 inhibitors?
Regulatory review highlights the contraindication of COX-2 inhibitors in patients with established cardiovascular disease due to increased thromboembolic risk.
Answers are grounded in this paper and cite their sources.
Warrants review of NSAID choices in vascular disease patients; leaves open comparative safety of non-selective agents.
In the 1990s, the pharmaceutical industry developed selective COX-2 inhibitors (coxibs) as alternatives to conventional nonsteroidal anti-inflammatory drugs (NSAIDs), with the expectation of similar analgetic and anti-inflammatory efficacy but a reduced risk of adverse gastrointestinal (GI) effects. Marketing authorisation (MA) was granted for rofecoxib and celecoxib as first representatives of this new pharmacological class at the end of the 1990s in the EU. In the following years MAs were granted for the 'second generation' coxibs etoricoxib, parecoxib/valdecoxib and lumiracoxib. However, data from large clinical 'outcome studies' as well as epidemiological data raised concerns about the cardiovascular (CV) safety of the coxibs. In consequence, two comprehensive review processes (referrals) were initiated by the European Medicines Agency (EMEA). As a result, in the EU the use of coxibs has been contraindicated in patients with established coronary heart disease, cerebrovascular disease and peripheral arterial disease and a number of warning statements concerning CV, GI and skin toxicity have been introduced in the coxib product informations. This article provides a description of the regulatory actions taken and discusses some specific aspects of the past and future regulatory assessment of coxibs.
No takes yet. Share an insight, caveat, or question.
Broich et al. (2006) studied this question.
Synapse has enriched 10 related papers. Consider them for comparative context: