ICD-10 Code S32.509A: Unspecified pubis fracture, initial encounter

Key takeaways

ICD-10 Code S32.509A describes an unspecified fracture of unspecified pubis at the initial encounter for a closed fracture, valid for FY2026 claims.

The seventh character A applies while the patient is receiving active treatment. Use D for routine subsequent healing, G for delayed healing, and K for nonunion.

Document the fracture type, the encounter type, and the pubis as the site. Use S32.501A for a right pubic fracture and S32.502A for a left one when the record states the side.

Practice management software like Pabau attaches ICD-10 codes to the encounter record and routes the claim through a clearinghouse, so nobody retypes the code.

ICD-10 Code S32.509A: Definition and billable status

ICD-10 Code S32.509A is a billable ICD-10-CM diagnosis code describing an unspecified fracture of unspecified pubis at the initial encounter for a closed fracture.

It is valid for FY2026, covering discharges and encounters on or after October 1, 2025. Both the UB-04 and the CMS-1500 claim form accept it.

The code sits in the S32 category (fracture of lumbar spine and pelvis) of the ICD-10-CM tabular list, under subcategory S32.5, fracture of pubis. Two characters stay unspecified here: the fracture subtype and the side. So the code fits only when the documentation supplies neither.

According to the CMS ICD-10-CM resources page, S32.509A carries no exclusion notes. It stands on its own as the primary code for a traumatic pelvic fracture.

Code at a glance

Use the table below as a quick reference before coding an initial encounter for a pubic fracture where laterality is not documented.

Clinical overview: Pubic ramus fractures

The pubis is the anterior portion of the pelvic ring, formed by the superior and inferior pubic rami joining at the pubic symphysis. Fractures here follow two mechanisms. Older adults with reduced bone density fall from standing height. Younger patients arrive from high-energy trauma, such as motor vehicle collisions and pedestrian impacts.

For coders, the clinical context decides which secondary diagnoses to consider. It also tells you whether the record can support a laterality-specific code. Five features of pubic fracture coding matter here:

• Mechanism: Falls are the most common cause in patients over 65, often linked to osteoporosis or other fragility conditions.
• Presentation: Groin or pelvic pain on weight-bearing, tenderness on palpation of the pubic rami, and difficulty ambulating.
• Imaging: Plain pelvic X-ray is the first-line study; CT pelvis provides greater detail for surgical planning.
• Stability: Isolated pubic ramus fractures are usually stable injuries not requiring surgical fixation, though bilateral fractures or associated posterior ring disruption may require operative management.
• Laterality documentation: Imaging reports and operative notes should clearly state left, right, or bilateral. When they do not, S32.509A is the correct code.

Understanding the seventh character: A, B, G, and K suffixes

The ICD-10-CM seventh character is required on all traumatic fracture codes in the S00-T88 block. The suffix tells payers which phase of care the encounter represents. Choosing the wrong suffix is one of the most common sources of fracture coding denials, according to AAPC’s ICD-10-CM coding guidance.

Common mistake: Using suffix A for all follow-up fracture visits. The ICD-10-CM Official Guidelines (Section I.C.19.a) are explicit. Suffix A applies only while the patient is receiving active treatment. That holds whether or not it is the patient’s first visit to that provider. Once active treatment ends and the patient enters the healing phase, the encounter type shifts to D, G, or K depending on healing progress.

Documentation requirements for S32.509A

Three elements must be supported by clinical documentation before S32.509A can be assigned. Missing any one of them forces the coder to either query the provider or select a different code.

• Fracture site is the pubis. The operative note, imaging report, or ED note must identify the pubis or pubic ramus as the fractured structure. A general “pelvic fracture” without further detail is insufficient without querying the provider.
• Fracture type is closed. Closed means the skin overlying the fracture site is intact. The physician must document this either explicitly (“closed fracture”) or implicitly through description. Coders cannot determine open versus closed independently.
• Encounter type is initial. The clinical note must reflect that the patient is receiving active treatment for the fracture at this encounter. Emergency department, urgent care, and first-specialist-contact visits typically qualify.
• Laterality is not documented. If the record specifies the side, use S32.501A for the right pubis or S32.502A for the left. S32.509A is correct only when the side is genuinely absent from the documentation. Checking that first protects you when an auditor asks why an unspecified code was used.

The cleanest habit is to get laterality into the note at the index encounter whenever imaging is available. That keeps unspecified codes off every subsequent claim for the same injury.

Related ICD-10 codes and crosswalk

Pubic fracture coding follows a consistent laterality and encounter-type structure. The table below maps S32.509A to its sibling codes and to the adjacent pelvic fracture categories coders reach for most often. Pabau’s diagnostic code library covers the rest of the S32 block.

Laterality and code specificity: When to use S32.509A vs. more specific codes

Unspecified codes are valid when documentation genuinely does not contain the information needed to assign a more specific code. They are not a shortcut around querying the provider. This distinction matters because payers and auditors increasingly flag patterns of overuse of unspecified codes as a documentation quality signal.

Here is the decision workflow that experienced coders use for pubic fractures:

1. Does the record identify the side? If yes, use the laterality-specific code: S32.501A for the right pubis, S32.502A for the left. Bilateral fractures are coded on each side. S32.509A is not appropriate.
2. Is imaging available? If an X-ray or CT report is in the chart and states a side, treat that as the side-specific documentation and use the laterality code. Imaging reports are acceptable source documents.
3. Is the side genuinely absent? If the ED note, imaging report, and operative note all omit laterality, S32.509A is correct. Document in the coding notes that laterality was not available.
4. Should you query? Yes, when the encounter generated imaging that was not reported or not attached to the record. A brief provider query gets the side onto the record and retires the unspecified code for future encounters.

Both decisions sit side by side below, in the order a coder makes them.

Following this workflow keeps unspecified code rates down. It also holds specificity steady across every diagnosis category, not just pelvic fractures.

Commonly paired CPT codes

CPT pairings depend entirely on the treatment rendered and vary by care setting. The table below reflects codes that frequently appear alongside S32.509A based on common clinical management pathways. These pairings are illustrative, not prescriptive. Always code from the documentation.

Billing and reimbursement considerations

S32.509A is accepted on both the CMS-1500 (professional) and the UB-04 (facility) claim form. That covers outpatient orthopedic offices, emergency departments, and inpatient hospital settings.

For inpatient admissions, S32.509A groups to MS-DRG 535 (fractures of hip and pelvis with MCC) or MS-DRG 536 (without MCC), depending on the documented comorbidities. A more specific laterality code does not change the DRG for this fracture category. It does feed the risk-adjustment models used in value-based payment programs.

Practices submitting pelvic fracture claims electronically can route S32.509A through Pabau’s Claim.MD clearinghouse integration. It validates the code against payer edits before submission. The integration reaches thousands of US payers and supports both the CMS-1500 and the 837P electronic claim format.

Teams handling high volumes of musculoskeletal claims should know what makes a clean claim before they submit one. Diagnosis codes also meet medical necessity edits at the payer, and a vague code is what usually trips them. Pabau’s claims management software attaches the ICD-10 code at the encounter level, so the diagnosis reaches the claim without a manual transfer step.

Osteoporotic and fragility pubic fractures: Coding nuances

Pubic ramus fractures in older adults are often fragility fractures. Low-energy trauma, such as a fall from standing height, breaks bone that normal density would have held. The coding turns on the secondary diagnosis.

When the physician documents osteoporosis as a contributing condition, a secondary M80.x code may belong alongside S32.509A. That family covers osteoporosis with a current pathological fracture. The ICD-10-CM Official Guidelines require documentation linking the osteoporosis to this fracture, not just a history of osteoporosis in the problem list.

• M80.051A: Age-related osteoporosis with current pathological fracture, right femur, initial encounter. An adjacent reference only, never a substitute for a pubic fracture code.
• M80.08XA: Age-related osteoporosis with current pathological fracture, vertebra, initial encounter. Included to show how the family is structured by site.
• M81.0: Age-related osteoporosis without current pathological fracture (use when osteoporosis is documented but no pathological fracture link is stated; S32.509A remains the primary).

Documentation trigger: Look for “fragility fracture,” “insufficiency fracture,” or “fracture due to osteoporosis” in the attending note or the discharge summary. Those phrases support dual coding.

A bare “history of osteoporosis” in the medical history does not. Without a stated clinical link to this fracture, there is nothing to hang an M80.x secondary on. Query the provider instead of adding the diagnosis on inference.

Secondary diagnosis coding here also feeds hierarchical condition category (HCC) risk scores in Medicare Advantage plans. So the same two lines in a note move both the claim and next year’s risk score.

Treatment context and clinical management

Coders working follow-up encounters need the typical treatment arc for isolated pubic fractures. It decides which seventh-character suffix applies on a return visit.

• Conservative management (most common): Pain control, limited weight-bearing, physical therapy. Healing typically occurs over 6 to 12 weeks. Follow-up encounters during this period use suffix D (routine healing) unless healing is delayed.
• Surgical fixation: Reserved for unstable pelvic ring injuries or bilateral fractures with posterior ring disruption. Postoperative follow-ups use suffix D initially, shifting to G if healing is delayed or K if nonunion is documented.
• Physical therapy: Gait training and strengthening exercises typically begin at 4 to 6 weeks for stable injuries. PT encounters are coded with the musculoskeletal diagnosis as the primary code alongside the applicable PT CPT codes (e.g., 97110, 97530).

Knowing this arc helps coders pick the correct subsequent encounter code, so each claim reflects the phase of care delivered. Submitting an initial-encounter suffix on a routine follow-up visit is an audit flag, and it is one of the easiest to spot from the outside.

How Pabau keeps the diagnosis code attached to the claim

In most practices the diagnosis is written in one place and typed into the claim in another. A coder reads the ED note, settles on S32.509A, and someone re-enters it in the billing tool. Each hand-off is a chance to drop a digit or the seventh character.

Pabau holds the encounter record and the claim in one system. The code assigned at the encounter is the code that leaves the practice, and the Claim.MD integration checks it against payer edits before submission. No one retypes the code, so no transcription step can corrupt it.

For a coding team, that turns rejections tied to a mistyped diagnosis code into a rarity rather than a monthly clean-up. It also leaves an audit trail showing which code was assigned at which encounter, and by whom.

Reduce coding errors on musculoskeletal claims

Pabau attaches ICD-10 codes at the point of care and routes them through the Claim.MD clearinghouse, cutting transcription errors and reducing pelvic fracture claim rejections.

Book a demo

Conclusion

S32.509A is a legitimate code, not a shortcut. Assigned where the record genuinely omits the side, it is defensible on any audit. Assigned out of habit, it becomes a pattern a payer can read straight off your claim history.

The trade-off worth remembering is timing. Specificity is cheap to capture at the index encounter and expensive to reconstruct a year later. One line in the note, or one short provider query, decides which code you end up defending.

Keeping the code attached to the encounter from documentation through to submission is what removes the retyping step. Book a demo to see how your coders and billers can work from one encounter record instead of two systems.

Continue your research

Need to understand how claims move from diagnosis to payment? What is medical billing covers the end-to-end revenue cycle workflow from encounter coding to remittance.

Want to reduce pelvic fracture claim denials? Denial management in healthcare explains the most common denial categories and how to fix the documentation behind them.

Submitting 837P claims electronically? Electronic remittance advice walks through how ERAs map back to submitted diagnosis codes and how to reconcile payer responses.

Frequently asked questions