Certified into the record
The exact text we saved
This is the version exactly as it was saved, character for character. The SHA-256 hash below is a 64-character code worked out from that text. Run the same text through SHA-256 and you get the same code; change a single letter and the code comes out completely different. Each version also stores the previous version’s hash, which chains them together so no version can be swapped out quietly.
TRUVACE RECORD VERSION record: TRV-2026-1176 version: 1 kind: certified reason: Certified into the record timestamp: 2026-09-23T06:53:39.340098Z status: published lens: g_space sector: health headline: Diagnostic accuracy & clinical importance of AI confidence for extremity fracture detection: 2,508-patient retrospective cohort dek: Purpose To estimate diagnostic performance of a deep learning algorithm for extremity fracture detection on radiographs in patients aged ≥ 2 years using a refined reference standard. Secondary, to compare positive predictive value (PPV) by the algorithm's built-in confidence level (high vs. low) and diagnostic performance between adults (≥ 18 years) and children. Methods This retrospective single-center study consecutively included patients with radiography of a suspected extremity fracture between January and D… gain_title: PPV for high-confidence was superior to low-confidence detections (99.1% vs 59.1%, p Conclusion The algorithm showed good diagnostic performance for extremity fracture detection on radiographs. problem_title: (none) trace_subject: (none) gain_reading: PPV for high-confidence was superior to low-confidence detections (99.1% vs 59.1%, p Conclusion The algorithm showed good diagnostic performance for extremity fracture detection on radiographs. gain_evidence: (none) problem_reading: (none) problem_evidence: (none) quick_read: Purpose To estimate diagnostic performance of a deep learning algorithm for extremity fracture detection on radiographs in patients aged ≥ 2 years using a refined reference standard. Secondary, to compare positive predictive value (PPV) by the algorithm's built-in confidence level (high vs. low) and diagnostic performance between adults (≥ 18 years) and children. The index test was the algorithm output (bounding boxes with confidence). Sensitivity, specificity, PPV and negative predictive value (NPV) were calculated with 95% confidence intervals; differences were tested using the McNemar and a score test and patient-clustered logistic regression. limitation: tag: Evidence-backed gain key_points: Purpose To estimate diagnostic performance of a deep learning algorithm for extremity fracture detection on radiographs in patients aged ≥ 2 years using a refined reference standard. | Secondary, to compare positive predictive value (PPV) by the algorithm's built-in confidence level (high vs. low) and diagnostic performance between adults (≥ 18 years) and children. | Methods This retrospective single-center study consecutively included patients with radiography of a suspected extremity fracture between January and December 2024. rundown: Purpose To estimate diagnostic performance of a deep learning algorithm for extremity fracture detection on radiographs in patients aged ≥ 2 years using a refined reference standard. Secondary, to compare positive predictive value (PPV) by the algorithm's built-in confidence level (high vs. low) and diagnostic performance between adults (≥ 18 years) and children. Methods This retrospective single-center study consecutively included patients with radiography of a suspected extremity fracture between January and December 2024. The index test was the algorithm output (bounding boxes with confidence). sources: - peer_reviewed | Emergency Radiology | https://doi.org/10.1007/s10140-026-02546-3 | 2026-09-22 prev: 0000000000000000000000000000000000000000000000000000000000000000
- SHA-256 hash
- cc2d9e7d627a39d6b995125b884f9c49ee083daa7c0805d4671feab5034abe4e
- Previous version’s hash
- 0000000000000000000000000000000000000000000000000000000000000000
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-1176 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.
ace