Skip to main content

Pathogen data in ChEMBL



Infectious disease is a leading cause of death globally and bioactivity data against pathogens (fungi, bacteria, viruses, and parasites) is an important category in ChEMBL, especially in light of the ongoing pandemic. In ChEMBL version 29, there are over 2 M bioactivity data points against fungal, bacterial or viral targets (for 460 K compounds) available for pathogen-related research.


How can I find pathogen data?


On the ChEMBL interface, the organism taxonomy is available as a filter that can be applied to bioactivity data. A sunburst visualisation of the organism taxonomy is also provided as an easy starting point to explore targets according to their taxonomy.



In the full database, the organism_classification table holds the underlying data and can be used in bespoke SQL queries. For example, queries may be performed to extract high level pathogen data such as all bioactivity data for small molecules screened against bacterial targets (example below) or more specific subsets focused on gram-positive pathogens or on a single bacterial species. The target type includes whole organisms as well as molecular targets (proteins, nucleic acids etc.) and additional filters can be applied to filter the target type as necessary.


What are the sources of pathogen data in ChEMBL?

We routinely extract bioactivity data from core medicinal chemistry journals and also accept deposited data (a full list can be found in the source table). In recent releases, data deposited by the Community for Open Antimicrobial Drug Discovery (CO-ADD, University of Queensland & Wellcome Trust) has enhanced our pathogen coverage. CO-ADD is an open-access, not-for-profit initiative whereby compounds provided by researchers and industry scientists are screened against a clinically relevant panel of bacteria and fungi. So far, 100 K activities (against ~ 24 K compounds) have been provided through CO-ADD. Since CO-ADD may re-screen hits against resistant bacterial strains or in cytotoxicity assays, more comprehensive data is available for some compounds. There are now 31 CO-ADD datasets in ChEMBL 29 (data source: src_ID 40) with more expected in upcoming releases.


ChEMBL also has a dedicated Neglected Tropical Disease repository (ChEMBL-NTD) for open-access primary screening and medicinal chemistry data directed at key parasites causing endemic tropical diseases. In addition, 22 datasets from screens of the ‘Malaria Box' (MMV) compound set are also provided through ChEMBL ensuring good coverage of key parasites. Currently, there are ~ 950 K activities for Plasmodium species alone.


Finally, ChEMBL version 27 was a special SARS-CoV-2 release focused on large-scale drug screening studies for anti-viral activity, in particular cell-based assays with well-characterised compounds. Rapid integration of SARS-CoV-2 activity data into ChEMBL provided a contribution towards the COVID-19 effort and several follow-up datasets have since been captured in subsequent releases.


Questions? Please get in touch on the Helpdesk or have a look through our training materials and FAQs.

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:   https://ftp.ebi.ac.uk/pub/databases/chembl/ChEMBLdb/releases/chembl_29 .  Please see ChEMBL_29 release notes for full details of all changes in this release: https://ftp.ebi.ac.uk/pub/databases/chembl/ChEMBLdb/releases/chembl_29/chembl_29_release_notes.txt 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

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

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

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