TRV-2026-2026Certified recordJournalism

Transparency, accountability, and scholarly integrity: A systematic narrative review of artificial intelligence governance frameworks in healthcare publication

Author summary Artificial intelligence is increasingly used in healthcare research, from developing clinical tools to helping prepare scientific papers. At the same time, many guidelines and policies have been created to tell researchers, journals, and reviewers how this work should be reported and managed. We reviewed this rapidly growing landscape to understand what guidance exists, how it has changed over time, and where important gaps remain. We identified 100 relevant publications, including 69 guidelines,…

Science · Problem Space — documented harm · certified 2026-10-20 · v1 · article view · machine-readable

Current reading — problem

Guidance for AI in healthcare research and publishing remains fragmented, varies in authority and development, and often covers disclosure at publication rather than responsibilities across an AI system's life.

What this doesn’t fix

The source states that the guidance landscape is fragmented, with documents varying in development and authority and often focusing on disclosure at publication rather than ongoing responsibilities.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-2026, v1: “Transparency, accountability, and scholarly integrity: A systematic narrative review of artificial intelligence governance frameworks in healthcare publication.” Truvace, 2026-10-20. /record/TRV-2026-2026 (accessed at citation time). sha256 3def127895a9be90…

Calibration history

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

  1. Certifiedv13def127895a9…

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