TRV-2026-1634Version 1 · Certified

Written 2026-10-17 01:09:05 UTC · current record

Reason for this version

Certified into the record

Canonical text (the exact bytes fingerprinted)

TRUVACE RECORD VERSION
record: TRV-2026-1634
version: 1
kind: certified
reason: Certified into the record
timestamp: 2026-10-17T01:09:05.174116Z
status: published
lens: g_space
sector: health
headline: Deep Learning-Based Scapular Morphology Assessment Pipeline for Glenoid Segmentation and Landmark Localization
dek: Scapular morphology plays a critical role in the diagnosis and treatment of shoulder disorders. However, current assessment methods primarily rely on manual annotation of three-dimensional computed tomography (3D CT) scans by clinicians, which are time-consuming, labor-intensive, and prone to inter-observer variability. The objective of this study is to develop and validate a deep learning-based open-source pipeline for automated scapular morphology assessment, aiming to improve accuracy, reproducibility, and cl…
gain_title: On retrospective shoulder CT data, the pipeline segmented the glenoid with high overlap and placed five scapular landmarks within 1.0 to 2.0 mm on average. Each case took about 22.55 seconds, versus slow manual annotation.
problem_title: (none)
trace_subject: (none)
gain_reading: On retrospective shoulder CT data, the pipeline segmented the glenoid with high overlap and placed five scapular landmarks within 1.0 to 2.0 mm on average. Each case took about 22.55 seconds, versus slow manual annotation.
gain_evidence: The glenoid segmentation model achieved a 3D Dice coefficient of 98.46% | The mean Euclidean localization error for the five scapular landmarks ranged from 1.0 to 2.0 mm. | The entire assessment process took average 22.55 s per case.
problem_reading: (none)
problem_evidence: (none)
quick_read: Researchers built an open-source deep learning pipeline that analyzes shoulder CT scans. One model outlines the glenoid, the socket of the shoulder blade, and a second model locates five anatomical landmarks on the scapula. The system was tested on 793 CT images from 774 patients collected retrospectively.

Scapular shape informs how shoulder disorders are diagnosed and treated, and manual measurement is slow and varies between observers. A fast, reproducible tool could ease that burden. The reported results come from a laboratory study of retrospective scans, so benefit in routine care is not yet shown.
limitation: 
tag: Evidence-backed gain
key_points: The dataset contained 793 shoulder CT images from 774 patients with a mean age of 60.00 ± 18.62 years. | A 2D U-Net handled glenoid segmentation on native-resolution axial slices with no down-sampling. | A 3D nnUNet located five landmarks: trigonum spinae, angulus inferior, processus coracoideus, acromion, and angulus acromialis. | Glenoid segmentation reached 96.59% precision and 97.30% recall alongside the 98.46% Dice score.
rundown: Current practice relies on clinicians manually annotating three-dimensional CT scans. The authors describe this as time-consuming, labor-intensive, and prone to inter-observer variability, which motivated an automated approach.

The pipeline pairs two models. A 2D U-Net segments the glenoid at full resolution, and a 3D nnUNet predicts the positions of five scapular landmarks. Performance was judged by Dice, precision and recall for segmentation, and by Euclidean distance from ground truth for landmarks.

The authors designed it as an open-source framework that can be integrated into clinical workflows or research environments through a clinician-preferred user interface. The study is classed as a descriptive laboratory study, level of evidence 2.
sources:
- peer_reviewed | Journal of Imaging Informatics in Medicine | https://doi.org/10.1007/s10278-026-02385-1 | 2026-10-09
prev: 0000000000000000000000000000000000000000000000000000000000000000
sha256
3938793e8d8bb434678792bd24c2985b6086e52d0d641cb897b04c8447d4de62
previous
0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-1634 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.