TRV-2026-1472Certified recordPeer-reviewed

Faculty-supervised AI-supported BOPPPS-CBL and performance on a simulated neurological-emergency assessment among junior-college medical interns: a batch-stratified randomized educational study

Background County hospitals and township health centers in China provide frontline care for time-sensitive neurological emergencies, and three-year junior-college clinical medicine programs are an important pathway into this workforce. We evaluated a faculty-supervised artificial intelligence (AI)-supported BOPPPS (Bridge-in, Objectives, Pre-assessment, Participatory Learning, Post-assessment, and Summary) and case-based learning (CBL) instructional package among junior-college medical interns. Methods In this p…

Health · Problem Space — documented harm · certified 2026-10-15 · v1 · article view · machine-readable

Current reading — problem

The AI-supported group reported a greater perceived preparation-time burden, and the study design could not rule out cueing or carry-over from reused case contexts.

What this doesn’t fix

The study was not prospectively registered, used a locally developed assessment with reused case contexts, and does not establish transfer to workplace clinical performance or patient outcomes.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1472, v1: “Faculty-supervised AI-supported BOPPPS-CBL and performance on a simulated neurological-emergency assessment among junior-college medical interns: a batch-stratified randomized educational study.” Truvace, 2026-10-15. /record/TRV-2026-1472 (accessed at citation time). sha256 fa33237177e3826b…

Calibration history

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

  1. Certifiedv1fa33237177e3…

    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-1472 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.