30/100

Emerging evidence

ProblemPublished recordHealthProblem Space

A review of digital orthopedic techniques in pre- and intra-operative management of scaphoid fracture

Truvace record
TRV-2026-1259raw data (JSON)
Version
v3Revised
First published
Evidence type
Commentary, opinion, or narrative review
Sources
1 sourcePeer-reviewed
sha256
fcf627082196…check it

Digital orthopedics integrates artificial intelligence, finite element analysis, virtual surgical planning, intraoperative navigation, robotics, and three-dimensional printing into a precise, individualized workflow for scaphoid fracture management. Artificial intelligence-based algorithms achieve high diagnostic accuracy for scaphoid fractures on plain radiographs, aid in detecting occult fractures, and support treatment decisions. Three-dimensional fracture mapping and finite element analysis enable quantitati…

The problem

A review of digital tools for scaphoid fractures found navigation is limited by registration errors, and robot-assisted surgery by longer setup, high costs and a 10-20 case learning curve; evidence is mostly small series and cadaver studies.

What this doesn’t fix

Current evidence base is limited to small case series and cadaveric studies, with robotics supported predominantly by level IV evidence, requiring standardized protocols and high-quality comparative trials.

Sources

1 on file
  1. EFORT Open Reviewsdoi:10.1530/eor-2026-0084
    Peer-reviewed2026-10-01

Cite this record

v3

Truvace Impact Record TRV-2026-1259, v3: “A review of digital orthopedic techniques in pre- and intra-operative management of scaphoid fracture.” Truvace, 2026-11-05. /record/TRV-2026-1259 (accessed on the day you copy it). sha256 fcf6270821969db4…

Change history

3 versions

Every change made to this record since it was first published, and why.

  1. Revisedv3fcf627082196…

    Voice pass: plainer wording and study attribution; no facts or figures changed.

  2. Revisedv212f679008fe1…

    Editorial pass: sharper headline; gain/problem restated as concrete outcomes; refiled trace to p_space (gain unsupported, problem outcome).

  3. Publishedv13e93d4a304e0…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-1259 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.