<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.3 20070202//EN" "journalpublishing.dtd">
<article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article">
<front>
<journal-meta>
<journal-id journal-id-type="publisher-id">Front. Med.</journal-id>
<journal-title>Frontiers in Medicine</journal-title>
<abbrev-journal-title abbrev-type="pubmed">Front. Med.</abbrev-journal-title>
<issn pub-type="epub">2296-858X</issn>
<publisher>
<publisher-name>Frontiers Media S.A.</publisher-name>
</publisher>
</journal-meta>
<article-meta>
<article-id pub-id-type="doi">10.3389/fmed.2016.00039</article-id>
<article-categories>
<subj-group subj-group-type="heading">
<subject>Medicine</subject>
<subj-group>
<subject>Technology Report</subject>
</subj-group>
</subj-group>
</article-categories>
<title-group>
<article-title>Distributed Cognition and Process Management Enabling Individualized Translational Research: The NIH Undiagnosed Diseases Program Experience</article-title>
</title-group>
<contrib-group>
<contrib contrib-type="author">
<name><surname>Links</surname> <given-names>Amanda E.</given-names></name>
<xref ref-type="aff" rid="aff1"><sup>1</sup></xref>
<xref ref-type="aff" rid="aff2"><sup>2</sup></xref>
<uri xlink:href="http://frontiersin.org/people/u/364514"/>
</contrib>
<contrib contrib-type="author">
<name><surname>Draper</surname> <given-names>David</given-names></name>
<xref ref-type="aff" rid="aff1"><sup>1</sup></xref>
<xref ref-type="aff" rid="aff2"><sup>2</sup></xref>
</contrib>
<contrib contrib-type="author">
<name><surname>Lee</surname> <given-names>Elizabeth</given-names></name>
<xref ref-type="aff" rid="aff1"><sup>1</sup></xref>
<xref ref-type="aff" rid="aff2"><sup>2</sup></xref>
</contrib>
<contrib contrib-type="author">
<name><surname>Guzman</surname> <given-names>Jessica</given-names></name>
<xref ref-type="aff" rid="aff1"><sup>1</sup></xref>
<xref ref-type="aff" rid="aff2"><sup>2</sup></xref>
</contrib>
<contrib contrib-type="author">
<name><surname>Valivullah</surname> <given-names>Zaheer</given-names></name>
<xref ref-type="aff" rid="aff1"><sup>1</sup></xref>
<xref ref-type="aff" rid="aff2"><sup>2</sup></xref>
</contrib>
<contrib contrib-type="author">
<name><surname>Maduro</surname> <given-names>Valerie</given-names></name>
<xref ref-type="aff" rid="aff1"><sup>1</sup></xref>
<xref ref-type="aff" rid="aff2"><sup>2</sup></xref>
</contrib>
<contrib contrib-type="author">
<name><surname>Lebedev</surname> <given-names>Vlad</given-names></name>
<xref ref-type="aff" rid="aff3"><sup>3</sup></xref>
</contrib>
<contrib contrib-type="author">
<name><surname>Didenko</surname> <given-names>Maxim</given-names></name>
<xref ref-type="aff" rid="aff3"><sup>3</sup></xref>
</contrib>
<contrib contrib-type="author">
<name><surname>Tomlin</surname> <given-names>Garrick</given-names></name>
<xref ref-type="aff" rid="aff3"><sup>3</sup></xref>
</contrib>
<contrib contrib-type="author">
<name><surname>Brudno</surname> <given-names>Michael</given-names></name>
<xref ref-type="aff" rid="aff4"><sup>4</sup></xref>
<xref ref-type="aff" rid="aff5"><sup>5</sup></xref>
</contrib>
<contrib contrib-type="author">
<name><surname>Girdea</surname> <given-names>Marta</given-names></name>
<xref ref-type="aff" rid="aff4"><sup>4</sup></xref>
<xref ref-type="aff" rid="aff5"><sup>5</sup></xref>
</contrib>
<contrib contrib-type="author">
<name><surname>Dumitriu</surname> <given-names>Sergiu</given-names></name>
<xref ref-type="aff" rid="aff4"><sup>4</sup></xref>
</contrib>
<contrib contrib-type="author">
<name><surname>Haendel</surname> <given-names>Melissa A.</given-names></name>
<xref ref-type="aff" rid="aff6"><sup>6</sup></xref>
</contrib>
<contrib contrib-type="author">
<name><surname>Mungall</surname> <given-names>Christopher J.</given-names></name>
<xref ref-type="aff" rid="aff7"><sup>7</sup></xref>
</contrib>
<contrib contrib-type="author">
<name><surname>Smedley</surname> <given-names>Damian</given-names></name>
<xref ref-type="aff" rid="aff8"><sup>8</sup></xref>
</contrib>
<contrib contrib-type="author">
<name><surname>Hochheiser</surname> <given-names>Harry</given-names></name>
<xref ref-type="aff" rid="aff9"><sup>9</sup></xref>
</contrib>
<contrib contrib-type="author">
<name><surname>Arnold</surname> <given-names>Andrew M.</given-names></name>
<xref ref-type="aff" rid="aff10"><sup>10</sup></xref>
</contrib>
<contrib contrib-type="author">
<name><surname>Coessens</surname> <given-names>Bert</given-names></name>
<xref ref-type="aff" rid="aff10"><sup>10</sup></xref>
</contrib>
<contrib contrib-type="author">
<name><surname>Verhoeven</surname> <given-names>Steven</given-names></name>
<xref ref-type="aff" rid="aff10"><sup>10</sup></xref>
</contrib>
<contrib contrib-type="author">
<name><surname>Bone</surname> <given-names>William</given-names></name>
<xref ref-type="aff" rid="aff1"><sup>1</sup></xref>
<xref ref-type="aff" rid="aff2"><sup>2</sup></xref>
<uri xlink:href="http://frontiersin.org/people/u/358301"/>
</contrib>
<contrib contrib-type="author">
<name><surname>Adams</surname> <given-names>David</given-names></name>
<xref ref-type="aff" rid="aff1"><sup>1</sup></xref>
<xref ref-type="aff" rid="aff2"><sup>2</sup></xref>
</contrib>
<contrib contrib-type="author">
<name><surname>Boerkoel</surname> <given-names>Cornelius F.</given-names></name>
<xref ref-type="aff" rid="aff1"><sup>1</sup></xref>
<xref ref-type="aff" rid="aff2"><sup>2</sup></xref>
<uri xlink:href="http://frontiersin.org/people/u/357887"/>
</contrib>
<contrib contrib-type="author">
<name><surname>Gahl</surname> <given-names>William A.</given-names></name>
<xref ref-type="aff" rid="aff1"><sup>1</sup></xref>
<xref ref-type="aff" rid="aff2"><sup>2</sup></xref>
</contrib>
<contrib contrib-type="author" corresp="yes">
<name><surname>Sincan</surname> <given-names>Murat</given-names></name>
<xref ref-type="aff" rid="aff1"><sup>1</sup></xref>
<xref ref-type="aff" rid="aff2"><sup>2</sup></xref>
<xref ref-type="corresp" rid="cor1">&#x0002A;</xref>
</contrib>
</contrib-group>
<aff id="aff1"><sup>1</sup><institution>NIH Undiagnosed Diseases Program, Common Fund, Office of the Director, National Institutes of Health (NIH)</institution>, <addr-line>Bethesda, MD</addr-line>, <country>USA</country></aff>
<aff id="aff2"><sup>2</sup><institution>National Human Genome Research Institute, National Institutes of Health (NIH)</institution>, <addr-line>Bethesda, MD</addr-line>, <country>USA</country></aff>
<aff id="aff3"><sup>3</sup><institution>RURO, Inc.</institution>, <addr-line>Frederick, MD</addr-line>, <country>USA</country></aff>
<aff id="aff4"><sup>4</sup><institution>Centre for Computational Medicine Hospital for Sick Children</institution>, <addr-line>Toronto, ON</addr-line>, <country>Canada</country></aff>
<aff id="aff5"><sup>5</sup><institution>Department of Computer Science, University of Toronto</institution>, <addr-line>Toronto, ON</addr-line>, <country>Canada</country></aff>
<aff id="aff6"><sup>6</sup><institution>Department of Medical Informatics and Clinical Epidemiology, Oregon Health &#x00026; Science University</institution>, <addr-line>Portland, OR</addr-line>, <country>USA</country></aff>
<aff id="aff7"><sup>7</sup><institution>Lawrence Berkeley National Laboratory, Division of Environmental Genomics and Systems Biology</institution>, <addr-line>Berkeley, CA</addr-line>, <country>USA</country></aff>
<aff id="aff8"><sup>8</sup><institution>Department of Clinical Pharmacology, Queen Mary University London</institution>, <addr-line>London</addr-line>, <country>UK</country></aff>
<aff id="aff9"><sup>9</sup><institution>Department of Biomedical Informatics and Intelligent Systems, University of Pittsburgh</institution>, <addr-line>Pittsburgh, PA</addr-line>, <country>USA</country></aff>
<aff id="aff10"><sup>10</sup><institution>Agilent Technologies, Inc.</institution>, <addr-line>Santa Clara, CA</addr-line>, <country>USA</country></aff>
<author-notes>
<fn fn-type="edited-by"><p>Edited by: Cristina Sampaio, CHDI Foundation, USA</p></fn>
<fn fn-type="edited-by"><p>Reviewed by: Domenico Criscuolo, Genovax, Italy; Katsura Tsukamoto, Gifu Pharmaceutical University, Japan</p></fn>
<corresp content-type="corresp" id="cor1">&#x0002A;Correspondence: Murat Sincan, <email>sincanm&#x00040;mail.nih.gov</email></corresp>
<fn fn-type="other" id="fn001"><p>Specialty section: This article was submitted to Regulatory Science, a section of the journal Frontiers in Medicine</p></fn>
</author-notes>
<pub-date pub-type="epub">
<day>12</day>
<month>10</month>
<year>2016</year>
</pub-date>
<pub-date pub-type="collection">
<year>2016</year>
</pub-date>
<volume>3</volume>
<elocation-id>39</elocation-id>
<history>
<date date-type="received">
<day>27</day>
<month>06</month>
<year>2016</year>
</date>
<date date-type="accepted">
<day>12</day>
<month>08</month>
<year>2016</year>
</date>
</history>
<permissions>
<copyright-statement>Copyright &#x000A9; 2016 Links, Draper, Lee, Guzman, Valivullah, Maduro, Lebedev, Didenko, Tomlin, Brudno, Girdea, Dumitriu, Haendel, Mungall, Smedley, Hochheiser, Arnold, Coessens, Verhoeven, Bone, Adams, Boerkoel, Gahl and Sincan.</copyright-statement>
<copyright-year>2016</copyright-year>
<copyright-holder>Links, Draper, Lee, Guzman, Valivullah, Maduro, Lebedev, Didenko, Tomlin, Brudno, Girdea, Dumitriu, Haendel, Mungall, Smedley, Hochheiser, Arnold, Coessens, Verhoeven, Bone, Adams, Boerkoel, Gahl and Sincan</copyright-holder>
<license xlink:href="http://creativecommons.org/licenses/by/4.0/"><p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (CC BY). The use, distribution or reproduction in other forums is permitted, provided the original author(s) or licensor are credited and that the original publication in this journal is cited, in accordance with accepted academic practice. No use, distribution or reproduction is permitted which does not comply with these terms.</p></license>
</permissions>
<abstract>
<p>The National Institutes of Health Undiagnosed Diseases Program (NIH UDP) applies translational research systematically to diagnose patients with undiagnosed diseases. The challenge is to implement an information system enabling scalable translational research. The authors hypothesized that similar complex problems are resolvable through process management and the distributed cognition of communities. The team, therefore, built the NIH UDP integrated collaboration system (UDPICS) to form virtual collaborative multidisciplinary research networks or communities. UDPICS supports these communities through integrated process management, ontology-based phenotyping, biospecimen management, cloud-based genomic analysis, and an electronic laboratory notebook. UDPICS provided a mechanism for efficient, transparent, and scalable translational research and thereby addressed many of the complex and diverse research and logistical problems of the NIH UDP. Full definition of the strengths and deficiencies of UDPICS will require formal qualitative and quantitative usability and process improvement measurement.</p>
</abstract>
<kwd-group>
<kwd>translational research</kwd>
<kwd>information system</kwd>
<kwd>ontology-based phenotyping</kwd>
<kwd>process management system</kwd>
<kwd>precision medicine</kwd>
</kwd-group>
<counts>
<fig-count count="4"/>
<table-count count="1"/>
<equation-count count="0"/>
<ref-count count="13"/>
<page-count count="9"/>
<word-count count="4483"/>
</counts>
</article-meta>
</front>
<body>
<sec id="S1" sec-type="introduction">
<title>Introduction</title>
<p>Established in 2008, the National Institutes of Health (NIH) undiagnosed diseases program (UDP) provides answers to patients with conditions that have eluded diagnosis and advances medical knowledge about rare and common diseases (<xref ref-type="bibr" rid="B1">1</xref>). The NIH UDP implements translational research by integrating extensive phenotyping with genetic studies in a systematic fashion.</p>
<p>Translational research is a discipline within biomedical and public health research that aims to improve the health of individuals and the community by &#x0201C;translating&#x0201D; findings into diagnostic tools, therapies, policies, and education. The NIH has made translational research a priority, forming centers of translational research at its institutes and launching the Clinical and translational science award program in 2006. Translational research can be divided into five components<xref ref-type="fn" rid="fn1"><sup>1</sup></xref> (<xref ref-type="bibr" rid="B2">2</xref>). The first component, bedside to bench (T0), is the transfer of the medical physiological understanding of human diseases to the laboratory in a manner enabling application of scientific reductionism. The second component, bench to bedside (T1), is the transfer of new understandings of disease mechanisms gained in the laboratory into the development of new methods for diagnosis, therapy, and prevention of human disease. The third component (T2) builds on the clinical efficacy work conducted in T1 processes and includes phase 3 clinical trials as well as addressing questions about who benefits. The fourth component (T3) is the translation of results from clinical studies into clinical practice and health decision-making. The fifth component (T4) is the extension of T3 translation to education of practitioners, adoption promotion, policy re-evaluation, and outcomes assessment. In this context, the NIH UDP focuses on the first two components of translational research.</p>
<p>The NIH UDP admits approximately 100&#x02013;120 families with different diseases annually and must systematically and scalably assess the evolutionary, developmental, and biochemical homeostases of each patient (<xref ref-type="bibr" rid="B3">3</xref>). Besides the sheer number of diseases, the challenges encountered by the NIH UDP include (1) a focus on individual patients, not cohorts; (2) data collection and aggregation; (3) uniform archiving of biospecimens with metadata; (4) process management; (5) secure data access; (6) generation and presentation of diagnostic hypotheses; (7) a forum for and recording of discussions, conclusions, and decisions; (8) formation of virtual villages of niche experts to focus on each patient; and (9) deposition of appropriate data into public databases.</p>
<p>These NIH UDP throughput and infrastructure requirements define a need for an intelligent scalable process management system. We hypothesized that integration of process management with distributed cognition (<xref ref-type="bibr" rid="B4">4</xref>) addresses the NIH UDP information system requirements. According to the theory of distributed cognition, a cognitive process is delimited by the functional relationships among the elements that participate in it, rather than by the spatial colocation of the elements, and is often characterized by (1) cognitive processes distributed across the members of a social group, (2) cognitive processes coordinating internal and external (material or environmental) structure, and (3) processes distributed through time (<xref ref-type="bibr" rid="B5">5</xref>). In this context, we reviewed some open source and commercial software packages (Table <xref ref-type="table" rid="T1">1</xref>). Our review of open source and commercial software packages, including electronic data capture (EDC) systems, clinical trial management systems (CTMS), collaboration systems, and laboratory information management systems (LIMS), showed that none had all the required features or had the upper level production management needed for translational research as envisioned for the NIH UDP (<xref ref-type="bibr" rid="B6">6</xref>, <xref ref-type="bibr" rid="B7">7</xref>). Similarly, evaluation of specialized systems such as EHR4CR<xref ref-type="fn" rid="fn2"><sup>2</sup></xref> and Taverna<xref ref-type="fn" rid="fn3"><sup>3</sup></xref> highlighted the strengths of each, but also positioned them hierarchically below the production system needed by the NIH UDP, i.e., the system required by the NIH UDP would link out to Taverna for required functions. Consequently, we decided address of the NIH UDP requirements and scalable T0 and T1 translational research required construction of a new system.</p>
<table-wrap position="float" id="T1">
<label>Table 1</label>
<caption><p><bold>Comparison of the NIH UDP requirements to representative existing software</bold>.</p></caption>
<table frame="hsides" rules="groups">
<thead>
<tr>
<th valign="top" align="left" rowspan="2">NIH UDP required features</th>
<th valign="top" align="left" rowspan="2">UDPICS<xref ref-type="table-fn" rid="tfn1"><sup>a</sup></xref></th>
<th valign="top" align="center" colspan="8">Representative alternative software<hr/></th>
</tr><tr>
<th valign="top" align="center">Genologics clarity LIMS<xref ref-type="table-fn" rid="tfn2"><sup>b</sup></xref></th>
<th valign="top" align="center">Alfresco one</th>
<th valign="top" align="center">Atlassian&#x02019;s confluence</th>
<th valign="top" align="center">Progeny suite</th>
<th valign="top" align="center">Exemplar knowledge management<xref ref-type="table-fn" rid="tfn2"><sup>b</sup></xref></th>
<th valign="top" align="center">RedCap</th>
<th valign="top" align="center">OpenClinica</th>
<th valign="top" align="center">TransMed suite</th>
</tr>
</thead>
<tbody>
<tr>
<td align="left" valign="top">Clinical data capture (i.e., phenotypes, demographics, visit information, etc.)</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
</tr>
<tr>
<td align="left" valign="top">Pedigree tools</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x02212;</td>
</tr>
<tr>
<td align="left" valign="top">Research data capture</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
</tr>
<tr>
<td align="left" valign="top">Individual patient-focused platform</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">NR</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">NR</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x02212;</td>
</tr>
<tr>
<td align="left" valign="top">Structured and unstructured data capabilities</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
</tr>
<tr>
<td align="left" valign="top">File upload and management capabilities</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">NR</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
</tr>
<tr>
<td align="left" valign="top">Internal biorepository (includes freezer designations, quality control measures, and metadata capture)</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x02212;</td>
</tr>
<tr>
<td align="left" valign="top">Process management (displays tasks completed, delinquent, and remaining)</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x02212;</td>
</tr>
<tr>
<td align="left" valign="top">Permission management</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">NR</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
</tr>
<tr>
<td align="left" valign="top">Communication tools</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x02212;</td>
</tr>
<tr>
<td align="left" valign="top">Presentation of diagnostic hypotheses to researchers and clinical staff (differential diagnosis)</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x02212;</td>
</tr>
<tr>
<td align="left" valign="top">Easy deposition of quality data into public repositories</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x02212;</td>
</tr>
<tr>
<td align="left" valign="top">APIs for communication with external platforms</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x02212;</td>
</tr>
<tr>
<td align="left" valign="top">Accessible to global collaborators/team members</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
</tr>
<tr>
<td align="left" valign="top">Minimal intrinsic data analysis tools that require maintenance</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x0002B;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x02212;</td>
<td align="center" valign="top">&#x0002B;</td>
</tr>
</tbody>
</table>
<table-wrap-foot>
<fn id="tfn1"><p><italic><sup>a</sup>Undiagnosed diseases program integrated collaboration system</italic>.</p></fn>
<fn id="tfn2"><p><italic><sup>b</sup>No demo available</italic>.</p></fn><p><italic>NR, not reported</italic>.</p></table-wrap-foot></table-wrap>
</sec>
<sec id="S2">
<title>Defining the NIH UDP Translational Research Process Series</title>
<p>The NIH UDP translational research process management is based on the hypothesis that translational research reduces to a series of tasks, outcomes, and decisions that can be captured in a searchable database. The secondary hypothesis is that standardized workflows are sufficiently flexible for testing scientific hypotheses and implementing research and clinical decisions. We designed, implemented, and refined the system as shown in Figure <xref ref-type="fig" rid="F1">1</xref>.</p>
<fig id="F1" position="float">
<label>Figure 1</label>
<caption><p><bold>Graphical representation of the process by which workflows were designed, implemented, and refined within UDPICS</bold>.</p></caption>
<graphic xlink:href="fmed-03-00039-g001.tif"/>
</fig>
<p>The processes and activities in the NIH UDP were categorized into three broad groups: clinical evaluation, agnostic screening for hypothesis generation, and hypothesis testing for elucidation of causation and biological mechanisms. We mapped the processes, tasks, and data elements of the NIH UDP by interviewing personnel (21 clinical staff members &#x02013; 10 physicians, 6 nurse practitioners, and 5 administrative support staff &#x02013; and 18 research staff members &#x02013; laboratory manager, 6 laboratory researchers, 3 laboratory technicians, and 8 bioinformatics support staff) using a standardized questionnaire available as Data Sheet 1 in Supplementary Material. We supplemented interview information with analysis of protocols and operating procedures and observation of individuals executing their tasks.</p>
<p>We used the yEd Graph Editor (yEd Graph Editor, Version 3.10.1. yWorks, Germany) to define &#x0003E;80 workflows [see Data Sheet 2 in Supplementary Material, which lists all the workflows and their properties within UDP integrated collaboration system (UDPICS) in JavaScript object notation (JSON) format] and &#x0003E;2000 discrete data elements (see Data Sheet 3 in Supplementary Material, which lists all the user-defined fields or data elements and their properties in JSON format) in &#x0003E;100 data tables; these spanned patient recruitment through patient data disposition. This process also delineated three permission levels characterizing roles, interactions, and data access (see Table 1 in Supplementary Material, which defines the three permission levels for both workflows and data elements that characterize how users interact with the processes and data within UDPICS).</p>
<p>We built the UDPICS on the Limfinity<sup>&#x000AE;</sup> framework (RURO, Inc., Frederick, MD, USA), a Ruby on Rails web application running on a Linux operating system. The Limfinity<sup>&#x000AE;</sup> framework supports a metadata-based data model and process design as well as common requirements like account and login management, system security, and database searches as well as the use of multiple backend database platforms, including MySQL (Structured Query Language), Oracle, Microsoft SQL, and PostgreSQL. HTML5 (Hyper Text Markup Language), CSS (Cascading Style Sheets), and JavaScript are used to create dynamic and responsive user interfaces.</p>
<p>We implemented UDPICS in five stages over 3&#x02009;years (Figure <xref ref-type="fig" rid="F2">2</xref>A). First, we defined patient recruitment and assessment workflows and transferred historical data. Second, we defined workflows for patient biospecimen processing, archiving, and metadata association and imported additional historical data. Third, we defined workflows for patient-focused research, including data transfer to and from collaborating external laboratories. Fourth, we implemented workflows for generation and characterization of patient-focused animal models. Last, we automated data deposition to repositories, such as the Database of Genotypes and Phenotypes (dbGaP). Upon implementation of each stage, users received individual training and wiki-based documentation. User requests for new features and bug reports were managed <italic>via</italic> a Redmine issue tracking system.<xref ref-type="fn" rid="fn4"><sup>4</sup></xref></p>
<fig id="F2" position="float">
<label>Figure 2</label>
<caption><p><bold>Description of UDPICS architecture and screen shot of PhenoGrid user interface</bold>. <bold>(A)</bold> Graphical display of all the components of UDPICS and the data that are distributed among those components. <bold>(B)</bold> Screenshot of the system showing PhenoGrid comparison of a patient&#x02019;s phenotype data against published human diseases and established mutant <italic>Mus musculus</italic> and <italic>Danio rerio</italic> lines.</p></caption>
<graphic xlink:href="fmed-03-00039-g002.tif"/>
</fig>
</sec>
<sec id="S3">
<title>Scaling the NIH UDP Translational Research Process Series</title>
<p>After establishing workflows spanning NIH UDP research from recruitment through patient data deposition, our challenge was to facilitate the concurrent study of many diseases. We hypothesized that the distributed cognition of niche experts efficiently solves patient problems. Distributed cognition acknowledges that cognitive processes are distributed across environments and social groups, rather than confined to a place, individual, or group (<xref ref-type="bibr" rid="B4">4</xref>). Consequently, cognition is socially and culturally dependent and is embodied in the social group&#x02019;s response to and the use of environment (<xref ref-type="bibr" rid="B4">4</xref>). A historical example of such a social group is a village, and with the advent of social media, village members can be drawn from the global population and assembled virtually. Both, physical and virtual villages require an organized structure, participation to maximize social capital, contribution of particular skills by each member to the community, communication within communal space for exchange of knowledge, and acceptance of the societal hierarchy. Incorporating these principles, UDPICS enabled methodical leveraging of global expertise to scale concurrent study of diseases (Figure <xref ref-type="fig" rid="F2">2</xref>A).</p>
<sec id="S3-1">
<title>Information Sharing and Common Language</title>
<sec id="S3-1-1">
<title>Patient Medical History and Phenotype</title>
<p>Using the integrated web-based phenotyping application, PhenoTips (<xref ref-type="bibr" rid="B8">8</xref>), clinical phenotypes are captured in a standardized nomenclature, human phenotype ontology (HPO) (<xref ref-type="bibr" rid="B9">9</xref>). In contrast to the systematized nomenclature of medicine (SNOMED) or international classification of diseases (ICD), HPO is a formal ontology amenable to application of computerized algorithms for delineation of differential diagnoses and variant rankings (<xref ref-type="bibr" rid="B10">10</xref>, <xref ref-type="bibr" rid="B11">11</xref>). UDPICS produces the HPO-dependent differential diagnosis with the OWLSim algorithm of Phenogrid (<xref ref-type="bibr" rid="B12">12</xref>) (Figure <xref ref-type="fig" rid="F2">2</xref>B) and the algorithm within PhenoTips (<xref ref-type="bibr" rid="B8">8</xref>).</p>
</sec>
<sec id="S3-1-2">
<title>Familial Structure</title>
<p>To generate pedigrees for segregation of disease within families, we incorporated a pedigree drawing tool based on Madeline (<xref ref-type="bibr" rid="B13">13</xref>). Derived PED files are used for downstream genomic studies.</p>
</sec>
<sec id="S3-1-3">
<title>Patient Sample Biorepository</title>
<p>To provide characterized biospecimens to the NIH UDP staff and collaborators, each specimen tracked within UDPICS is annotated with patient metrics, the date and time of collection, current medications, processing duration, and quality measures. UDPICS also tracks specimen storage location, use, and distribution.</p>
</sec>
<sec id="S3-1-4">
<title>Research Data</title>
<p>Undiagnosed diseases program integrated collaboration system contains sharable electronic laboratory notebooks (ELNs) for dissemination of research information. Each notebook is linked to a task, patient, or cohort. Each ELN is divided among the independent research groups working on a problem, and subdivided according to researchers in the group. Each note has three levels of electronic sign-off and locking: the performing researcher generates and signs the experimental note; the supervising principal investigator reviews and signs; and, if appropriate, the NIH UDP research manager reviews and signs.</p>
</sec>
</sec>
<sec id="S3-2">
<title>Communication Tools</title>
<sec id="S3-2-1">
<title>Dashboards</title>
<p>Undiagnosed diseases program integrated collaboration system contains customizable dashboards for displaying information. Examples include the number of patients in each workflow state, age distribution of patients, and current status of patient genomic studies (Figure <xref ref-type="fig" rid="F3">3</xref>A).</p>
<fig id="F3" position="float">
<label>Figure 3</label>
<caption><p><bold>Screen shots of user interfaces for possible dashboards, the Gantt chart, and the to-do list</bold>. <bold>(A)</bold> Screenshot of the system showing two customized dashboards that display specific data on all or a subset of patients in a graphical format. Please note that the figures in this screenshot are examples, not accurate depictions of NIH UDP patient demographics. <bold>(B)</bold> Screenshot of the system showing a Gantt chart displaying tasks and processes associated with a patient and the progress of each. <bold>(C)</bold> Screenshot of a user&#x02019;s to-do list showing the tasks assigned to the user, including the allowed duration and number of days overdue.</p></caption>
<graphic xlink:href="fmed-03-00039-g003.tif"/>
</fig>
</sec>
<sec id="S3-2-2">
<title>Gantt Chart</title>
<p>The Gantt chart provides a status overview on each workflow for a patient or project cohort. It displays progress and duration and serves as an active link to the details of each task (Figure <xref ref-type="fig" rid="F3">3</xref>B).</p>
</sec>
<sec id="S3-2-3">
<title>Lists</title>
<p>Undiagnosed diseases program integrated collaboration system contains two central lists: a to-do list and an activity list. The to-do list displays a user&#x02019;s current tasks and the time for completion (Figure <xref ref-type="fig" rid="F3">3</xref>C). The activity list links to actions that the user chose to be notified of.</p>
</sec>
<sec id="S3-2-4">
<title>Comments</title>
<p>To facilitate discussion and participation, each UDPICS ELN note has a comment bar for supervisors and collaborators to provide feedback (Figure <xref ref-type="fig" rid="F4">4</xref>A). Viewing and commenting on ELN notes is controlled by permissions.</p>
<fig id="F4" position="float">
<label>Figure 4</label>
<caption><p><bold>Screen shots of user interfaces for a page in the electronic laboratory notebook (ELN) and of the Chat tool</bold>. <bold>(A)</bold> Screenshot of a note in a patient&#x02019;s ELN that outlines a hypothetical experiment performed by a researcher. <bold>(B)</bold> Screenshot of a chat regarding a specific patient and the communication between the clinical group and the bioinformatics group.</p></caption>
<graphic xlink:href="fmed-03-00039-g004.tif"/>
</fig>
</sec>
<sec id="S3-2-5">
<title>Chat</title>
<p>To capture discussion and decisions, UDPICS includes a chat feature for communication among internal and external users. Each chat, which can include multiple users, is embedded within a specific patient record or cohort project and can be further linked to a task or note (Figure <xref ref-type="fig" rid="F4">4</xref>B).</p>
</sec>
<sec id="S3-2-6">
<title>Email Notifications</title>
<p>Undiagnosed diseases program integrated collaboration system sends email alerts for user-defined issues of importance. These issues currently include quality control, task completion, and upload of specific reports.</p>
</sec>
</sec>
</sec>
<sec id="S4">
<title>Udpics Improved Operational Efficiency</title>
<p>As a quantitative measure of system usefulness, we assessed time to accomplish three tasks: bulk shipment of samples from the biorepository, submission of data to databases, and exchange of data and reagents with collaborators. For bulk shipment of samples from 100 patients, the time to organize a report on plasma, urine, and cerebrospinal fluid specimens and associated metadata was approximately three workdays prior to UDPICS implementation; it was only 2&#x02009;h after. For data submission to dbGaP, data assembly required extraction from multiple databases and paper files over three to five workdays before implementation of UDPICS and approximately one workday after. Assembly and processing of a material or intellectual transfer agreement application took three to five workdays and, upon approval, one to two workdays for the transfer of the material or data; after UDPICS implementation, data assembly and transfer occurred instantaneously with the only delay being the human approval process. Lastly, sharing of results among NIH personnel and collaborators previously required emails or phone calls over several days, whereas after implementation, UDPICS provided instantaneous knowledge of experiment status.</p>
<p>Anecdotal feedback from users has been positive. They particularly enjoy the improved transparency, accountability, and coherence of information. Clinical staff can now avoid mixed messages to patients, and collaborators have access to a complete data set.</p>
</sec>
<sec id="S5" sec-type="discussion">
<title>Discussion</title>
<p>The NIH UDP developed UDPICS, a web-based information and process management system, to support scalable translational research and, thereby, bridge the gap between the patient bedside and the research bench. Leveraging the principles of distributed cognition, this software solution addressed the needs of the NIH UDP through its focus on individual patients, data aggregation capabilities, archiving of quality biospecimens with associated metadata, efficient linking to other systems for data collection and analysis, robust process management, granular data permissions, transparent presentation of diagnostic hypotheses and decisions to researchers and clinical staff, support for virtual villages of geographically dispersed niche experts, and efficient transfer of data into public databases. Consequently, through the UDPICS ecosystem, the NIH UDP improved operating efficiency, standardized processes and data, and facilitated communication and information sharing among participants.</p>
<p>Although existing software tools had some overlapping functionality, the UDP&#x02019;s needs exceeded the capabilities of existing platforms. Specifically, in addition to collecting research data in electronic format as for a traditional clinical trial, the NIH UDP required a comprehensive collaboration system that supported phenotyping, biospecimen management, native workflow integration, and model organism management. UDPICS, thus, aggregated many functions to achieve essential novel capabilities and validated the hypothesis that distributed cognition enables scalable translational research.</p>
<p>The theory of distributed cognition acknowledges that cognitive processes are distributed across various environments and social groups, rather than confined to one place, individual, or group (<xref ref-type="bibr" rid="B5">5</xref>). Consequently, cognition is socially and culturally dependent and is embodied in the social group&#x02019;s response to and the use of their environment (<xref ref-type="bibr" rid="B4">4</xref>). Historically, humans have solved complex problems through the distribution of cognitive processes among a social group with a variety of skills, e.g., a village. With the advent of social media, village members can be drawn from the global population and assemble virtually. Distributed cognition within a virtual village, therefore, differs little from that of a physical village excepting the absence of physical proximity of the members. Both types of villages require an organized structure, participation to maximize social capital, contribution of particular skills by each member to the community, communication within communal space for exchange of knowledge, and acceptance of the societal hierarchy. By incorporating these principles, UDPICS enabled methodical leveraging of global expertise through formation of virtual villages and, thereby, provided the NIH UDP a platform for scalable translational research.</p>
<p>The implementation challenges faced by the NIH UDP for UDPICS were common to those observed for other enterprise software. Although there were technical challenges of transfer of data from legacy systems, security, and systems integration, the major challenges were organizational and human. UDPICS required a change in organizational culture for all participants within the NIH UDP, and, thus, its implementation required a holistic perspective of the entire process. To achieve this, the implementation required the commitment of senior management; the support of, ongoing communication with, and training of users; and alteration of workflows and interfaces to meet user needs. When users realized that the system contained all the data and processes required for performance of their tasks, they endorsed the system and the NIH UDP realized increased operating efficiency.</p>
<p>Undiagnosed diseases program integrated collaboration system has benefited the NIH UDP and its collaborators by providing a common information source, improving communication; enhancing decision-making and planning capabilities, integrating workflows, maintaining best practices, providing system-wide security, enabling real-time data access, defining regular, consistent data, and increasing data integrity, validity, and reliability. Having achieved the trust of its users, UDPICS became the nexus for the NIH UDP and its collaborators. We propose, therefore, that implementation of UDPICS or an equivalent system incorporating distributed cognition and process management will similarly benefit other programs conducting T0 and T1 translational research.</p>
<p>Undiagnosed diseases program integrated collaboration system supports static database requirements and fully integrates the complex dynamics of the research process. It also provides tools to automate the flow of information and ensure data quality, e.g., user task lists, email notifications, and full scriptability from the administrative interface. Also, the flexibility of the system design and the easy-to-use graphical interface enable the NIH UDP and its collaborators to access the information needed to complete their research projects and provide feedback to each other easily and efficiently.</p>
<p>This initial version of UDPICS requires further development and formal assessment. First, for security reasons UDPICS was developed as independent software; however, it would ideally connect to other databases such as the NIH Clinical Center electronic medical record rather than requiring manual re-entry of EMR data. Second, fully informed translational research requires participation of the patient and/or the caretakers; therefore, future development will include a portal through which patients can (1) provide self-phenotyping, e-consenting, and form completion; (2) access appointment calendars and research data; and (3) participate in the research process.</p>
<p>Full assessment of UDPICS&#x02019;s benefit to the NIH UDP and other translational research programs requires formal qualitative and quantitative measures. Having such measures of its benefits will allow other institutions to judge the potential value of this software infrastructure for their personalized medicine programs.</p>
<p>In summary, the systematic implementation and incorporation of the principles of process management and distributed cognition within UDPICS has enabled scalable translational research through improved efficiency, quality control, and leveraging of global expertise within the NIH UDP. UDPICS has also addressed each of the challenges that the NIH UDP identified for such software. Much work remains, however, to enable patient participation and improve interaction with other biomedical research software systems.</p>
</sec>
<sec id="S6">
<title>Author Contributions</title>
<p>DA, CB, WB, WG, and MS conceived the methodology. AL, DD, EL, JG, ZV, VM, and MS developed the system for use at the NIH UDP. VL, MD, and GT provided the Limfinity<sup>&#x000AE;</sup> platform and support for development needs. MB, MG, and SD provided support for PhenoTips. AA, BC, SV, and WB provided support for Cartagenia Bench Lab NGS. HH and MH performed usability evaluation for UDPICS and PhenoTips. MH, CM, DS, and HH provided cross species phenotype comparison, ontological algorithms, and visualization from the Monarch Initiative. AL, CB, and MS wrote the manuscript. All authors read and approved the final manuscript.</p>
</sec>
<sec id="S7">
<title>Conflict of Interest Statement</title>
<p>VL and MD are stakeholders in RURO, Inc.; the UDPICS infrastructure or framework can be viewed as Translational Science Informatics at <uri xlink:href="https://ruro.com/solutions/featured-translational-science">https://ruro.com/solutions/featured-translational-science</uri>. GT and AL are employed by RURO, Inc. AA, BC, SV, and WB are employed by Agilent Technologies. The remaining authors declare no conflicts of interest. This article does not involve a research protocol requiring approval by the relevant institutional review board or ethics committee.</p>
</sec>
</body>
<back>
<ack>
<p>The authors thank the National Human Genome Research Institute Information Technology staff for their untiring collaboration and advice.</p>
</ack>
<sec id="S8">
<title>Funding</title>
<p>This work was supported in part by the Common Fund, Office of the Director and the Intramural Research Program of the National Human Genome Research Institute (Z01-HG000215-07, Z01-200352-02; NIH, Bethesda, MD, USA). Computational analysis was conducted by the C3G Genomics Innovation Node, funded by Genome Canada through Ontario Genomics and Genome Quebec.</p>
</sec>
<sec id="S9" sec-type="supplementary-material">
<title>Supplementary Material</title>
<p>The Supplementary Material for this article can be found online at <uri xlink:href="http://journal.frontiersin.org/article/10.3389/fmed.2016.00039">http://journal.frontiersin.org/article/10.3389/fmed.2016.00039</uri></p>
<supplementary-material xlink:href="table_1.csv" id="SM1" mimetype="applicationn/csv" xmlns:xlink="http://www.w3.org/1999/xlink"/>
<supplementary-material xlink:href="data_sheet_1.pdf" id="SM2" mimetype="applicationn/pdf" xmlns:xlink="http://www.w3.org/1999/xlink"/>
<supplementary-material xlink:href="data_sheet_2.doc" id="SM3" mimetype="applicationn/doc" xmlns:xlink="http://www.w3.org/1999/xlink"/>
<supplementary-material xlink:href="data_sheet_3.doc" id="SM4" mimetype="applicationn/doc" xmlns:xlink="http://www.w3.org/1999/xlink"/>
</sec>
<ref-list>
<title>References</title>
<ref id="B1"><label>1</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Gahl</surname> <given-names>WA</given-names></name> <name><surname>Markello</surname> <given-names>TC</given-names></name> <name><surname>Toro</surname> <given-names>C</given-names></name> <name><surname>Fajardo</surname> <given-names>KF</given-names></name> <name><surname>Sincan</surname> <given-names>M</given-names></name> <name><surname>Gill</surname> <given-names>F</given-names></name> <etal/></person-group> <article-title>The National Institutes of Health Undiagnosed Diseases Program: insights into rare diseases</article-title>. <source>Genet Med</source> (<year>2012</year>) <volume>14</volume>:<fpage>51</fpage>&#x02013;<lpage>9</lpage>.<pub-id pub-id-type="doi">10.1038/gim.0b013e318232a005</pub-id><pub-id pub-id-type="pmid">22237431</pub-id></citation></ref>
<ref id="B2"><label>2</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Khoury</surname> <given-names>MJ</given-names></name> <name><surname>Gwinn</surname> <given-names>M</given-names></name> <name><surname>Yoon</surname> <given-names>PW</given-names></name> <name><surname>Dowling</surname> <given-names>N</given-names></name> <name><surname>Moore</surname> <given-names>CA</given-names></name> <name><surname>Bradley</surname> <given-names>L</given-names></name></person-group>. <article-title>The continuum of translation research in genomic medicine: how can we accelerate the appropriate integration of human genome discoveries into health care and disease prevention?</article-title> <source>Genet Med</source> (<year>2007</year>) <volume>9</volume>:<fpage>665</fpage>&#x02013;<lpage>74</lpage>.<pub-id pub-id-type="doi">10.1097/GIM.0b013e31815699d0</pub-id><pub-id pub-id-type="pmid">18073579</pub-id></citation></ref>
<ref id="B3"><label>3</label><citation citation-type="book"><person-group person-group-type="author"><name><surname>Child</surname> <given-names>B</given-names></name></person-group>. <source>Genetic Medicine: A Logic of Disease</source>. <publisher-loc>Baltimore</publisher-loc>: <publisher-name>Johns Hopkins University Press</publisher-name> (<year>2003</year>).</citation></ref>
<ref id="B4"><label>4</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Hollan</surname> <given-names>J</given-names></name> <name><surname>Hutchins</surname> <given-names>E</given-names></name> <name><surname>Kirsh</surname> <given-names>D</given-names></name></person-group>. <article-title>Distributed cognition: toward a new foundation for human-computer interaction research</article-title>. <source>ACM Trans Comput Hum Interact</source> (<year>2000</year>) <volume>7</volume>:<fpage>174</fpage>&#x02013;<lpage>96</lpage>.<pub-id pub-id-type="doi">10.1145/353485.353487</pub-id></citation></ref>
<ref id="B5"><label>5</label><citation citation-type="book"><person-group person-group-type="author"><name><surname>Hutchins</surname> <given-names>E</given-names></name></person-group>. <source>Cognition in the Wild</source>. <publisher-loc>Cambridge, MA</publisher-loc>: <publisher-name>The MIT Press</publisher-name> (<year>1995</year>).</citation></ref>
<ref id="B6"><label>6</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Berman</surname> <given-names>AE</given-names></name> <name><surname>Barnett</surname> <given-names>WK</given-names></name> <name><surname>Mooney</surname> <given-names>SD</given-names></name></person-group>. <article-title>Collaborative software for traditional and translational research</article-title>. <source>Hum Genomics</source> (<year>2012</year>) <volume>6</volume>:<fpage>21</fpage>.<pub-id pub-id-type="doi">10.1186/1479-7364-6-21</pub-id><pub-id pub-id-type="pmid">23157911</pub-id></citation></ref>
<ref id="B7"><label>7</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Canuel</surname> <given-names>V</given-names></name> <name><surname>Rance</surname> <given-names>B</given-names></name> <name><surname>Avillach</surname> <given-names>P</given-names></name> <name><surname>Degoulet</surname> <given-names>P</given-names></name> <name><surname>Burgun</surname> <given-names>A</given-names></name></person-group>. <article-title>Translational research platforms integrating clinical and omics data: a review of publicly available solutions</article-title>. <source>Brief Bioinform</source> (<year>2015</year>) <volume>16</volume>:<fpage>280</fpage>&#x02013;<lpage>90</lpage>.<pub-id pub-id-type="doi">10.1093/bib/bbu006</pub-id><pub-id pub-id-type="pmid">24608524</pub-id></citation></ref>
<ref id="B8"><label>8</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Girdea</surname> <given-names>M</given-names></name> <name><surname>Dumitriu</surname> <given-names>S</given-names></name> <name><surname>Fiume</surname> <given-names>M</given-names></name> <name><surname>Bowdin</surname> <given-names>S</given-names></name> <name><surname>Boycott</surname> <given-names>KM</given-names></name> <name><surname>Ch&#x000E9;nier</surname> <given-names>S</given-names></name> <etal/></person-group> <article-title>PhenoTips: patient phenotyping software for clinical and research use</article-title>. <source>Hum Mutat</source> (<year>2013</year>) <volume>34</volume>:<fpage>1057</fpage>&#x02013;<lpage>65</lpage>.<pub-id pub-id-type="doi">10.1002/humu.22347</pub-id><pub-id pub-id-type="pmid">23636887</pub-id></citation></ref>
<ref id="B9"><label>9</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>K&#x000F6;hler</surname> <given-names>S</given-names></name> <name><surname>Doelken</surname> <given-names>SC</given-names></name> <name><surname>Mungall</surname> <given-names>CJ</given-names></name> <name><surname>Bauer</surname> <given-names>S</given-names></name> <name><surname>Firth</surname> <given-names>HV</given-names></name> <name><surname>Bailleul-Forestier</surname> <given-names>I</given-names></name> <etal/></person-group> <article-title>The Human Phenotype Ontology project: linking molecular biology and disease through phenotype data</article-title>. <source>Nucleic Acids Res</source> (<year>2014</year>) <volume>42</volume>:<fpage>D966</fpage>&#x02013;<lpage>74</lpage>.<pub-id pub-id-type="doi">10.1093/nar/gkt1026</pub-id><pub-id pub-id-type="pmid">24217912</pub-id></citation></ref>
<ref id="B10"><label>10</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Robinson</surname> <given-names>PN</given-names></name> <name><surname>Kohler</surname> <given-names>S</given-names></name> <name><surname>Oellrich</surname> <given-names>A</given-names></name></person-group>; <person-group person-group-type="author"><collab>Sanger Mouse Genetics Project</collab> <name><surname>Wang</surname> <given-names>K</given-names></name> <name><surname>Mungall</surname> <given-names>CJ</given-names></name> <etal/></person-group> <article-title>Improved exome prioritization of disease genes through cross-species phenotype comparison</article-title>. <source>Genome Res</source> (<year>2014</year>) <volume>24</volume>:<fpage>340</fpage>&#x02013;<lpage>8</lpage>.<pub-id pub-id-type="doi">10.1101/gr.160325.113</pub-id><pub-id pub-id-type="pmid">24162188</pub-id></citation></ref>
<ref id="B11"><label>11</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Singleton</surname> <given-names>MV</given-names></name> <name><surname>Guthery</surname> <given-names>SL</given-names></name> <name><surname>Voelkerding</surname> <given-names>KV</given-names></name> <name><surname>Chen</surname> <given-names>K</given-names></name> <name><surname>Kennedy</surname> <given-names>B</given-names></name> <name><surname>Margraf</surname> <given-names>RL</given-names></name> <etal/></person-group> <article-title>Phevor combines multiple biomedical ontologies for accurate identification of disease-causing alleles in single individuals and small nuclear families</article-title>. <source>Am J Hum Genet</source> (<year>2014</year>) <volume>94</volume>:<fpage>599</fpage>&#x02013;<lpage>610</lpage>.<pub-id pub-id-type="doi">10.1016/j.ajhg.2014.03.010</pub-id><pub-id pub-id-type="pmid">24702956</pub-id></citation></ref>
<ref id="B12"><label>12</label><citation citation-type="web"><person-group person-group-type="author"><name><surname>Mungall</surname> <given-names>CJ</given-names></name></person-group>. <source>Monarch-Initiative/OWLSim-v3</source>. (<year>2016</year>). Available from: <uri xlink:href="https://github.com/monarch-initiative/owlsim-v3">https://github.com/monarch-initiative/owlsim-v3</uri>.</citation></ref>
<ref id="B13"><label>13</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Trager</surname> <given-names>EH</given-names></name> <name><surname>Khanna</surname> <given-names>R</given-names></name> <name><surname>Marrs</surname> <given-names>A</given-names></name> <name><surname>Siden</surname> <given-names>L</given-names></name> <name><surname>Branham</surname> <given-names>KE</given-names></name> <name><surname>Swaroop</surname> <given-names>A</given-names></name> <etal/></person-group> <article-title>Madeline 2.0 PDE: a new program for local and web-based pedigree drawing</article-title>. <source>Bioinformatics</source> (<year>2007</year>) <volume>23</volume>:<fpage>1854</fpage>&#x02013;<lpage>6</lpage>.<pub-id pub-id-type="doi">10.1093/bioinformatics/btm242</pub-id><pub-id pub-id-type="pmid">17488757</pub-id></citation></ref>
</ref-list>
<fn-group>
<fn id="fn1"><p><sup>1</sup><uri xlink:href="https://casemed.case.edu/ctsc/cores/documents/CTSC_Projects_and_Translational_Research_2010-0111%20Final.pdf">https://casemed.case.edu/ctsc/cores/documents/CTSC_Projects_and_Translational_Research_2010-0111%20Final.pdf</uri></p></fn>
<fn id="fn2"><p><sup>2</sup><uri xlink:href="http://www.ehr4cr.eu">http://www.ehr4cr.eu</uri></p></fn>
<fn id="fn3"><p><sup>3</sup><uri xlink:href="http://www.taverna.org.uk">http://www.taverna.org.uk</uri></p></fn>
<fn id="fn4"><p><sup>4</sup><uri xlink:href="http://www.redmine.org">http://www.redmine.org</uri>, Redmine. 1.3.2.stable</p></fn>
</fn-group>
</back>
</article>
