TRV-2026-1542Version 1 · Certified

Written 2026-10-16 06:54:35 UTC · current record

Reason for this version

Certified into the record

Canonical text (the exact bytes fingerprinted)

TRUVACE RECORD VERSION
record: TRV-2026-1542
version: 1
kind: certified
reason: Certified into the record
timestamp: 2026-10-16T06:54:35.218949Z
status: published
lens: g_space
sector: health
headline: Construction of an AI-Assisted Pedigree Mapping System for Hereditary Gynecological Tumors: Algorithm Development and Pilot Validation Study
dek: Background: 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.
Objective: 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.
Methods: This study adopt…
gain_title: A specialized language model system that collects family history through conversation and builds standardized pedigree maps showed accurate node and relationship generation and positive user feedback in a pilot, suggesting it could ease genetic counseling workflows.
problem_title: (none)
trace_subject: (none)
gain_reading: A specialized language model system that collects family history through conversation and builds standardized pedigree maps showed accurate node and relationship generation and positive user feedback in a pilot, suggesting it could ease genetic counseling workflows.
gain_evidence: Test users generally gave positive reviews of the system's innovation, ease of use, and intuitiveness of information presentation
problem_reading: (none)
problem_evidence: (none)
quick_read: Researchers built an interdisciplinary, participatory-design system around a specialized large language model for gynecologic oncology. Over four iterative cycles they added retrieval-augmented knowledge bases and a graph-based kinship inference and validation module so patients could give family history in conversation and receive a standardized pedigree map.

Pedigree mapping is the first step of genetic counseling, and manual drawing and data collection are described as inefficient and error-prone. The pilot results are encouraging, but they are preliminary, and the authors say the tool still needs pilot clinical validation before it could be integrated into routine clinical workflows.
limitation: The evidence is from a pilot validation, and the authors state that integration into routine clinical workflows depends on further pilot clinical validation.
tag: Evidence-backed gain
key_points: The team included gynecologic oncologists, genetic counselors, AI engineers, and patient representatives. | The knowledge base grew from 100 core information nodes and about 800 expression examples to 245 nodes and 2256 examples. | The system combines retrieval-augmented generation with a graph-based kinship inference and validation module. | Test users rated innovation, ease of use, and clarity of information presentation positively.
rundown: The system uses a proprietary specialized large language model with a microservices architecture, including a pedigree data collection component, to automate family history collection through dialogue.

Performance was improved by optimizing dialogue strategies, expanding the knowledge base, and applying self-developed algorithms to raise data extraction accuracy. The AI function was limited in the early stage but improved in later iterations.

Evaluation covered the accuracy of pedigree map generation and user feedback on usability. The authors conclude the tool is an accurate, efficient auxiliary tool with promising preliminary performance.
sources:
- peer_reviewed | JMIR Medical Informatics | https://doi.org/10.2196/78080 | 2026-10-15
prev: 0000000000000000000000000000000000000000000000000000000000000000
sha256
89a4654edafb5607b6ebc69a86c6bec5196c410d37238eeda548031d72137f3a
previous
0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-1542 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.