<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JFR</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Form Res</journal-id>
      <journal-title>JMIR Formative Research</journal-title>
      <issn pub-type="epub">2561-326X</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">v6i6e36914</article-id>
      <article-id pub-id-type="pmid">35737451</article-id>
      <article-id pub-id-type="doi">10.2196/36914</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Original Paper</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Original Paper</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Mobile-Based and Self-Service Tool (iPed) to Collect, Manage, and Visualize Pedigree Data: Development Study</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Mavragani</surname>
            <given-names>Amaryllis</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Zhang</surname>
            <given-names>Qi</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Mohamad</surname>
            <given-names>Ummul H</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Lai</surname>
            <given-names>Chao-Han</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" equal-contrib="yes">
          <name name-style="western">
            <surname>Sun</surname>
            <given-names>Chen</given-names>
          </name>
          <degrees>MA</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-1017-2255</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author" equal-contrib="yes">
          <name name-style="western">
            <surname>Xu</surname>
            <given-names>Jing</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-2249-8316</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author" equal-contrib="yes">
          <name name-style="western">
            <surname>Tao</surname>
            <given-names>Junxian</given-names>
          </name>
          <degrees>MA</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-6992-0716</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Dong</surname>
            <given-names>Yu</given-names>
          </name>
          <degrees>MA</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-4891-0815</ext-link>
        </contrib>
        <contrib id="contrib5" contrib-type="author">
          <name name-style="western">
            <surname>Chen</surname>
            <given-names>Haiyan</given-names>
          </name>
          <degrees>MA</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-1768-6825</ext-link>
        </contrib>
        <contrib id="contrib6" contrib-type="author">
          <name name-style="western">
            <surname>Jia</surname>
            <given-names>Zhe</given-names>
          </name>
          <degrees>MA</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-4440-0236</ext-link>
        </contrib>
        <contrib id="contrib7" contrib-type="author">
          <name name-style="western">
            <surname>Ma</surname>
            <given-names>Yingnan</given-names>
          </name>
          <degrees>MA</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-9975-0044</ext-link>
        </contrib>
        <contrib id="contrib8" contrib-type="author">
          <name name-style="western">
            <surname>Zhang</surname>
            <given-names>Mingming</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-6179-8544</ext-link>
        </contrib>
        <contrib id="contrib9" contrib-type="author">
          <name name-style="western">
            <surname>Wei</surname>
            <given-names>Siyu</given-names>
          </name>
          <degrees>MA</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-7611-4528</ext-link>
        </contrib>
        <contrib id="contrib10" contrib-type="author">
          <name name-style="western">
            <surname>Tang</surname>
            <given-names>Guoping</given-names>
          </name>
          <degrees>MA</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-9378-3547</ext-link>
        </contrib>
        <contrib id="contrib11" contrib-type="author">
          <name name-style="western">
            <surname>Lyu</surname>
            <given-names>Hongchao</given-names>
          </name>
          <degrees>MA</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-7748-7844</ext-link>
        </contrib>
        <contrib id="contrib12" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Jiang</surname>
            <given-names>Yongshuai</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>College of Bioinformatics Science and Technology</institution>
            <institution>Harbin Medical University</institution>
            <addr-line>194 Xuefu Road</addr-line>
            <addr-line>Nangang District</addr-line>
            <addr-line>Harbin, 150081</addr-line>
            <country>China</country>
            <phone>86 451 86620941</phone>
            <email>jiangyongshuai@gmail.com</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-7163-6554</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>College of Bioinformatics Science and Technology</institution>
        <institution>Harbin Medical University</institution>
        <addr-line>Harbin</addr-line>
        <country>China</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>The Fourth Affiliated Hospital</institution>
        <institution>Zhejiang University School of Medicine</institution>
        <addr-line>Zhejiang</addr-line>
        <country>China</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Yongshuai Jiang <email>jiangyongshuai@gmail.com</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <month>6</month>
        <year>2022</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>23</day>
        <month>6</month>
        <year>2022</year>
      </pub-date>
      <volume>6</volume>
      <issue>6</issue>
      <elocation-id>e36914</elocation-id>
      <history>
        <date date-type="received">
          <day>29</day>
          <month>1</month>
          <year>2022</year>
        </date>
        <date date-type="rev-request">
          <day>28</day>
          <month>4</month>
          <year>2022</year>
        </date>
        <date date-type="rev-recd">
          <day>15</day>
          <month>5</month>
          <year>2022</year>
        </date>
        <date date-type="accepted">
          <day>6</day>
          <month>6</month>
          <year>2022</year>
        </date>
      </history>
      <copyright-statement>©Chen Sun, Jing Xu, Junxian Tao, Yu Dong, Haiyan Chen, Zhe Jia, Yingnan Ma, Mingming Zhang, Siyu Wei, Guoping Tang, Hongchao Lyu, Yongshuai Jiang. Originally published in JMIR Formative Research (https://formative.jmir.org), 23.06.2022.</copyright-statement>
      <copyright-year>2022</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR Formative Research, is properly cited. The complete bibliographic information, a link to the original publication on https://formative.jmir.org, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://formative.jmir.org/2022/6/e36914" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Pedigree data (family history) are indispensable for genetics studies and the assessment of individuals' disease susceptibility. With the popularity of genetics testing, the collection of pedigree data is becoming more common. However, it can be time-consuming, laborious, and tedious for clinicians to investigate all pedigree data for each patient. A self-service robot could inquire about patients' family history in place of professional clinicians or genetic counselors.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>The aim of this study was to develop a mobile-based and self-service tool to collect and visualize pedigree data, not only for professionals but also for those who know little about genetics.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>There are 4 main aspects in the iPed construction, including interface building, data processing, data storage, and data visualization. The user interface was built using HTML, JavaScript libraries, and Cascading Style Sheets (version 3; Daniel Eden). Processing of the submitted data is carried out by PHP programming language. MySQL is used to document and manage the pedigree data. PHP calls the R script to accomplish the visualization.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>iPed is freely available to all users through the iPed website. No software is required to be installed, no pedigree files need to be prepared, and no knowledge of genetics or programs is required. The users can easily complete their pedigree data collection and visualization on their own and through a dialogue with iPed. Meanwhile, iPed provides a database that stores all users’ information. Therefore, when the users need to construct new pedigree trees for other genetic traits or modify the pedigree trees that have already been created, unnecessary duplication of operations can be avoided.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>iPed is a mobile-based and self-service tool that could be used by both professionals and nonprofessionals at any time and from any place. It reduces the amount of time required to collect, manage, and visualize pedigree data.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>pedigree</kwd>
        <kwd>pedigree data</kwd>
        <kwd>visualization</kwd>
        <kwd>self-service</kwd>
        <kwd>mobile-based</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>Genetics plays a vital role in all diseases, and therefore, pedigree data are frequently used for clinical diagnosis [<xref ref-type="bibr" rid="ref1">1</xref>]. Over the past few years, more attention has been paid to formulating an efficient model for disease risk prediction. Accurate risk prediction can be of significant help in disease prevention and follow-up strategies [<xref ref-type="bibr" rid="ref2">2</xref>]. There is consensus that family history is an important risk factor in estimating an individual’s susceptibility to diseases, especially hereditary diseases, as it reflects the shared heredity and environment [<xref ref-type="bibr" rid="ref3">3</xref>-<xref ref-type="bibr" rid="ref5">5</xref>]. Numerous studies have applied family history as a risk factor to study the treatment and outcomes of schizophrenia [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref7">7</xref>]; predict cardiovascular disease risk [<xref ref-type="bibr" rid="ref8">8</xref>]; and assess the risk of common cancers such as gastric cancer [<xref ref-type="bibr" rid="ref9">9</xref>], colorectal cancer [<xref ref-type="bibr" rid="ref10">10</xref>], and breast cancer [<xref ref-type="bibr" rid="ref11">11</xref>]. However, pedigree data collection is so limited by familiarity and family communication of patients that it is hard to acquire in a clinical environment [<xref ref-type="bibr" rid="ref12">12</xref>]. In addition, genetic information will change over time as the number of family members and confirmed relatives increases [<xref ref-type="bibr" rid="ref12">12</xref>].</p>
      <p>To address these issues, several web-based tools have been developed to collect and visualize pedigree data. However, it is indispensable for clinicians and genetics counselors to possess professional knowledge in order to use these tools. For example, <italic>Pedigreejs</italic> [<xref ref-type="bibr" rid="ref13">13</xref>] is a pedigree editor based on JavaScript that can produce SVG format images in web browsers [<xref ref-type="bibr" rid="ref14">14</xref>]; however, it is not easy to use for many users who are unfamiliar with JavaScript or specific web programming visualization libraries [<xref ref-type="bibr" rid="ref15">15</xref>]. <italic>Ped_draw</italic> [<xref ref-type="bibr" rid="ref15">15</xref>] can generate an image file as a command line or web tool on the condition that users prepare pedigree data first. <italic>Panogram</italic> [<xref ref-type="bibr" rid="ref16">16</xref>] and <italic>HaploPainter</italic> [<xref ref-type="bibr" rid="ref17">17</xref>] are both software to visualize the pedigree data, while the image file is not free to use.</p>
      <p>We developed iPed, a mobile-based and self-service tool, to collect and visualize pedigree data. Mobile-based technologies are more widespread than web-based technologies, and they can improve the quality of life and reduce health care costs effectively [<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref19">19</xref>]. Collection and visualization of pedigree data is accomplished by responding to some questions posed by iPed. There is no need to prepare an input file or perform any other operation except tapping on some options on the phone. iPed’s intelligent robot significantly reduces the work pressure of the clinician in querying about the patient’s family history. Furthermore, by storing pedigree data in a database, iPed makes it more convenient for users to manage their information.</p>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Overview of Modules</title>
        <p>iPed has 3 main parts: (1) <italic>Your pedigree</italic>, which stores information about family members; (2) <italic>History</italic>, which includes the phenotypic information users have previously entered and the visualizations; (3) <italic>New</italic>, which collects family information about a selected or newly created phenotype through answers to some questions asked by iPed. The interface was built using HTML, which includes a set of tags that unify the format of documents on the network and connect scattered internet resources into a logical whole. JavaScript libraries are used to respond to browser events, including changing information of family members in <italic>Your pedigree</italic>, modifying the phenotype data in <italic>History</italic>, and the dialogue with iPed when creating a new phenotype in <italic>New</italic>. The combination of HTML and JavaScript can complete the interaction between users and iPed. In addition, Cascading Style Sheets (version 3; Daniel Eden), a language that defines style structures such as font, color, and position, is applied to modify web pages.</p>
      </sec>
      <sec>
        <title>Data Processing</title>
        <p>ThinkPHP (version 3.1.3; Chen Liu et al), a fast, compatible, and simple lightweight PHP development framework, is applied for the processing of the submitted data. The user could tap on the options to answer questions asked by iPed. When the dialogue ends, the data collection is finished at the same time. iPed will then convert the data into a specific format for further storage and visualization.</p>
      </sec>
      <sec>
        <title>Data Storage</title>
        <p>All data including family members’ age and phenotypic information are stored in MySQL (version 5.0; Oracle Corporation), the most commonly used relational database management system. PhpMyAdmin (version 3.3.7; The phpMyAdmin Project) is a PHP and web-based MySQL database management tool for managing MySQL databases with a web interface.</p>
      </sec>
      <sec>
        <title>Pedigree Data Visualization</title>
        <p>iPed completes the data visualization by calling the R script in PHP. Kinship2 [<xref ref-type="bibr" rid="ref20">20</xref>], an R package restructured from kinship package [<xref ref-type="bibr" rid="ref21">21</xref>], is used to visualize the pedigree data. Conventionally, squares and circles represent males and females, respectively. If the person has the phenotype, the pattern will be colored black; otherwise, it will be white. The connecting lines between patterns indicate genetic relationships.</p>
      </sec>
      <sec>
        <title>Ethics Consideration</title>
        <p>This study did not require ethics approval as it did not involve any human subjects and the mobile-based tool was developed for visualization of pedigree data for all users.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Pedigree and First Phenotype Data Collection</title>
        <p>iPed is a mobile-based, web-based, self-service tool for collecting and visualizing pedigree data on genetic phenotypes. A first-time user needs to register to save personal information for the next use. After a successful login, the user can select a phenotype of interest (<xref rid="figure1" ref-type="fig">Figure 1</xref>B), including disease phenotypes (eg, lung cancer, breast cancer, and rheumatoid arthritis), common phenotypes (eg, double eyelid, tall, and right-handed), and entertaining phenotypes (eg, singing well, high income, or social phobias). The user can also create a new phenotype and complete the family data collection for the created phenotype through an interactive dialogue with an intelligent robot (<xref rid="figure1" ref-type="fig">Figure 1</xref>C). The robot will ask some questions about the user’s age, whether the user has the phenotype, whether the user has a spouse or child, and whether the user’s relatives and their families have the phenotype (<xref rid="figure2" ref-type="fig">Figure 2</xref>).</p>
        <p>After the first use, iPed will save the user’s family information in <italic>Your</italic> <italic>Pedigree</italic> (<xref rid="figure1" ref-type="fig">Figure 1</xref>F), including family members and their ages. This makes it convenient to directly collect pedigree data about the user’s family members when the user describes a new genetic phenotype.</p>
        <p>When the users log in again, they can check their family information (<italic>Your pedigree</italic>), view the genetic phenotypic information (eg, the phenotype name, such as <italic>dimple</italic>), and the corresponding visualization (<italic>Visualize the pedigree</italic>). They can also select a new phenotype on the home page (<italic>New</italic>) to visualize the information (<xref rid="figure1" ref-type="fig">Figure 1</xref>A).</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>Main pages when the user logs back into iPed the next time. (A) The home page; (B) alternative phenotypes on iPed when the user taps on <italic>New</italic>; (C) the dialogue between the user and the robot when the user needs to define a new phenotype; (D) visualization of the genetic phenotypic data; (E) the genetic phenotype the user has entered, including the family members and their phenotypic information; (F) <italic>Your pedigree</italic> shows the family members and their ages.</p>
          </caption>
          <graphic xlink:href="formative_v6i6e36914_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <fig id="figure2" position="float">
          <label>Figure 2</label>
          <caption>
            <p>The flow path of the questions asked by the intelligent robot when the user logs into iPed for the first time.</p>
          </caption>
          <graphic xlink:href="formative_v6i6e36914_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Phenotype Data Visualization and Modification</title>
        <sec>
          <title>Phenotype Data Visualization</title>
          <p>Phenotype data visualization is accessible by tapping on <italic>Visualize the pedigree</italic>, and the user can see the visualized phenotypic information on the result page (<xref rid="figure1" ref-type="fig">Figure 1</xref>D). When the users find information that needs to be changed, they can tap on <italic>Visualize the phenotype once more</italic> to complete the modification.</p>
        </sec>
        <sec>
          <title>Phenotype Data Modification</title>
          <p>When information needs to be modified, the user can just click on the name of phenotype such as <italic>dimple</italic> (<xref rid="figure1" ref-type="fig">Figure 1</xref>A) or tap on <italic>Visualize the phenotype once more</italic> on the result page (<xref rid="figure1" ref-type="fig">Figure 1</xref>D) and change the targeted family member’s status on the page showing phenotypic information (<xref rid="figure1" ref-type="fig">Figure 1</xref>E). If the family member’s status is changed, tapping on <italic>Modify pedigree</italic> (<xref rid="figure1" ref-type="fig">Figure 1</xref>E) will direct the user to <italic>Your pedigree</italic>. <italic>Your</italic> <italic>Pedigree</italic> provides options to add or delete family members and modify their ages. It should be noted that the already existing family members cannot be added again. After modifying the family member’s information, the user can return to change the member’s phenotypic information. After finishing all the modifications, the user can visualize the phenotypic information afresh.</p>
        </sec>
      </sec>
      <sec>
        <title>New Phenotype Data Adding</title>
        <p>If users intend to visualize new phenotypic data, they could tap on <italic>New</italic> on the home page, select an unfulfilled phenotype that they are interested in (<xref rid="figure1" ref-type="fig">Figure 1</xref>B), and complete the dialogue with the robot. The robot will simply ask whether the members added by the user have this phenotype. Afterward, it will generate the corresponding visualization.</p>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>Pedigree data are crucial in genetics studies and disease diagnosis, development, and prognosis. There are thousands of studies that have applied family history as a risk factor. However, this information is not easy to collect and manage. iPed provides a self-service tool for users to collect and visualize this information. With iPed, users do not need to prepare an input file first or learn any knowledge about genetics. They can visualize their pedigree data just by answering the intelligent robot’s questions, without any professional operations. At the same time, all the information submitted by users is stored in a database, so that visualizing a new phenotype or modifying previously entered data is more convenient.</p>
      </sec>
      <sec>
        <title>Comparison With Prior Work</title>
        <p>Recently, some web-based tools for collecting and visualizing pedigree data have been developed. There are some limitations to these existing tools; if the user would like to use these tools, they have to gain some knowledge first. For example, <italic>Pedigreejs</italic> [<xref ref-type="bibr" rid="ref13">13</xref>] is a web-based tool that is difficult to use for those who have little knowledge about JavaScript or specific web programming visualization libraries. <italic>HaploForge</italic> [<xref ref-type="bibr" rid="ref22">22</xref>] is another web application that is hard to use, as the meaning of the different symbols and connecting lines can be confusing for users who do not know about genetics; it is always difficult to know how to proceed to the next operation. <italic>Ped_draw</italic> [<xref ref-type="bibr" rid="ref23">23</xref>] can be used only when users prepare pedigree data first. In addition, many tools such as <italic>panogram</italic> [<xref ref-type="bibr" rid="ref16">16</xref>] and <italic>HaploPainter</italic> [<xref ref-type="bibr" rid="ref17">17</xref>] are not free to use for all users. There are also some tools such as <italic>PediDraw</italic> [<xref ref-type="bibr" rid="ref24">24</xref>] and <italic>Madeline 2.0 PDE</italic> [<xref ref-type="bibr" rid="ref25">25</xref>] that were first released over a decade ago, and access to them is presently unstable or even disabled.</p>
        <p>iPed is a mobile-based and self-service tool that can be used easily in place of software needing installation or web-based tools requiring professional knowledge. Collecting pedigree data is easier, as users only need to answer some questions asked by an intelligent robot and tap on some options. It is a simple and efficient tool for both professional and nonprofessional uses. Meanwhile, iPed provides a database to save all information submitted by users, providing greater convenience for subsequent uses. Additionally, iPed is free for everyone to use.</p>
      </sec>
      <sec>
        <title>Strengths and Limitations</title>
        <p>iPed enables the collection of pedigree data through dialogue with an intelligent robot. As the pedigree data are usually complex, the possibility of missing some information is high, and that can lead to wrong conclusions. The dialogue with iPed helps the user recall their pedigree data more comprehensively. Questions asked by iPed include the following: “How many uncles do you have?” “Is your uncle married?” “How many children does your uncle have?” and “Do your uncle’s children have the phenotype?” Without any other operations, the users can answer the questions just by tapping on the “yes,” “no,” or “unknown” options, and the pedigree data collection is accomplished when the dialogue ends. The pedigree data visualization will then generate automatically. Moreover, considering that there are associations between diverse phenotypes, iPed will save all the information submitted by the users after the first use. Therefore, it is easy to look over the phenotypes that have been entered before. iPed offers substantial help in clinical diagnosis of complications and genetics studies about the correlations of different phenotypes.</p>
        <p>Although iPed provides many novel functions, there are still some limitations. First, in the visualization of pedigree data, the color black traditionally indicates a person with the phenotype and white indicates one without the phenotype. iPed will offer a more powerful function if more colors are introduced, indicating different meanings. Second, users should select a phenotype before the pedigree data collection, so that the resultant picture shows information for the specified phenotype. How to present multiple phenotypes in a single picture will be considered in the future. We will constantly update and upgrade iPed to offer a significantly better user experience.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>iPed was developed as a mobile-based and self-service tool to collect and visualize pedigree data [<xref ref-type="bibr" rid="ref26">26</xref>]; it can be used by professional researchers, clinicians, and those who possess little relevant knowledge. iPed shortens the amount of time patients spend in the hospital and improves the efficiency of the clinicians. With iPed, collection, management, and use of pedigree data will no longer be difficult.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group/>
    <ack>
      <p>This work is funded by National Natural Science Foundation of China (grants 31970651, and 92046018). It was also supported by the Tianyuan Fund for Mathematics of the National Natural Science Foundation of China (grant 12026414), and Basic Public Welfare Research Project of Zhejiang Province (grant LGF20C060001).</p>
    </ack>
    <fn-group>
      <fn fn-type="con">
        <p>YJ conceptualized and designed the work. CS, JX, JT, HC, and YD performed research and drafted and modified the manuscript. All authors contributed to discussing and revising the manuscript.</p>
      </fn>
      <fn fn-type="conflict">
        <p>None declared.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Jackson</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Marks</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>May</surname>
              <given-names>GHW</given-names>
            </name>
            <name name-style="western">
              <surname>Wilson</surname>
              <given-names>JB</given-names>
            </name>
          </person-group>
          <article-title>The genetic basis of disease</article-title>
          <source>Essays Biochem (2018)</source>
          <year>2018</year>
          <month>12</month>
          <volume>62</volume>
          <issue>5</issue>
          <fpage>643</fpage>
          <lpage>723</lpage>
          <pub-id pub-id-type="doi">10.1042/ebc20170053</pub-id>
          <pub-id pub-id-type="medline">30509934</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Jostins</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Barrett</surname>
              <given-names>JC</given-names>
            </name>
          </person-group>
          <article-title>Genetic risk prediction in complex disease</article-title>
          <source>Hum Mol Genet</source>
          <year>2011</year>
          <month>10</month>
          <day>15</day>
          <volume>20</volume>
          <issue>R2</issue>
          <fpage>R182</fpage>
          <lpage>8</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/21873261"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/hmg/ddr378</pub-id>
          <pub-id pub-id-type="medline">21873261</pub-id>
          <pub-id pub-id-type="pii">ddr378</pub-id>
          <pub-id pub-id-type="pmcid">PMC3179379</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ofori</surname>
              <given-names>SN</given-names>
            </name>
            <name name-style="western">
              <surname>Odia</surname>
              <given-names>OJ</given-names>
            </name>
          </person-group>
          <article-title>Risk assessment in the prevention of cardiovascular disease in low-resource settings</article-title>
          <source>Indian Heart J</source>
          <year>2016</year>
          <month>05</month>
          <volume>68</volume>
          <issue>3</issue>
          <fpage>391</fpage>
          <lpage>8</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S0019-4832(15)00237-0"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.ihj.2015.07.004</pub-id>
          <pub-id pub-id-type="medline">27316504</pub-id>
          <pub-id pub-id-type="pii">S0019-4832(15)00237-0</pub-id>
          <pub-id pub-id-type="pmcid">PMC4911434</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Jacobs</surname>
              <given-names>MF</given-names>
            </name>
          </person-group>
          <article-title>Predicting cancer risk based on family history</article-title>
          <source>Elife</source>
          <year>2021</year>
          <month>09</month>
          <day>29</day>
          <volume>10</volume>
          <fpage>10</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.7554/eLife.73380"/>
          </comment>
          <pub-id pub-id-type="doi">10.7554/eLife.73380</pub-id>
          <pub-id pub-id-type="medline">34586069</pub-id>
          <pub-id pub-id-type="pii">73380</pub-id>
          <pub-id pub-id-type="pmcid">PMC8480971</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Igo</surname>
              <given-names>RP</given-names>
            </name>
            <name name-style="western">
              <surname>Kinzy</surname>
              <given-names>TG</given-names>
            </name>
            <name name-style="western">
              <surname>Cooke Bailey</surname>
              <given-names>JN</given-names>
            </name>
          </person-group>
          <article-title>Genetic risk scores</article-title>
          <source>Curr Protoc Hum Genet</source>
          <year>2019</year>
          <month>12</month>
          <day>25</day>
          <volume>104</volume>
          <issue>1</issue>
          <fpage>e95</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/31765077"/>
          </comment>
          <pub-id pub-id-type="doi">10.1002/cphg.95</pub-id>
          <pub-id pub-id-type="medline">31765077</pub-id>
          <pub-id pub-id-type="pmcid">PMC6941594</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mortensen</surname>
              <given-names>PB</given-names>
            </name>
            <name name-style="western">
              <surname>Pedersen</surname>
              <given-names>MG</given-names>
            </name>
            <name name-style="western">
              <surname>Pedersen</surname>
              <given-names>CB</given-names>
            </name>
          </person-group>
          <article-title>Psychiatric family history and schizophrenia risk in Denmark: which mental disorders are relevant?</article-title>
          <source>Psychol Med</source>
          <year>2009</year>
          <month>07</month>
          <day>17</day>
          <volume>40</volume>
          <issue>2</issue>
          <fpage>201</fpage>
          <lpage>210</lpage>
          <pub-id pub-id-type="doi">10.1017/s0033291709990419</pub-id>
          <pub-id pub-id-type="medline">19607751</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Käkelä</surname>
              <given-names>Juha</given-names>
            </name>
            <name name-style="western">
              <surname>Marttila</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Keskinen</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Veijola</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Isohanni</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Koivumaa-Honkanen</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Haapea</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Jääskeläinen</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Miettunen</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Association between family history of psychiatric disorders and long-term outcome in schizophrenia - the Northern Finland birth cohort 1966 study</article-title>
          <source>Psychiatry Res</source>
          <year>2017</year>
          <month>03</month>
          <volume>249</volume>
          <fpage>16</fpage>
          <lpage>22</lpage>
          <pub-id pub-id-type="doi">10.1016/j.psychres.2016.12.040</pub-id>
          <pub-id pub-id-type="medline">28063393</pub-id>
          <pub-id pub-id-type="pii">S0165-1781(16)30756-9</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mehta</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Virani</surname>
              <given-names>SS</given-names>
            </name>
            <name name-style="western">
              <surname>Ayers</surname>
              <given-names>CR</given-names>
            </name>
            <name name-style="western">
              <surname>Sun</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Hoogeveen</surname>
              <given-names>RC</given-names>
            </name>
            <name name-style="western">
              <surname>Rohatgi</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Berry</surname>
              <given-names>JD</given-names>
            </name>
            <name name-style="western">
              <surname>Joshi</surname>
              <given-names>PH</given-names>
            </name>
            <name name-style="western">
              <surname>Ballantyne</surname>
              <given-names>CM</given-names>
            </name>
            <name name-style="western">
              <surname>Khera</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Lipoprotein(a) and family history predict cardiovascular disease risk</article-title>
          <source>J Am Coll Cardiol</source>
          <year>2020</year>
          <month>08</month>
          <day>18</day>
          <volume>76</volume>
          <issue>7</issue>
          <fpage>781</fpage>
          <lpage>793</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S0735-1097(20)35737-5"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jacc.2020.06.040</pub-id>
          <pub-id pub-id-type="medline">32792075</pub-id>
          <pub-id pub-id-type="pii">S0735-1097(20)35737-5</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Yuan</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>He</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Family history of gastric cancer and helicobacter pylori treatment</article-title>
          <source>N Engl J Med</source>
          <year>2020</year>
          <month>05</month>
          <day>28</day>
          <volume>382</volume>
          <issue>22</issue>
          <fpage>2171</fpage>
          <lpage>2172</lpage>
          <pub-id pub-id-type="doi">10.1056/NEJMc2003542</pub-id>
          <pub-id pub-id-type="medline">32459942</pub-id>
          <pub-id pub-id-type="pii">10.1056/NEJMc2003542#sa4</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Pesola</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Eloranta</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Martling</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Saraste</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Smedby</surname>
              <given-names>KE</given-names>
            </name>
          </person-group>
          <article-title>Family history of colorectal cancer and survival: a Swedish population-based study</article-title>
          <source>J Intern Med</source>
          <year>2020</year>
          <month>06</month>
          <day>03</day>
          <volume>287</volume>
          <issue>6</issue>
          <fpage>723</fpage>
          <lpage>733</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1111/joim.13036"/>
          </comment>
          <pub-id pub-id-type="doi">10.1111/joim.13036</pub-id>
          <pub-id pub-id-type="medline">32012369</pub-id>
          <pub-id pub-id-type="pmcid">PMC7318575</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Brewer</surname>
              <given-names>HR</given-names>
            </name>
            <name name-style="western">
              <surname>Jones</surname>
              <given-names>ME</given-names>
            </name>
            <name name-style="western">
              <surname>Schoemaker</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Ashworth</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Swerdlow</surname>
              <given-names>AJ</given-names>
            </name>
          </person-group>
          <article-title>Family history and risk of breast cancer: an analysis accounting for family structure</article-title>
          <source>Breast Cancer Res Treat</source>
          <year>2017</year>
          <month>08</month>
          <day>3</day>
          <volume>165</volume>
          <issue>1</issue>
          <fpage>193</fpage>
          <lpage>200</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/28578505"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s10549-017-4325-2</pub-id>
          <pub-id pub-id-type="medline">28578505</pub-id>
          <pub-id pub-id-type="pii">10.1007/s10549-017-4325-2</pub-id>
          <pub-id pub-id-type="pmcid">PMC5511313</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Helfand</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>A comparison of genetic risk score with family history for estimating prostate cancer risk</article-title>
          <source>Asian J Androl</source>
          <year>2016</year>
          <volume>18</volume>
          <issue>4</issue>
          <fpage>515</fpage>
          <pub-id pub-id-type="doi">10.4103/1008-682x.177122</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="web">
          <source>Pedigreejs</source>
          <access-date>2022-06-10</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ccge-boadicea.github.io/pedigreejs/">https://ccge-boadicea.github.io/pedigreejs/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Carver</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Cunningham</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Babb de Villiers</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Hartley</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Tischkowitz</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Walter</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Easton</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Antoniou</surname>
              <given-names>AC</given-names>
            </name>
          </person-group>
          <article-title>pedigreejs: a web-based graphical pedigree editor</article-title>
          <source>Bioinformatics</source>
          <year>2018</year>
          <month>03</month>
          <day>15</day>
          <volume>34</volume>
          <issue>6</issue>
          <fpage>1069</fpage>
          <lpage>1071</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/29095980"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/bioinformatics/btx705</pub-id>
          <pub-id pub-id-type="medline">29095980</pub-id>
          <pub-id pub-id-type="pii">4583632</pub-id>
          <pub-id pub-id-type="pmcid">PMC5860312</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Velinder</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Marth</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>ped_draw: pedigree drawing with ease</article-title>
          <source>BMC Bioinformatics</source>
          <year>2020</year>
          <month>12</month>
          <day>09</day>
          <volume>21</volume>
          <issue>1</issue>
          <fpage>569</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcbioinformatics.biomedcentral.com/articles/10.1186/s12859-020-03917-4"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12859-020-03917-4</pub-id>
          <pub-id pub-id-type="medline">33297934</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12859-020-03917-4</pub-id>
          <pub-id pub-id-type="pmcid">PMC7727153</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="web">
          <source>panogram</source>
          <access-date>2022-06-10</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://panogram.github.io/panogram/">http://panogram.github.io/panogram/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="web">
          <article-title>HaploPainter</article-title>
          <source>SourceForge</source>
          <access-date>2022-06-10</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://sourceforge.net/projects/haplopainter/">https://sourceforge.net/projects/haplopainter/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ayatollahi</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Ghalandar Abadi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Hemmat</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Web and mobile-based technologies for monitoring high-risk pregnancies</article-title>
          <source>BMJ Health Care Inform</source>
          <year>2019</year>
          <month>06</month>
          <day>14</day>
          <volume>26</volume>
          <issue>1</issue>
          <fpage>e000025</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://informatics.bmj.com/lookup/pmidlookup?view=long&#38;pmid=31201201"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmjhci-2019-000025</pub-id>
          <pub-id pub-id-type="medline">31201201</pub-id>
          <pub-id pub-id-type="pii">bmjhci-2019-000025</pub-id>
          <pub-id pub-id-type="pmcid">PMC7062320</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Emami</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Asadi</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Garavand</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>The features of mobile-based software in self-management of patients with asthma: a review article</article-title>
          <source>Tanaffos</source>
          <year>2020</year>
          <month>01</month>
          <volume>19</volume>
          <issue>1</issue>
          <fpage>10</fpage>
          <lpage>19</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/33101427"/>
          </comment>
          <pub-id pub-id-type="medline">33101427</pub-id>
          <pub-id pub-id-type="pii">tanaffos-19-10</pub-id>
          <pub-id pub-id-type="pmcid">PMC7569493</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sinnwell</surname>
              <given-names>JP</given-names>
            </name>
            <name name-style="western">
              <surname>Therneau</surname>
              <given-names>TM</given-names>
            </name>
            <name name-style="western">
              <surname>Schaid</surname>
              <given-names>DJ</given-names>
            </name>
          </person-group>
          <article-title>The kinship2 R package for pedigree data</article-title>
          <source>Hum Hered</source>
          <year>2014</year>
          <month>7</month>
          <day>29</day>
          <volume>78</volume>
          <issue>2</issue>
          <fpage>91</fpage>
          <lpage>3</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.karger.com?DOI=10.1159/000363105"/>
          </comment>
          <pub-id pub-id-type="doi">10.1159/000363105</pub-id>
          <pub-id pub-id-type="medline">25074474</pub-id>
          <pub-id pub-id-type="pii">000363105</pub-id>
          <pub-id pub-id-type="pmcid">PMC4154601</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zhao</surname>
              <given-names>JH</given-names>
            </name>
          </person-group>
          <article-title>Pedigree-drawing with R and graphviz</article-title>
          <source>Bioinformatics</source>
          <year>2006</year>
          <month>04</month>
          <day>15</day>
          <volume>22</volume>
          <issue>8</issue>
          <fpage>1013</fpage>
          <lpage>4</lpage>
          <pub-id pub-id-type="doi">10.1093/bioinformatics/btl058</pub-id>
          <pub-id pub-id-type="medline">16488908</pub-id>
          <pub-id pub-id-type="pii">btl058</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="web">
          <source>HaploForge</source>
          <access-date>2022-06-10</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://github.com/mtekman/HaploForge">https://github.com/mtekman/HaploForge</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="web">
          <source>Ped_draw</source>
          <access-date>2022-06-10</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://peddraw.github.io">https://peddraw.github.io</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>He</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <article-title>PediDraw: a web-based tool for drawing a pedigree in genetic counseling</article-title>
          <source>BMC Med Genet</source>
          <year>2007</year>
          <month>06</month>
          <day>08</day>
          <volume>8</volume>
          <issue>1</issue>
          <fpage>31</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedgenet.biomedcentral.com/articles/10.1186/1471-2350-8-31"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/1471-2350-8-31</pub-id>
          <pub-id pub-id-type="medline">17555606</pub-id>
          <pub-id pub-id-type="pii">1471-2350-8-31</pub-id>
          <pub-id pub-id-type="pmcid">PMC1904184</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Trager</surname>
              <given-names>EH</given-names>
            </name>
            <name name-style="western">
              <surname>Khanna</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Marrs</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Siden</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Branham</surname>
              <given-names>KE</given-names>
            </name>
            <name name-style="western">
              <surname>Swaroop</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Richards</surname>
              <given-names>JE</given-names>
            </name>
          </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>
          <month>07</month>
          <day>15</day>
          <volume>23</volume>
          <issue>14</issue>
          <fpage>1854</fpage>
          <lpage>6</lpage>
          <pub-id pub-id-type="doi">10.1093/bioinformatics/btm242</pub-id>
          <pub-id pub-id-type="medline">17488757</pub-id>
          <pub-id pub-id-type="pii">btm242</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="web">
          <source>iPed</source>
          <access-date>2022-06-10</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.onethird-lab.com/iPed/">http://www.onethird-lab.com/iPed/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
