TRV-2026-1542Certified recordPeer-reviewed

Construction of an AI-Assisted Pedigree Mapping System for Hereditary Gynecological Tumors: Algorithm Development and Pilot Validation Study

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…

Health · Good Space — documented gain · certified 2026-10-16 · v1 · article view · machine-readable

Current reading — gain

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.

What this doesn’t fix

The evidence is from a pilot validation, and the authors state that integration into routine clinical workflows depends on further pilot clinical validation.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1542, v1: “Construction of an AI-Assisted Pedigree Mapping System for Hereditary Gynecological Tumors: Algorithm Development and Pilot Validation Study.” Truvace, 2026-10-16. /record/TRV-2026-1542 (accessed at citation time). sha256 89a4654edafb5607…

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv189a4654edafb…

    Certified into the record

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.