-
Notifications
You must be signed in to change notification settings - Fork 54
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
Comments
This is related to/partly duplicates #265 |
Clinical-grade disease-gene associations: 3928 genes in OMIM currently associated to disease, <3500 single-gene, classical Mendelian though
See Slack commentary in curation channel |
@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 |
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 For example: https://search.thegencc.org/genes/HGNC:17416
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 |
I guess GenCC has potentially conflicting classifications for the same OMIM
or Orphanet disease ID whereas ClinGen will have a consistent annotation?
One option is to just take all Definitive annotations and not worry about
conflicts.
…On Mon, Jul 3, 2023 at 3:42 PM Jules Jacobsen ***@***.***> wrote:
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'
<https://search.thegencc.org/submitters/GENCC_000110>, 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.
—
Reply to this email directly, view it on GitHub
<#159 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABHO4PBONCSRH2QVAL4ZZBDXOLK5DANCNFSM4CX27QMA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
The issue is the Orphanet only assert Our current
Altering it to look like this, would be a lot more useful (the OMIM_GENE_ID column is unused in the application):
This would involve some kind or four-way merge of OMIM, HPOA, Orphanet and GenCC annotations 😱 |
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. |
cc @putmantime, we have also been looking at comparing g2d associations,
let's coordinate efforts
…On Mon, Jul 3, 2023 at 7:42 AM Jules Jacobsen ***@***.***> wrote:
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'
<https://search.thegencc.org/submitters/GENCC_000110>, 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.
—
Reply to this email directly, view it on GitHub
<#159 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAMMOKOTF6TW6UIURFLLHDXOLK5DANCNFSM4CX27QMA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
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.
The text was updated successfully, but these errors were encountered: