TRV-2026-1796Version 1 · Certified
Reason for this version
Certified into the record
Canonical text (the exact bytes fingerprinted)
TRUVACE RECORD VERSION record: TRV-2026-1796 version: 1 kind: certified reason: Certified into the record timestamp: 2026-10-18T06:54:52.321393Z status: published lens: g_space sector: health headline: Automated Bergmann-Kliesch Score assessment in testicular biopsies using artificial intelligence-based whole-slide image analysis: a retrospective monocentric development and validation study dek: Background The Bergmann-Kliesch Score is a histopathological grading system used to evaluate spermatogenesis in testicular biopsies, quantifying the fraction of seminiferous tubules containing elongated spermatids. It serves as a key parameter in the clinical process of men with non-obstructive azoospermia (NOA) undergoing testicular sperm extraction (TESE) for subsequent intracytoplasmic sperm injection (ICSI). Manual Bergmann-Kliesch Score assessment is time-consuming and subject to inter- and intraobserver va… gain_title: An AI pipeline automated Bergmann-Kliesch Score assessment from biopsy slide images and agreed strongly with pathologist reference scores on a held-out test set of 15 patients. problem_title: (none) trace_subject: (none) gain_reading: An AI pipeline automated Bergmann-Kliesch Score assessment from biopsy slide images and agreed strongly with pathologist reference scores on a held-out test set of 15 patients. gain_evidence: AI-derived Bergmann-Kliesch Scores showed strong agreement with pathologist-assigned reference scores | the pipeline correctly classified all test-set cases problem_reading: (none) problem_evidence: (none) quick_read: Researchers at the University Medical Center Frankfurt built a two-model machine-learning pipeline to grade spermatogenesis in testicular biopsies. It analyzes digitized slides stained with haematoxylin-eosin and with OCT3/4 and produces a Bergmann-Kliesch Score automatically. The cohort was 74 retrospective patients who had testicular sperm extraction. The work matters because manual scoring is slow and varies between and within observers, and the score guides care for men with non-obstructive azoospermia. The evidence is still early. It comes from one center and a small test set, and it has not yet been linked to fertility treatment outcomes or checked externally. limitation: tag: Evidence-backed gain key_points: The cohort was 74 retrospective patients who underwent testicular sperm extraction at one German university medical center. | One U-Net model segmented seminiferous tubules on HE slides, with a multi-class Dice coefficient of 0.897 on the validation set. | A second model detected elongated spermatids on OCT3/4 slides, trained on 14,226 manually annotated cells. | On the 15-patient test set, Pearson r was 0.957 and mean absolute error was 0.93. | Across all 74 patients, agreement was lower but still robust: Pearson r 0.851 and mean absolute error 1.52. rundown: The pipeline segments tubules in HE-stained slides with a U-Net using a ResNet-34 backbone, trained on 60 slides. A second U-Net with the same backbone was trained on 15 OCT3/4-stained slides to find elongated spermatids. Rigid alignment and B-spline warping register the two stain types so spermatid detections can be projected onto the tubular segmentation. This lets the system estimate the fraction of tubules containing elongated spermatids, which is what the score measures. On the held-out test set, Spearman ρ was 0.856, R2 was 0.916 and root mean squared error was 1.28. At the clinical cutoff of a score of 1 or higher, all test cases were classified correctly. Across the full cohort, root mean squared error rose to 2.20. sources: - peer_reviewed | Basic and Clinical Andrology | https://doi.org/10.1186/s12610-026-00329-x | 2026-10-06 prev: 0000000000000000000000000000000000000000000000000000000000000000
- sha256
- 767464391b69fcc6cc734d09185ccf0ae89760c9295ac0fb066655fbb0fde2bc
- previous
- 0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page
Fetch the canonical text of any version from /api/record/TRV-2026-1796 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.
ace