<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "journalpublishing.dtd"><article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" dtd-version="2.0" xml:lang="en" article-type="research-article"><front><journal-meta><journal-id journal-id-type="nlm-ta">JMIR Med Inform</journal-id><journal-id journal-id-type="publisher-id">medinform</journal-id><journal-id journal-id-type="index">7</journal-id><journal-title>JMIR Medical Informatics</journal-title><abbrev-journal-title>JMIR Med Inform</abbrev-journal-title><issn pub-type="epub">2291-9694</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">v14i1e78080</article-id><article-id pub-id-type="doi">10.2196/78080</article-id><article-categories><subj-group subj-group-type="heading"><subject>Original Paper</subject></subj-group></article-categories><title-group><article-title>Construction of an AI-Assisted Pedigree Mapping System for Hereditary Gynecological Tumors: Algorithm Development and Pilot Validation Study</article-title></title-group><contrib-group><contrib contrib-type="author" equal-contrib="yes"><name name-style="western"><surname>Xu</surname><given-names>Jing</given-names></name><degrees>MD</degrees><xref ref-type="aff" rid="aff1">1</xref><xref ref-type="fn" rid="equal-contrib1">*</xref></contrib><contrib contrib-type="author" equal-contrib="yes"><name name-style="western"><surname>Wang</surname><given-names>Yajun</given-names></name><degrees>MS</degrees><xref ref-type="aff" rid="aff2">2</xref><xref ref-type="fn" rid="equal-contrib1">*</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Wang</surname><given-names>Hui</given-names></name><degrees>MS</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Sun</surname><given-names>Jiayang</given-names></name><degrees>MS</degrees><xref ref-type="aff" rid="aff2">2</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Lei</surname><given-names>Xingang</given-names></name><degrees>MS</degrees><xref ref-type="aff" rid="aff2">2</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Xu</surname><given-names>Congjian</given-names></name><degrees>MD</degrees><xref ref-type="aff" rid="aff3">3</xref></contrib><contrib contrib-type="author" corresp="yes"><name name-style="western"><surname>Kang</surname><given-names>Yu</given-names></name><degrees>MD</degrees><xref ref-type="aff" rid="aff1">1</xref><xref ref-type="aff" rid="aff4">4</xref></contrib></contrib-group><aff id="aff1"><institution>Obstetrics and Gynecology Hospital of Fudan University</institution><addr-line>Fangxie Road, No. 419</addr-line><addr-line>Shanghai, China</addr-line><country>China</country></aff><aff id="aff2"><institution>Shanghai Taihealth Intelligent Technology Co, Ltd</institution><addr-line>Shanghai, China</addr-line><country>China</country></aff><aff id="aff3"><institution>Westlake University</institution><addr-line>Hangzhou</addr-line><country>China</country></aff><aff id="aff4"><institution>Department of Gynecology, Affiliated Hangzhou First People's Hospital, School of Medicine, Westlake University</institution><addr-line>Hangzhou</addr-line><country>China</country></aff><contrib-group><contrib contrib-type="editor"><name name-style="western"><surname>Benis</surname><given-names>Arriel</given-names></name></contrib></contrib-group><contrib-group><contrib contrib-type="reviewer"><name name-style="western"><surname>Ospina</surname><given-names>Juan</given-names></name></contrib><contrib contrib-type="reviewer"><name name-style="western"><surname>Godino</surname><given-names>Lea</given-names></name></contrib><contrib contrib-type="reviewer"><name name-style="western"><surname>Ranganath</surname><given-names>Pooja Kadaba</given-names></name></contrib></contrib-group><author-notes><corresp>Correspondence to Yu Kang, MD, Obstetrics and Gynecology Hospital of Fudan University, Fangxie Road, No. 419, Shanghai, China, China, 86 33189900; <email>yukang@fudan.edu.cn</email></corresp><fn fn-type="equal" id="equal-contrib1"><label>*</label><p>these authors contributed equally</p></fn></author-notes><pub-date pub-type="collection"><year>2026</year></pub-date><pub-date pub-type="epub"><day>15</day><month>10</month><year>2026</year></pub-date><volume>14</volume><elocation-id>e78080</elocation-id><history><date date-type="received"><day>24</day><month>01</month><year>2026</year></date><date date-type="rev-recd"><day>16</day><month>08</month><year>2026</year></date><date date-type="accepted"><day>09</day><month>09</month><year>2026</year></date></history><copyright-statement>&#x00A9; Jing Xu, Yajun Wang, Hui Wang, Jiayang Sun, Xingang Lei, Congjian Xu, Yu Kang. Originally published in JMIR Medical Informatics (<ext-link ext-link-type="uri" xlink:href="https://medinform.jmir.org">https://medinform.jmir.org</ext-link>), 15.10.2026. </copyright-statement><copyright-year>2026</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 (<ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">https://creativecommons.org/licenses/by/4.0/</ext-link>), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR Medical Informatics, is properly cited. The complete bibliographic information, a link to the original publication on <ext-link ext-link-type="uri" xlink:href="https://medinform.jmir.org/">https://medinform.jmir.org/</ext-link>, as well as this copyright and license information must be included.</p></license><self-uri xlink:type="simple" xlink:href="https://medinform.jmir.org/2026/1/e78080"/><abstract><sec><title>Background</title><p>Pedigree mapping serves as the first step in genetic counseling. Traditional methods relying on manual pedigree drawing and information collection are inefficient and prone to errors.</p></sec><sec><title>Objective</title><p>This study aimed to design an intelligent pedigree mapping system based on a specialized model, intended to automate family history collection and standardized pedigree map generation through conversational interaction, thereby enhancing the clinical efficiency of genetic counseling.</p></sec><sec sec-type="methods"><title>Methods</title><p>This study adopted a participatory design and iterative development approach. We formed an interdisciplinary team comprising gynecologic oncologists, genetic counselors, AI engineers, and patient representatives. The system was built around a proprietary, specialized large language model for gynecologic oncology, featuring a microservices architecture that included pedigree data collection. Through 4 iterative cycles, we integrated specialized knowledge bases using retrieval-augmented generation technology and applied a novel graph-based kinship inference and validation module. The system&#x2019;s performance was comprehensively evaluated based on the accuracy of pedigree map generation and user feedback on usability.</p></sec><sec sec-type="results"><title>Results</title><p>We significantly improved system performance by optimizing dialogue strategies, expanding the knowledge base, and applying self-developed algorithms to improve data extraction accuracy. The initial database of the system defined 100 core information nodes and matched approximately 800 user expression examples, while the final pilot version of the database was expanded to 245 core information nodes and 2256 user expression examples. Although the AI function was limited in the early stage, the final version of the system demonstrated outstanding accuracy in generating genealogy nodes and relationships. Test users generally gave positive reviews of the system&#x2019;s innovation, ease of use, and intuitiveness of information presentation, believing it to have great potential in clinical practice.</p></sec><sec sec-type="conclusions"><title>Conclusions</title><p>The developed system is an accurate, efficient auxiliary tool, and pilot validation showed promising preliminary performance. After pilot clinical validation, it holds promise for integration into routine clinical workflows to optimize genetic counseling services.</p></sec></abstract><kwd-group><kwd>hereditary gynecological tumors</kwd><kwd>artificial intelligence</kwd><kwd>AI</kwd><kwd>pedigree mapping</kwd><kwd>retrieval-augmented generation</kwd><kwd>large language models</kwd></kwd-group></article-meta></front><body><sec id="s1" sec-type="intro"><title>Introduction</title><p>Hereditary gynecological tumors account for up to 15% to 20% of all gynecological malignancies [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref2">2</xref>]. Genetic counseling [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref4">4</xref>] is crucial for early screening, intervention, and personalized treatment decisions for high-risk individuals and is a critical step in reducing the risk of hereditary tumors and improving treatment outcomes. The traditional model of genetic counseling is face-to-face, but remote consultation, including telephone consultation, video consultation, and online consultation, has gradually become an integral part of genetic counseling in recent years [<xref ref-type="bibr" rid="ref5">5</xref>].</p><p>Pedigree mapping serves as the first step in genetic counseling. However, current clinical practice faces severe challenges: the genetic counseling process heavily relies on manual family history collection and pedigree drawing by physicians or counselors. When dealing with families involving multiple generations and complex kinship relationships (eg, half-siblings and adoption), the rates of information omission and error increase significantly. This not only consumes valuable consultation time but also severely limits the accessibility and standardization of genetic counseling services.</p><p>In recent years, the rapid advancement of AI, particularly large language models (LLMs), has brought revolutionary opportunities to address this clinical bottleneck [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref7">7</xref>]. While general-purpose LLMs demonstrate powerful language understanding capabilities [<xref ref-type="bibr" rid="ref8">8</xref>], their tendency toward clinical hallucination&#x2014;generating inaccurate or unsubstantiated medical information&#x2014;poses a serious safety risk in the highly specialized medical field. Therefore, developing specialty-specific large models with medical knowledge has become an imperative trend [<xref ref-type="bibr" rid="ref9">9</xref>].</p><p>Against this backdrop, this study aimed to design, develop, and validate a pilot version of an intelligent auxiliary pedigree mapping system based on a gynecological oncology specialty LLM. To ensure the clinical practicality and user acceptance of the system, this study adopted a participatory design approach throughout the entire process. Senior gynecologic oncologists, genetic counselors, and patient representatives were involved in all stages, ensuring that the final product could be seamlessly integrated into existing clinical workflows and effectively address users&#x2019; core points. The system achieved the key functions through preconsultation multiturn dialogue with users: automatically and accurately extracting structured personal and family history information and generating standardized, visual pedigree charts in real time.</p><p>This study&#x2019;s core objectives were to design an intelligent pedigree mapping system to enhance the clinical efficiency of genetic counseling and provide a replicable and scalable &#x201C;China-Shanghai Solution&#x201D; for deeply empowering clinical precision medicine with AI technology.</p></sec><sec id="s2" sec-type="methods"><title>Methods</title><sec id="s2-1"><title>Design Population and Patient Engagement</title><p>To ensure the clinical practicality and national applicability of the system, we invited senior gynecologic oncologists, genetic counselors, clinical research nurses, and patient representatives to participate in several online and offline seminars.</p></sec><sec id="s2-2"><title>System Design and Architecture</title><p>This study was a technological innovation and validation research that used participatory design and agile iterative development methods (<xref ref-type="fig" rid="figure1">Figure 1</xref>). The research process strictly adhered to ethical guidelines, with all involved patient data anonymized and the study approved by the relevant ethics committee.</p><fig position="float" id="figure1"><label>Figure 1.</label><caption><p>System design and development process.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="medinform_v14i1e78080_fig01.png"/></fig></sec><sec id="s2-3"><title>Build a Preliminary Dialogue and Genealogy Chart Generation Program</title><p>As the first step in building the system, multiple experienced genetic counselors collaborated with AI engineers to develop initial scripts for the system&#x2019;s knowledge base and dialogue flows. To ensure the professionalism and accuracy of medical information, every guided question was reviewed by clinical genetics experts. Meanwhile, medical education specialists also participated to ensure that the dialogue language remained accessible and avoided potential misunderstandings caused by technical jargon.</p><p>When a user (patient) mentioned disease information about relatives (eg, &#x201C;my mother&#x2019;s sister was diagnosed with ovarian cancer at age 50&#x201D;) during dialogue with the agent, the system&#x2019;s back end natural language processing engine and specialized LLM worked collaboratively to perform entity recognition (identifying kinship relationships, diseases, and ages) and relationship extraction. Subsequently, using proprietary optimization algorithms, the system further enhanced the accuracy of relationship entities, automatically constructed a visualized pedigree chart according to genetic standards, and rendered it in real time.</p></sec><sec id="s2-4"><title>User Interface and System Architecture</title><p>We developed a mobile app that served as a user interface for both physicians and patients. The entire system was based on a microservices architecture, which ensured secure and efficient communication between the physician and the patient, as well as between the front end and back end natural language processors. To protect user privacy, all sensitive information was encrypted before data transmission, and conversation content was processed and stored anonymously, accessible only to authorized administrators for system optimization.</p><p>The system consisted of a base large model, 2 core agents, 3 support platforms, and 2 types of terminal apps. The base model was the self-developed multimodal medical model. The core agents were the family acquisition agent and the risk computation agent. The system provided services through 2 entrances: the physician side (web) and the patient side (app).</p></sec><sec id="s2-5"><title>Design and Test</title><sec id="s2-5-1"><title>Initial Workshop</title><p>We organized 6 symposiums nationwide, with the participation of 58 experts in the fields of gynecology, genetics, and information technology from different hospitals. These workshops provided us with a clear scope of the system&#x2019;s core capabilities, defined initial conversations, and allowed us to collect a large amount of real-world data for dialogue database expansion.</p></sec><sec id="s2-5-2"><title>User Testing</title><p>We invited 11 testers, including clinical geneticists, genetic counselors, research nurses, and 2 BRCA mutation carrier representatives, to test the prototype for 4 weeks. They were asked to have at least 5 independent conversations with the system during this time, each lasting at least 5 minutes, and to record the problems they encountered and their experience.</p></sec><sec id="s2-5-3"><title>Formal Usability Testing</title><p>We recruited an additional 9 testers (7 health care workers and 2 patient representatives) to complete a series of preset tasks (eg, complete family history information input and interpret the system-generated family tree and risk warnings) in an observational environment. Project personnel recorded their operational paths and difficulties and collected feedback in real time.</p></sec></sec><sec id="s2-6"><title>Datasets and Evaluation Procedure</title><p>The iterative process was initially planned to include 3 iterations, but during the development process, to address the accuracy of AI models when dealing with complex kinships, we decided to add a fourth iteration dedicated to manually reviewing and optimizing the genealogy map generation algorithm. Each iteration signified a significant expansion of the database and substantial improvements in system functionality.</p><p>We manually evaluated all conversations generated during the user testing and the generated family charts to assess system performance, categorizing the results into 3 categories: correct (accurate information extraction and correct family chart structure), wrong (missing key information or mismatched relationships), or fallback (the system could not understand the user&#x2019;s answer and asked the user to phrase it in a different way).</p><p>All data used for tool iteration were derived from real-world, multiturn dialogue records generated by users during system use. At the initial stage of tool development, multiple experienced genetic counselors, clinical geneticists, and medical education specialists jointly reviewed the dialogue flow scripts, based on which the development team finalized requirements and established preliminary process rules. During iteration, the rules were continuously refined using real-world conversation data validated by experts; by contrast, dialogue data collected at user testing checkpoints served as an independent test set, and user feedback was systematically incorporated into the rule revision loop to ensure the objectivity and clinical relevance of improvements. The gold standard was jointly established by a panel of industry experts. Annotation, including entity recognition and attribute labeling of pedigree data, was primarily performed by relevant project personnel and 1 clinical staff member. All annotation disagreements were resolved through multiple offline discussions until consensus was reached, and the entire annotation process was strictly independent of the iterative optimization data to guarantee the reliability of the evaluation results.</p></sec><sec id="s2-7"><title>AI System Architecture</title><sec id="s2-7-1"><title>Specialized Medical LLM (Proprietary Medical LLM)</title><p>The core generative capability of this model was provided by an open-source model with a large parameter count, and no downstream task fine-tuning was performed on the model to maximally preserve the generalizability of the foundation model while reducing adaptation costs.</p><p>The overall dialogue workflow of the model was designed entirely based on the retrieval-augmented generation (RAG) architecture: during medical knowledge consultation dialogues, the agent retrieved highly relevant knowledge snippets from an external medical knowledge base according to the current dialogue context and injected them as augmented context into the model, thereby dynamically supplementing the model&#x2019;s knowledge reservoir and compensating for the deficiencies of general-purpose foundation models in specialized medical domains.</p><p>Rule-based algorithms were used to constrain and calibrate the dialogue flow: through predefined step state identifiers and logical branches, the flow direction was strictly enforced to ensure that the interaction path conformed to the standard pedigree information collection protocol. These algorithms also performed real-time validation and constrained the model-generated responses, effectively suppressing factual errors and fabrications, thus substantially reducing model hallucination. By combining the language capabilities of the large model, external knowledge retrieval, and explicit rule-based control, the system achieved more controllable and trustworthy intelligent interaction in medical dialogue scenarios without requiring fine-tuning.</p></sec><sec id="s2-7-2"><title>Patient-Side Data Collection</title><p>On the patient side, information was sequentially provided through dialogue, including gender, age, personal tumor history, family tumor history, kinship structure, age of onset, death status, and genetic testing information. The agent transformed unstructured statements into attribute-structured family history data through intent recognition, entity recognition, and kinship relation parsing, forming a standardized structure directly usable for pedigree chart rendering. To enhance extraction reliability, the agent cross-validated intermediate results by integrating risk rules, RAG retrieval outcomes, a rule engine, and structural consistency verification and automatically initiated follow-up questions for any uncertain information.</p></sec><sec id="s2-7-3"><title>Final Output</title><p>On the basis of the extracted structured family history, the agent generated a pedigree chart and simultaneously performed risk assessment for hereditary breast and ovarian cancer syndrome, Lynch syndrome, and Peutz-Jeghers syndrome. Ultimately, the agent output genetic counseling recommendations.</p></sec></sec><sec id="s2-8"><title>Safety and Hallucination Control</title><p>The agent was exclusively designed for gynecological oncology medical knowledge consultation, family history collection, and pedigree chart generation and did not output diagnostic or therapeutic decisions. The RAG system was restricted to a defined knowledge source, and all results were accompanied by source attribution. Knowledge extraction incorporated confidence filtering, rule-based validation, and human review; newly added knowledge must not conflict with existing high-confidence knowledge. Both the generated pedigree chart and the rules participated in result verification. These measures collectively supported the claim that the agent was subject to multilayered constraints and did not engage in free-form generation.</p><p>In the process of extracting family tumor history information and generating the pedigree chart, a mechanism of relationship confidence control and kinship consistency verification was introduced. For recognition results with low confidence or conflicting kinship relations, the agent did not directly incorporate them into the pedigree chart but instead triggered targeted follow-up questions. If the uncertainty persisted, a conservative fallback strategy was adopted, marking the relevant nodes or relationships as &#x201C;unknown&#x201D; or &#x201C;pending confirmation.&#x201D;</p><p>The generated pedigree chart was further validated against predefined kinship rules, including branch affiliation (paternal vs maternal), generational level, intragenerational and intergenerational relationships, key connecting kinships, and consistency checks for duplicate members. This approach thereby enhanced the logical consistency and traceability of the structured family tumor history results.</p></sec><sec id="s2-9"><title>Ethical Consideration</title><p>The present study involving clinical hereditary cancer information from patients was approved by the ethics committee of the Obstetrics and Gynecology Hospital of Fudan University (2021&#x2010;09-X1). Prior informed consent was obtained from all users, who were required to agree to relevant protocols and policies before participation; all collected data were deidentified prior to use to ensure that no personally identifiable information was involved.</p></sec></sec><sec id="s3" sec-type="results"><title>Results</title><p>In the first iteration phase, we built a systematic database of knowledge and dialogue based on the results of the workshop (<xref ref-type="table" rid="table1">Table 1</xref>). It defined 100 core information nodes (eg, specific kinship or disease) and matched them with approximately 800 recognizable user representation paradigms (recognition breadth ratio of 8.0). Informal testing of prototypes showed that 40% (40/100) of core information nodes had errors in genealogy generation, with the main problem being the inability to accurately identify complex or vague kinship titles such as &#x201C;cousin.&#x201D;</p><table-wrap id="t1" position="float"><label>Table 1.</label><caption><p>The 4 iterative phases of system design and development.</p></caption><table id="table1" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom"/><td align="left" valign="bottom" colspan="4">Phase</td></tr><tr><td align="left" valign="bottom"/><td align="left" valign="bottom">Iteration 1</td><td align="left" valign="bottom">Iteration 2</td><td align="left" valign="bottom">Iteration 3</td><td align="left" valign="bottom">Iteration 4</td></tr></thead><tbody><tr><td align="left" valign="top">Method</td><td align="left" valign="top">Workshops and prototyping</td><td align="left" valign="top">User testing and manual evaluation</td><td align="left" valign="top">Formal usability test</td><td align="left" valign="top">Manual review of algorithms and databases</td></tr><tr><td align="left" valign="top">Participants, n</td><td align="left" valign="top">58</td><td align="left" valign="top">9</td><td align="left" valign="top">9</td><td align="left" valign="top">3 (core team)</td></tr><tr><td align="left" valign="top">Revision level</td><td align="left" valign="top">Preliminary construction</td><td align="left" valign="top">Major revisions</td><td align="left" valign="top">Major revisions</td><td align="left" valign="top">Major revisions</td></tr><tr><td align="left" valign="top">Fidelity level</td><td align="left" valign="top">Low</td><td align="left" valign="top">Low</td><td align="left" valign="top">Medium</td><td align="left" valign="top">High</td></tr><tr><td align="left" valign="top">Core information</td><td align="left" valign="top">Core requirements were clarified, but AI performance was insufficient</td><td align="left" valign="top">Key technical bottlenecks identified</td><td align="left" valign="top">Optimized user interface and interaction logic</td><td align="left" valign="top">The genealogy chart generation error rate was significantly reduced</td></tr></tbody></table></table-wrap><p>Subsequent iteration step 2 (user testing) recorded a total of 822 user inputs (<xref ref-type="table" rid="table2">Table 2</xref>). We found that 519 (63.1%) inputs were processed efficiently, while 303 (36.9%) inputs triggered fallbacks because the system could not understand them. Of these, 69.2% (359/519) efficiently processed inputs were generated with correct family plot nodes, while a significant portion contained errors.</p><p>This observation prompted us to focus on reconstructing the identification logic of all kinship relationships. This iterative step eventually resulted in 50 new conversation scenarios, and the database expanded to 150 core information nodes and 1250 user expression examples.</p><table-wrap id="t2" position="float"><label>Table 2.</label><caption><p>Overview of user testing in user interface and system architecture.</p></caption><table id="table2" frame="hsides" rules="groups"><thead><tr><td align="left" valign="top">Characteristic</td><td align="left" valign="top">Value</td></tr></thead><tbody><tr><td align="left" valign="top">Testers, n</td><td align="left" valign="top">9</td></tr><tr><td align="left" valign="top">Conversations recorded, n</td><td align="left" valign="top">71</td></tr><tr><td align="left" valign="top">Total test duration (min)</td><td align="left" valign="top">507</td></tr><tr><td align="left" valign="top">Average duration per conversation (minutes:seconds)</td><td align="left" valign="top">7:11</td></tr><tr><td align="left" valign="top">Total user input, n</td><td align="left" valign="top">822</td></tr><tr><td align="left" valign="top">Input that triggered fallback (n=822), n (%)</td><td align="left" valign="top">303 (36.9)</td></tr><tr><td align="left" valign="top">Successfully processed input (n=822), n (%)</td><td align="left" valign="top">519 (63.1)</td></tr><tr><td align="left" valign="top">Correctly processed inputs (n=519), n (%)</td><td align="left" valign="top">359 (69.2)</td></tr><tr><td align="left" valign="top">Inputs with errors (n=519), n (%)</td><td align="left" valign="top">160 (30.8)</td></tr></tbody></table></table-wrap><p>Feedback from iteration 3 (formal usability testing) was invaluable (<xref ref-type="table" rid="table3">Table 3</xref>). According to user feedback, all testers (9/9, 100%) agreed that the automatic generation of family trees saved time and was very intuitive. More than half of the testers (7/9, 77.8%) found the dialogue interface to be user-friendly and easy to use. During the testing process, testers also provided some suggestions, such as the need to ensure the accuracy of the results, the desire for manual editing of family trees, and the hope for features like exporting family trees in PDF format.</p><table-wrap id="t3" position="float"><label>Table 3.</label><caption><p>Overview of tester feedback on key features in usability testing.</p></caption><table id="table3" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Problems</td><td align="left" valign="bottom">Feedback overview (number of people who provided this feedback)</td></tr></thead><tbody><tr><td align="left" valign="top">What features work well?</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Automatically generates a genealogy chart, which is very intuitive (9)</p></list-item><list-item><p>Conversational interface is user-friendly and easy to use (7)</p></list-item><list-item><p>Saves a lot of time on manual recording and drawing (9)</p></list-item></list></td></tr><tr><td align="left" valign="top">What features are not good?</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Inability to deal with some complex family relationships (5)</p></list-item><list-item><p>Occasionally unable to understand my statement, triggering a fallback (2)</p></list-item><list-item><p>The generated family chart cannot be edited directly (8)</p></list-item></list></td></tr><tr><td align="left" valign="top">Do you think this system meets clinical needs?</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Yes, great potential for efficiency (9)</p></list-item><list-item><p>Yes, but only if accuracy is guaranteed (7)</p></list-item><list-item><p>Yes, it would be better if it could be integrated with an electronic medical record system (5)</p></list-item></list></td></tr><tr><td align="left" valign="top">What features do you want to add?</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Manual editing of family charts (8)</p></list-item><list-item><p>Risk assessment summary or &#x201C;heatmap&#x201D; (7)</p></list-item><list-item><p>Export the family chart as an image or PDF (6)</p></list-item></list></td></tr></tbody></table></table-wrap><p>On the basis of this feedback, we made significant revisions to the system. The IT team embedded the family chart online editing function and the risk heatmap module. We further expanded the database to 200 core information nodes and 1800 user expression examples.</p><p>The core challenge revealed by the second and third iterations was the accuracy of genealogy mapping. Therefore, we added a fourth iteration, increasing the number of core information nodes to 245 and nearly doubling the number of recognizable user expression examples to a total of 2256.</p><p>After 4 rounds of iterative optimization, the final pilot version of the system achieved significant improvements in various performance indicators. The system successfully processed a total of 2042 pieces of data to generate 218 sets of genealogy charts. The system demonstrated high technical stability, experiencing no software crashes or rendering failures during this testing phase. The data were generated by 37 users, including physicians, nurses, and nonmedical workers.</p><p>We selected 50 family pedigrees for analysis. All conversational data and system-generated pedigree maps were cross-checked, and a comparison was made between manually drawn pedigree maps and those generated by AI. The primary verification focused on whether the role and gender of each member node matched. The evaluation of pedigree map construction included checking whether all connections in the diagrams were correct and ensuring the accuracy of parental, spousal, and sibling relationships.</p><p>The first step involved verifying node-level information: whether the total number of members matched; identifying whether the role and gender of each member node (eg, grandfather, grandmother, and proband) were consistent; and counting all member nodes in the pedigree map, as well as correctly identified, missing, and extraneously extracted member nodes.</p><p>The second step involved verifying relationship-level information: checking whether all connections in the diagram were correct, including parental, spousal, and sibling relationships; and counting all relationships in the pedigree map, as well as correctly identified, missing, and extraneously extracted relationships.</p><p>The third step involved verifying clinical attribute-level information: ensuring node matching, attribute keys, and attribute values were consistent for each member, including attributes such as current age, age of onset, disease, age at death, and cause of death.</p><p>After the verification, on independent test sets containing complex kinships, the genealogy graph had remarkable precision in node and relationship generation and clinical attribution (<xref ref-type="table" rid="table4">Table 4</xref>). The length of dialogue in the system varied depending on the complexity of the pedigree, but the content was simple and easy to understand. Upon completing the dialogue, the average time to generate a pedigree was under 3 minutes, which was significantly shorter than the typical 10 to 20 minutes required in clinical settings and greatly contributed to improving the efficiency of clinical genetic counseling.</p><table-wrap id="t4" position="float"><label>Table 4.</label><caption><p>Performance evaluation of AI-generated pedigree charts across 3 semantic dimensions.</p></caption><table id="table4" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom" rowspan="2">Dimension and metric</td><td align="left" valign="bottom" colspan="3">Global counts<sup><xref ref-type="table-fn" rid="table4fn1">a</xref></sup></td><td align="left" valign="bottom" rowspan="2">Micro-average<sup><xref ref-type="table-fn" rid="table4fn5">e</xref></sup> (%)</td><td align="left" valign="bottom" rowspan="2">Macro-average<sup><xref ref-type="table-fn" rid="table4fn6">f</xref></sup> (95% CI)</td></tr><tr><td align="left" valign="bottom">TP<sup><xref ref-type="table-fn" rid="table4fn2">b</xref></sup></td><td align="left" valign="bottom">FP<sup><xref ref-type="table-fn" rid="table4fn3">c</xref></sup></td><td align="left" valign="bottom">FN<sup><xref ref-type="table-fn" rid="table4fn4">d</xref></sup></td></tr></thead><tbody><tr><td align="left" valign="top">Entities (nodes)</td><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Precision</td><td align="char" char="." valign="top">&#x2014;<sup><xref ref-type="table-fn" rid="table4fn7">g</xref></sup></td><td align="left" valign="top">&#x2014;</td><td align="char" char="ndash" valign="top">&#x2014;</td><td align="char" char="." valign="top">99.3</td><td align="char" char="." valign="top">99.23 (98.17-100.00)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Recall</td><td align="char" char="." valign="top">547</td><td align="char" char="." valign="top">4</td><td align="char" char="." valign="top">28</td><td align="char" char="." valign="top">95.1</td><td align="char" char="." valign="top">95.67 (92.96-98.39)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><italic>F</italic><sub>1</sub>-score (Support:575)<sup><xref ref-type="table-fn" rid="table4fn8">h</xref></sup></td><td align="char" char="." valign="top" colspan="3"/><td align="char" char="." valign="top">97.2</td><td align="char" char="." valign="top">97.19 (95.39-98.99)</td></tr><tr><td align="left" valign="top">Relations (edges)</td><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Precision</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="char" char="." valign="top">99.3</td><td align="char" char="." valign="top">99.2 (98.05-100.00)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Recall</td><td align="char" char="." valign="top">1201</td><td align="char" char="." valign="top">9</td><td align="char" char="." valign="top">95</td><td align="char" char="." valign="top">92.7</td><td align="char" char="." valign="top">94.52 (91.00-98.04)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><italic>F</italic><sub>1</sub>-score (Support:1296)<sup><xref ref-type="table-fn" rid="table4fn8">h</xref></sup></td><td align="char" char="." valign="top" colspan="3"/><td align="char" char="." valign="top">95.9</td><td align="char" char="." valign="top">96.35 (93.98-98.72)</td></tr><tr><td align="left" valign="top">Attributes (clinical information)</td><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Precision</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">&#x2014;</td><td align="char" char="." valign="top">98.9</td><td align="char" char="." valign="top">99.32 (98.00-100.00)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Recall</td><td align="char" char="." valign="top">89</td><td align="char" char="." valign="top">1</td><td align="char" char="." valign="top">3</td><td align="char" char="." valign="top">96.7</td><td align="char" char="." valign="top">97.62 (94.95-100.00)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><italic>F</italic><sub>1</sub>-score (Support:92)<sup><xref ref-type="table-fn" rid="table4fn8">h</xref></sup></td><td align="char" char="." valign="top" colspan="3"/><td align="char" char="." valign="top">97.8</td><td align="char" char="." valign="top">98.23 (96.24-100.00)</td></tr></tbody></table><table-wrap-foot><fn id="table4fn1"><p><sup>a</sup>Global counts are cumulative counts of TP, FP, and FN summed across all 50 samples.</p></fn><fn id="table4fn2"><p><sup>b</sup>TP: true positive.</p></fn><fn id="table4fn3"><p><sup>c</sup>FP: false positive.</p></fn><fn id="table4fn4"><p><sup>d</sup>FN: false negative.</p></fn><fn id="table4fn5"><p><sup>e</sup>Micro-average was calculated using global sums: precision=&#x03A3;TP/(&#x03A3;TP+&#x03A3;FP); recall=&#x03A3;TP/(&#x03A3;TP+&#x03A3;FN), representing overall performance at the instance level.</p></fn><fn id="table4fn6"><p><sup>f</sup>Macro-average is the arithmetic mean of per-sample metrics. 95% CI calculated as mean&#x00B1;1.96&#x00D7;SE, indicating consistency across samples with different family structures.</p></fn><fn id="table4fn7"><p><sup>g</sup>Not applicable.</p></fn><fn id="table4fn8"><p><sup>h</sup>Support indicates the total number of ground truth instances (TP+FN).</p></fn></table-wrap-foot></table-wrap></sec><sec id="s4" sec-type="discussion"><title>Discussion</title><sec id="s4-1"><title>Principal Findings</title><p>In this study, an intelligent assisted diagnostic decision-making system designed for hereditary gynecological tumors was successfully constructed and preliminarily verified. The final pilot version achieved near-perfect accuracy in generating genealogy nodes and relationships. Although AI functions were initially limited, the final system received positive feedback from test users regarding its innovation, ease of use, and intuitive information presentation. The developed system was an accurate, efficient auxiliary tool. After sufficient clinical validation, it holds promise for integration into routine clinical workflows to optimize genetic counseling services. The entire development process was more challenging than expected, but it turned out that AI tools have the potential to become a powerful complement to traditional genetic counseling models by combining large specialized models with clinical workflows [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref11">11</xref>].</p><p>The core strength of this project was its specialization and participatory design. Unlike tools that rely on general large models, the specialized large model we used effectively reduced the risk of generating clinically inaccurate information through knowledge-base construction in the field of gynecological oncology. The participatory design approach used throughout ensured that the functions, interactions, and outputs of the system (eg, the style of the family map) were closely aligned with the actual work habits and needs of clinicians, which is the key to the successful implementation of the technology in clinical practice. It is worth noting that the core information nodes of the database expanded from the initial 100 to the final 245, while the number of user expression examples recognizable by the system increased from 800 to 2256 (the recognition breadth ratio increased from 8.0 to 9.2), reflecting the great efforts we made to improve the AI&#x2019;s understanding capabilities and the accuracy of genealogy map generation during the development process.</p><p>The biggest challenge in the development process, consistent with the literature, was the precise translation of highly unstructured, ambiguous natural language conversations into structured data and knowledge graphs (ie, family maps) that complied with medical genetics norms. Our experience shows that the general capabilities of LLMs alone are not enough to solve this problem. The introduction of the graph-based kinship inference and validation module and the implementation of multiple rounds of data-driven iterative optimization are effective ways to overcome this challenge. The significant increase in the scale of the system&#x2019;s database intuitively reflects the great efforts made to improve AI understanding capabilities.</p><p>The clinical significance of this system is far-reaching. By allowing patients to interact with the system before consultation, family history collection, the longest and most error-prone task in the traditional mode can be efficiently completed. This allows genetic counselors to free valuable clinic time from tedious data entry and mapping work and focus more on in-depth communication with patients, interpreting complex genetic reports, and providing psychological support, thereby greatly improving the quality and accessibility of genetic counseling.</p><p>The value of this informatics approach is not limited to accuracy metrics. In routine clinical practice, shifting family history collection, the longest and most error-prone task, to a self-service interaction before the consultation frees counselors from manual charting and lets them spend the saved time on interpretation, risk communication, and psychological support; standardized capture also reduces between-center variation. On the personalized-care side, pairing the gynecology-oncology RAG knowledge base with rule-based risk logic and the graph-based kinship inference module converts unstructured family narratives into individual-specific pedigrees and risk cues, so assessment can follow the patient rather than a generic template. From a population health policy perspective, taking the tool into primary care and community settings would broaden access to pedigree-based screening for high-risk families, supply the data needed for cost-effectiveness analyses, and help shape standardized family history protocols that extend hereditary cancer prevention to the population level.</p></sec><sec id="s4-2"><title>Limitations</title><p>Although the development of the system involved the participation of multicenter experts across the country, its clinical validation was mainly carried out at a single medical center with a small sample size. Larger-scale, multicenter prospective studies are needed in the future to verify its effectiveness and generalization ability in different clinical settings. During the design phase, despite the full involvement of patient representatives, it would have been better to involve a more diverse patient population in each round of testing. We have initiated a follow-up study to conduct in-depth interviews with patients using the system in a real-world clinical setting, the results of which will be used for the final iteration of the system.</p><p>While certain pedigree resources were consulted during the development of the tool, its functionality relies on active user input. The primary focus of this paper is the conversion of natural language into structured pedigree representation; benchmarking against existing pedigree software or other AI tools has not yet been conducted. Currently, most existing pedigree drawing software relies heavily on manual data entry and structured form-filling, lacking the capability to process unstructured, multiturn natural language dialogues. Therefore, conducting a direct, quantitative head-to-head comparison is challenging, as the input modalities are fundamentally different. However, we recognize the importance of this comparison, and such comparisons have been considered for inclusion in subsequent testing.</p></sec><sec id="s4-3"><title>Conclusions</title><p>Successful implementation of AI tools in health care requires systems that can accurately analyze user inputs and provide correct and reliable outputs. As AI technology evolves to better understand the nuances of written language on a deeper level, patients will be able to fully understand and prepare information through interaction with the intelligent system before meeting with the physician. This not only makes physician-patient communication more efficient and targeted but also makes personalized medicine truly a reality. Tools such as the hereditary gynecological tumor assistance system are expected to become efficient tools for genetic counselors.</p></sec></sec></body><back><ack><p>No generative AI tools were used in the creation of this manuscript.</p></ack><notes><sec><title>Funding</title><p>The authors declared no financial support was received for this work.</p></sec><sec><title>Data Availability</title><p>The data generated in this study are available upon request from the corresponding author.</p></sec></notes><fn-group><fn fn-type="con"><p>JX and YW conceptualized and designed the study, analyzed the data, and wrote the original manuscript draft. HW and JS contributed to data analysis and investigation. XL provided technical support and resources. YK and CX supervised the study and critically reviewed and edited the manuscript. All authors read and approved the final manuscript.</p><p>JX and YW are co-first authors.</p><p>CX is the co-corresponding author of this paper and can be reached at: xucj@hotmail.com.</p></fn><fn fn-type="conflict"><p>JS, YW, and XL are employees of Shanghai Taihealth Intelligent Technology Co., Ltd., the developer of the system evaluated in this study. The company plans to commercialize the product. Other authors do not have any conflicts to declare.</p></fn></fn-group><glossary><title>Abbreviations</title><def-list><def-item><term id="abb1">LLM</term><def><p>large language model</p></def></def-item><def-item><term id="abb2">RAG</term><def><p>retrieval-augmented generation</p></def></def-item></def-list></glossary><ref-list><title>References</title><ref id="ref1"><label>1</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Caruso</surname><given-names>G</given-names> </name><name name-style="western"><surname>Weroha</surname><given-names>SJ</given-names> </name><name name-style="western"><surname>Cliby</surname><given-names>W</given-names> </name></person-group><article-title>Ovarian cancer: a review</article-title><source>JAMA</source><year>2025</year><month>10</month><day>14</day><volume>334</volume><issue>14</issue><fpage>1278</fpage><lpage>1291</lpage><pub-id pub-id-type="doi">10.1001/jama.2025.9495</pub-id><pub-id pub-id-type="medline">40690248</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>Capasso</surname><given-names>I</given-names> </name><name name-style="western"><surname>Santoro</surname><given-names>A</given-names> </name><name name-style="western"><surname>Lucci Cordisco</surname><given-names>E</given-names> </name><etal/></person-group><article-title>Lynch syndrome and gynecologic tumors: incidence, prophylaxis, and management of patients with cancer</article-title><source>Cancers (Basel)</source><year>2023</year><month>02</month><day>22</day><volume>15</volume><issue>5</issue><fpage>1400</fpage><pub-id pub-id-type="doi">10.3390/cancers15051400</pub-id><pub-id pub-id-type="medline">36900193</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>Levine</surname><given-names>R</given-names> </name><name name-style="western"><surname>Kahn</surname><given-names>RM</given-names> </name><name name-style="western"><surname>Perez</surname><given-names>L</given-names> </name><etal/></person-group><article-title>Cascade genetic testing for hereditary cancer syndromes: a review of barriers and breakthroughs</article-title><source>Fam Cancer</source><year>2024</year><month>06</month><volume>23</volume><issue>2</issue><fpage>111</fpage><lpage>120</lpage><pub-id pub-id-type="doi">10.1007/s10689-024-00373-4</pub-id><pub-id pub-id-type="medline">38530571</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>Kim</surname><given-names>M</given-names> </name><name name-style="western"><surname>Cheol Lim</surname><given-names>M</given-names> </name><name name-style="western"><surname>Ji Nam</surname><given-names>E</given-names> </name><etal/></person-group><article-title>Awareness of genetic counseling and genetic testing for hereditary gynecologic cancers among Korean healthcare providers: a survey</article-title><source>J Genet Couns</source><year>2022</year><month>04</month><volume>31</volume><issue>2</issue><fpage>546</fpage><lpage>553</lpage><pub-id pub-id-type="doi">10.1002/jgc4.1524</pub-id><pub-id pub-id-type="medline">34674340</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>Chu</surname><given-names>AT</given-names> </name><name name-style="western"><surname>Chung</surname><given-names>CC</given-names> </name><name name-style="western"><surname>Hue</surname><given-names>SP</given-names> </name><name name-style="western"><surname>Chung</surname><given-names>BH</given-names> </name></person-group><article-title>The growing needs of genetic counselling-feasibility in utilization of tele-genetic counselling in Asia and Hong Kong</article-title><source>Front Genet</source><year>2023</year><volume>14</volume><fpage>1239817</fpage><pub-id pub-id-type="doi">10.3389/fgene.2023.1239817</pub-id><pub-id pub-id-type="medline">37600657</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>Siglen</surname><given-names>E</given-names> </name><name name-style="western"><surname>Vetti</surname><given-names>HH</given-names> </name><name name-style="western"><surname>Lunde</surname><given-names>AB</given-names> </name><etal/></person-group><article-title>Ask Rosa - the making of a digital genetic conversation tool, a chatbot, about hereditary breast and ovarian cancer</article-title><source>Patient Educ Couns</source><year>2022</year><month>06</month><volume>105</volume><issue>6</issue><fpage>1488</fpage><lpage>1494</lpage><pub-id pub-id-type="doi">10.1016/j.pec.2021.09.027</pub-id><pub-id pub-id-type="medline">34649750</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>Patel</surname><given-names>JM</given-names> </name><name name-style="western"><surname>Hermann</surname><given-names>CE</given-names> </name><name name-style="western"><surname>Growdon</surname><given-names>WB</given-names> </name><name name-style="western"><surname>Aviki</surname><given-names>E</given-names> </name><name name-style="western"><surname>Stasenko</surname><given-names>M</given-names> </name></person-group><article-title>ChatGPT accurately performs genetic counseling for gynecologic cancers</article-title><source>Gynecol Oncol</source><year>2024</year><month>04</month><volume>183</volume><fpage>115</fpage><lpage>119</lpage><pub-id pub-id-type="doi">10.1016/j.ygyno.2024.04.006</pub-id><pub-id pub-id-type="medline">38676973</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>Ferber</surname><given-names>D</given-names> </name><name name-style="western"><surname>El Nahhas</surname><given-names>OS</given-names> </name><name name-style="western"><surname>W&#x00F6;lflein</surname><given-names>G</given-names> </name><etal/></person-group><article-title>Development and validation of an autonomous artificial intelligence agent for clinical decision-making in oncology</article-title><source>Nat Cancer</source><year>2025</year><month>08</month><volume>6</volume><issue>8</issue><fpage>1337</fpage><lpage>1349</lpage><pub-id pub-id-type="doi">10.1038/s43018-025-00991-6</pub-id><pub-id pub-id-type="medline">40481323</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>Sato</surname><given-names>A</given-names> </name><name name-style="western"><surname>Haneda</surname><given-names>E</given-names> </name><name name-style="western"><surname>Hiroshima</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Narimatsu</surname><given-names>H</given-names> </name></person-group><article-title>Preliminary screening for hereditary breast and ovarian cancer using an AI chatbot as a genetic counselor: clinical study</article-title><source>J Med Internet Res</source><year>2024</year><month>11</month><day>27</day><volume>26</volume><fpage>e48914</fpage><pub-id pub-id-type="doi">10.2196/48914</pub-id><pub-id pub-id-type="medline">39602801</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>Greene</surname><given-names>A</given-names> </name><name name-style="western"><surname>Greene</surname><given-names>CC</given-names> </name><name name-style="western"><surname>Greene</surname><given-names>C</given-names> </name></person-group><article-title>Artificial intelligence, chatbots, and the future of medicine</article-title><source>Lancet Oncol</source><year>2019</year><month>04</month><volume>20</volume><issue>4</issue><fpage>481</fpage><lpage>482</lpage><pub-id pub-id-type="doi">10.1016/S1470-2045(19)30142-1</pub-id><pub-id pub-id-type="medline">30942174</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>Kearney</surname><given-names>E</given-names> </name><name name-style="western"><surname>Wojcik</surname><given-names>A</given-names> </name><name name-style="western"><surname>Babu</surname><given-names>D</given-names> </name></person-group><article-title>Artificial intelligence in genetic services delivery: utopia or apocalypse?</article-title><source>J Genet Couns</source><year>2020</year><month>02</month><volume>29</volume><issue>1</issue><fpage>8</fpage><lpage>17</lpage><pub-id pub-id-type="doi">10.1002/jgc4.1192</pub-id><pub-id pub-id-type="medline">31749317</pub-id></nlm-citation></ref></ref-list></back></article>