HCLSIG BioRDF Subgroup/Tasks/OMIM Neural diseases

From W3C Wiki
< HCLSIG BioRDF Subgroup‎ | Tasks
Revision as of 20:10, 19 April 2006 by (Talk)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Task: Create RDF to describe entries in the NCBI database Online Mendelian Inheritance in Man (OMIM)

Task Objectives:

  1. Find and use controlled vocabulary for disease/condition that will enable later linking of different content.
  2. Generate RDF annotation suitable for linking disease, gene, and papers about the disease, and for gathering into the BioRDF demo.

Participants: Davide Zaccagnini, Chris Mungall?

Use case context: Link to and from information about inherited neurological diseases.


Problem statement for this use case:

In order to bridge the gap from bench to bedside, we need explicitly represented resources that cross the boundary from disease to genetics. OMIM is one such resource, giving information about the disease itself, relating it to known information about genes or loci playing a role in the disease. By linking back to papers in pubmed, a researcher can quickly navigate to the primary source for the information. Major entities that might be made available in RDF from OMIM are gene, chromosome and position within, disease symptoms as freetext, names of populations with different prevalance, and pubmed identifiers.


Deliverables

  1. Informal proposal of what the content of the RDF will be. Which fields are structured/unstructured. Minimal: Disease name, Gene, chromosome, locus, references to papers.
  2. Choice of controlled vocabulary/ontology for disease, if feasible.
  3. Version of RDF suitable for linking gene, chromosome, papers, diseases. To limit the scope we could choose to translate the 1000 or so records retrieved on a search for "neuro".
  4. List of opportunities for extraction of further information by text mining.
  5. Any artifacts generated in the process, scripts, spreadsheets etc.
  6. Lessons learned

Related resources:

Task supports and dependencies:

Tools and Services:

Timeline for Task Completion

  • Stage 1
  • Stage 2

Categories: