Developing a Kidney and Urinary Pathway Knowledge Base

S Jupp, J Klein, J Schanstra, R Stevens

    Research output: Contribution to journalArticlepeer-review

    Abstract

    BackgroundChronic renal disease is a global health problem. The identification of suitable biomarkers could facilitate early detection and diagnosis and allow better understanding of the underlying pathology. One of the challenges in meeting this goal is the necessary integration of experimental results from multiple biological levels for further analysis by data mining. Data integration in the life science is still a struggle, and many groups are looking to the benefits promised by the Semantic Web for data integration.ResultsWe present a Semantic Web approach to developing a knowledge base that integrates data from high-throughput experiments on kidney and urine. A specialised KUP ontology is used to tie the various layers together, whilst background knowledge from external databases is incorporated by conversion into RDF. Using SPARQL as a query mechanism, we are able to query for proteins expressed in urine and place these back into the context of genes expressed in regions of the kidney.ConclusionsThe KUPKB gives KUP biologists the means to ask queries across many resources in order to aggregate knowledge that is necessary for answering biological questions. The Semantic Web technologies we use, together with the background knowledge from the domain's ontologies, allows both rapid conversion and integration of this knowledge base. The KUPKB is still relatively small, but questions remain about scalability, maintenance and availability of the knowledge itself.AvailabilityThe KUPKB may be accessed via http://www.e-lico.eu/kupkb webcite.
    Original languageEnglish
    JournalJournal of Biomedical Semantics
    Volume2
    Issue numberSuppl. 2
    DOIs
    Publication statusPublished - 2011

    Fingerprint

    Dive into the research topics of 'Developing a Kidney and Urinary Pathway Knowledge Base'. Together they form a unique fingerprint.

    Cite this