TRV-2026-1280Certified recordPeer-reviewed

Applications and performance of imaging artificial intelligence in detecting and staging avascular necrosis of the femoral head: a systematic review and meta-analysis

Objective To evaluate the diagnostic accuracy of imaging artificial intelligence (AI) models for detecting avascular necrosis of the femoral head (AVNFH) and to examine whether diagnostic performance differs according to imaging modality, disease-stage focus, and validation strategy. Materials and methods In accordance with PRISMA-DTA, we conducted a systematic search in four main databases. Two independent reviewers evaluated the studies, extracted relevant data, and assessed the quality following the QUADAS-2…

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

Current reading — gain

Imaging AI models achieved high pooled diagnostic accuracy for detecting avascular necrosis of the femoral head in research datasets.

Current reading — problem

Risk of bias, heterogeneity, and limited external testing restrict confidence that reported accuracy will translate to routine clinical use.

What this doesn’t fix

Confidence in clinical applicability is limited by risk of bias, between-study heterogeneity, and sparse external testing, with only five external test-set estimates in primary analysis.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1280, v1: “Applications and performance of imaging artificial intelligence in detecting and staging avascular necrosis of the femoral head: a systematic review and meta-analysis.” Truvace, 2026-10-05. /record/TRV-2026-1280 (accessed at citation time). sha256 e5cea0f3f722c1a9…

Calibration history

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

  1. Certifiedv1e5cea0f3f722…

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