Skip to main content

Mechanism of Action and Drug Indication data on the interface.

Two new 'Browse' pages have been added to the interface; Browse Drug Mechanisms and Browse Drug Indications. Users can now access these 2 pages directly to explore all the data. Or alternatively, they can land on these pages from drugs, compounds and targets in ChEMBL.

Accessing all the data from the main page


The 'circles' visualisation on the main page shows a summary of the entities in ChEMBL. Circles for Drug Mechanisms of Action and Drug Indications have been added. By clicking on the circles, you will be taken to a page that allows you to explore the corresponding entity. 
Visualisation that summarises the entities in ChEMBL, Drug Mechanisms of Action and Drug Indications are now included.

The Browse Drug Mechanisms and Browse Drug Indications pages allow you to use filters, link to other entities, and download the data in the same way as the other 'Browse' pages.

All Drug Mechanism data.
All Drug Indication data.

Accessing Drug Indication and Drug Mechanism data related to other entities


You can now explore the Drug Indication and Drug Mechanism data in relation to the following entities:

From Browse Drug Mechanisms you can:
  • Browse related Drugs
  • Browse related Compounds
  • Browse related Targets

From Browse Drug Indications you can:
  • Browse related Drugs
  • Browse related Compounds

From Browse Drugs you can:
  • Browse related Drug Mechanisms
  • Browse related Drug Indications
  • Browse related Activities

Example A:


1. Go to the Browse Drug Mechanisms page. Find all drugs with mechanisms as neurokinin receptor antagonists.
Note that the data describes the mechanisms of action of 17 compounds for 3 targets.



2. Select all items and click on 'Browse Drugs', a new tab will open showing the drugs for the targets selected in step 1.



3. Click on 'Browse Drug Indications' to view all annotated indications for the drugs in step 2.




Example B:


1. Go to the Browse Drug Indications page. Find all drugs whose indication is asthma. There are 175 entries with asthma as an indication.



2. Select all items and click on 'Browse Drugs', a new tab will open showing the drugs for the indications selected in step 1.




3. Click on 'Browse Drug Mechanisms' to view of all annotated mechanisms for the drugs in step 2.



Accessing Drug Indication and Drug Mechanism data from report cards

You can now go to a dedicated page from the Drug Mechanism and Drug Indication data in the report cards. For example go to the report card for IMATINIB (CHEMBL941)

https://www.ebi.ac.uk/chembl/compound_report_card/CHEMBL941/

In the Drug Mechanism section you can see the data for that compound. If you click on 'Browse All', you will be directed to the Browse Drug Mechanisms page showing the data.

Drug Mechanisms section for the report card of IMATINIB (CHEMBL941)

Similarly, in the Drug Indications section you can click on 'Browse All' to be directed to a 'Browse Drug Indications' page showing all the data.
Drug Indications section for the report card of IMATINIB (CHEMBL941)


If you have any questions, please contact the ChEMBL Team support (chembl-help [at] ebi.ac.uk)




Comments

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