Skip to main content

The AIDX






ChEMBL has recently begun to display the ‘AIDX’ field as part of our assay data. In this Blog post you can find out more about the AIDX as well as how to best populate this field when depositing data to ChEMBL.


What is the AIDX?


ChEMBL extracts bioactivity data from the core medicinal literature but also accepts deposited data from the scientific community. In fact, deposited data now provides more than half of the bioactivity data within ChEMBL. During the preparation of data for submission to ChEMBL, depositors format and assign identifiers to their data to allow integration into ChEMBL and the AIDX is the depositor-defined identifier for assays. Each AIDX corresponds to a distinct assay with a defined experimental set-up (aim, target and method). Concise and meaningful AIDXs are ideal since these are not easily replicated by different depositors.


 


Suggested AIDX format: Smith_KinaseXYZ_Assay36 (abbreviation of the group leader, target, assay number).


Poor AIDX format: ‘1’, ‘2’, ‘3’


Reuse of AIDXs - depositing additional bioactivity data to an existing assay


Depositors occasionally submit additional bioactivity data for assays that already exist within ChEMBL. For example when a single institute is performing the same set of assays for newly synthesised compounds, or a contract research organisation is characterising compounds using a defined set of assays. Here, depositors can reuse an existing AIDX for new bioactivity data, but the AIDX must match the previous identifier exactly and the assay set up should be identical. Depositors are responsible for ensuring that the assay set up is consistent between datasets and that a standard protocol and appropriate positive and negative controls are included to ensure variation is within expected limits.


Can I reuse an existing depositor AIDX if my assay uses the same commercial screening kit?


Commercial kits may have a standard assay set up but we consider assays run by different institutions, using the same commercial kit, as distinct. The depositor AIDXs for these screening assays should be distinct if performed at different institutes. However, to allow comparison between similar assays, kit identifiers/catalogue numbers should ideally be included within the assay description.


e.g. Inhibition of XYZ target at 10uM tested using the Eurofins SafetyScreen44 (BI) (P270) - P270 is the catalogue number.


Summary


Overall, the AIDX is an identifier that depositors use when submitting experimental data to ChEMBL. Occasionally, this identifier can be re-used for data from a single institute or from CROs. Assays from different institutes are considered distinct but we suggest that users include a catalogue number for commercial kits to facilitate comparisons across similar assays.


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

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 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

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.

In search of the perfect assay description

Credit: Science biotech, CC BY-SA 4.0 Assays des cribe 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. Ver sion 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 method .  The ideal assay description is succinct but contains all the necessary information for easy interpretation by database u