Measurements Automatically Extracted from Zero Echo Time MRI Using Deep Learning Image Segmentation and Geometric Modeling Agree with Expert Manual Readings

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

arXiv:2608.07368v1 Announce Type: cross Abstract: Computed tomography (CT) remains the reference for 3D osseous morphometry in femoroacetabular impingement (FAI) but requires ionizing radiation and manual measurement. Zero echo time (ZTE) MRI visualizes cortical bone and yields FAI angles that agree with CT, but automated angle extraction remains limited. We developed and validated automated FAI angle computation from ZTE MRI and assessed agreement with expert manual measurements in a cross-sectional study (level of evidence, 3). Pelvic ZTE MRI was acquired in 73 participants (mean age 36.8 +/- 18.5 years; 51 women, 22 men), yielding 135 hips. nnU-Net was trained on 100 manually curated hips to segment the femur, pelvis, and three osseous landmarks. Custom geometric algorithms computed alpha, femoral neck-shaft, Tonnis, coronal and sagittal center-edge, and acetabular version angles from inferred segmentations. Measurements on 35 test hips were compared with the mean of two radiologists' manual measures using intraclass correlation (ICC) and Bland-Altman analysis. Dice exceeded 0.96 for bone and ranged from 0.65 to 0.83 for landmarks. Median landmark error was 0.38 mm (femoral head), 0.82 mm (lateral acetabulum), and =0.82) but poor for alpha and femoral neck-shaft. Model versus rater-mean agreement was excellent for acetabular version, coronal center-edge, and Tonnis (0.92-0.96), good for mid-acetabular sagittal center-edge (0.74), and fair for alpha (0.45) and femoral neck-shaft (0.55). Model Bland-Altman limits of agreement were narrower than interrater limits for most …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://arxiv.org/abs/2608.07368
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.