[go: nahoru, domu]

Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Diagnostic-grade Exomiser #159

Open
damiansm opened this issue Nov 29, 2016 · 9 comments
Open

Diagnostic-grade Exomiser #159

damiansm opened this issue Nov 29, 2016 · 9 comments

Comments

@damiansm
Copy link
Contributor

Diagnostic-grade Exomiser with a manually curated source of reliable disease-gene associations i.e. like what we do for Genomics England with PanelApp. The trouble is no-one has this knowledgebase yet and guessing it will be a while before ClinGen really gets there? This may be another use-case where we want to allow people to use their own data as an option. I could see an Exomiser that took in the PanelApp disease-gene associations would be really powerful for GeL and of course I could hack it for them but I suspect other groups would be keen.

@damiansm damiansm added this to the 9.0.0 - The Rich Client Release milestone Nov 29, 2016
@damiansm damiansm added this to TODO - enhancements in Release 9.0.0 Jul 10, 2017
@damiansm damiansm moved this from Viz improvements to New features in Release 9.0.0 Jul 20, 2017
@damiansm damiansm added this to New scores or algs in Issues triage Oct 30, 2018
@julesjacobsen
Copy link
Contributor

This is related to/partly duplicates #265

@damiansm
Copy link
Contributor Author

Clinical-grade disease-gene associations: 3928 genes in OMIM currently associated to disease, <3500 single-gene, classical Mendelian though

  1. work with PanelApp team to get an OMIM disease ID for every curated gene - resurrect what I did before and see if they made progress with OpenTargets
  2. do a similar level of curation on the remaining dis-gene associations in OMIM and Orphanet

See Slack commentary in curation channel

@julesjacobsen julesjacobsen modified the milestones: 9.0.0, 15.0.0 Feb 2, 2023
@julesjacobsen
Copy link
Contributor

@damiansm There is ClinGen and TheGenCC which could fulfill this criteria, assuming we used the 'definitive' associations.

This would require a database change to store the data and some means of enabling this from the user command through to the application only using these annotations.

@damiansm
Copy link
Contributor Author
damiansm commented Jul 3, 2023

@julesjacobsen Yes - this recent work makes this task a lot easier. It could be as easy as trimming the disease2gene table we load into Exomiser based on knowledge from GenCC. Looks like MONOD based but original OMIM ID is also stored: https://search.thegencc.org/genes/HGNC:13666

@julesjacobsen
Copy link
Contributor
julesjacobsen commented Jul 3, 2023

Good to know they have the original OMIM ID in there as that will be really useful. The next question is what classification to use when there are conflicts between submitters. In this case Ambry and TGMI say Definitive, Invitae go for Strong (although they never use definitive (https://search.thegencc.org/submitters/GENCC_000106)) and Orphanet only ever use Supportive, so I guess going with a Strong or Definitive assertion should be safe to do if trying to summarise.

For example:

https://search.thegencc.org/genes/HGNC:17416

gene_curie gene_symbol disease_curie disease_title disease_original_curie disease_original_title classification_curie classification_title moi_curie moi_title submitter_curie submitter_title
HGNC:17416 ADGRV1 MONDO:0011558 Usher syndrome type 2C OMIM:605472 OMIM:605472 GENCC:100002 Strong HP:0000007 Autosomal recessive GENCC:000111 PanelApp Australia
HGNC:17416 ADGRV1 MONDO:0016484 Usher syndrome type 2 Orphanet:231178 Orphanet:231178 GENCC:100009 Supportive HP:0000007 Autosomal recessive GENCC:000110 Orphanet
HGNC:17416 ADGRV1 MONDO:0016484 Usher syndrome type 2 MONDO:0016484 Usher syndrome type 2 GENCC:100001 Definitive HP:0000007 Autosomal recessive GENCC:000102 ClinGen
HGNC:17416 ADGRV1 MONDO:0011443 febrile seizures, familial, 4 OMIM:604352 OMIM:604352 GENCC:100004 Limited HP:0000006 Autosomal dominant GENCC:000101 Ambry Genetics
HGNC:17416 ADGRV1 MONDO:0019497 nonsyndromic genetic hearing loss MONDO:0019497 nonsyndromic genetic hearing loss GENCC:100005 Disputed Evidence HP:0000007 Autosomal recessive GENCC:000102 ClinGen

The only problem is that ClinGen only curate to MONDO and these don't always align with OMIM (at least in this case it does with Orphanet) so the Orphanet and ClinGen submissions could be merged with Definitive evidence but there is still an issue about if and where to use MONDO identifiers.

@damiansm
Copy link
Contributor Author
damiansm commented Jul 3, 2023 via email

@julesjacobsen
Copy link
Contributor
julesjacobsen commented Jul 3, 2023

The issue is the Orphanet only assert Supporting, ClinGen assert the full range and only use MONDO identifiers. PanelApp (GEL & Aus) use mostly OMIM identifiers for original submissions, but The GenCC map everything to MONDO. OMIM still haven't submitted any assertions.

Our current disease table looks like this:

DISEASE_ID OMIM_GENE_ID DISEASENAME GENE_ID TYPE INHERITANCE
OMIM:604352 OMIM:602851 ?Febrile seizures, familial, 4 84059 ? D
OMIM:605472 OMIM:602851 Usher syndrome, type 2C 84059 D R
ORPHA:231178 OMIM:602851 Usher syndrome type 2 84059 D R
ORPHA:36387 OMIM:602851 Generalized epilepsy with febrile seizures-plus 84059 D D

Altering it to look like this, would be a lot more useful (the OMIM_GENE_ID column is unused in the application):

DISEASE_ID MONDO_ID DISEASENAME GENE_ID TYPE INHERITANCE GENCC_VALIDITY
OMIM:604352 MONDO:0011443 Febrile seizures, familial, 4 84059 ? D Limited
OMIM:605472 MONDO:0011558 Usher syndrome, type 2C 84059 D R Strong
ORPHA:231178 MONDO:0016484 Usher syndrome type 2 84059 D R Definitive (Supportive in Orphanet)
ORPHA:36387 MONDO:0018214 Generalized epilepsy with febrile seizures-plus 84059 D D (our data come from Orphanet but there is no assertion for this D2G yet, probably safe to assume Supportive)

This would involve some kind or four-way merge of OMIM, HPOA, Orphanet and GenCC annotations 😱

@damiansm
Copy link
Contributor Author
damiansm commented Jul 4, 2023

Lets decide what if we are going to use the data for first and for what? If we just want to have a definitive only setting then we can just flag those associations in the disease table. If we want to display the tag for all rows or use it for weighting etc then we need all the data.

@cmungall
Copy link
Contributor
cmungall commented Jul 5, 2023 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Release 9.0.0
New features
Development

No branches or pull requests

3 participants