Download to read offline
Uploaded byAlasdair Gray
Computing Identity Co-Reference Across Drug Discovery Datasets
The document discusses the challenges of identity co-reference in drug discovery datasets, emphasizing the concept that the number of identifiers for an individual may equal or exceed the number of institutions involved. It outlines a method for resolving identities, including the implementation of rules to ensure accurate connections between genes, proteins, and compounds, while capturing provenance. Conclusions highlight the advantages of computing co-reference, which includes reduced data requirements and increased dataset coverage.
Computing Identity Co-Reference Across Drug Discovery Datasets
- 1. Computing Identity Co-reference AcrossDrug Discovery Datasets Christian Y A Brenninkmeijer, Ian Dunlop Carole Goble, Alasdair J G Gray, and Steve Pettifer www.openphacts.org @open_phacts A.J.G.Gray@hw.ac.uk @gray_alasdair
- 2. Multiple Identities Andy Law'sThird Law “The number of unique identifiers assigned to an individual is never less than the number of Institutions involved in the study” http://bioinformatics.roslin.ac.uk/lawslaws/ GB:29384 P12047 Are these the same thing? X31045 10/12/2013 SWAT4LS 2013 1
- 3. Gleevec® = ImatinibMesylate Imatinib Imatinib Mesylate Mesylate YLMAHDNUQAMNNX-UHFFFAOYSA-N ChemSpider 10/12/2013 Drugbank SWAT4LS 2013 PubChem 2
- 4.
- 5.
- 6. Multiple Links: DifferentReasons Link: skos:closeMatch Reason: non-salt form 10/12/2013 Link: skos:exactMatch Reason: drug name SWAT4LS 2013 6
- 7. Open PHACTS DiscoveryPlatform Apps Interactive responses Method Calls Domain API Drug Discovery Platform Production quality integration platform 10/12/2013 SWAT4LS 2013 7
- 8. OPS Discovery Platform CorePlatform Apps Identity Resolution Service Identifier Management Service “Adenosine receptor 2a” Linked Data API (RDF/XML, TTL, JSON) P12374 EC2.43.4 CS4532 Domain Specific Services Semantic Workflow Engine Chemistry Registration Normalisatio n & Q/C Data Cache (Virtuoso Triple Store) Indexing VoID VoID VoID Nanopub Public Ontologies Db Db 10/12/2013 VoID Nanopub Db Nanopub Db SWAT4LS 2013 Public Content VoID Commercial User Annotations 8
- 9.
- 10. Connectivity of InitialLinksets Datasets 37 Linksets 104 Links 7,096,712 Justifications 10/12/2013 7 SWAT4LS 2013 10
- 12. Genes == Proteins? BRCA1 Breastcancer type 1 susceptibility protein http://en.wikipedia.org/wiki/File:BRCA1_en.p ng http://en.wikipedia.org/wiki/File:Pr otein_BRCA1_PDB_1jm7.png 10/12/2013 SWAT4LS 2013 12
- 13.
- 14. Co-reference Computation Rules ensure •Unrestricted transitivity within conceptual type • Restrict crossing conceptual types 0..* 0..1 0..* Based on justifications 0..1 Provenance captured 0..* 10/12/2013 SWAT4LS 2013 14
- 15. Connectivity of InitialLinksets Datasets 37 Linksets 104 Links 7,096,712 Justifications 10/12/2013 7 SWAT4LS 2013 15
- 16.
- 17.
- 18. Conclusions • Computing co-referenceadvantageous – Requires less raw linksets – Larger coverage across datasets • Rules ensure control – Genes can equal proteins – Compounds never equal proteins • Provenance captured throughout 10/12/2013 SWAT4LS 2013 18
- 19.
Editor's Notes
- #2 Each captures a subtly different view of the worldAre they the same? … depends on your point of view
- #3 Example drug:Gleevec Cancer drug for leukemiaLookup in three popular public chemical databasesDifferent resultsData is messy!
- #4 Enter with ChemSpider URI forImatinibThis is not Gleevec
- #7 sameAs != sameAs depends on your point of viewLinks relate individual data instances: source, target, predicate, reason.Links are grouped into Linksets which have VoID header providing provenance and justification for the link.
- #8 A platform for integratedpharmacology data Reliedupon by pharma companiesPublic domain, commercial, and private data sourcesProvidesdomainspecific APIMakingiteasyto build multiple drugdiscoveryapplications:examplesdeveloped in the project
- #9 Import data into cacheAPI calls populate SPARQL queriesIntegration approachData kept in original modelData cached in central triple storeAPI call translated to SPARQL queryQuery expressed in terms of original dataQueries expanded by IMS to cover URIs of original datasets
- #10 User starts typingServer sends back suggestionsUser selects oneURI sent to platformIntegrated Information returned
- #11 Can enter with IDs from any of the supported datasets
- #12 Platform extracts data from certain datasetsThese need to be connectedHere there is no issue in computing transitive as they are all the same compound based on InChI keyWould compute the full set of links
- #13 Do genes == proteins?Different conceptual types: gene and proteinOften used as a shortcut for retrieval: BRCA1 easier to remember and type!Require the ability to equate them in the IMS----But if you’re saying why genes=proteins you may also want to be prepared for questions of when genes!=proteins. Splice variation is a common example, n the FAS receptor:http://en.wikipedia.org/wiki/Alternative_splicing#Exon_definition:_Fas_receptor there is one gene but it can be made into two distinct proteins - which have different biological effects), so you can obviously mix bio data that shouldnt be mixed by integrating these two functions on the same ID. [We currently dont handle this well in OPS]And the most used example here, the ghrelin gene is transcribed into a protein which is cleaved in two to form two completely different hormones, ghrelin and obestatin, which do very different things. But come from the same gene http://en.wikipedia.org/wiki/Ghrelin#Synthesis_and_variants
- #14 Insulin ReceptorIssue when linking through PDB due to the way that proteins are crystalised
- #16 Can enter with IDs from any of the supported datasets