in the effort to identify which gene or genes produce what disease phenotype , geneticists are producing an increasing number of genome - wide linkage analyses and gene association studies that are generating too many to test candidate genes .
for this reason , during the past five years , the problem of automating the prioritization of candidate genes to inherited diseases has received increasing attention from the bioinformatics community .
computational approaches were made possible due to the availability of the complete human genome sequence and to considerable developments on database annotation and data integration for molecular biology databases . as a result ,
these methods apply a variety of approaches exploiting known or deduced pieces of information that range from using only the genomic sequence of the target region to data mining analyses that include literature and different annotation systems . for details about these methods
a recent work where many of these methods were applied to the prioritization of gene candidates for obesity and type 2 diabetes , shows that there are many discrepancies between the produced candidate gene lists ( 13 ) .
this study suggests the concurrent use of as many approaches as possible when working with particular diseases , especially as there are large differences in the kind and amount of useful information that it is available for each disease .
following this idea , we are developing and maintaining g2d ( genes to diseases ) , a resource that seeks to encompass an increasing number of methodologies to obtain disease - related genes .
g2d is a web resource for prioritizing genes as candidates to inherited diseases , which started as a public server in 2002 . at the time
, we provided the users with pre - analyses of hundreds of inherited diseases by applying a literature and data mining algorithm based on fuzzy binary relations ( 2 ) using the disease 's phenotype as input . in 2005
one is the use of genes in a different genomic location already known or suspected to produce a similar variant of the disease of interest .
the expectation is that the disease - responsible gene will have a similar function to those .
this is a more stringent approximation and requires more information about the disease , but it is obviously correct in some cases .
the second approach added to g2d , uses as input a second locus where the phenotype has also been mapped in addition to the one where the user is looking for the mutation ( as in complex diseases ) .
the expectation is that the products of the genes in several of the loci may be functionally associated , e.g. by participating in the same pathway , or even by being part of a protein complex ( 9,11 ) .
the system will prioritize the candidates according to whether functional interactions ( both known and predicted ) between proteins encoded in genes of both loci are detected .
we used the human protein interactions from the string database ( 15 ) as our source database . besides this web implementation
, g2d has been applied by us to the prioritization of genes for complex diseases in two different studies so far : the aforementioned collective computational study to suggest candidates for obesity and type 2 diabetes ( 13 ) , and to the selection of asthma candidates for genotyping in two linkage regions in a french canadian founder population ( manuscript in preparation ) .
given a chromosomal region where the user is looking for candidate genes , there are three ways of using the g2d server depending on the algorithm that will be applied .
the first option takes as input the phenotype of the disease of interest described by means of an online mendelian inferitance in man ( omim ) disease entry ( 16 ) .
the system will prioritize the genes according to the description of the phenotype as provided by the mesh disease annotations ( http://www.nlm.nih.gov/mesh/ ) to the linked bibliography in the corresponding omim entry . for details of this method see ( 2 ) .
a second option is to input one or several human or mouse genes that are already known or are suspected to be involved in the disease .
the system will prioritize the genes in the target region according to their similarity to the known gene(s ) as given by their go annotations and high sequence homology . in order to do this
, we compute scores for all go terms according to their similarity to the go terms of the known genes ( measured in terms of their resnik similarity ) .
next , we apply this go scoring system to the annotated genes in entrez gene .
their corresponding refseq proteins are compared through blastx to the chromosomal target region , and the scoring is transferred to the hits that are below the selected e - value .
the third option can be used when another chromosomal region has been also linked to the disease of interest .
the system will look for protein  protein interactions in the string database , both known and predicted that may be occurring between a gene in the region of interest and a gene in the second region . since many interactions in string are predicted , every interaction has associated a score ( string score ) that reflects how likely is to be a true interaction .
candidates that are more likely to interact with a gene in the second region are then prioritized . in our benchmark
( see conclusion and supplementary page in our web site ) , we observed higher precision when string scores are very high .
additionally , it is possible to access from our server a database of pre - calculated results for more than 550 monogenic diseases on published linkage regions using the phenotype method . in the next sections ,
we describe the different use options through examples . we have prepared step - by - step web tutorials that contain very detailed information .
they can be accessed from our web server page ( see tutorial section at our web site ) .
the system will prioritize the genes according to the description of the phenotype and its precomputed associations to gene features as extracted from the literature and the entrez gene database .
the input consists simply of the region where the user is looking for the mutation , and the phenotype of interest , given as an omim identifier .
for example , suppose that you are interested in candidate genes to hirschsprung disease in 22q13.2 .
you have to enter in the appropriate boxes a mim number that defines the disease and the target region . in this particular case
, you would enter 131224 ( the i d of the omim entry for hirschsprung disease ) in the phenotype box , and q13.2 in the location box .
you would also select the chromosome , 22 and  bands in the location box as you have entered the genomic region in the form of a cytogenetic band .
the output is an ordered list of candidate genes , both known and predicted , ordered according to their susceptibility for producing the phenotype . for each candidate
, you can explore any overlapping with ests and pseudogenes , as well as trace back the reasoning the system followed to associate the candidates to the disease .
this method can be used when one or more genes are already known or are suspected to be related to the disease . in order to use it , you have to provide your target region in the location box in the same way as for the phenotype method , plus one or several human genes associated to the disease or related mouse genes . following with our example ,
hirschsprung disease is suspected to be a multigenic disease , and it is known that mutations in the endothelin - b receptor ( etrb ) gene cause one of the variants of this disease . in order to find similar or functionally related genes to etrb in 22q13.2 , you could input the entrez gene ids of human and mouse etrbs in the known genes box .
, the output is an ordered list of candidate genes that you may explore in a similar manner .
candidates that overlap with genes that have ( string ) interactions with any of the known genes input by the user are flagged .
the third method for finding candidate genes for multiple gene phenotypes relies on protein  protein functional interactions , either known or predicted .
the rational is that mutations on two proteins that participate on the same pathway , or are directly interacting , will produce the same or very similar phenotypes .
the input for this method consists of the target region , entered in the location box like in the previous two methods , and a second region where the phenotype of interest has been also mapped to .
the second region is entered in the second locus box in the same manner , specifying format and chromosome .
the output is a list of genes in the target region that may interact , according to string ( 15 ) , with any genes(s ) in the second box locus .
candidates are sorted by how likely are their corresponding interactions to be true indicated by their associated string scores with 0.99 as maximum value . as an illustration ,
suppose that you are interested in candidates for myocardial infarction susceptibility ( mis ) on 1p36-p34 , one of the loci where the condition has been linked to ( 17 ) .
the omim entry for mis ( 608446 ) shows that it is linked as well to regions 1q25 , 6q25.1 and 1p22.1 . by entering 1q25 as the second locus
, the output page displays 20 candidates corresponding to proteins in 1p36-p34 that interact , according to the string database , with at least one protein in 1q25 .
the first candidate ( see figure 1 ) is the tumor necrosis factor receptor superfamily , member 4 tnfrsf4 ( entrez gene i d 7293 , located on 1p36 ) .
this gene comes out as the top candidate because of its direct interaction ( string score = 0.999 ) with tnfsf4 , the tumor necrosis factor ( ligand ) superfamily , member 4 ( tax - transcriptionally activated glycoprotein 1 , 34  kda ) ( entrez gene i d 7292 ) .
the latter has been recently associated to atherosclerosis susceptibility increasing the risk for myocardial infarction ( 18 ) making tnfrsf4  a very good candidate .
tnfrsf4 is therefore a quite attractive candidate from a biological point of view , not yet tested but within the linkage peak identified by the group that linked mis to 1p36-p34 ( e.j .
figure 1.g2d web server interface used to detect genes associated to mis using the protein - protein method .
top left : the user inputs the coordinates for locus 1 ( 1p36-p34 ) and locus 2 ( 1q25 ) that have been genetically linked to mis .
top right : g2d displays 20 gene candidates in locus 1 that code for proteins that interact with proteins encoded by genes found in locus 2 .
bottom : tumor necrosis factor tnfsf4 and its receptor tnfrsf4 are encoded in locus 2 and locus 1 , respectively , being therefore good candidates ; a similar pair of genes ( tnfsf8/tnfrsf8 ) appears as candidate 3 .
g2d web server interface used to detect genes associated to mis using the protein - protein method .
top left : the user inputs the coordinates for locus 1 ( 1p36-p34 ) and locus 2 ( 1q25 ) that have been genetically linked to mis .
top right : g2d displays 20 gene candidates in locus 1 that code for proteins that interact with proteins encoded by genes found in locus 2 .
bottom : tumor necrosis factor tnfsf4 and its receptor tnfrsf4 are encoded in locus 2 and locus 1 , respectively , being therefore good candidates ; a similar pair of genes ( tnfsf8/tnfrsf8 ) appears as candidate 3 .
the g2d web server allows users to prioritize candidate genes for practically any disease phenotype in omim through three different methods .
the results of benchmarking the methods on 227 diseases that have been shown to be caused by more than one gene , are given in detail in our web server ( see supplementary section at our web site ) , and they can serve as a guidance on the expected performance of each method .
the phenotype and the known - genes methods show a similar performance prioritizing the responsible gene in average among the top 25 and 27% of all genes in the band , respectively , when considering target bands of 30 mb ( averaging a content of 300 genes ) .
it must be taken into account , however , that more input information about the molecular cause of the disease is required by the known - genes method . the protein 
protein interactions method has a very low recall but shows high precision when the string scores associated to the candidates are  high and  very high ( 0.9 score value and higher ) .
this method could be applied to a proportion of one in four cases , and in such situations the responsible gene was among the top 10 candidates , 70% of the times for bands of size 30 mb . running times for the algorithms vary from very few seconds to almost immediate yielding of results .
users can examine , for all three procedures , the rational used by the system to make the prioritization , keeping the process transparent .
we support this by including extensive hyperlinks to related resources such as ncbi sequence databases , gene ontology and the ucsc genome browser .
 g2d ( genes to diseases ) is a web resource for prioritizing genes as candidates for inherited diseases . 
 it uses three algorithms based on different prioritization strategies . 
 the input to the server is the genomic region where the user is looking for the disease - causing mutation , plus an additional piece of information depending on the algorithm used . 
 this information can either be the disease phenotype ( described as an online mendelian inheritance in man ( omim ) identifier ) , one or several genes known or suspected to be associated with the disease ( defined by their entrez gene identifiers ) , or a second genomic region that has been linked as well to the disease . in the latter case , the tool uses known or predicted interactions between genes in the two regions extracted from the string database . 
 the output in every case is an ordered list of candidate genes in the region of interest . 
 for the first two of the three methods , the candidate genes are first retrieved through sequence homology search , then scored accordingly to the corresponding method . 
 this means that some of them will correspond to well - known characterized genes , and others will overlap with predicted genes , thus providing a wider analysis . 
 g2d is publicly available at http://www.ogic.ca/projects/g2d_2/ 
BACKGROUND
OUTLINE OF THE G2D SERVER
USE OF PHENOTYPE
USE OF KNOWN GENES
USE OF STRING PROTEINPROTEIN INTERACTIONS
CONCLUSION
SUPPLEMENTARY DATA