CorePulse Case Study / AI CPT Code Matching, Orthopedic Surgery

When the short descriptor lies, read the long descriptor.

The short answer: on complex foot and ankle procedures, the CPT short descriptor is often the same word for six different codes, and that is exactly where manual coding slips. CorePulse reads the operative note line by line against the full AMA CPT long descriptors, surfaces the one code whose long descriptor the note actually satisfies, and shows it side by side with the coder's pick so a human confirms before anything bills. The coder stays in control. The trap gets caught earlier.

Long

Descriptor read, not short

6→1

Bunion family disambiguated

Suggest

Never a silent override

FY2026

Guideline-anchored

// the failure mode

One short descriptor. Six codes. The note is the tiebreaker.

Take a hallux valgus correction. Every code in the family reads as some version of "bunionectomy" at a glance. The detail that decides the code lives in the AMA long descriptor, and it only resolves once you read what the surgeon actually did to the bone.

What the short descriptor shows

28296 · "Bunionectomy"

28292 · "Bunionectomy"

28298 · "Bunionectomy"

Coding off the short list, three codes look interchangeable. A pick made on habit or the last chart is a coin flip, and the denial or downcode shows up weeks later.

→

What the long descriptor decides

28296 — Correction, hallux valgus, with distal metatarsal osteotomy, any method

28292 — ...with resection of proximal phalanx base, when performed, any method

28298 — ...with proximal phalanx osteotomy, any method

The op note says "Chevron osteotomy of the distal first metatarsal." Only 28296 matches. CorePulse anchors the pick to that phrase in the long descriptor and points the coder straight at the sentence.

// side-by-side comparison matrix

CorePulse vs the manual pick, on six foot and ankle traps

Each row is a real place where the short descriptor hides the answer. Read left to right: the signal in the note, the code a rushed short-descriptor read tends to land on, the code the long descriptor actually supports, and the guideline that governs it.

Signal in the operative note	Short-descriptor trap	CorePulse long-descriptor match	Guideline anchor
Chevron (Austin) osteotomy of the distal first metatarsal with screw fixationHallux valgus correction	28292 or 28298 Base resection / phalanx osteotomy, wrong bone site	28296 "with distal metatarsal osteotomy, any method" phrase-matched	AMA CPT long descriptor
PIP interphalangeal fusion, second toeHammertoe correction	28286 Cock-up fifth toe (Ruiz-Mora), different procedure	28285 "(eg, interphalangeal fusion, partial or total phalangectomy)" phrase-matched	AMA CPT long descriptor
Subtalar joint only fused; midtarsal joints preservedHindfoot arthrodesis	28715 Triple arthrodesis, overstates joints fused	28725 "Arthrodesis; subtalar" joint-count checked	AMA CPT long descriptor + NCCI PTP (adjacent-joint prep bundling)
Strayer recession at the musculotendinous junction of the gastrocnemiusHeel-cord lengthening	27685 or 27606 Tendon lengthening / percutaneous tenotomy	27687 "Gastrocnemius recession (eg, Strayer procedure)" phrase-matched	AMA CPT long descriptor
Hallux valgus, documented left footDiagnosis coding	M20.10 Unspecified laterality, avoidable non-specificity	M20.12 Left; matched to the correct code year for the date of service laterality retained	ICD-10-CM Official Guidelines FY2026
Bunionectomy and hammertoe correction, same session, separate digit/siteMulti-procedure claim	Both lines, no edit review Or a reflex modifier 59 with nothing behind it	Flags the PTP pair Suggests 59 / anatomic X-modifier only when a distinct site is documented, never as a default documentation-gated	NCCI PTP edits + CMS PFS global surgical package

Illustrative cases built from public AMA CPT descriptors and the cited 2026 guidelines. Codes shown for method illustration, not as coding advice for a specific claim.

// how the match happens

Five steps from operative note to a confirmable suggestion

De-identify

PHI is stripped at the boundary before any model call. No identified note leaves the workflow.

Extract signals

The procedure sentences, anatomy, laterality, and method are pulled from the note.

Read long descriptors

Signals are matched against full CPT long descriptors, not the short list, so bone site and technique decide the code.

Run the guardrails

NCCI PTP pairs, the global package, and ICD-10-CM specificity rules run before anything is offered.

Show, don't override

The suggestion lands next to the coder's pick with the matched descriptor phrase. A human confirms.

// what it is anchored to

Cited by name, kept current for 2026

Descriptor matching is only as good as the rulebook behind it. CorePulse ties every suggestion to a named, current source.

AMA CPT

Full long descriptors are the matching target, not the short display strings that make the family look identical.

Current CPT code set

CMS PFS

Physician Fee Schedule global surgical package rules govern what is already included in the primary procedure.

CY2026 final rule

NCCI

Procedure-to-procedure edits are checked on the complete claim; a modifier is suggested only when documentation supports it.

Quarterly PTP edits, 2026

ICD-10-CM

Laterality and specificity follow the Official Guidelines for Coding and Reporting, matched to the date of service.

FY2026, effective Oct 1 2025

Catch the descriptor trap before it becomes a denial

CorePulse does not replace your coders. It reads every complex foot and ankle note against the full CPT long descriptors, runs the NCCI and CMS PFS guardrails, and hands your team a confirmable second read anchored to the exact phrase that decides the code. Fewer downcodes, cleaner first-pass claims, and a defensible trail on every suggestion.

See CorePulse on your own charts →

ASP-RCM Solutions · orthopedic and surgical coding, built inside your RCM workflow