X03.0XXA vs X03.0XXS
X03.0XXA (Exposure to flames in controlled fire, not in building or structure, initial encounter) compared with X03.0XXS (Exposure to flames in controlled fire, not in building or structure, sequela), from the official CMS tabular data.
Summary
No tabular note links these codes. Both belong to category X03, and nothing in the tabular list prevents reporting each when it is documented.
Registry fact- What is different?
Title wording.The titles share “Exposure to flames in controlled fire, not in building or structure”; X03.0XXA says “initial encounter” where X03.0XXS says “sequela”.
Registry fact
- Can these codes be reported together?
No instruction prevents it.No note in either entry names the other. Both belong to category X03; each may be reported when its own documentation is present.
Registry fact
- Is there an Excludes1 relationship?
None.Neither entry carries an Excludes1 note that names the other code. X03.0XXA carries 1 Excludes1 note and X03.0XXS carries 1 Excludes1 note covering other codes; the side-by-side table quotes them.
Official rule
- Is there an Excludes2 relationship?
None.Neither entry carries an Excludes2 note that names the other code. X03.0XXA carries 3 Excludes2 notes and X03.0XXS carries 3 Excludes2 notes covering other codes; the side-by-side table quotes them.
Official rule
- Is one more specific?
No.Neither is a subdivision of the other, and neither title is the unspecified form; they describe different conditions within category X03.
Registry fact
- Is one a parent or header code?
No.Both are billable codes, and neither contains the other.
Registry fact
- Are there sequencing instructions?
None.Neither entry carries a Code First or Use Additional Code note that names the other.
Official rule
- Are there other coding relationships?
None found.No laterality, encounter-phase, Table of Neoplasms, Table of Drugs and Chemicals, or history-versus-active-disease relationship links these codes.
MedCoder-derived
Official rule: a tabular instructional note or a section of the ICD-10-CM Official Guidelines, quoted as published. Registry fact: the codes’ own published attributes (titles, billable status, position in the hierarchy, code set). MedCoder-derived: a reading MedCoder computes from those facts; it is not itself a rule. How to read the labels
Can these codes be reported together?
Yes, when each is documented. X03.0XXA and X03.0XXS both belong to category X03.
No Excludes1/Excludes2 relationship exists between these codes in the official tabular list. The code titles state what each one covers, and the documentation decides which applies.
Side by side
| X03.0XXAExposure to flames in controlled fire, not in building or structure, initial encounter | X03.0XXSExposure to flames in controlled fire, not in building or structure, sequela | |
|---|---|---|
| Billing status | Billable | Billable |
| Classification | V00-Y99 — External Causes of Morbidity (V00-Y99) | V00-Y99 — External Causes of Morbidity (V00-Y99) |
| Definition | Exposure to flames in controlled fire, not in building or structure, initial encounter is a billable ICD-10-CM diagnosis code (X03.0XXA). | Exposure to flames in controlled fire, not in building or structure, sequela is a billable ICD-10-CM diagnosis code (X03.0XXS). |
| 7th character | The appropriate 7th character is to be added to each code from category X03 | The appropriate 7th character is to be added to each code from category X03 |
| Includes | exposure to bon fire exposure to camp-fire exposure to trash fire | exposure to bon fire exposure to camp-fire exposure to trash fire |
| Excludes1 | arson (X97) | arson (X97) |
| Excludes2 | explosions (W35-W40) lightning (T75.0-) transport accident (V01-V99) | explosions (W35-W40) lightning (T75.0-) transport accident (V01-V99) |
Notes are the code’s own tabular entry, quoted as published. A note that names the other code is the one the verdict above rests on.
Derived from the official CMS ICD-10-CM tabular data (FY2027). A coding-rule comparison, not billing advice: payer-specific edits and medical-necessity policy are outside its scope. All data sources