ICD code S32.461G – Displaced acetabulum fracture

Key takeaways

S32.461G is billable for a displaced transverse-posterior fracture of the right acetabulum at a follow-up visit where healing is delayed.

7th character G means delayed healing. Use D instead when the fracture is healing normally at a subsequent encounter.

The physician’s note must state that healing is delayed, for example citing inadequate callus on imaging, because coders cannot infer it from symptoms.

Pabau, the practice management platform we build, submits S32.461G claims electronically and tracks them, but the 7th character still comes from the physician’s note.

ICD-10 Code S32.461G: code details at a glance

ICD-10 Code S32.461G is the billable ICD-10-CM code for a displaced associated transverse-posterior fracture of the right acetabulum with delayed healing at follow-up. It is valid for fiscal years 2025 and 2026, and the table below holds the reference data coders need before submission.

Verify current validity against the CMS ICD-10 codes page, which publishes the official annual code files each October. Codes in the S32 block have stayed stable across recent fiscal years. Checking before each October update still avoids rejected claims on revised descriptors.

Clinical description: displaced associated transverse-posterior fracture of the acetabulum

The acetabulum is the cup-shaped socket in the pelvis that forms the hip joint with the femoral head. A displaced associated transverse-posterior fracture is a two-component injury. The Judet-Letournel classification calls it an “associated pattern” because it combines two elementary fracture types. One is a transverse fracture line crossing the acetabulum, and the other is a fracture of the posterior wall.

“Displaced” means the fracture fragments have shifted out of their anatomical position. This matters for coding because nondisplaced fractures of the same pattern take different codes, S32.464- to S32.466-.

• Transverse component: a horizontal fracture line dividing the acetabulum into superior and inferior halves, disrupting the weight-bearing dome
• Posterior wall component: fracture of the posterior rim of the acetabulum, which normally prevents posterior femoral head dislocation
• Associated pattern: both components are present at once, and neither alone qualifies for this specific code
• Displaced: fragment displacement confirmed on imaging; the nondisplaced equivalent uses a different 6th character
• Right-sided: 6th character “1” specifies the right acetabulum; left-sided injuries are coded S32.462G

This fracture pattern is typically caused by high-energy trauma, with motor vehicle collisions, falls from height, and dashboard injuries the most common mechanisms. Older patients may sustain it from lower-energy falls when bone quality is compromised. Two components make surgical fixation more technically demanding than either elementary type alone. That is why follow-up care is intensive and delayed healing is a recognized complication.

Understanding the 7th character G: subsequent encounter for fracture with delayed healing

The 7th character G, as defined in the ICD-10-CM Official Guidelines (Section I.C.19.c), denotes a subsequent encounter at which the fracture is healing with delay. It sits between routine healing (D) and confirmed nonunion (K). The table below compares all six valid 7th characters for the S32.461 family: A, B, D, G, K and S.

A frequent coder error is using G when D applies, or the reverse. The physician’s note is the only basis for this choice. Coders must not infer healing status from symptoms, pain complaints, or the number of weeks since injury.

The note must state explicitly that healing is delayed. It should describe the clinical evidence, such as inadequate callus formation on radiographs or an assessment of stalled progress. It should also support the conclusion that nonunion has not been confirmed.

When is S32.461G the correct code? Coding guidelines and documentation

S32.461G is correct only when all five of the following conditions are met. Verify each against the physician note before submitting the claim.

1. The encounter is a follow-up, not active treatment. Active-treatment visits use 7th character A, or B for an open fracture. These include the initial surgery, the first emergency department evaluation, and any visit starting definitive management. Once the patient returns for monitoring, the subsequent encounter extensions (D, G and K) apply.
2. The fracture is a displaced associated transverse-posterior pattern. The physician note or operative report must document both the transverse component and the posterior wall component. A transverse-only or posterior-wall-only fracture does not match this descriptor.
3. The injured side is the right acetabulum. The 6th character “1” is laterality-specific. Left-sided injuries are S32.462G, and unspecified laterality uses S32.463G. Confirm the side documented in the physician’s note before assigning laterality.
4. Healing is delayed, not routine. The physician note must explicitly characterize healing as delayed. Acceptable supporting language includes “inadequate callus formation on radiograph,” “healing slower than expected,” and “fracture lines still visible at [X] weeks post-op.” Do not code G based solely on the patient’s pain level or time elapsed.
5. Nonunion has not been confirmed. Once the physician confirms nonunion, use K. S32.461G is the transitional code when the clinical picture is concerning but definitive failure has not been established.

When the documentation context is ambiguous, review the tabular Excludes notes for the S32 block alongside the Official Guidelines before you assign the code.

Sibling codes: S32.461G vs S32.461D, S32.461K and S32.461S

Choosing among the six valid S32.461 extensions hinges on the clinical status the physician documents. The table below compares the four that coders confuse most often at follow-up visits.

A practical test: if the physician’s note says anything equivalent to “healing well” or “on track,” the code is S32.461D, not S32.461G. If the note says “slower than expected” or “delayed,” G applies. If the note records nonunion as a confirmed diagnosis, switch to the nonunion extension. A visit treating avascular necrosis or post-traumatic arthritis caused by the fracture takes the S extension, with a separate code for the resulting condition. The guide below maps all six extensions to the two questions that decide them.

Commonly paired CPT codes and procedures

At a subsequent encounter for delayed healing, the services billed alongside S32.461G depend on what the physician performs at that visit. The table below lists the CPT codes most commonly paired with S32.461G in orthopedic and rehabilitation settings.

Physical therapy services billed with S32.461G need documentation that ties the therapeutic goal to the delayed healing status. Payers may deny PT claims if the functional impairment is attributed only to the acute fracture rather than to the documented complication of delayed healing.

Payer requirements and prior authorization for S32.461G

Prior authorization requirements for services coded with S32.461G vary by payer type and plan year. Always verify current requirements directly with the specific payer before the patient encounter.

• Medicare: Under Medicare Part B, follow-up office visits (E/M codes) for established patients with fracture complications do not typically require prior authorization. Imaging ordered at that visit may still trigger a documentation requirement under certain Local Coverage Determinations (LCDs). Review the relevant orthopedic LCD in the Medicare Coverage Database for your MAC jurisdiction.
• Medicaid: Prior authorization rules vary by state. Complex pelvic fracture follow-up often requires pre-authorization in Medicaid managed care plans, particularly when surgical revision is being considered. Confirm with each state plan individually.
• Commercial insurance: Plans vary widely. Imaging and surgical procedures ordered at the follow-up encounter are the most common trigger for prior authorization requirements. Obtain authorizations before scheduling CT or MRI for delayed healing assessment.
• Medicare Advantage: MA plans apply their own prior authorization policies, which may be more restrictive than traditional Medicare. Confirm with the specific plan. The insurance eligibility verification step should always include checking plan-specific authorization requirements for fracture-related services.

Understanding the medical billing process for complex fracture follow-up helps billing teams anticipate which services need pre-authorization. They can then secure it before the encounter rather than scrambling after a denial arrives.

Common claim denial reasons and how to prevent them

Denials on S32.461G cluster around a predictable set of documentation and coding failures. Good claims software for practices submits and tracks each claim, but it cannot judge whether the note supports a G extension. The table below maps the most common denial reasons to their root causes and fixes.

Denial management workflows that track which denial categories recur on fracture follow-up claims let you aim documentation education at the root cause. Practices that only fix individual denied claims see the same denial types return on the next billing cycle.

Submitting and tracking S32.461G claims

Claims carrying S32.461G go out on the CMS-1500 (professional) or UB-04 (facility) claim form. Submitting a clean claim for a delayed-healing fracture visit means checking four elements before the claim leaves the practice:

• The correct 7th character for this encounter
• Confirmed laterality against the documented side
• Documentation that supports the healing-status assertion
• Any required prior authorization, attached as supporting documentation

After adjudication, the payer returns an electronic remittance advice (ERA, or 835 file). It carries claim adjustment reason codes (CARCs) that map to the denial categories above. The medical billing denial codes reference explains how to read and act on each CARC returned on a rejected S32.461G claim. Reading them on receipt shortens the appeals cycle and gets the corrected claim back to the payer faster.

Coding resources for the S32 pelvic fracture block

Official and third-party resources coders should bookmark when working with S32.461G and the broader S32 pelvic fracture block:

• CDC/NCHS ICD-10-CM web tool: official tabular list lookup by fiscal year; the authoritative source for code validity and Excludes notes
• WHO ICD-10 browser: international ICD-10 hierarchy; useful for understanding the structural context of the S32 block outside the CM edition
• AAPC Codify ICD-10-CM: includes Excludes notes, code history, and crosswalk data for the S32.461 family

How Pabau keeps fracture follow-up claims moving

Once the physician’s note supports G, the remaining work is getting the claim out and watching what comes back. Without an integrated system, billing staff key each claim into a payer portal, then chase its status by phone, one claim at a time.

Pabau turns the visit invoice into an electronic CMS-1500 claim through its Claim.MD integration, which reaches thousands of US payers. It checks the patient’s coverage in real time before the visit and tracks each claim’s status after submission.

When the payer responds, the ERA comes back into Pabau and ties the payment to the claim it settles. Your team sees a denied S32.461G claim next to its reason code, so they can fix the note or the extension and resubmit. Pabau submits the codes your coders assign, and the choice between D and G still rests on the physician’s documentation.

Submit and track fracture claims in one place

Pabau turns visit invoices into electronic claims, checks coverage in real time, and brings remittances back into your billing workflow. Your team sees each denied claim and its reason code without chasing payer portals.

Book a demo

Conclusion

Treat G as a documentation question before it is a coding one. If the note doesn’t state that healing is delayed, query the physician before the claim goes out. Coding from pain scores or elapsed weeks is what turns a defensible G into a denial.

Revisit the extension at every follow-up. A fracture coded G at one visit may be coded D at the next as healing catches up, or K once the physician confirms nonunion. Re-reading the note each time stops last visit’s extension from riding onto today’s claim.

To see how Pabau submits fracture follow-up claims and brings remittances back into one billing workflow, book a demo.

Continue your research

Need a framework for handling medical billing denials? Denial management in healthcare covers the workflows that reduce repeat denials across orthopedic and specialty billing.

Want to understand how electronic remittances work after a claim is adjudicated? Electronic remittance advice explains ERA/835 files and how to read CARC denial codes returned on fracture claims.

Looking for guidance on medical billing fundamentals before diving into ICD-10? Revenue cycle management explains the end-to-end billing process for practices managing complex injury claims.

Frequently asked questions