TRV-2026-1236Version 1 · Certified

Written 2026-10-01 06:56:31 UTC · current record

Reason for this version

Certified into the record

Canonical text (the exact bytes fingerprinted)

TRUVACE RECORD VERSION
record: TRV-2026-1236
version: 1
kind: certified
reason: Certified into the record
timestamp: 2026-10-01T06:56:31.923069Z
status: published
lens: p_space
sector: health
headline: Artificial Intelligence-Based Chatbots in Genetic Counseling Practice: Current Uptake, Utilization, and Perspectives
dek: AI-driven chatbots have been utilized in healthcare to automate administrative tasks, improve patient education, and expand access to medical information; however, their role in genetic counseling remains underexplored. To investigate the adoption, perceptions, and potential utility of AI-based chatbots in genetic counseling practice, 217 genetic counselors and genetic counseling students from across North America were surveyed regarding chatbot usage, confidence in their application, and perceived benefits and…
gain_title: (none)
problem_title: Counselors reported low confidence in chatbots for sensitive result disclosure and major concerns about patient comprehension and information accuracy.
trace_subject: (none)
gain_reading: (none)
gain_evidence: (none)
problem_reading: Counselors reported low confidence in chatbots for sensitive result disclosure and major concerns about patient comprehension and information accuracy.
problem_evidence: patient comprehension (167/195; 85.6%)
quick_read: A peer-reviewed survey of 217 genetic counselors and students in North America examined current uptake of AI chatbots in genetic counseling. While 76.5% reported using general chatbots outside clinical settings, only 8.8% reported using or recommending clinical genetics chatbots, mainly for at-risk family communication and patient education.

The findings matter because they show a perceived efficiency upside alongside persistent safety and training gaps that could affect patient understanding of genetic risk. Uncertainty remains about how to ensure accurate, up-to-date information and appropriate task boundaries, especially for disclosing uncertain or positive results, before chatbots can be integrated and regulated in routine care.
limitation: Adoption is constrained by minimal formal training and unresolved concerns about accuracy and patient understanding, based on a self-reported survey sample.
tag: Evidence-backed problem
key_points: Survey of 217 genetic counselors and students across North America found 76.5% used general AI chatbots outside clinic but only 8.8% used or recommended clinical genetics chatbots in practice. | Among clinical users, top uses were communication with at-risk family members (61.1%) and patient education (55.6%). | Confidence was highest for gathering family history information (40.7%) and lowest for disclosing variants of uncertain significance or positive results (2.5%).
rundown: The study surveyed 217 genetic counselors and students in North America about general and clinical genetics chatbot use, confidence, and perceived benefits and limitations.

Results showed a gap between general AI use and clinical adoption, with only 18 of 204 reporting clinical use, primarily for family communication and education, alongside confidence gradients by task.

Respondents flagged benefits for efficiency but also risks around comprehension and accuracy, with only 8.2% reporting prior AI training, suggesting need for structured education before wider implementation.
sources:
- peer_reviewed | Journal of Genetic Counseling | https://doi.org/10.1002/jgc4.70296 | 2026-10-01
prev: 0000000000000000000000000000000000000000000000000000000000000000
sha256
bc2ff4e1a530c596fca3a3e86a524fb286a495595e48248a0f5d283d34168dc7
previous
0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-1236 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.