Auto-Coding ICD-10 for Diabetic Foot Ulcers: How the Diagnosis Engine Works

Diabetic foot ulcer coding is where most wound care documentation platforms stop being useful. Getting E11.621 paired with the correct L97.4xx or L97.5xx requires laterality, exact site, and depth — all of which have to come from the note. Here's how WoundScribe's coding agent handles it.

From narrative to structured findings

When you dictate 'non-healing ulcer on the plantar aspect of the right great toe, exposed subcutaneous fat, no bone visible,' the scribe agent extracts:

• Body site: right great toe, plantar
• Depth: fat layer exposed
• Etiology signals: diabetes history, neuropathy, prior DFU
• Complication signals: drainage, odor, probe-to-bone result

Mapping to ICD-10 with specificity

Those structured findings resolve to E11.621 (Type 2 diabetes mellitus with foot ulcer) plus L97.512 (non-pressure chronic ulcer of other part of right foot with fat layer exposed). Laterality and depth are never guessed — if the note doesn't state them, the agent asks before finalizing.

Suspected vs. confirmed complications

Probe-to-bone positive with exposed bone doesn't automatically become M86.171. The agent codes the documented ulcer with bone exposed (L97.5x3) and flags 'suspected osteomyelitis' as a working diagnosis pending imaging — matching how payers expect the record to read.

Linking to charges

Each diagnosis carries forward to the superbill and links to the specific CPT it supports: the ulcer code supports the debridement, the diabetes code supports the E/M complexity, the neuropathy code supports the offloading. See how this ties into diabetic foot care end-to-end.

Why the note has to drive the code

Audits work backwards from the claim to the record. When the AI scribe for wound care builds the code from your own words, there's no gap between what you documented and what was billed — which is the whole point.