Skip to main content

ChEMBL_17 Released

We are pleased to announce the release of ChEMBL_17. This version of the database, prepared on 29th August 2013 contains:

  • 1,519,640 compound records
  • 1,324,941 compounds (of which 1,318,187 have mol files)
  • 12,077,491 activities
  • 734,201 assays
  • 9,356 targets
  • 51,277 documents

You can download the data from the ChEMBL FTP site. For more information please read the release notes.

Data changes since the last release:

Drug mechanism of action

For all FDA-approved drugs, information regarding the mechanism of action and associated efficacy targets has been curated from primary sources, such as literature and drug prescribing information. Targets have only been included for a drug if a) the drug is believed to interact directly with the target and b) there is evidence that this interaction contributes towards the efficacy of that drug in the indication(s) for which it is approved.

Metal-containing compounds

Structures for around 3200 metal-containing compounds have been removed from the database (though the bioactivity and other information for these compounds is retained). For more information, please see the previous blog posts:

New data sets

Several new deposited/extracted data sets have also been included in the latest release: two deposited data sets from GlaxoSmithKine for Ghrelin receptor agonists and Motilin receptor agonists, a data set of the results of screening the MMV Malaria Box compound collection for activity against Schistosoma mansoni, two data sets screening the GSK PKIS compound collection for inhibition of luciferase activity, and finally pathology data from the Open TG-GATES project.

Interface changes since the last release:

Browse Drug Targets tab

A new tab has been created to show the new mechanism of action information for FDA approved drugs together with the references from which the information was obtained, and links to the relevant drug/target report card pages.

Document Report Card

A new table has been added to the document report card, showing other ChEMBL documents that are related to the current document. Pair-wise document similarity is assessed by two components. The first component is defined by whether a document cites or is referenced by the other. The second component is defined by the amount of overlap between the compounds and biological targets reported in the two respective documents. This overlap is quantified by the Tanimoto coefficient. Documents with the highest Tanimoto similarity scores to the query document are listed in this section. For example, the following page shows 5 additional ChEMBL documents that are deemed similar to the paper currently being viewed.

Database changes since the last release:

A number of new tables have been added to store the drug mechanism of action information (please see release notes and schema documentation for full details). In addition, a number of minor changes have been made to existing tables:

The PROTEIN_FAMILY_CLASSIFICATION table has been deprecated and replaced by a new hierarchical version: PROTEIN_CLASSIFICATION.

The MOLREGNO field has been removed from the ATC_CLASSIFICATION table and moved to a new mapping table: MOLECULE_ATC_CLASSIFICATION.

The MOLFORMULA field has been moved from the COMPOUND_STRUCTURES table to the COMPOUND_PROPERTIES table (and renamed).

The ChEMBL Team


Can you make available the list CHEMBL ids of those 3200 metal-containing compounds?

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