ICD code X96.1XXS – Gasoline bomb assault, sequela

Key takeaways

X96.1XXS reports the cause of a late effect from a gasoline or petrol bomb assault, and it is never the first-listed code.

List the residual condition first, then the original injury code with a 7th character S, then X96.1XXS.

X96.1 is a four-character stem, so two placeholder Xs fill positions 5 and 6 before the S.

Activity (Y93) and status (Y99) codes do not apply to sequela claims, and a place code (Y92) is generally reported only at the initial encounter.

Pabau, the practice software we build, submits claims through Claim.MD, with eligibility checks and ERA remittance returned to your team.

X96.1XXS at a glance: The fields to confirm first

ICD-10 code X96.1XXS reports assault by gasoline bomb at a sequela visit, when the patient is treated for a late effect of the attack. It always follows the code for the condition you treat.

Start every X96.1XXS claim with the basics below. They confirm the mechanism, the encounter type and where the code sits. Check the fiscal year as well, since the ICD-10-CM code set updates every October 1.

How X96.1XXS is built, one character at a time

Each character in X96.1XXS does a job. Once you know them, you can spot a malformed code before the clearinghouse does.

The stem X96.1 has only four characters. ICD-10-CM needs the encounter character in position 7, so two Xs fill positions 5 and 6. A claim showing X96.1S or X96.1XS carries a code that is not in the tabular list, and the clearinghouse or payer will reject it.

When the S in X96.1XXS fits the visit

Use S when the patient comes in for a condition that grew out of the original injury. The burn itself has already been treated. Today’s visit is about what it left behind.

The 7th character on X96.1 should match the injury code it travels with. Here is how the three options split.

No minimum time separates D from S. What decides it is whether active care for the original injury has ended. A patient can return for a sequela weeks or even years after the attack.

Gasoline bomb cases that call for X96.1XXS

These visits fit X96.1XXS when the record ties the condition to the earlier attack.

• Revision of hypertrophic burn scarring on the forearm, months after the grafts healed
• Contracture release where burn scarring now limits movement at a joint
• A pain management visit for chronic pain due to trauma from the burns
• Outpatient therapy for chronic PTSD that the provider links to the assault
• A dermatology review of scar tissue that itches, cracks or tightens the skin

When a different code fits better

• Debridement, grafting or wound care for the original burns is still underway. Use X96.1XXA.
• The patient is in for a routine check while the burn heals. Use X96.1XXD.
• The explosion was accidental. Use a W40 code, explosion of other materials.
• The note describes an incendiary device or arson rather than a bomb. Use X97, assault by smoke, fire and flames.
• The attack is documented as terrorism. Use a Y38.2- code instead.

A grenade is coded elsewhere too. The FY2026 External Cause Index sends a grenade used in an assault to X96.8, so a grenade-assault sequela is X96.8XXS. If the note confirms an assault but never names the means, the external cause is Y09 instead.

Sequence X96.1XXS behind the condition you treat

X96.1XXS describes how the harm happened, so it always sits behind a diagnosis. Build the claim in this order.

1. The residual condition. This is what you are treating today. Examples include L90.5 (scar conditions and fibrosis of skin), L91.0 (hypertrophic scar), G89.21 (chronic pain due to trauma) and F43.12 (chronic PTSD).
2. The original injury code with S. Add it with 7th character S where the record documents a physical injury. For a burn, use the T20-T25 code for the site and degree.
3. X96.1XXS. It closes the list as the external cause.

A worked example

A patient returns 18 months after a gasoline bomb attack for revision of a forearm burn scar. The third-degree burn of the right forearm healed long ago. Code L90.5 first, then T22.311S, then X96.1XXS. Here is how those three lines stack on the claim.

Leave the initial-visit extras off

Place of occurrence codes from Y92 are generally reported only at the initial encounter. Activity codes (Y93) and external cause status codes (Y99) do not apply to sequela encounters at all. So a clean sequela claim carries no Y93 or Y99 code, and usually no Y92 code either.

Choose X96.1XXS over its sibling explosive codes

Category X96 splits assaults by the type of explosive. Pick the code that matches the device named in the note. Falling back to X96.9 when the note says gasoline bomb loses specificity, and a payer audit can flag it.

Several neighboring codes sit outside X96 altogether. The X96 Excludes1 note sends assault by an incendiary device to X97. It also sends terrorism involving explosive material to Y38.2-. Antipersonnel bomb use in military or war goes to Y36.2-, while an accidental explosion belongs in W40. Confirm each boundary against the current CMS ICD-10 files before you bill.

The device in the note also decides whether the case stays in X96 at all. An assault committed with a paintball gun rather than an explosive takes the sequela to X95.02XS.

Documentation that holds up a gasoline bomb sequela code

The note has to support each part of the code. Check for four elements before you assign it.

1. Assault intent. The record states that another person caused the injury on purpose. Wording such as “victim of a gasoline bomb attack” works. “Burn from explosion” does not confirm intent.
2. The device. The note names a gasoline bomb or a petrol bomb. “Explosion” on its own supports X96.9, not X96.1.
3. Sequela status. Active treatment of the original burn has ended. A phrase like “residual scarring from healed burns” makes that clear.
4. The causal link. The provider ties today’s condition to the attack. A PTSD diagnosis with no documented link to the assault does not support X96.1XXS.

When any element is missing, query the provider. Do not assume assault intent without provider documentation. A written query also gives your medical billing compliance program a record of how the code was chosen.

How an X96.1XXS claim moves through each payer

X96.1XXS rides along with the claim rather than earning payment itself. The payer adjudicates on the diagnosis and procedure codes in front of it. How much attention the external cause gets depends on who pays.

On the way back, the electronic remittance advice (ERA) shows the reason for any denial. Read it promptly to see whether the S, the sequence or the note tripped the claim. It also helps to review clean claim requirements before a batch of trauma claims goes out.

Common X96.1XXS mistakes that send claims back

Watch for these five errors before an X96.1XXS claim goes out.

1. Dropping a placeholder. X96.1S and X96.1XS are not valid codes. Always send seven characters.
2. Using S too early. If grafting or wound care continues, the encounter is A or D.
3. Listing X96.1XXS first. External cause codes never lead. The residual condition goes first.
4. Coding a grenade here. A grenade assault indexes to X96.8, so its sequela is X96.8XXS.
5. Carrying over initial-visit codes. Y93 and Y99 do not belong on a sequela claim. Y92 is generally reported only at the initial encounter.

Tracking which error returns most often is part of steady denial management. That pattern shows where coder training should focus next.

Before you submit: Your X96.1XXS checklist

Run through these six checks on every sequela claim for a gasoline bomb assault.

• The code has seven characters, with X in positions 5 and 6.
• The provider has documented that active treatment of the original injury has ended.
• The residual condition is listed first, and the injury code with S comes second.
• The note names a gasoline or petrol bomb, not a grenade or an incendiary device.
• The note confirms assault intent, or a provider query is on file.
• No Y93 or Y99 code appears, and Y92 is generally left to the initial encounter.

How Pabau keeps sequela claims moving to the payer

Sequela claims tend to slip at the handoffs. The coder reads one screen, the biller types into another, and the claim drifts away from the note.

Pabau’s claims management software starts the claim from the patient record instead. It pre-fills the claim form from the invoice. Before you send, it checks that the required claim fields are complete.

In the US, Pabau submits claims through the Claim.MD clearinghouse, which also runs eligibility checks before the visit. ERA remittance then comes back to Pabau, so your team sees each payer’s response in one place. Coding choices like the 7th character stay with your coders.

Send sequela claims with fewer handoffs

Pabau pre-fills claims from the patient record and submits them through Claim.MD, with eligibility checks and ERA remittance returned to your team.

Book a demo

Conclusion

X96.1XXS gets easier once you treat it as the last line on the claim. The residual condition explains the visit, and the S injury code links it to the burn. X96.1XXS then names the gasoline bomb behind both.

The risk sits in the note more than in the code book. If intent, the device or sequela status is unclear, query the provider before you code. That one step saves a resubmission later.

Book a demo to see how Pabau carries sequela claims from the patient record to the payer.

Continue your research

Need to understand how clearinghouse validation works? Claim.MD clearinghouse overview explains how electronic claims move from the practice to the payer.

Coding the PTSD behind a sequela visit? ICD-10 code F43.1 for PTSD covers the post-traumatic stress disorder codes that often lead these claims.

Working with another burn sequela? ICD-10 code T22.332S shows how a third-degree upper arm burn is coded once it has healed.

Reading denials on returned claims? What is electronic remittance advice (ERA)? walks through the remittance file that explains each payer decision.

New to the revenue cycle? Medical billing fundamentals covers the path from claim creation through remittance posting.

Frequently asked questions