TRV-2026-1503Version 1 · Certified

Written 2026-10-15 22:02:36 UTC · current record

Reason for this version

Certified into the record

Canonical text (the exact bytes fingerprinted)

TRUVACE RECORD VERSION
record: TRV-2026-1503
version: 1
kind: certified
reason: Certified into the record
timestamp: 2026-10-15T22:02:36.125024Z
status: published
lens: trace
sector: education
headline: Medical students' appraisal of curated AI answers in a cardiovascular system course
dek: Study objective: The purpose of this study is to evaluate medical student perspective of AI-curated responses through qualitative feedback and assessment of accuracy and helpfulness.
Design: First, students submitted questions about course content. Next, these questions were inputted into OpenEvidence. Finally, generated responses were edited by investigators and evaluated by students and faculty.
Main outcome measures: The primary outcome of this study was the accuracy, helpfulness, and qualitative feedback for…
gain_title: Students generally rated AI-curated answers to their own cardiovascular course questions as helpful.
problem_title: Students had difficulty grading the accuracy of the AI answers, which were also seen as overly detailed and lacking visual explanations.
trace_subject: Medical student use of OpenEvidence-generated answers in a cardiovascular system course
gain_reading: Students generally rated AI-curated answers to their own cardiovascular course questions as helpful.
gain_evidence: students found most AI responses to be helpful
problem_reading: Students had difficulty grading the accuracy of the AI answers, which were also seen as overly detailed and lacking visual explanations.
problem_evidence: Students also noted difficulty in grading the accuracy of AI responses | AI responses were often too detailed and lacked visual explanations
quick_read: Students in a cardiovascular system course submitted questions about the material, which investigators ran through the OpenEvidence tool. The generated answers were edited by investigators and then rated by students and faculty for accuracy and helpfulness, with students also giving written feedback.

The findings suggest AI answers can serve as a useful study aid, yet students' own difficulty in verifying accuracy is a concern when learners rely on such tools. The excerpt does not give numerical ratings or faculty accuracy results, so how correct the answers actually were remains unclear.
limitation: Responses were edited by investigators before evaluation, and the summary gives no quantitative results, so the findings may not reflect unedited AI output or measured accuracy.
tag: Dual reading
key_points: The study used questions submitted by medical students about cardiovascular course content. | Questions were entered into OpenEvidence and the responses were edited by investigators before evaluation. | Students and faculty both evaluated the responses for accuracy and helpfulness. | Most responses were judged helpful, but students said they were often too detailed. | Students reported that responses lacked beneficial visual diagrams and found accuracy hard to assess.
rundown: The research followed a three-step design: collecting student questions, generating answers with OpenEvidence, and having investigators edit them before students and faculty evaluated them. The primary outcomes were accuracy, helpfulness, and qualitative feedback.

The reported results were mixed. Helpfulness ratings were generally positive, but the authors conclude that significant shortcomings exist, including excessive detail, absent visual explanations, and students' trouble in judging whether answers were accurate.
sources:
- peer_reviewed | American Heart Journal Plus: Cardiology Research and Practice | https://doi.org/10.1016/j.ahjo.2026.100924 | 2026-09-30
prev: 0000000000000000000000000000000000000000000000000000000000000000
sha256
3cadd0365ef2c7a22634892f01275d1b857e4edddbe32d3d323a374afd86ab80
previous
0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page

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