Skip to main content

In search of the perfect assay description


Credit: Science biotech, CC BY-SA 4.0

Assays describe the experimental set-up when testing the activity of drug-like compounds against biological targets; they provide useful context for researchers interested in drug-target relationships. Version 33 of ChEMBL contains 1.6 million diverse assays spanning ADMET, physicochemical, binding, functional and toxicity experiments. A set of well-defined and structured assay descriptions would be valuable for the drug discovery community, particularly for text mining and NLP projects. These would also support ChEMBL's ongoing efforts towards an in vitro assay classification. This Blog post will consider the features of the 'perfect' assay description and provide a guide for depositors on the submission of high quality data.


ChEMBL's assays are typically structured with the overall aim, target, and methodThe ideal assay description is succinct but contains all the necessary information for easy interpretation by database users, as well as comparison between similar assays. Relevant parameters depend on the nature of the assay; for example, protein binding assays should include details of any protein sequence variation as well as other biological entities present in the assay (e.g. subcellular fractions). On the other hand, the drug concentration and route of administration are more relevant for the interpretation of ADMET assays. 


There are five assay types within ChEMBL: Binding (B), Functional (F), ADME (A), Toxicity (T), Physicochemical (P) as well as an Unclassified (U) type for assays that don't fit these groups. During curation, we map assays to the tested biological target. Our targets may be a defined molecular entity such as the single protein ABL kinase or a broader non-molecular target such as the whole organism E. coli. Most assays report a biological target, but exceptions include those exploring the physicochemical properties of drugs or their absorption, distribution, metabolism, and excretion where a defined target may not be relevant, or known.



Typical structure of ChEMBL assays


Binding (Type B) and functional (Type F) assays



Binding and functional assays test the binding or activity of drug-like compounds at defined biological targets and comprise the bulk of assays within ChEMBL. It’s important to capture all target features that could impact drug activity within these assay descriptions. This includes protein variation, fusions and isoform information.



Assay descriptions reporting molecular targets. In addition to the overall aim, target and method, biological entities (cell extracts, tissues) and/or expression information (bacteria, cell-line, purified protein) and protein variation (wild-type or mutated) should be included. The assays above are: type B; row 1, type F; row 2type F; row 3, and type F; row 4.


For assays performed in higher level systems such as cells, tissues or whole organisms, phenotypes such as drug-resistance and the targeted biological pathways, drug delivery method (e.g. route, dose) and model system are important and should be covered in the assay description 


Assay descriptions reporting non-molecular targets. For higher-level systems such as cells, tissues, and organisms, relevant dosing information and phenotypes (e.g. drug-sensitive/resistant) should be included. 


Physicochemical (type P) assays 

Physicochemical assays provide valuable information on drug properties, such as solubility and lipophilicity, and are relevant to drug design and formulation. Inclusion of parameters such as the pH, temperature, and solvent in the assay description improves their usability.



A physicochemical assay.


ADME (type A) and toxicity (type T) assays

Pharmacokinetic studies provide an insight into the action and processing of a drug in vivo. Inclusion of the dose, route of administration, time of measurement, model system and sampled tissue in the corresponding assay descriptions allows researchers to explore the ADME(T) properties of drugs. A set of well-defined CMax assays, for example, will include the dose, dose unit, route of administration and time whereas biodistribution assays should record the target tissue where known and relevant. 



ADMET assays including metadata such as dose, tissue and route of administration. In these cases, a molecular target is not annotated.


Safety studies form a critical part of the drug development process and identifying the potential for toxicity/adverse side effects at the earliest stage during a drug discovery programme can save time and resources. Furthermore, publication of late-stage animal toxicity assays can provide an insight into the mechanism of drug toxicity. A good assay description with record the adversely affected target tissue or biological process as well as the nature of the adverse effect.



Toxicity assays: Annotation of the target tissue (kidney) provides valuable safety-related data. 



We hope that carefully captured assay descriptions will increase the usability of ChEMBL assays in future, and also support our efforts to classify in vitro assays and facilitate the rapid and accurate mapping of assays to the correct ChEMBL target. Complex datasets containing multiplex assays may require further annotation and metadata for their interpretation. Additional metadata can be submitted for both the assay set-up and bioactivity results in the ASSAY_PARAMETERS and ACTIVITY_PROPERTIES tables. More details on these tables will follow in a future Blog post. 


Questions? Get in touch in the Helpdesk with any further questions or browse our assays.

Comments

Popular posts from this blog

Improvements in SureChEMBL's chemistry search and adoption of RDKit

    Dear SureChEMBL users, If you frequently rely on our "chemistry search" feature, today brings great news! We’ve recently implemented a major update that makes your search experience faster than ever. What's New? Last week, we upgraded our structure search engine by aligning it with the core code base used in ChEMBL . This update allows SureChEMBL to leverage our FPSim2 Python package , returning results in approximately one second. The similarity search relies on 256-bit RDKit -calculated ECFP4 fingerprints, and a single instance requires approximately 1 GB of RAM to run. SureChEMBL’s FPSim2 file is not currently available for download, but we are considering generating it periodicaly and have created it once for you to try in Google Colab ! For substructure searches, we now also use an RDKit -based solution via SubstructLibrary , which returns results several times faster than our previous implementation. Additionally, structure search results are now sorted by

ChEMBL brings drug bioactivity data to the Protein Data Bank in Europe

In the quest to develop new drugs, understanding the 3D structure of molecules is crucial. Resources like the Protein Data Bank in Europe (PDBe) and the Cambridge Structural Database (CSD) provide these 3D blueprints for many biological molecules. However, researchers also need to know how these molecules interact with their biological target – their bioactivity. ChEMBL is a treasure trove of bioactivity data for countless drug-like molecules. It tells us how strongly a molecule binds to a target, how it affects a biological process, and even how it might be metabolized. But here's the catch: while ChEMBL provides extensive information on a molecule's activity and cross references to other data sources, it doesn't always tell us if a 3D structure is available for a specific drug-target complex. This can be a roadblock for researchers who need that structural information to design effective drugs. Therefore, connecting ChEMBL data with resources like PDBe and CSD is essen

Improved querying for SureChEMBL

    Dear SureChEMBL users, Earlier this year we ran a survey to identify what you, the users, would like to see next in SureChEMBL. Thank you for offering your feedback! This gave us the opportunity to have some interesting discussions both internally and externally. While we can't publicly reveal precisely our plans for the coming months (everything will be delivered at the right time), we can at least say that improving the compound structure extraction quality is a priority. Unfortunately, the change won't happen overnight as reprocessing 167 millions patents takes a while. However, the good news is that the new generation of optical chemical structure recognition shows good performance, even for patent images! We hope we can share our results with you soon. So in the meantime, what are we doing? You may have noticed a few changes on the SureChEMBL main page. No more "Beta" flag since we consider the system to be stable enough (it does not mean that you will never

ChEMBL 34 is out!

We are delighted to announce the release of ChEMBL 34, which includes a full update to drug and clinical candidate drug data. This version of the database, prepared on 28/03/2024 contains:         2,431,025 compounds (of which 2,409,270 have mol files)         3,106,257 compound records (non-unique compounds)         20,772,701 activities         1,644,390 assays         15,598 targets         89,892 documents Data can be downloaded from the ChEMBL FTP site:  https://ftp.ebi.ac.uk/pub/databases/chembl/ChEMBLdb/releases/chembl_34/ Please see ChEMBL_34 release notes for full details of all changes in this release:  https://ftp.ebi.ac.uk/pub/databases/chembl/ChEMBLdb/releases/chembl_34/chembl_34_release_notes.txt New Data Sources European Medicines Agency (src_id = 66): European Medicines Agency's data correspond to EMA drugs prior to 20 January 2023 (excluding vaccines). 71 out of the 882 newly added EMA drugs are only authorised by EMA, rather than from other regulatory bodies e.g.

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