ICD code S52.92XC – Left forearm fracture, initial open encounter

Key takeaways

S52.92XC is an initial encounter code. It covers active treatment of an open left-forearm fracture graded Gustilo type IIIA, IIIB, or IIIC.

Active treatment includes the ED visit, the surgery, and any return trip to the operating room before the fracture is in its healing phase.

Once active treatment ends, the 7th character moves to F for routine healing, J for delayed healing, N for nonunion, or R for malunion.

The Gustilo grade must come from the ED or operative note. A coder cannot infer IIIA, IIIB, or IIIC from a wound description alone.

Pabau, the practice and billing software we build, flags missing or invalid claim details before a claim reaches the clearinghouse.

ICD-10 code S52.92XC: Definition and billable status

ICD-10 code S52.92XC is a valid, billable ICD-10-CM diagnosis code. Its official full descriptor is “Unspecified fracture of left forearm, initial encounter for open fracture type IIIA, IIIB, or IIIC.”

The code sits within category S52 (Fracture of forearm) in the ICD-10-CM injury chapter. You can confirm it in the CDC/NCHS ICD-10-CM tabular list. It applies only to US clinical modification coding (ICD-10-CM). Codes for each named forearm bone sit in our searchable diagnostic code library.

Breaking down the S52.92XC code structure

Each character in S52.92XC carries a specific meaning within the ICD-10-CM alphanumeric system. Reading the code one character at a time helps coders spot a wrong selection before the claim goes out.

The placeholder “X” is not optional. ICD-10-CM requires seven characters for codes in the S52.9 subcategory, and the X fills the 6th position so the encounter character lands in the 7th. Leaving it out produces an invalid code that clearinghouses reject on submission.

Understanding “unspecified fracture of left forearm”

“Unspecified” means the record does not say whether the fracture involves the radius, the ulna, or both. It is not a shortcut for incomplete charting. It fits only when that detail is not yet available from the documentation.

When imaging or the operative note names the bone, coders must use the more precise code. The unspecified code is appropriate only when:

• Imaging was not performed, or was not yet read, at the time of the encounter
• The treating physician’s note does not specify radius, ulna, or a combined injury
• The clinical record explicitly notes uncertainty about the fracture site

Once the bone is known, move to the matching subcategory. S52.0 covers the upper end of the ulna and S52.1 the upper end of the radius. S52.2 and S52.3 cover the ulnar and radial shafts. S52.5 and S52.6 cover the lower ends of the radius and ulna. ICD-10-CM has no single subcategory for both shafts, so a both-bone shaft fracture takes one S52.2- code and one S52.3- code. Choosing S52.92XC when a more specific code is available is a coding accuracy failure that auditors catch quickly.

What does 7th character “C” mean in fracture coding?

In category S52, 7th character C means an initial encounter for an open fracture graded Gustilo type IIIA, IIIB, or IIIC. Under the ICD-10-CM coding guidelines, “initial” is not limited to the first visit. It covers every encounter where the patient receives active treatment for the fracture.

That includes the emergency department visit, the surgery, and a return trip for repeat debridement or flap coverage. It also covers evaluation and continuing treatment by a new physician. When active treatment ends and the patient is healing, the code moves to a subsequent encounter character.

S52 uses 16 seventh characters. Each one combines the encounter phase with the fracture type, so read the table across a row and down a column:

The right-hand column is the one that matters for this patient’s whole episode of care. A Gustilo III fracture starts on C and moves to F, J, N, or R once healing begins. It never drops to D, because D describes a closed fracture.

Gustilo classification for open fractures: Types IIIA, IIIB, and IIIC

The Gustilo-Anderson classification, first published by Gustilo and Anderson in the Journal of Bone and Joint Surgery (1976), grades open fractures. It weighs wound size, soft tissue damage, and vascular involvement. Only types IIIA, IIIB, and IIIC support 7th character C.

The treating physician assigns the grade in the operative report or the emergency department note. Coders cannot infer it from wound size or from the nursing assessment. If the note says “open fracture” without a type, query the physician before assigning C.

Clinical scenario: When to use S52.92XC

A 34-year-old construction worker arrives at a community hospital emergency department after his left forearm is caught in machinery. Bone is visible through a large, contaminated wound. The on-call orthopedic surgeon documents a Gustilo IIIA open fracture of the left forearm.

The ED team gives IV antibiotics, irrigates and splints the wound, and transfers him to a trauma center. The 73090 forearm radiograph is still unread at transfer. The ED note does not say which bone is broken.

The ED claim uses S52.92XC. The coder confirms the following before coding:

1. Laterality is left in the ED note and the orthopedic consult
2. The fracture is open and graded Gustilo IIIA by the treating physician
3. The encounter is initial, because the patient is receiving active treatment for a new injury
4. The forearm site is unspecified, because no note names the radius or the ulna

At the trauma center, the surgeon performs irrigation, debridement, and external fixation. The CT report names fractures of both the radial and ulnar shafts. The trauma surgeon’s claim keeps the initial encounter character C but drops the unspecified code. It reports S52.302C for the left radial shaft and S52.202C for the left ulnar shaft.

Six weeks later, he returns for a wound check while the fracture heals as expected. That visit is no longer initial. It is coded with 7th character F on those more specific shaft codes, S52.302F and S52.202F. F marks a subsequent encounter for an open type III fracture with routine healing.

The site and the 7th character change at different points in the episode, as the path below shows.

Adjacent and commonly confused codes

S52.92XC sits within a dense cluster of codes that differ by a single character. Selecting the wrong one sends the claim back or triggers a medical necessity denial. These are the official S52.92X codes, plus the right-side counterpart.

Documentation requirements for accurate S52.92XC coding

Payers reviewing S52.92XC claims look for five documentation elements. Missing any one of them puts the claim at risk of denial.

• Laterality: The word “left” must appear in the encounter note. A bilateral injury needs a code for each side.
• Open fracture confirmation: The note must describe the fracture as open (compound). An unlabeled fracture defaults to closed in ICD-10-CM.
• Gustilo grade: The ED or operative note must state IIIA, IIIB, or IIIC. A grade the coder assigns from a wound description is a compliance risk.
• Active treatment: The note must show the patient is receiving active treatment, such as ED care, surgery, or a planned return to the operating room.
• Unspecified site rationale: If imaging or the operative note names the bone, the coder must use the more specific code instead.

Accurate documentation also supports clean claim submission downstream. When the diagnosis and procedure codes match the record, payers are less likely to request more documentation.

Payer requirements and prior authorization

Payers generally accept initial encounter claims for open fractures as medically necessary when the record supports them. The record needs to show the injury event, the Gustilo grade, and the treatment given. The key payer expectations for S52.92XC claims:

• The injury date and mechanism must be documented, along with external cause codes where the payer requires them
• The diagnosis must fit the procedure billed, such as open fracture debridement, fixation, or vascular repair
• Emergency surgery generally does not need prior authorization, but a planned return to the operating room may need it
• An ED visit on the day the decision for surgery is made may need modifier 57 on the E/M line

Pabau’s claim validation and the Claim.MD clearinghouse catch missing or invalid claim details before submission. Matching the diagnosis to the procedure stays a coding check for your team.

Teams with a high volume of orthopedic trauma claims can use denial management workflows to track repeat denials and fix them at the documentation level.

Common CPT codes billed with S52.92XC

Initial encounters for high-grade open forearm fractures usually run through the ED and the operating room. They often include one or more of the following procedure codes. National Correct Coding Initiative (NCCI) edits apply, so confirm bundling rules with the payer before you submit a combination.

Watch the pairing between a bone-specific CPT code and an unspecified diagnosis. A claim that bills 25575 for both shafts alongside S52.92XC tells the payer the bone was known. Payer edits and auditors flag that mismatch. Use S52.92XC on the encounters where the site was genuinely unknown, and the specific code once it is documented.

Top claim denial reasons for S52.92XC and how to avoid them

Denials on S52.92XC claims follow predictable patterns. Knowing the cause behind each one shortens the correction cycle. The clean claim standards are the same for any complex diagnosis code, but the failure modes here are specific.

Practices with repeat denials on orthopedic trauma claims benefit from tracking them at the code level. Structured medical billing workflows that flag S52.92XC claims for review get a denied claim corrected and resubmitted sooner.

How Pabau supports clean open fracture claims

In most practices, the Gustilo grade and the encounter phase live in free-text notes. Someone at the billing desk reads those notes days later and picks a 7th character. That is where C gets carried into follow-up visits, and where an ungraded open fracture gets guessed at.

Pabau’s claims management software takes the clerical work off that desk. Each claim is pre-filled from the invoice and validated for missing or invalid details. It is then submitted through the clearinghouse.

Your coders still assign the grade and the 7th character from the chart. What changes is that an incomplete claim is flagged before it goes out, instead of coming back from the payer as a rejection.

Reduce fracture claim rework with Pabau

Pabau pre-fills each claim from the invoice and flags missing or invalid details before submission. Orthopedic and surgical practices can then track claim status in one place.

Book a demo

Conclusion

S52.92XC belongs to the acute phase of a serious injury, from the emergency department through the operating room. The costly error comes later, when C stays on the claim after active treatment ends. By then the visit should have moved to F, J, N, or R.

Treat the unspecified site as temporary too. As soon as imaging or the operative note names the bone, the more specific code is the right one. Build both checks into your pre-submission review, and many avoidable denials on this code can be prevented.

Pabau’s claim validation flags missing or invalid claim details before submission, which supports your wider medical billing compliance work. Book a demo to see how Pabau keeps open fracture claims matched to the chart.

Continue your research

Coding the debridement on an open fracture? CPT code 11012 covers debridement down to bone at an open fracture site, a common pairing with S52.92XC.

Stabilizing a contaminated wound first? CPT code 20690 covers a uniplanar external fixation system, often used as temporary stabilization for IIIA and IIIB wounds.

Struggling with denials on fracture encounter codes? Denial codes in medical billing explains the most common CARC codes and how to build a systematic response workflow.

Looking for broader orthopedic billing context? What is revenue cycle management covers the end-to-end claims process for practices managing high-acuity surgical care.

Frequently asked questions