TRV-2026-2005Certified recordPeer-reviewed

Differential-fusion YOLO for MB2 canal detection and recognition in cone-beam computed tomographic images

This study aimed to develop and validate an artificial intelligence (AI)-based system, called Differential-Fusion YOLO (DF-YOLO), for MB2 canal detection and recognition in cone-beam computed tomography (CBCT) images. DF-YOLO is a dual-branch convolutional architecture that integrates differential feature extraction with adaptive fusion to highlight subtle anatomical variations between adjacent slices. A clinical CBCT dataset comprising 148 microscopically confirmed MB2-positive cases (7,804 axial slices) was re…

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

Current reading — gain

The DF-YOLO model detected MB2 canal structures on CBCT slices with 87.4% recall and, in an exploratory patient-level test, 93.8% sensitivity, and it ran faster than manual slice annotation.

Current reading — problem

In the exploratory patient-level analysis, specificity was only 60.0% in a small MB2-negative cohort, so the model may flag canals in cases without them.

What this doesn’t fix

The study is retrospective with small test and reader datasets and few negative cases. It lacks external validation, so the authors say it is not ready for clinical implementation.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-2005, v1: “Differential-fusion YOLO for MB2 canal detection and recognition in cone-beam computed tomographic images.” Truvace, 2026-10-20. /record/TRV-2026-2005 (accessed at citation time). sha256 13ae68a053fcca0c…

Calibration history

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

  1. Certifiedv113ae68a053fc…

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