S02.30XG — Fracture of orbital floor, unspecified side, subsequent encounter for fracture with delayed healing
Is S02.30XG billable?
Yes, but S02.30XG is an unspecified code. S02.30XG is a valid, billable ICD-10-CM code for encounters from October 1, 2026 through September 30, 2027. However, S02.30XG is an unspecified or catch-all code. Payers apply additional scrutiny to unspecified codes and many deny them when the medical record supports a more specific option, so check the documentation before selecting S02.30XG — the more specific alternatives are listed below.
S02.30XG at a glance
| Code | S02.30XG |
|---|---|
| Description | Fracture of orbital floor, unspecified side, subsequent encounter for fracture with delayed healing |
| Billable | Yes |
| Code set | ICD-10-CM FY2027 |
| Valid for encounters | October 1, 2026 – September 30, 2027 |
| 7th character "G" | subsequent encounter for fracture with delayed healing |
What does the 7th character "G" mean in S02.30XG?
In S02.30XG, the 7th character G means subsequent encounter for fracture with delayed healing. The 7th character is required for S02.30XG to be a valid, complete code.
Same condition, different episode of care — switch the 7th character:
Which MS-DRGs does S02.30XG group to?
S02.30XG sits in MDC 08 and helps define the logic of 3 MS-DRGs (version 44, FY2027). Which one a stay actually groups to also depends on procedures and secondary diagnoses.
- 559Aftercare, Musculoskeletal System and Connective Tissue with MCCmedical
- 560Aftercare, Musculoskeletal System and Connective Tissue with CCmedical
- 561Aftercare, Musculoskeletal System and Connective Tissue without CC/MCCmedical
How is S02.30XG listed in the Alphabetic Index?
The Alphabetic Index lists these routes under S02.3, the nearest indexed parent of S02.30XG. Use them to find the family, then select the specific code.
- Fracture, traumatic › blow-out (abduction) (adduction) (separation)
- Fracture, traumatic › orbit, orbital › floor (abduction) (adduction) (separation)
Excludes1 — never code together — inherited from S02.3
The conditions below can never be reported together with S02.30XG on the same claim. An Excludes1 note means the two conditions cannot occur in the same patient, so reporting both is a coding error.
- orbit NOS (S02.85)
Use additional code — inherited from Chapter 19
Report an additional code alongside S02.30XG to fully describe the condition. S02.30XG 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.30XG, but a patient may have both at the same time. When documentation supports it, S02.30XG and the excluded code may both be reported.
Excludes2 — not included here — inherited from S00-S09
The conditions below are not part of S02.30XG, but a patient may have both at the same time. When documentation supports it, S02.30XG 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.3
The conditions below are not part of S02.30XG, but a patient may have both at the same time. When documentation supports it, S02.30XG 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.30XG 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.30XG is sequenced first depends on the reason for the encounter.
- any associated intracranial injury (S06.-)
How long has S02.30XG existed?
S02.30XG first appears in FY2018 (FY2017 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.