Skip to main content

Monarch presenting at ASHG 2014, Oct 18-22, San Diego


We'll be heading to American Society for Human Genetics 2014 conference in San Diego, October 18-22. Please check out our work in the following sessions:
  • 170. PhenomeCentral: An integrated portal for sharing patient phenotype and genotype data for rare genetic disorders. Mon Oct 20 5:30p. Concurrent Platform Session C: From Bytes To Phenotypes. Hall B1, Ground Level, Convention Center
    Michael Brudno will present the new data sharing portal PhenomeCentral, which facilitates the identification of phenotypically similar patients, utilizing the Human Phenotype Ontology (HPO) for linking patient phenotypes. Monarch contributes the API for the Annotation Sufficiency metric, actively develops on the HPO, and has provided user testing and documentation. Cases from our work with the NIH Intramural Undiagnosed Disease Program (UDP) have been deposited into PhenomeCentral.
  • 1499T. Standardized phenotyping enables rapid and accurate prioritization of disease-associated and previously unreported sequence variants. Tue Oct 21 2-3pm.
    William Bone will present our work with the NIH UDP, particularly about the use of Exomiser 2.0 as a rapid and effective method to screen for variants. The updated algorithm uses a combination of disease-gene and model organism phenotypes, together with protein-protein associations for candidate prioritization.
  • 1643T. Phenotype terminologies in use for genotype-phenotype databases: A common core for standardisation and interoperability. Tue Oct 21 2-3pm.
    Peter Robinson will present the efforts to develop a core terminology of phenotypes that is interoperable with all terminologies in current use including PhenoDB, London Dysmorphology Database, Orphanet, Human Phenotype Ontology, Elements of Morphology, ICD10, UMLS, SNOMED CT, MeSH, and MedDRA.
We will also be spending time at the Global Alliance for Genomics and Health pre-meeting, where we will participate in the Data and Clinical working group breakout sessions on metadata and ontologies.

Popular posts from this blog

How to annotate a patient's phenotypic profile

How to annotate a patient's phenotypic profile using PhenoTips and the Human Phenotype Ontology Purpose We have observed that performance of computational search algorithms within and across species improves if a comprehensive list of phenotypic features is recorded. It is helpful if the person annotating thinks of the set of annotations as a query against all known phenotype profiles. Therefore, the set of phenotypes chosen for the annotation must be as specific as possible, and represent the most salient and important observable phenotypes. Towards this end, Monarch has been asked to provide guidance on how to create a quality patient profile using the Human Phenotype Ontology (HPO). Below we detail our annotation guidelines for use in the PhenoTips application, our partner organization.  The guidelines can also be considered more generically so as to be applicable to any annotation effort using HPO or even using other phenotype ontologies.  The annotations should be lim

Finally, a medical terminology that patients, doctors, and machines can all understand.

By Nicole Vasilevsky, Mark Engelstad, Erin Foster, Julie McMurry, Chris Mungall, Peter Robinson, Sebastian Köhler, Melissa Haendel For many patients with rare and undiagnosed diseases, getting an accurate diagnosis, or even finding the appropriate experts is a long and winding road. To accelerate and facilitate this process, we developed a medical vocabulary (“HPO”) which is comprised of 12,000 terms that doctors can use to codify the precise and distinct observations about patients and their conditions. The HPO is structured in a way that enables machines to intelligently compare a patient’s profile with what scientists worldwide have already uncovered about diseases and their genetic causes. Until now, most of the HPO labels and synonyms were composed of clinical terms unfamiliar to patients. For example, a patient may know they are ‘color-blind’, but may not be familiar with the clinical term ‘Dyschromatopsia’. This is why we developed a layer of 5,000 corresponding terms tha

Why the Human Phenotype Ontology?

We've often been asked, why should we use the Human Phenotype Ontology to describe patient phenotypes, rather than a more widely-used clinical vocabulary such as ICD or SNOMED? Here are the answers to some of these frequently asked questions: 1. We should use what other big NIH projects, like ClinVar, are using. ClinVar is using HPO terms to describe phenotypes. This is done in collaboration with MedGen, which has imported HPO terms. Here is an example: http://www.ncbi.nlm.nih.gov/medgen/504827 There are now many bioinformatics tools that use the HPO to empower exome diagnostics. The Monarch team has published two of these recently 1) Exomiser ( Robinson et al., 2014 Genome Res. ) => For discovering new disease genes via model organism data, several successful use cases at UDP and elsewhere 2) PhenIX ( Zemojtel et al., 2014 Science Translational Medicine ) => For clinical diagnostics of “difficult” cases. This paper was on Russ Altman's year in review at AMIA this year.