TRV-2026-1637Certified recordPeer-reviewed

Artificial intelligence ethical awareness and academic integrity among medical students at the University of Khartoum: a cross-sectional study

Integration of artificial intelligence in healthcare and medical education implies significant opportunities along with significant ethical challenges. Despite the substantial medical student uptake of artificial intelligence globally, little comprehensive assessments of ethical awareness are being conducted. This study aimed to assess artificial intelligence awareness and academic integrity level among University of Khartoum medical students and to examine relationships between the awareness level, demographic…

Health · The Trace — both readings · certified 2026-10-17 · v1 · article view · machine-readable

Current reading — gain

Students showed moderate ethical awareness overall, with privacy and data protection scoring highest (median 4.67), suggesting a solid base in some areas of AI ethics.

Current reading — problem

Formal AI instruction is minimal for most students, and awareness of transparency and fairness is weakest, so ethical competence depends largely on informal exposure.

What this doesn’t fix

The sample was recruited by convenience sampling with quota allocation at a single institution, and the authors say longitudinal research is needed to track how AI ethics awareness evolves during training.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1637, v1: “Artificial intelligence ethical awareness and academic integrity among medical students at the University of Khartoum: a cross-sectional study.” Truvace, 2026-10-17. /record/TRV-2026-1637 (accessed at citation time). sha256 dec5070b333617a0…

Calibration history

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

  1. Certifiedv1dec5070b3336…

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