Skip to main content

New Drug Approvals 2011 - Pt. XXI Rivaroxaban (XareltoTM)

ATC code: B01AX06

On July 1st, FDA approved Rivaroxaban (trade name: Xarelto, Research code: BA-59-7939, NDA 022406), an anti-coagulant to prevent deep vein thrombosis (DVT) in patients with knee or hip replacement surgery. Rivaroxaban is the first orally applied direct inhibitor of Factor Xa (FXa), a key regulatory of the coagulation cascade. In DVT, a blood clot is formed which can dislodge and travel to the lungs, causing pulmonary embolism which can be potentially fatal.

Factor Xa (EC number, UniProt ID P00742, OMIM 613872) is a serine endopeptidase, cleaving prothrombin into its active form, thrombin, which then activates further downstream factors which ultimately lead to platelet activation and fibrin formation, clotting the damaged blood vessels. The sequence of Factor X is

>Factor X

Factor X itself is synthesized as an inactive precursor, and is further processed into a mature form, consisting of a light and an "activated" heavy chain (=FXa, residues 235-488, bold in the above sequence, carrying a trypsin-like domain, Pfam PF00089) (green and red in the below picture, respectively). There is a plethora of experimentally solved structures available for FXa, and also a holostructure of FXa in complex with Rivaroxaban, PDBe:2w26.

Rivaroxaban (ChEMBL ID 198362, ATC code B01AX06, PubChem CID 6433119) has molecular weight of 435.9 Da, an ALogP of 1.8, 5 rotatable bonds, 6 hydrogen bond acceptors, 1 hydrogen bond donor, and is thus fully Rule-of-Five compliant. It is dosed as a pure (S)-enantiomer. Canonical Smiles, Smiles=Clc1ccc(s1)C(=O)NC[C@H]2CN(C(=O)O2)c3ccc(cc3)N4CCOCC4=O, Standard InChi, InChI=1S/C19H18ClN3O5S/c20-16-6-5-15(29-16)18(25)21-9-14-10-23(19(26)28-14)13-3-1-12(2-4-13)22-7-8-27-11-17(22)24/h1-6,14H,7-11H2,(H,21,25)/t14-/m0/s1. Rivaroxaban is known to have a sub-nanomolar (0.7 nM) IC50 to the active site of human FXa.

Xarelto is administered orally as a 10 mg tablet once daily for 12 or 35 days (after knee/hip replacement surgery, respectively), yielding ~23 umol of active substance per single dose. Most relevant risks connected to Xarelto treatment are serious and fatal bleeding.

It has been given a boxed warning for spinal/epidural hematoma in surgical settings. It has not been tested in pregnant women, nursing mothers, or pediatric settings; majority of participants in clinical trials were 65 years and over, and the efficacy of Xarelto in the elderly was found to be similar to that seen in younger patients. The effect of Xarelto lasts 8-12 hours, but FXa activity stays depleted during 24 hours, so a once-daily dose is sufficient.

It has high (80-100%) bioactivity and is rapidly absorbed, reaching Cmax at 2 to 4 hours. Its volume is distribution is Vss=50 L. Little metabolism is observed for rivaroxaban, with the majority of the dose excreted unchanged.

The USAN/INN name stem, -xaban of rivaroxaban, designates a FXa inhibitor. Alternative anticoagulants, inhibiting FXa indirectly, include Heparin (ChEMBL ID 526514), an activator of Antithrombin, which itself is a FXa inactivator; Warfarin (ChEMBL ID 1464), a vitamin K antagonist, vitamin K being required for FXa biosynthesis. However, numerous other direct FXa inhibitors are currently being developed, e.g. Apixaban (BMS-562247-01, ChEMBL ID 231779), Betrixaban (PRT-054021, ChEMBL ID 512351), Edobaxan (Du-176b), Eribaxaban (PD-348292), Fidexaban (ZK-807834), Otamixaban (XRP-0673), YM-150, YM-466, Letaxaban (TAK-442), and GW-813893.

Xarelto has been developed by Bayer Schering AG. In US, it will be marketed by Janssen Pharmaceuticals, Inc.

The product website can be found here, the full prescribing information, here.


Popular posts from this blog

A python client for accessing ChEMBL web services

Motivation The CheMBL Web Services provide simple reliable programmatic access to the data stored in ChEMBL database. RESTful API approaches are quite easy to master in most languages but still require writing a few lines of code. Additionally, it can be a challenging task to write a nontrivial application using REST without any examples. These factors were the motivation for us to write a small client library for accessing web services from Python. Why Python? We choose this language because Python has become extremely popular (and still growing in use) in scientific applications; there are several Open Source chemical toolkits available in this language, and so the wealth of ChEMBL resources and functionality of those toolkits can be easily combined. Moreover, Python is a very web-friendly language and we wanted to show how easy complex resource acquisition can be expressed in Python. Reinventing the wheel? There are already some libraries providing access to ChEMBL d

ChEMBL 29 Released

  We are pleased to announce the release of ChEMBL 29. This version of the database, prepared on 01/07/2021 contains: 2,703,543 compound records 2,105,464 compounds (of which 2,084,724 have mol files) 18,635,916 activities 1,383,553 assays 14,554 targets 81,544 documents Data can be downloaded from the ChEMBL FTP site: .  Please see ChEMBL_29 release notes for full details of all changes in this release: New Deposited Datasets EUbOPEN Chemogenomic Library (src_id = 55, ChEMBL Document IDs CHEMBL4649982-CHEMBL4649998): The EUbOPEN consortium is an Innovative Medicines Initiative (IMI) funded project to enable and unlock biology in the open. The aims of the project are to assemble an open access chemogenomic library comprising about 5,000 well annotated compounds covering roughly 1,000 different proteins, to synthesiz

Identifying relevant compounds in patents

  As you may know, patents can be inherently noisy documents which can make it challenging to extract drug discovery information from them, such as the key targets or compounds being claimed. There are many reasons for this, ranging from deliberate obfuscation through to the long and detailed nature of the documents. For example, a typical small molecule patent may contain extensive background information relating to the target biology and disease area, chemical synthesis information, biological assay protocols and pharmacological measurements (which may refer to endogenous substances, existing therapies, reaction intermediates, reagents and reference compounds), in addition to description of the claimed compounds themselves.  The SureChEMBL system extracts this chemical information from patent documents through recognition of chemical names, conversion of images and extraction of attached files, and allows patents to be searched for chemical structures of interest. However, the curren

Julia meets RDKit

Julia is a young programming language that is getting some traction in the scientific community. It is a dynamically typed, memory safe and high performance JIT compiled language that was designed to replace languages such as Matlab, R and Python. We've been keeping an an eye on it for a while but we were missing something... yes, RDKit! Fortunately, Greg very recently added the MinimalLib CFFI interface to the RDKit repertoire. This is nothing else than a C API that makes it very easy to call RDKit from almost any programming language. More information about the MinimalLib is available directly from the source . The existence of this MinimalLib CFFI interface meant that we no longer had an excuse to not give it a go! First, we added a BinaryBuilder recipe for building RDKit's MinimalLib into Julia's Yggdrasil repository (thanks Mosè for reviewing!). The recipe builds and automatically uploads the library to Julia's general package registry. The build currently targe

New Drug Warnings Browser

As mentioned in the announcement post of  ChEMBL 29 , a new Drug Warnings Browser has been created. This is an updated version of the entity browsers in ChEMBL ( Compounds , Targets , Activities , etc). It contains new features that will be tried out with the Drug Warnings and will be applied to the other entities gradually. The new features of the Drug Warnings Browser are described below. More visible buttons to link to other entities This functionality is already available in the old entity browsers, but the button to use it is not easily recognised. In the new version, the buttons are more visible. By using those buttons, users can see the related activities, compounds, drugs, mechanisms of action and drug indications to the drug warnings selected. The page will take users to the corresponding entity browser with the items related to the ones selected, or to all the items in the dataset if the user didn’t select any. Additionally, the process of creating the join query is no