Skip to main content

ChEMBL Identifiers




A few notes about the use and format of identifiers in ChEMBL:

Each of the major entity types within ChEMBL (documents, assays, compounds and targets) are assigned unique ChEMBL identifiers, which take the form of a ‘CHEMBL’ prefix followed immediately by an integer (e.g., CHEMBL25 is the compound aspirin, CHEMBL210 is the human beta-2 adrenergic receptor "target"). There is no distinction between the format of the identifier for different types of entities, but a given ChEMBL identifier will only ever be assigned to a single entity (i.e., CHEMBL25 will only ever be used for the compound aspirin and never for an assay, document or target). A lookup table is provided in the database, to resolve which identifiers correspond to which entity types. 

ChEMBL identifiers are stable with respect to the entities they represent. For compounds (with known/defined structures), ChEMBL identifiers represent distinct compound structures, as defined by the standard InChI, e.g., CHEMBL25 represents: InChI=1S/C9H8O4/c1-6(10)13-8-5-3-2-4-7(8)9(11)12/h2-5H,1H3,(H,11,12). Therefore, two compounds reported in different papers but having the same standard InChI will be assigned the same ChEMBL ID. 

These ChEMBL IDs will never be reassigned to a structure with a different standard InChI. However, since compounds may be reported or drawn incorrectly in the literature, it is sometimes necessary to alter the compound ChEMBL ID (structure) to which a particular bioactivity measurement links. In this case, the old (incorrect) ChEMBL identifier may be 'downgraded' in the database if no other data link to it. Downgraded compounds are not currently displayed on the live interface, but are retained in the database and the ChEMBL ID lookup table, and could be re-instated in future (with the same ChEMBL ID) if new data become available for them. 

External identifiers for ChEMBL entities are also recorded in the database, where possible. For example, in addition to ChEMBL IDs and InChI/InChIKeys, all small molecule compounds with defined structures are assigned ChEBI identifiers. Where data are taken from other resources, the original identifiers are also retained (e.g., SIDs and AIDs for PubChem substances and assays, HET codes for PDBe ligands). PubMed identifiers or Digital Object Identifiers (DOIs) are stored for documents, and protein targets are represented by primary accessions from the UniProt database.

Comments

Popular posts from this blog

Using ChEMBL web services via proxy.

It is common practice for organizations and companies to make use of proxy servers to connect to services outside their network. This can cause problems for users of the ChEMBL web services who sit behind a proxy server. So to help those users who have asked, we provide the following quick guide, which demonstrates how to access ChEMBL web services via a proxy. Most software libraries respect proxy settings from environmental variables. You can set the proxy variable once, normally HTTP_PROXY and then use that variable to set other related proxy environment variables: Or if you have different proxies responsible for different protocols: On Windows, this would be: If you are accessing the ChEMBL web services programmatically and you prefer not to clutter your environment, you can consider adding the proxy settings to your scripts. Here are some python based recipes: 1. Official ChEMBL client library If you are working in a python based environment, we recommend

Multi-task neural network on ChEMBL with PyTorch 1.0 and RDKit

  The use and application of multi-task neural networks is growing rapidly in cheminformatics and drug discovery. Examples can be found in the following publications: - Deep Learning as an Opportunity in VirtualScreening - Massively Multitask Networks for Drug Discovery - Beyond the hype: deep neural networks outperform established methods using a ChEMBL bioactivity benchmark set But what is a multi-task neural network? In short, it's a kind of neural network architecture that can optimise multiple classification/regression problems at the same time while taking advantage of their shared description. This blogpost gives a great overview of their architecture. All networks in references above implement the hard parameter sharing approach. So, having a set of activities relating targets and molecules we can train a single neural network as a binary multi-label classifier that will output the probability of activity/inactivity for each of the targets (tasks) for a given q

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

LSH-based similarity search in MongoDB is faster than postgres cartridge.

TL;DR: In his excellent blog post , Matt Swain described the implementation of compound similarity searches in MongoDB . Unfortunately, Matt's approach had suboptimal ( polynomial ) time complexity with respect to decreasing similarity thresholds, which renders unsuitable for production environments. In this article, we improve on the method by enhancing it with Locality Sensitive Hashing algorithm, which significantly reduces query time and outperforms RDKit PostgreSQL cartridge . myChEMBL 21 - NoSQL edition    Given that NoSQL technologies applied to computational chemistry and cheminformatics are gaining traction and popularity, we decided to include a taster in future myChEMBL releases. Two especially appealing technologies are Neo4j and MongoDB . The former is a graph database and the latter is a BSON document storage. We would like to provide IPython notebook -based tutorials explaining how to use this software to deal with common cheminformatics p

Webinar: using an API to access ChEMBL

  If you use ChEMBL via the interface and are interested in programmatic approaches then join  our  webinar   on November 10th @ 15:30 to find out more ! In this webinar, we'll provide an overview of the ChEMBL and UniChem APIs and work through some common examples. In the meantime, don’t forget that we have further documentation on our  web services  as well as a recent ChEMBL  webinar, a Blog and series of  FAQs .  Questions? Send us a message through the  Helpdesk .