TRV-2026-1490Certified recordPeer-reviewed

Artificial Intelligence in Eye Disease: A Systematic Review of Screening, Diagnosis, Prognosis, Treatment-Response Prediction, and Clinical Decision Support

Background/Objectives: Artificial intelligence (AI) is expanding eye care beyond image-based detection toward prognosis, treatment-response prediction, monitoring, triage, and clinician-facing decision support. We evaluated AI across eye-disease screening, diagnosis, prognosis, treatment response, and decision support, emphasizing validation, explainability, and clinical readiness. Methods: This PROSPERO-registered review followed the Preferred Reporting Items for Systematic Reviews and Meta-Analyses (PRISMA) 20…

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

Current reading — problem

Eye-disease AI is not yet clinically ready: independent validation is incomplete, direct clinician comparators are scarce, and safety, workflow and patient-outcome evidence is sparse.

What this doesn’t fix

Heterogeneity precluded meta-analysis, and the authors report incomplete independent validation, few direct comparators and sparse evaluation of safety, workflow effects and patient outcomes.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1490, v1: “Artificial Intelligence in Eye Disease: A Systematic Review of Screening, Diagnosis, Prognosis, Treatment-Response Prediction, and Clinical Decision Support.” Truvace, 2026-10-15. /record/TRV-2026-1490 (accessed at citation time). sha256 9e37524a4057909f…

Calibration history

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

  1. Certifiedv19e37524a4057…

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