TRV-2026-1622Certified recordPeer-reviewed

Artificial Intelligence-Assisted Current Procedural Terminology Coding in Pediatric Orthopaedic Surgery: Promise or Premature?

Background: Accurate assignment of Current Procedural Terminology (CPT) codes is essential for reimbursement, compliance, and quality reporting in pediatric orthopaedic surgery. Manual coding remains resource-intensive and prone to error and variability. Large language models (LLMs) represent a potential solution for automating CPT assignment directly from operative documentation. This study evaluated the performance of ChatGPT-4o and ChatGPT-5 in generating accurate CPT codes from deidentified pediatric orthopa…

Health · The Trace — both readings · certified 2026-10-16 · v1 · article view · machine-readable

Current reading — gain

On 20 pediatric orthopaedic operative notes, ChatGPT-5 raised exact-match CPT coding accuracy to 60% from 30% for ChatGPT-4o, supporting use as a supervised first-pass coding aid.

Current reading — problem

Even the better model overcoded 25% and undercoded 30% of cases, leaving error rates above acceptable thresholds for unsupervised billing deployment.

What this doesn’t fix

The study used only 20 notes from one institution's case mix, and the authors state that larger-scale validation and integration studies are needed before broader implementation.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1622, v1: “Artificial Intelligence-Assisted Current Procedural Terminology Coding in Pediatric Orthopaedic Surgery: Promise or Premature?.” Truvace, 2026-10-16. /record/TRV-2026-1622 (accessed at citation time). sha256 1b355f511ea0c856…

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv11b355f511ea0…

    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-1622 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.