TRV-2026-1613Certified recordPeer-reviewed

Clinician-Facing Artificial Intelligence-Based Clinical Decision Support Systems Evaluated in Real-World Health Care Settings: A PubMed/MEDLINE-Based, PMC-Weighted Scoping Review and Evidence Map

Background: Clinician-facing artificial intelligence-based clinical decision support systems (AI-CDSSs) are increasingly evaluated with real-world data, but evidence on implementation, human factors, responsible AI, and patient benefit remains unclear. The objective of this research is to map applications, technical characteristics, evaluation approaches, integration, outcomes, and implementation gaps of clinician-facing AI-CDSSs in real-world health care settings. Methods: PubMed/MEDLINE was searched on 15 June…

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

Current reading — problem

Among 1181 included reports on clinician-facing AI decision support, most stopped at clinical validation, and few evaluated implementation, safety, fairness or economics, so patient benefit is not yet demonstrated.

What this doesn’t fix

AI-assisted screening and charting received only targeted human review and quality control, and full-corpus dual-human screening was not performed, which limits confidence in the evidence map.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1613, v1: “Clinician-Facing Artificial Intelligence-Based Clinical Decision Support Systems Evaluated in Real-World Health Care Settings: A PubMed/MEDLINE-Based, PMC-Weighted Scoping Review and Evidence Map.” Truvace, 2026-10-16. /record/TRV-2026-1613 (accessed at citation time). sha256 1b728117693eabe4…

Calibration history

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

  1. Certifiedv11b728117693e…

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