ICD-10 code T31.22: Burns involving 20-29% of body surface with 20-29% third degree burns

ICD-10 code T31.22 covers burns across 20-29% of total body surface area (TBSA), with 20-29% of the body surface burned to full thickness. It is a billable, specific ICD-10-CM code, valid for HIPAA-covered transactions in the FY2026 edition effective October 1, 2025.

Two numbers decide the code, and each has to be documented on its own. The first is the total burned surface. The second is the full-thickness share of it. A note that records the total but skips the depth split cannot support T31.22 over T31.21 or T31.20.

Found our content helpful?

Key takeaways

ICD-10 code T31.22 classifies burns covering 20-29% TBSA with a 20-29% third-degree (full-thickness) component, distinct from the site-specific T20-T25 codes used alongside it.

T31.22 is billable and valid for HIPAA-covered transactions in the FY2026 ICD-10-CM edition, effective October 1, 2025.

T31.20 covers a 0-9% third-degree component and T31.21 covers 10-19%. Only T31.22 applies once the third-degree share reaches 20-29%.

CMS guidelines generally require T31 codes as additional codes when site-specific T20-T25 codes are already assigned. Documentation has to capture total TBSA and the third-degree percentage separately.

Practice management software like Pabau helps burn care teams submit T31.22 claims accurately and track denials before they age into write-offs.

Official description and billable status

The full official description of ICD-10 code T31.22 is “Burns involving 20-29% of body surface with 20-29% third degree burns”. It is a billable, specific ICD-10-CM diagnosis code. According to the CDC/NCHS ICD-10-CM coding tool, the code is valid for HIPAA-covered claim submissions in the 2026 edition, effective October 1, 2025.

The code sits in chapter 19 of ICD-10-CM, which covers injury, poisoning and certain other consequences of external causes (S00-T88). Because T31.22 describes burn extent rather than burn site, it is most often assigned as an additional code alongside a site-specific T20-T25 code. The sequencing section below sets out when that changes.

Where T31.22 sits in the T31 hierarchy

T31.22 is a fifth-character code within the T31 burn-extent category. Knowing where it sits makes the adjacent codes easier to navigate. The CMS ICD-10-CM code files publish the full parent-child structure each fiscal year, and the table below runs from chapter down to code.

The rest of the ICD-10-CM code library follows the same parent-child logic used across injury codes. The category names the condition, the subcategory sets the extent band, and the fifth character pins the third-degree percentage. A coder who treats T31.2 as billable will see it rejected at the clearinghouse, because the fifth character is missing.

What T31.22 means: TBSA and third-degree classification

T31.22 uses a two-axis classification. The first axis is the total TBSA affected, at 20-29% across all burn depths. The second is the third-degree (full-thickness) share of the body surface, also at 20-29%. Both have to be captured independently in the clinical record before the code can be assigned.

Take a patient with burns covering 25% TBSA, of which 22% are full-thickness and 3% are partial-thickness. That chart qualifies for T31.22. A patient with 25% TBSA burns but only 15% third-degree burns falls into T31.21 instead. The note has to state both percentages separately for the assignment to hold under audit.

How TBSA is calculated

Clinicians calculate TBSA using the Rule of Nines or the Lund-Browder chart, and patient age decides which one. The Rule of Nines is the standard adult tool. The Lund-Browder chart adjusts for the proportionally larger head and smaller limbs in pediatric patients. According to the AAPC ICD-10-CM code reference, coders should verify which clinical tool the burn assessment note used before assigning a T31 extent code.

Rule of nines and burn extent documentation

The Rule of Nines divides the adult body into regions, each representing a fixed percentage of TBSA. Which regions are documented decides whether the total lands in the 20-29% range that T31.22 requires.

• Head and neck: 9% TBSA
• Each upper extremity (arm): 9% TBSA (18% combined)
• Anterior trunk: 18% TBSA
• Posterior trunk: 18% TBSA
• Each lower extremity (leg): 18% TBSA
• Perineum: 1% TBSA

A burn covering the anterior trunk (18%) plus one arm (9%) reaches 27% TBSA, which puts the patient in the T31.2x subcategory. Other combinations land just outside the band, and that is where the wrong subcategory tends to get picked.

Pediatric patients need the Lund-Browder adjustment. Applying adult Rule of Nines percentages to a child overestimates the head-and-neck contribution and underestimates the legs. The total then lands in the wrong extent band.

T31.22 vs T31.20 and T31.21

The three sibling codes under T31.2x share the same total TBSA band and differ only by third-degree share. This is the most common differentiation point for burns in this extent range, and picking the wrong sibling is a frequent denial trigger. Payers validate the code against the third-degree percentage recorded in the operative or burn assessment report.

T31.22 is the right code when full-thickness destruction runs across 20-29% of body surface. When the record puts full-thickness damage under 10%, the claim goes out with T31.20 instead. Confirm the T31.2 subcategory in the tabular list before you resolve the fifth character, because an error in either direction produces a miscoded claim.

T31.22 vs T20-T25 burn codes: when to use each

T31.22 and the T20-T25 site-specific codes answer different questions and are frequently used together on the same claim. T20-T25 codes identify where a burn sits and the depth at that site. T31.22 identifies how much of the body surface is burned and how much of it is full-thickness. The ICD-10-CM Official Guidelines for Coding and Reporting, Section I.C.19, published by CMS, assign T31 codes as additional codes when the burn site is specified.

Official coding guidelines for burn extent codes

Section I.C.19 of the ICD-10-CM Official Guidelines for Coding and Reporting governs burn code sequencing. Five rules matter most on a T31.22 claim.

• When the burn site is documented, assign the corresponding T20-T25 code first.
• Assign T31.22 as an additional code to report total TBSA and the third-degree proportion.
• T31.22 may be the principal diagnosis when the burn site is not specified, or when burn extent is the primary reason for the encounter. Inpatient monitoring of a patient transferred from another facility is the usual example.
• When multiple sites are burned at different depths, sequence the code for the most severe depth first.
• Assign a separate code for each distinct burn site, rather than combining several sites under one T20-T25 code.

Electronic submission adds one more check before the payer sees the claim. A clearinghouse carrying an ICD-10-CM catalogue can flag an unsupported code pairing at the point of submission. Claims software for coders then records the denial reason code on every returned claim. A repeat T31 sequencing mistake reads as a pattern rather than a one-off.

Excludes notes and the corrosion boundary

T31.22 inherits its exclusion notes from the T31 parent category, and they apply to every T31.2x code. Both are worth checking before the code goes on the claim.

• Excludes1 (T31 category): Corrosions classified by extent of body surface involved belong in T32, not T31, even when the TBSA extent matches. A chemical burn coded to T31.22 is an inaccurate code and a potential audit target.
• Applicable to (T31 category): Burns classified according to the percentage of total body surface involved. T31 applies when body surface extent is the organizing clinical fact.

Corrosion codes in T32 follow the same two-axis structure as T31, with an extent band plus a third-degree proportion. So a chemical injury across 20-29% TBSA with 20-29% full-thickness involvement is coded T32.22, not T31.22. Confusing thermal burns with corrosions is a known audit trigger, which is why a burn agent check belongs in the process before code assignment.

Documentation requirements for the claim

T31.22 needs specific clinical documentation before it can be assigned, and vague charting such as “extensive burns to upper body” will not carry it. Coders should confirm five elements in the record before submission.

1. Total TBSA percentage: A numeric percentage, not a range or a descriptor, taken from the Rule of Nines or the Lund-Browder chart. It belongs in the burn assessment note or the operative report.
2. Third-degree (full-thickness) percentage: A separate numeric percentage for the full-thickness portion. This is the second axis of T31.22, and it cannot be inferred from the overall TBSA figure.
3. Burn depth classification by site: Each burned area classified by depth, which supports the T20-T25 site code and the T31.22 extent code together.
4. Burn agent: Confirmation that the cause is thermal rather than chemical. A corrosive agent moves the claim to T32.22.
5. Assessment method: Whether adult Rule of Nines or pediatric Lund-Browder was used. Payers and auditors sometimes ask for this to confirm the calculation was age-appropriate.

A T31.22 claim submitted without any one of these is exposed to denial. Building the checks into the pre-submission review catches the deficiency before the claim reaches the clearinghouse. Missing third-degree percentage documentation remains the leading cause of T31.2x rejections.

How Pabau keeps burn documentation and claims in one record

Most burn teams find a T31.22 problem after the payer does. The remittance lands weeks later with a reason code, someone pulls the chart, and the third-degree percentage was never written down. The encounter is old by then, and the coder is reconstructing it.

Practice management software like Pabau holds the burn assessment, the codes and the claim in one client record. The TBSA and depth figures sit on the encounter being billed, so nobody hunts through a separate document to confirm them. Claims go out electronically, and each returned claim brings its denial reason code back to the same place.

That makes the pattern visible while it is still fixable. When three T31.2x claims come back for the same missing percentage, the repair belongs in the burn assessment template. A monthly appeals queue only treats the symptom.

Reduce T31.22 claim denials with smarter billing workflows

Pabau’s claims management software tracks burn diagnosis codes from submission through payment and flags sequencing errors before they reach the payer. It connects directly to Claim.MD for electronic claim processing across thousands of US payers.

Book a demo

Conclusion

T31.22 is a simple code to assign once the chart carries both numbers. The trouble starts upstream, in a burn assessment that records an overall percentage and leaves the depth split to inference. No amount of care at the coding step recovers a figure the clinician never wrote down.

So the fix belongs in the documentation template rather than in the coding review. Ask the burn assessment to capture total TBSA, the full-thickness percentage and the method used, and the fifth character stops being a judgment call. Book a demo to see how Pabau keeps that documentation attached to the claim it supports.

Continue your research

Need a clean claim checklist for injury codes? Clean claim submission covers the pre-submission verification steps that prevent burn code denials from leaving the practice.

Tracking denial patterns across T31 claims? Denial codes in medical billing explains CARC codes and how to build a denial response workflow for injury code rejections.

Want to understand how T31.22 fits into the broader revenue cycle? Revenue cycle management explains how burn diagnosis coding connects to eligibility, submission, and payment posting workflows.

New to the claim lifecycle behind these codes? What is medical billing walks through each step from the patient encounter to a paid claim.

Already sitting on a stack of rejected burn claims? Denial management in healthcare sets out how to work an appeal queue and stop the same rejection repeating.

Frequently asked questions