ICD-10 code S02.32XB: Fracture of orbital floor, left side

Key takeaways

ICD-10 code S02.32XB describes a fracture of the orbital floor, left side, initial encounter for open fracture, under ICD-10-CM Chapter 19

The billable code runs to seven characters. S02.32 covers the left orbital floor, X fills the sixth position as a placeholder, and B marks the initial open fracture encounter

Orbital floor fractures sit under S02.3, not S02.1. The Tabular List carries an Excludes2 note between the floor and the orbital roof (S02.12-), so the two are never interchangeable

Under category S02 the 7th character B means an open fracture with no Gustilo subdivision. Only the forearm, femur, and lower leg categories split open fractures by Gustilo type

Practice management software like Pabau keeps laterality and open status on the patient record from the first encounter. The coder is then not guessing weeks later

ICD-10 code S02.32XB: definition and clinical description

ICD-10 code S02.32XB is a billable diagnostic code in the ICD-10-CM classification system. It describes a fracture of the orbital floor, left side, at the initial encounter for an open fracture. Coders in emergency medicine, ophthalmology, plastic surgery, and maxillofacial surgery use it the first time a patient presents with this injury.

The code sits in the S02 category, fractures of skull and facial bones. That category belongs to ICD-10-CM Chapter 19, which covers injury, poisoning, and certain other consequences of external causes (S00-T88). Its parent subcategory is S02.3, fracture of orbital floor. Getting the hierarchy and the 7th character right prevents claim denials and audit findings.

S02.32XB code details at a glance

The table below summarises the key attributes of S02.32XB for quick reference during coding and billing workflows.

Anatomical context: fracture of the left orbital floor

The orbital floor is the thin bony shelf that forms the bottom of the eye socket. It separates the orbit from the maxillary sinus beneath, and the ICD-10-CM Tabular List also calls it the inferior orbital wall.

The floor is composed largely of the maxilla, with contributions from the zygomatic and palatine bones. Because of its thin profile, it is particularly vulnerable to blunt force trauma. The orbital roof, by contrast, is part of the base of the skull, which is why the two are coded in different subcategories.

Accurate coding of left orbital floor fractures starts with the injury mechanism. Coders working in plastic surgery EMR software environments see this pattern most often in facial trauma cases.

The left side designation in S02.32XB comes from the 5th character, and it is required whenever the record states a side. Falling back to S02.30X- when the imaging or operative report clearly says left costs specificity and is a common audit trigger.

What is a blowout fracture?

A blowout fracture occurs when direct force is applied to the eye or periorbital region, causing an abrupt rise in intraorbital pressure. The orbital floor, being the weakest wall, fractures inferiorly into the maxillary sinus to relieve that pressure. The eyeball itself typically remains intact.

• Common mechanism: blunt trauma from fists, balls, motor vehicle impacts, or falls
• Key clinical features: periorbital ecchymosis, enophthalmos, diplopia, infraorbital hypoesthesia
• Imaging: CT of the orbits confirms floor disruption and any soft tissue herniation
• Index entry: the ICD-10-CM Alphabetic Index lists blow-out fracture under Fracture, orbit, floor, pointing to S02.3-
• Laterality importance: S02.32X- is the left side and S02.31X- is the right, so the code must match the imaging findings

Clinicians should document the injury mechanism, laterality, and open versus closed status explicitly in the operative or emergency note. Vague documentation is the primary reason left orbital floor fracture claims are returned for additional information. A facial trauma consultation form capturing these data points at the first encounter reduces downstream coding ambiguity.

Understanding the 7th character extensions for S02.32X

The 7th character is where most coding errors occur with this code family. S02.32 is only five characters long, so it takes the placeholder X in the sixth position and then a 7th character to become billable. Each character tells the payer the encounter type and the fracture status.

When to use S02.32XB vs. S02.32XA

Both characters apply to an initial encounter, and the fracture status decides which one you use. S02.32XA applies when the left orbital floor fracture is closed, with no wound communicating with the fracture site. S02.32XB applies when the record documents an open fracture, with a wound reaching the bone or with bone exposed.

Category S02 does not subdivide open fractures by Gustilo type. Only three categories use the Gustilo 7th characters, and they are the forearm (S52), the femur (S72), and the lower leg (S82).

In those categories, B means an open fracture of type I or II and C means type IIIA to IIIC. For an orbital floor fracture, B covers any open fracture the record documents. There is no separate character for a more severe open orbital fracture.

Category S02 also carries a standing instruction that a fracture not indicated as open or closed is coded to closed. Silence in the note therefore pushes the claim to S02.32XA, not S02.32XB.

Do not assign S02.32XB to a subsequent visit either. Once the patient returns, switch to the D, G, or K character depending on healing status. Using B at a return visit is a common error that payers flag during audits.

Code hierarchy: parent and sibling codes for S02.32XB

S02.32XB sits inside a structured hierarchy. Reading it from the top helps you find the sibling codes for right-side and unspecified injuries. It also confirms the right choice when documentation is thin. The WHO ICD-10 browser provides the international framework from which ICD-10-CM is derived.

The same hierarchical principle runs through every injury code in the ICD-10-CM diagnostic code reference. You move from category to subcategory, then to the specific code with its required character extensions. Never assign S02.3 or S02.32 on their own, because neither is billable without the placeholder and the 7th character.

Excludes notes: orbital floor, orbital roof, and orbital walls

The Tabular List draws hard lines between the orbital floor and the structures around it. Some of those lines are Excludes2 notes and one is an Excludes1 note. The difference changes what you can report on the same claim.

Excludes2 means the excluded condition is not part of S02.3-, so a patient can carry both codes when both injuries are documented. Excludes1 is stricter. S02.85 and S02.32XB never appear on the same claim for the same orbit.

Coding guidelines and documentation requirements for ICD-10 code S02.32XB

The ICD-10-CM Official Guidelines for Coding and Reporting, Section I.C.19, govern how Chapter 19 injury codes are applied. For S02.32XB, three documentation elements are non-negotiable.

• Open status documented: the record must state that the fracture is open. Under category S02 a fracture not identified as open or closed defaults to closed, which means the 7th character A.
• Laterality confirmed: left must appear in the imaging report, operative note, or clinical record. An unqualified orbital floor fracture falls to S02.30X-, which carries lower specificity.
• Encounter type stated: the first time the patient is seen for this fracture is the initial encounter. Subsequent care, even by a different provider, uses D, G, or K as appropriate.

Under Section I.C.20, external cause codes should accompany S02.32XB to describe the mechanism and the place of occurrence. Common pairings are W19.XXXA for an unspecified fall and Y04.0XXA for an assault in an unarmed fight. Payers increasingly require these supplementary codes on trauma claims.

Thorough clinical documentation at healthcare practices is the most effective way to keep these claims from being returned. Patient record management software helps here. A form that prompts clinicians to record mechanism, laterality, and open or closed status at every trauma encounter takes the guesswork out of coding.

Common co-codes used with S02.32XB

Orbital floor fractures rarely occur in isolation. Blunt trauma strong enough to fracture the floor often causes other injuries, and a complete claim codes each confirmed diagnosis. Incomplete co-coding is a common reason trauma claims are underpaid relative to their DRG assignment.

Sequencing matters. S02.32XB is generally the principal diagnosis when the left orbital floor fracture is the condition chiefly responsible for the encounter. If an intracranial injury from the S06 range drives the admission, sequence that first per the ICD-10-CM Official Guidelines. Claims management software that checks the required submission fields before releasing a claim keeps incomplete paperwork from reaching the payer.

Subsequent encounter and sequela coding

The episode of care does not end with S02.32XB. Every follow-up visit for the same orbital floor fracture takes a different 7th character, reflecting where the patient sits in the healing arc.

• 7th character D (routine healing): the patient returns for scheduled follow-up, and imaging or examination confirms normal progress
• 7th character G (delayed healing): healing is slower than expected at the follow-up interval, and the record should say so explicitly
• 7th character K (nonunion): the fracture has failed to unite, which usually opens a surgical discussion and changes the DRG assignment
• 7th character S (sequela): a late effect of the original fracture, such as persistent enophthalmos, diplopia, or infraorbital nerve damage

On a sequela visit, list the code for the nature of the sequela first and S02.32XS second. A patient with persistent diplopia from a healed left orbital floor fracture is coded H53.2, then S02.32XS.

This sequencing rule is set out in the CMS ICD-10 coding guidelines. Applying the ICD-10-CM coding guidelines consistently across the full episode of care protects against retrospective audit findings.

Billing and reimbursement considerations for orbital floor fracture coding

Open and closed fractures do not always land in the same reimbursement bracket, so the 7th character carries financial weight too. Where S02.32XB groups depends on the principal diagnosis and on any procedures performed during the stay. Confirm the grouping in the current CMS release rather than in a coding reference.

Common claim denial reasons for orbital floor fracture codes include:

• Missing laterality: submitting S02.30X- when the record clearly documents the left side
• Wrong encounter character: using B at a follow-up visit instead of D, G, or K
• Absent external cause codes: payers in many states expect at least one Chapter 20 code on a trauma claim
• Thin open fracture documentation: an open wound near the eye is not the same as a note stating the orbital floor fracture is open

DRG and APC grouping weights are updated annually by CMS, so any reimbursement figure in a coding reference goes stale within a fiscal year. Verify against the current CMS fee schedule and check the code itself with the AAPC ICD-10-CM code lookup alongside payer coverage policies.

HIPAA requires that any ICD-10-CM code in an electronic transaction be valid and current. Confirm S02.32XB is unrevised in the active CMS release before each claim cycle.

HIPAA-compliant medical office workflows build that check into the billing cycle. Digital intake forms that capture open or closed status and laterality at first contact remove the reliance on retrospective chart review.

How Pabau supports accurate orbital floor fracture coding

Most of what goes wrong with S02.32XB happens before anyone opens the coding software. The note does not say which side, or it never states that the fracture was open, and the coder is left guessing weeks later.

Pabau is an all-in-one practice management system for medical and aesthetic practices. Its digital forms let you build a trauma template that will not submit until laterality and open or closed status are filled in.

Treatment notes, imaging summaries, and before-and-after photos stay on the same patient record, so the documentation supporting the code sits in one place. Every subscription includes the full platform, so none of this sits behind a higher tier.

On the billing side, Pabau’s claims management checks that a claim carries the fields an insurer needs before it can be sent. A status dashboard then shows where every submitted claim stands. Reporting lets you pull your own S02.3x encounters and check the A-to-B ratio each quarter.

Capture the documentation your orbital fracture codes depend on

Pabau gives plastic surgery, ophthalmology, and emergency practices required-field trauma forms and one record per patient. Claims are then checked for missing submission details before they go out.

Book a demo

Conclusion

Orbital floor fractures are among the most documentation-sensitive injuries in Chapter 19, and S02.32XB is no exception. Getting the subcategory, the laterality, the placeholder, and the 7th character right at first contact decides whether the claim pays or comes back for rework.

The one distinction worth committing to memory is that the orbital floor is S02.3- and the orbital roof is S02.12-. They are different bones, and the Tabular List keeps them apart with an Excludes2 note.

Pabau’s structured clinical records and claims management software help plastic surgery, ophthalmology, and emergency practices capture laterality and open status at the first encounter. From there, you can follow the claim through to payment. To see how that works in a trauma coding workflow, book a demo.

Continue your research

Need a template for capturing trauma documentation at first contact? Facial trauma consultation form provides a structured framework for recording mechanism, laterality, and wound classification at the initial encounter.

Managing complex multi-code trauma claims? Intracranial hemorrhage ICD-10 coding covers sequencing rules when S06 codes co-exist with facial fractures.

Looking for guidance on compliance and documentation standards? Medical forms at your healthcare practice explains how structured clinical forms reduce coding ambiguity and audit risk.

Frequently asked questions