TRV-2026-1917Certified recordPeer-reviewed

From innovation to implementation: a global scoping review of artificial intelligence applications, governance, and challenges in humanitarian contexts

Background: Artificial intelligence (AI) is increasingly being explored as a tool for supporting humanitarian action through hazards and crisis prediction, real time monitoring of evolving crisis conditions and humanitarian needs, resource allocation, and decision-making. However, evidence on how AI is implemented, evaluated, and governed across humanitarian contexts remains fragmented. In this scoping review, we mapped the global evidence on the application of AI in humanitarian settings, including its distribu…

Policy · Problem Space — documented harm · certified 2026-10-19 · v1 · article view · machine-readable

Current reading — problem

Most reported humanitarian AI systems are still prototypes or retrospectively validated models, few are deployed in the field, and community participation, equity, and governance frameworks are inconsistently reported.

What this doesn’t fix

The evidence base is fragmented and dominated by prototypes and retrospectively validated models, so the review cannot show how AI performs in real operational humanitarian deployments.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1917, v1: “From innovation to implementation: a global scoping review of artificial intelligence applications, governance, and challenges in humanitarian contexts.” Truvace, 2026-10-19. /record/TRV-2026-1917 (accessed at citation time). sha256 99c3bd9465316860…

Calibration history

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

  1. Certifiedv199c3bd946531…

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