TRV-2026-1003Certified recordPeer-reviewed

Artificial Intelligence Accurately Assists in Billing for Orthopaedic Lower Extremity Surgery: Performance of the Mistral-NeMo Language Model

Purpose To elucidate Mistral-NeMo's proficiency as a novel artificial intelligence assistant to verify coding accuracy and improve efficiency in manual medical coding practices in orthopaedic surgery. Methods This study tested Mistral-NeMo on 1000 operative notes labeled with the Current Procedural Terminology (CPT) codes from 177 providers. In total, there were 46 unique CPT codes; the most common were 29881 (knee arthroscopy with meniscectomy for both medial and lateral menisci), 29880 (knee arthroscopy with m…

Health · The Trace — both readings · certified 2026-09-07 · v2 · article view · machine-readable

Current reading — gain

Mistral-NeMo verified orthopaedic lower-extremity billing by correctly identifying 90% of true CPT codes and rejecting 99.8% of incorrect codes when provided with billing descriptions.

Current reading — problem

Mistral-NeMo's high CPT-code accuracy was observed only when billing descriptions were included in the prompt, leaving performance without them untested.

What this doesn’t fix

Performance depended on contextual information and was insignificant without billing descriptions, limiting use on operative notes alone.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1003, v2: “Artificial Intelligence Accurately Assists in Billing for Orthopaedic Lower Extremity Surgery: Performance of the Mistral-NeMo Language Model.” Truvace, 2026-10-26. /record/TRV-2026-1003 (accessed at citation time). sha256 e383f5240a6007a5…

Calibration history

Every change to this record since certification, in the open.

  1. Revisedv2e383f5240a60…

    Direction audit: the problem line described the method, not an outcome; restated as the finding.

  2. Certifiedv1b2ef82ff6a5b…

    Certified into the record

Verify this record
How to verify without trusting this page

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