X96.0 — Assault by antipersonnel bomb
Is X96.0 billable?
No — X96.0 is a non-billable header code. X96.0 groups more specific codes and cannot be submitted on a claim. A valid ICD-10-CM code must be reported at the highest level of specificity available in its branch. Select one of the 3 billable codes beneath X96.0.
X96.0 at a glance
| Code | X96.0 |
|---|---|
| Description | Assault by antipersonnel bomb |
| Billable | No — header code |
| Code set | ICD-10-CM FY2027 |
| Valid for encounters | October 1, 2026 – September 30, 2027 |
How is X96.0 listed in the External Cause Index?
These are the routes through the External Cause of Injuries Index that lead to X96.0 — how the injury happened, rather than what the injury was.
- Assault › bomb › antipersonnel (homicidal) (by) (in)
- Explosion › antipersonnel bomb › assault (accidental) (of) (with secondary fire)
- Explosion › antipersonnel bomb › homicide (accidental) (of) (with secondary fire)
Excludes1 — never code together
The conditions below can never be reported together with X96.0 on the same claim. An Excludes1 note means the two conditions cannot occur in the same patient, so reporting both is a coding error.
- antipersonnel bomb use in military or war (Y36.2-)
Excludes1 — never code together — inherited from X92-Y09
The conditions below can never be reported together with X96.0 on the same claim. An Excludes1 note means the two conditions cannot occur in the same patient, so reporting both is a coding error.
Excludes1 — never code together — inherited from X96
The conditions below can never be reported together with X96.0 on the same claim. An Excludes1 note means the two conditions cannot occur in the same patient, so reporting both is a coding error.
What codes fall under X96.0? (3)
How long has X96.0 existed?
X96.0 has been in ICD-10-CM since at least FY2016, the earliest fiscal year on record here.
Derived from the official order files for FY2016–FY2026. FY2017 and FY2020 publish no order file, so those years are not covered.