TruaceTracing the truth around AIWednesday, August 26, 2026
TRV-2026-0017Version 1 · Certified

Written 2026-07-11 23:04:25 UTC · current record

Reason for this version

Certified into the record

Canonical text (the exact bytes fingerprinted)

TRUVACE RECORD VERSION
record: TRV-2026-0017
version: 1
kind: certified
reason: Certified into the record
timestamp: 2026-07-11T23:04:25.100895Z
status: published
lens: general
sector: health
headline: Real-World Impact and Educational Effectiveness of an AI-Powered Medical History-Taking System: Retrospective Propensity Score-Matched Cohort Study
dek: Background Medical history-taking is a core clinical skill; yet, traditional teaching methods face challenges. We developed an artificial intelligence–powered medical history-taking training and evaluation system (AMTES) and established its technical feasibility as an extracurricular resource. Evidence on whether such tools improve learning outcomes when voluntarily embedded in routine curricul...
gain_reading: Background Medical history-taking is a core clinical skill; yet, traditional teaching methods face challenges. We developed an artificial intelligence–powered medical history-taking training and evaluation system (AMTES) and established its technical feasibility as an extracurricular resource. Evidence on whether such tools improve learning outcomes when voluntarily embedded in routine curricul...
problem_reading: (none)
limitation: Machine-ingested summary: the claims above reflect a single primary source and have not been weighed against contradicting evidence by a Truvace editor yet.
tag: (none)
key_points: (none)
rundown: (none)
sources:
- peer_reviewed | JMIR Medical Education | https://doi.org/10.2196/89367 | 2026-02-24
prev: 0000000000000000000000000000000000000000000000000000000000000000
sha256
d29f0ef0554108fdc8c9a1be9068371772efe8f42a22e754fa5dcc8d3ab57bc9
previous
0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page

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