52/100

Moderate evidence

ProblemPublished recordHealthProblem Space

What Patients are Reading About Prenatal Cell-Free DNA: An Analysis of Leading Publicly Available AI-Chatbots

Truvace record
TRV-2026-2943raw data (JSON)
Version
v1Published
First published
Evidence type
Benchmark or lab evaluation
Sources
1 sourcePeer-reviewed
sha256
9548efceb476…check it

Objective: To characterize the quality, consistency, and framing of information about prenatal cell-free DNA (cfDNA) screening generated by publicly available chatbots, including variation across simulated user age profiles. Methods: We conducted a qualitative content analysis of outputs from three publicly available chatbots. To reduce carryover effects and personalization, prompts were entered using a VPN, private browsing, and cleared browser cookies. Outputs were generated using distinct simulated user age p…

The problem

In a qualitative analysis of three public chatbots, researchers found misinformation, frequent omission of cfDNA screening limitations, wording that sometimes confused screening with diagnosis, and few or no citations to high-quality sources.

What this doesn’t fix

The work was a qualitative content analysis of three chatbots using simulated user age profiles, not an assessment of real patients' questions or outcomes.

Sources

1 on file
  1. Prenatal Diagnosisdoi:10.1002/pd.70291
    Peer-reviewed2026-11-14

Cite this record

v1

Truvace Impact Record TRV-2026-2943, v1: “What Patients are Reading About Prenatal Cell-Free DNA: An Analysis of Leading Publicly Available AI-Chatbots.” Truvace, 2026-11-15. /record/TRV-2026-2943 (accessed on the day you copy it). sha256 9548efceb47609d8…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv19548efceb476…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-2943 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.