Browse
Submit Data
Databases
API
Help

Dataset Information

0 Views

0 Connections

0 Citations

0 Reanalyses

0 Downloads

Omics score: 0

HUGO Gene Nomenclature Committee (HGNC) recommendations for the designation of gene fusions.

ABSTRACT: Gene fusions have been discussed in the scientific literature since they were first detected in cancer cells in the early 1980s. There is currently no standardized way to denote the genes involved in fusions, but in the majority of publications the gene symbols in question are listed either separated by a hyphen (-) or by a forward slash (/). Both types of designation suffer from important shortcomings. HGNC has worked with the scientific community to determine a new, instantly recognizable and unique separator-a double colon (::)-to be used in the description of fusion genes, and advocates its usage in all databases and articles describing gene fusions.

SUBMITTER: Bruford EA

PROVIDER: S-EPMC8550944 | biostudies-literature | 2021 Nov

REPOSITORIES: biostudies-literature

ACCESS DATA

Json Xml

Publications

HUGO Gene Nomenclature Committee (HGNC) recommendations for the designation of gene fusions.

Bruford Elspeth A EA Antonescu Cristina R CR Carroll Andrew J AJ Chinnaiyan Arul A Cree Ian A IA Cross Nicholas C P NCP Dalgleish Raymond R Gale Robert Peter RP Harrison Christine J CJ Hastings Rosalind J RJ Huret Jean-Loup JL Johansson Bertil B Le Beau Michelle M Mecucci Cristina C Mertens Fredrik F Verhaak Roel R Mitelman Felix F

Leukemia 20211006 11

Gene fusions have been discussed in the scientific literature since they were first detected in cancer cells in the early 1980s. There is currently no standardized way to denote the genes involved in fusions, but in the majority of publications the gene symbols in question are listed either separated by a hyphen (-) or by a forward slash (/). Both types of designation suffer from important shortcomings. HGNC has worked with the scientific community to determine a new, instantly recognizable and ...[more]

PMID: 34615987

Similar Datasets

The Chicken Gene Nomenclature Committee report.

Project description:Comparative genomics is an essential component of the post-genomic era. The chicken genome is the first avian genome to be sequenced and it will serve as a model for other avian species. Moreover, due to its unique evolutionary niche, the chicken genome can be used to understand evolution of functional elements and gene regulation in mammalian species. However comparative biology both within avian species and within amniotes is hampered due to the difficulty of recognising functional orthologs. This problem is compounded as different databases and sequence repositories proliferate and the names they assign to functional elements proliferate along with them. Currently, genes can be published under more than one name and one name sometimes refers to unrelated genes. Standardized gene nomenclature is necessary to facilitate communication between scientists and genomic resources. Moreover, it is important that this nomenclature be based on existing nomenclature efforts where possible to truly facilitate studies between different species. We report here the formation of the Chicken Gene Nomenclature Committee (CGNC), an international and centralized effort to provide standardized nomenclature for chicken genes. The CGNC works in conjunction with public resources such as NCBI and Ensembl and in consultation with existing nomenclature committees for human and mouse. The CGNC will develop standardized nomenclature in consultation with the research community and relies on the support of the research community to ensure that the nomenclature facilitates comparative and genomic studies.

| S-EPMC2966335 | biostudies-literature

Molecular mechanisms of cell death: recommendations of the Nomenclature Committee on Cell Death 2018.

Project description:Over the past decade, the Nomenclature Committee on Cell Death (NCCD) has formulated guidelines for the definition and interpretation of cell death from morphological, biochemical, and functional perspectives. Since the field continues to expand and novel mechanisms that orchestrate multiple cell death pathways are unveiled, we propose an updated classification of cell death subroutines focusing on mechanistic and essential (as opposed to correlative and dispensable) aspects of the process. As we provide molecularly oriented definitions of terms including intrinsic apoptosis, extrinsic apoptosis, mitochondrial permeability transition (MPT)-driven necrosis, necroptosis, ferroptosis, pyroptosis, parthanatos, entotic cell death, NETotic cell death, lysosome-dependent cell death, autophagy-dependent cell death, immunogenic cell death, cellular senescence, and mitotic catastrophe, we discuss the utility of neologisms that refer to highly specialized instances of these processes. The mission of the NCCD is to provide a widely accepted nomenclature on cell death in support of the continued development of the field.

| S-EPMC5864239 | biostudies-literature

International Consensus Recommendations for Eosinophilic Gastrointestinal Disease Nomenclature.

Project description:Background & aimsSubstantial heterogeneity in terminology used for eosinophilic gastrointestinal diseases (EGIDs), particularly the catchall term "eosinophilic gastroenteritis," limits clinical and research advances. We aimed to achieve an international consensus for standardized EGID nomenclature.MethodsThis consensus process utilized Delphi methodology. An initial naming framework was proposed and refined in iterative fashion, then assessed in a first round of Delphi voting. Results were discussed in 2 consensus meetings, and the framework was updated and reassessed in a second Delphi vote, with a 70% threshold set for agreement.ResultsOf 91 experts participating, 85 (93%) completed the first and 82 (90%) completed the second Delphi surveys. Consensus was reached on all but 2 statements. "EGID" was the preferred umbrella term for disorders of gastrointestinal (GI) tract eosinophilic inflammation in the absence of secondary causes (100% agreement). Involved GI tract segments will be named specifically and use an "Eo" abbreviation convention: eosinophilic gastritis (now abbreviated EoG), eosinophilic enteritis (EoN), and eosinophilic colitis (EoC). The term "eosinophilic gastroenteritis" is no longer preferred as the overall name (96% agreement). When >2 GI tract areas are involved, the name should reflect all of the involved areas.ConclusionsThis international process resulted in consensus for updated EGID nomenclature for both clinical and research use. EGID will be the umbrella term, rather than "eosinophilic gastroenteritis," and specific naming conventions by location of GI tract involvement are recommended. As more data are developed, this framework can be updated to reflect best practices and the underlying science.

| S-EPMC9378753 | biostudies-literature

Report of the Nomenclature Committee for Fungi - 21: Lists from working groups.

Project description:Six lists of names from working groups set up under Art. 14.13 are approved, consisting of three names of families, 43 names of genera and five names of species, to be treated as conserved against the listed synonymous or homonymous names. Lists were compiled by working groups approved by the International Commission on the Taxonomy of Fungi and the Nomenclature Committee for Fungi: on Cordyceps, Diaporthales, Dothideomycetes, Hypocreales, Leotiomycetes, and Trichoderma and Hypocrea. Issues around interpretation of Art. 14.13 and 56.3 and implementation of Art. 57.2 are discussed.

| S-EPMC5493535 | biostudies-other

Recommendations for standardizing nomenclature for dietary (poly)phenol catabolites.

Project description:There is a lack of focus on the protective health effects of phytochemicals in dietary guidelines. Although a number of chemical libraries and databases contain dietary phytochemicals belonging to the plant metabolome, they are not entirely relevant to human health because many constituents are extensively metabolized within the body following ingestion. This is especially apparent for the highly abundant dietary (poly)phenols, for which the situation is compounded by confusion regarding their bioavailability and metabolism, partially because of the variety of nomenclatures and trivial names used to describe compounds arising from microbial catabolism in the gastrointestinal tract. This confusion, which is perpetuated in online chemical/metabolite databases, will hinder future discovery of bioactivities and affect the establishment of future dietary guidelines if steps are not taken to overcome these issues. In order to resolve this situation, a nomenclature system for phenolic catabolites and their human phase II metabolites is proposed in this article and the basis of its format outlined. Previous names used in the literature are cited along with the recommended nomenclature, International Union of Pure and Applied Chemistry terminology, and, where appropriate, Chemical Abstracts Service numbers, InChIKey, and accurate mass.

| S-EPMC7528558 | biostudies-literature

qnr Gene nomenclature.

Project description: Not available

| S-EPMC2443900 | biostudies-literature

Pharmacogenetic allele nomenclature: International workgroup recommendations for test result reporting.

Project description:This article provides nomenclature recommendations developed by an international workgroup to increase transparency and standardization of pharmacogenetic (PGx) result reporting. Presently, sequence variants identified by PGx tests are described using different nomenclature systems. In addition, PGx analysis may detect different sets of variants for each gene, which can affect interpretation of results. This practice has caused confusion and may thereby impede the adoption of clinical PGx testing. Standardization is critical to move PGx forward.

| S-EPMC4724253 | biostudies-literature

International Union of Pharmacology. LXXII. Recommendations for trace amine receptor nomenclature.

Project description:Trace amines such as p-tyramine and beta-phenylethylamine are found endogenously as well as in the diet. Concomitant ingestion of these foodstuffs with monoamine oxidase inhibitors may result in the hypertensive crisis known as the "beer, wine, and cheese effect" attributed to their sympathomimetic action. Trace amines have been shown to act on one of a novel group of mammalian seven transmembrane spanning G protein-coupled receptors belonging to the rhodopsin superfamily, cloned in 2001. This receptor encoded by the human TAAR1 gene is also present in rat and mouse genomes (Taar1) and has been shown to be activated by endogenous trace amine ligands, including p-tyramine and beta-phenylethylamine. A number of drugs, most notably amphetamine and its derivatives, act as agonists at this receptor. This review proposes an official nomenclature designating TAAR1 as the trace amine 1 receptor following the convention of naming receptors after the endogenous agonist, abbreviated to TA(1) where necessary. It goes on to discuss briefly the significance of the receptor, agents acting upon it, its distribution, and currently hypothesized physiological and pathophysiological roles. In humans, a further five genes are thought to encode functional receptors (TAAR2, TAAR5, TAAR6, TAAR8, and TAAR9). TAAR3 seems to be a pseudogene in some individuals but not others. TAAR4 is a pseudogene in humans, but occurs with TAAR3 as a functional gene in rodents. Nine further genes are present in rats and mice. The endogenous ligands are not firmly established but some may respond to odorants consistent with their expression in olfactory epithelium.

| S-EPMC2830119 | biostudies-literature

Temporary FDA Advisory Committee Members, Recommendations, and Agency Actions, 2017-2021.

Project description: Not available

| S-EPMC11445682 | biostudies-literature

Interkingdom gene fusions.

Project description:BackgroundGenome comparisons have revealed major lateral gene transfer between the three primary kingdoms of life - Bacteria, Archaea, and Eukarya. Another important evolutionary phenomenon involves the evolutionary mobility of protein domains that form versatile multidomain architectures. We were interested in investigating the possibility of a combination of these phenomena, with an invading gene merging with a pre-existing gene in the recipient genome.ResultsComplete genomes of fifteen bacteria, four archaea and one eukaryote were searched for interkingdom gene fusions (IKFs); that is, genes coding for proteins that apparently consist of domains originating from different primary kingdoms. Phylogenetic analysis supported 37 cases of IKF, each of which includes a 'native' domain and a horizontally acquired 'alien' domain. IKFs could have evolved via lateral transfer of a gene coding for the alien domain (or a larger protein containing this domain) followed by recombination with a native gene. For several IKFs, this scenario is supported by the presence of a gene coding for a second, stand-alone version of the alien domain in the recipient genome. Among the genomes investigated, the greatest number of IKFs has been detected in Mycobacterium tuberculosis, where they are almost always accompanied by a stand-alone alien domain. For most of the IKF cases detected in other genomes, the stand-alone counterpart is missing.ConclusionsThe results of comparative genome analysis show that IKF formation is a real, but relatively rare, evolutionary phenomenon. We hypothesize that IKFs are formed primarily via the proposed two-stage mechanism, but other than in the Actinomycetes, in which IKF generation seems to be an active, ongoing process, most of the stand-alone intermediates have been eliminated, perhaps because of functional redundancy.

| S-EPMC16144 | biostudies-literature

OmicsDI is part of the ELIXIR infrastructure

OmicsDI is an Elixir interoperability service. Learn more ›

Tweets

OmicsDI Databases

PRIDE
PeptideAtlas
MassIVE
JPOST Repository
Physiome Model Repository

EGA
EVA
ENA
LINCS
PAXDB
Cell Collective

MetaboLights
Metabolomics Workbench
MetabolomeExpress
GNPS
BioModels
FAIRDOMHub

ArrayExpress
dbGaP
ExpressionAtlas
GEO
NODE

Information

Databases
Help
API
Contact us
Code on GitHub
Terms of use
Submit Data