S02.841 — Fracture of lateral orbital wall, right side
Is S02.841 billable?
No — S02.841 is a non-billable header code. S02.841 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 6 billable codes beneath S02.841.
Billable codes under this header
- S02.841AFracture of lateral orbital wall, right side, initial encounter for closed fracture
- S02.841BFracture of lateral orbital wall, right side, initial encounter for open fracture
- S02.841DFracture of lateral orbital wall, right side, subsequent encounter for fracture with routine healing
- S02.841GFracture of lateral orbital wall, right side, subsequent encounter for fracture with delayed healing
- S02.841KFracture of lateral orbital wall, right side, subsequent encounter for fracture with nonunion
- S02.841SFracture of lateral orbital wall, right side, sequela
S02.841 at a glance
| Code | S02.841 |
|---|---|
| Description | Fracture of lateral orbital wall, right side |
| Billable | No — header code |
| Code set | ICD-10-CM FY2027 |
| Valid for encounters | October 1, 2026 – September 30, 2027 |
How is S02.841 listed in the Alphabetic Index?
The Alphabetic Index lists these routes under S02.84, the nearest indexed parent of S02.841. Use them to find the family, then select the specific code.
- Fracture, traumatic › orbit, orbital › wall › lateral (abduction) (adduction) (separation)
Use additional code — inherited from Chapter 19
Report an additional code alongside S02.841 to fully describe the condition. S02.841 is sequenced first.
- code to identify any retained foreign body, if applicable (Z18.-)
Excludes2 — not included here — inherited from Chapter 19
The conditions below are not part of S02.841, but a patient may have both at the same time. When documentation supports it, S02.841 and the excluded code may both be reported.
Excludes2 — not included here — inherited from S00-S09
The conditions below are not part of S02.841, but a patient may have both at the same time. When documentation supports it, S02.841 and the excluded code may both be reported.
- burns and corrosions (T20-T32)
- effects of foreign body in ear (T16)
- effects of foreign body in larynx (T17.3)
- effects of foreign body in mouth NOS (T18.0)
- effects of foreign body in nose (T17.0-T17.1)
- effects of foreign body in pharynx (T17.2)
- effects of foreign body on external eye (T15.-)
- frostbite (T33-T34)
- insect bite or sting, venomous (T63.4)
Excludes2 — not included here — inherited from S02.8
The conditions below are not part of S02.841, but a patient may have both at the same time. When documentation supports it, S02.841 and the excluded code may both be reported.
Excludes2 — not included here — inherited from S02.84
The conditions below are not part of S02.841, but a patient may have both at the same time. When documentation supports it, S02.841 and the excluded code may both be reported.
Code also — inherited from S00-S09
Two codes may be needed to describe the condition fully. Whether S02.841 is sequenced first depends on the reason for the encounter.
- for any associated infection
Code also — inherited from S02
Two codes may be needed to describe the condition fully. Whether S02.841 is sequenced first depends on the reason for the encounter.
- any associated intracranial injury (S06.-)
What codes fall under S02.841? (6)
- S02.841AFracture of lateral orbital wall, right side, initial encounter for closed fracture
- S02.841BFracture of lateral orbital wall, right side, initial encounter for open fracture
- S02.841DFracture of lateral orbital wall, right side, subsequent encounter for fracture with routine healing
- S02.841GFracture of lateral orbital wall, right side, subsequent encounter for fracture with delayed healing
- S02.841KFracture of lateral orbital wall, right side, subsequent encounter for fracture with nonunion
- S02.841SFracture of lateral orbital wall, right side, sequela
How long has S02.841 existed?
S02.841 first appears in FY2021 (FY2020 is not available, so it may have appeared then).
Derived from the official order files for FY2016–FY2026. FY2017 and FY2020 publish no order file, so those years are not covered.