ICD-10 code T30.0: Unspecified burn coding guide

Key takeaways

T30.0 is the billable ICD-10-CM code for a burn when the record names neither the body region nor the degree.

CMS keeps T30.0 off inpatient claims. The tabular note reads, “This code is not for inpatient use. Code to specified site and degree of burns.”

Use it only when both the site and the degree are missing from the whole record. If either one appears, a code from T20-T29 applies.

On an inpatient admission, query the provider for site and degree first. A lone T30.0 groups to MS-DRG 935, non-extensive burns.

Four companion codes ride with T30.0. They cover external cause, place of occurrence, activity, and external cause status.

ICD-10 code T30.0 covers a burn when the record names neither the body region nor the degree. It is billable and HIPAA-valid, but CMS keeps it off inpatient claims. The tabular note says plainly that this code is not for inpatient use.

So T30.0 belongs on outpatient and emergency department claims, and nowhere else. Miss that, and the claim comes back or draws an audit, because an inpatient burn record needs a site and a degree.

Below you will find when T30.0 fits, what the record has to show, the codes around it, and how the claim moves.

ICD-10 code T30.0 is billable, with one hard restriction

T30.0 carries the official description “burn of unspecified body region, unspecified degree.” It is a billable, specific ICD-10-CM code, valid in HIPAA-covered transactions. The FY2026 edition took effect on October 1, 2025, and runs through September 30, 2026.

The code sits in the injury chapter, S00-T88, inside the burns and corrosions subrange T30-T32. Within that subrange it is the residual code. You reach for it when the note names neither the site nor the depth of the burn. The CMS ICD-10-CM code set confirms both the description and the billable status.

One restriction shapes every decision below. The tabular note reads, “This code is not for inpatient use. Code to specified site and degree of burns.” That puts T30.0 in outpatient and emergency department territory, where the site and the degree are sometimes genuinely missing at billing.

Only the fourth character makes T30 billable

T30 on its own cannot go on a claim. The fourth character is what turns the category into a claim-ready code, so T30.0 is accepted and bare T30 is not. Its sibling T30.4 covers a corrosion of unspecified body region and degree, and it works the same way.

The path from chapter to code is short. The table below sets it out level by level, so you can see where the billable line falls.

Submitting T30 without the fourth character is a standard edit-based rejection, and most clearinghouses catch it before transmission. That parent-to-child pattern repeats across the tabular list, so the same fourth-character check applies to the other ICD-10-CM codes you assign.

Use T30.0 only when site and degree are both missing

T30.0 is a residual code, so both facts have to be absent before it fits. The body region has to be missing and the degree has to be missing, across the whole record. Cross-check the tabular instruction notes in the CDC ICD-10-CM web tool before you assign it.

• Use T30.0 when: the documentation states only “burn” or “burn injury”, with no body site and no degree. Check the ED note, the operative report, and the progress notes first.
• Do not use it when the region is identifiable: “burn to the right hand” names a site even without the word dorsum. That detail sends you to T20-T29.
• Do not use it when the degree is implied: “blistering” points to second degree at minimum, which is enough for a degree subcode.
• Never use it on an inpatient claim: the tabular instruction rules it out. Query the provider, then code the burn by site and degree.
• Query before you default: a coder-initiated query that yields a site and a degree moves the case to T20-T29. That is what an inpatient claim needs.

One practical exception sits in the emergency department. Coders there sometimes handle records for patients brought in unconscious, where the first note says only “burns”. T30.0 can carry that initial encounter while the examination is pending. Drop it the moment the record gains a site or a degree before billing.

These documentation phrases all point to T30.0

Provider notes rarely use the tabular wording, so the alphabetic index carries a set of accepted synonyms that land on T30.0. Recognizing them keeps a coder from hunting for a code that does not exist, or from picking a specific one the record cannot support.

• Burn NOS (burn, not otherwise specified)
• Burn of unspecified site
• Burn unspecified
• Unspecified burn
• Burn of unspecified body region, unspecified degree
• Thermal burn, site and degree unspecified
• Burn injury, unspecified

Most EHR systems surface these as auto-suggest options, which is part of why T30.0 gets overused. If the note uses one of them and adds nothing else, T30.0 is the right call on an outpatient or emergency department claim.

Four companion codes have to ride with T30.0

The ICD-10-CM Official Guidelines require external cause reporting alongside any burn code, and T30.0 is no exception. A missing external cause code is the most frequent reason a burn claim comes back. Good denial management starts with catching that omission before submission.

Four code categories belong on the claim with T30.0:

• External cause of the burn (X00-X19, X75-X77, X96-X98): the source of the injury, such as fire, a hot liquid, electricity, or radiation. This is the one coders skip most often.
• Place of occurrence (Y92): where the burn happened, from a home kitchen to a public building.
• Activity (Y93): what the patient was doing at the time of the burn.
• External cause status (Y99): whether the injury was civilian, military, or work-related.

Sequencing is straightforward. The burn code leads, and the external cause codes follow it. Never pair T30.0 with a site-specific code from T20-T29 for the same injury, because the two statements contradict each other.

A payer-specific checklist for those four categories cuts front-end edits sharply. Some Medicare contractors single out burn claims with missing external cause codes during probe reviews, so the checklist earns its keep twice.

What the record needs before T30.0 holds up

Treat T30.0 as the last resort in burn coding rather than the first option. Any detail that specifies the burn moves the assignment to T20-T29, and those codes are both more accurate and usually better reimbursed.

The table below shows what the record has to capture, and which way each element pushes the code.

Structured burn assessment forms are the cheapest fix here. Prompt the provider for body region and degree at the point of care, and most cases move off T30.0 inside a quarter.

The burn codes that usually fit better than T30.0

T30.0 sits inside a family of codes that classify burns by site, by degree, and by total body surface area. One rule runs through all of them, which is to code to the highest level of specificity the documentation supports.

The reference table maps the codes you will be choosing between most often.

When a TBSA percentage is documented alongside a T30.0 case, add the matching T31 code as a secondary. The AAPC’s ICD-10-CM code lookup tool lists the full T20-T32 range with the tabular notes attached to each code.

How to choose between T30.0 and a site-specific code

Assign the most specific code the documentation supports. That one rule settles most burn cases. The flow below runs it as three questions in order, starting with the one that rules T30.0 out entirely.

The scenarios that turn up in practice map onto that logic as follows.

POA reporting never applies to a correctly coded T30.0

Present on admission (POA) reporting never applies to a correctly coded T30.0. POA indicators are an inpatient requirement under the Medicare Inpatient Prospective Payment System, and the tabular list keeps T30.0 off inpatient claims.

That makes the choice of POA indicator a moot question on a clean claim. When a burn admission arrives without a site or a degree, the answer is a provider query rather than a POA value. The FY2026 Official Guidelines call category T30 extremely vague and say it should rarely be used.

Errors still slip through. A coder who assigns T30.0 on an inpatient record has to put something in the POA field, and abstraction software will accept it. The table sets out what each indicator means, and what it signals when T30.0 turns up on an inpatient claim.

An auditor reads a T30.0 with a POA indicator as a documentation problem, because the code should not be on the claim at all. Fix it upstream instead. Route unspecified burn admissions into a query workflow before the coder ever reaches the POA field.

A stray T30.0 groups to MS-DRG 935, the lowest weight

MS-DRGs are an inpatient payment system, so T30.0 should never drive one. Treat any T30.0 on an IPPS claim as a coding error to unwind, not a grouping to work with.

It still helps to know where the code lands, because that is what missing specificity costs. A lone T30.0 sits in major diagnostic category (MDC) 22, burns, and groups to MS-DRG 935, non-extensive burns. That is the lowest-weighted DRG in the category.

The code carries no site, no degree, and no total body surface area, so the grouper has nothing to weight the stay with. MDC 22 holds six burn DRGs, and every other one needs documentation that T30.0 does not carry.

The distance between 935 and 934 is the price of a missing degree. A query that confirms a full thickness burn moves the case, and a query that confirms a site moves it out of T30.0 altogether.

Check current weights against the CMS FY2026 MS-DRG Definitions Manual before you use them for reimbursement modeling.

Where T30.0 claims usually go wrong

The most common mistake is also the simplest, which is putting T30.0 on an inpatient claim. The tabular note rules it out, so the code should never reach an IPPS bill in the first place.

Five errors account for most of the rework on burn claims:

• Using T30.0 on an inpatient record. An auditor reads it as a documentation problem rather than a coding choice. Query the provider, then code from T20-T29.
• Defaulting to T30.0 when only the degree is missing. A named body region sends you to T20-T29 with an unspecified-degree subcode instead.
• Ignoring implied specificity. Blistering points to second degree at minimum, so the record is not silent on the depth after all.
• Dropping the companion codes. T30.0 without an external cause code is an edit waiting to happen at the clearinghouse.
• Coding a corrosion as a burn. A chemical injury with no site and no degree is T30.4, not T30.0.

Run this check before you submit a T30.0 claim

Two minutes of checking prevents most T30.0 rework. Work down the list before the claim leaves the practice.

• The encounter is outpatient or emergency department, not inpatient.
• The site and the degree are absent from the ED note, the nursing notes, the operative report, and the progress notes.
• A query went out if the documentation was ambiguous, and the provider answered it.
• An external cause code from X00-X19, X75-X77, or X96-X98 is on the claim.
• Y92, Y93, and Y99 are all present.
• A T31 code is attached if a TBSA percentage is documented.
• No T20-T29 code covers the same injury on the same claim.

Here is how that plays out. An urgent care note reads “dressing change, burn injury, healing well”, with no site, no degree, and no TBSA. The coder queries and the provider adds nothing further.

T30.0 is correct here. It goes out with an X-code for the flame source, plus Y92, Y93, and Y99 for the place, the activity, and the patient’s status.

Getting a T30.0 claim through the clearinghouse cleanly

A burn claim coded to T30.0 has to meet the same clean claim standard as any injury code. The companion codes have to be on the form before it goes out. Missing supplemental codes are one of the top edit reasons clearinghouses flag on injury claims.

Practice management software like Pabau closes that loop in one place. Pabau’s claims management software connects the clinical note, the code assignment, and the submission.

Claims then go out as CMS-1500 and 837P files through its Claim.MD integration, which reaches thousands of payers. Code validation runs before the claim leaves the practice, so a missing companion code surfaces while you can still fix it.

Real-time eligibility checks and electronic remittance advice (ERA/835) then match each payment back to the claim that earned it. When a burn claim underpays, you see it against the expected amount rather than finding it a month later in a reconciliation.

Submit burn claims that clear the first time

Pabau connects the clinical note, ICD-10 code assignment, and claim submission in one workflow. Code validation runs before the claim leaves the practice, so companion codes are not the reason it comes back.

Book a demo

Conclusion

T30.0 is a legitimate code with a narrow job. It belongs on outpatient and emergency department claims where the record genuinely says nothing about the site or the degree, and nowhere else. On an inpatient record, CMS expects a query and a code that names both.

So every T30.0 that could have been a T20-T29 code points back at documentation rather than at coding. Fix it upstream. Structure burn documentation at the point of care, run a consistent query process for thin notes, and let pre-submission edits catch the companion codes.

Accuracy on a code like this one is a billing habit more than a coding skill. Pabau keeps documentation, coding, and claim submission in one workflow, so the check happens before the claim goes out.

Book a demo to see how a burn claim moves through it from note to payment.

Continue your research

Need guidance on burn injury billing compliance? Medical billing compliance covers the key regulatory requirements for accurate injury code submission.

Want to understand how clearinghouses process ICD-10 claims? Claim.MD clearinghouse guide explains how electronic claims are validated and routed to payers.

Looking for denial management strategies for injury codes? Denial management in healthcare outlines workflows for tracking and appealing common burn claim denials.

Interested in clean claim best practices? Clean claim requirements breaks down what payers check before processing any ICD-10-CM claim.

Frequently asked questions