ICD code S72.111P – Displaced fracture of greater trochanter of right femur

Key takeaways

ICD-10 code S72.111P covers a displaced fracture of the right greater trochanter. It applies at a subsequent visit, after the closed fracture healed with malunion.

The 7th character P carries three facts at once: a subsequent encounter, a closed fracture, and malunion healing.

Malunion means the bone healed in poor alignment, so it takes P. Nonunion means it never healed, and that takes K.

There is no S72.119. Under S72.11, unspecified laterality is S72.113 when displaced and S72.116 when it is not.

Practice management software like Pabau puts a searchable ICD-10 library in the record and checks required claim fields before submission.

S72.111P at a glance

S72.111P is not a new code. It has been valid since ICD-10-CM took effect on October 1, 2015, and it carries through to the FY2026 code set.

You can check the current files on the CMS ICD-10 code release page. Because it is billable and specific, it stands on its own on a claim.

What each character of S72.111P actually says

Every segment carries a specific clinical meaning, and reading them in order decodes any S72 variant quickly.

Look closely at what the 6th character does. It carries displacement and side together, so 1 means displaced and right, while 4 means nondisplaced and right. That is why S72.119 does not exist.

The habit of reading 9 as unspecified comes from other subcategories and does not apply here. Under S72.11, an unspecified femur is S72.113 when the fracture is displaced and S72.116 when it is not.

The 7th character is where S72 claims go wrong

Three facts sit inside that one letter: encounter type, fracture type, and healing outcome. Get any of the three wrong and the code is wrong, even though the first six characters are perfect.

Here is the full set that applies to S72.

Notice the pattern in the closed column. A, D, G, K, and P all describe closed fractures, and each one names a different phase or outcome.

Character P applies only to closed fractures. If the original injury was open Type I or II, the malunion character is Q instead. For open Type IIIA, IIIB, or IIIC with malunion, it is R.

Where S72.111P sits in the ICD-10-CM tree

The code sits at the bottom of a clean parent-to-child chain, and only the bottom rung is billable. According to the CDC/NCHS ICD-10-CM web tool, the path runs as follows.

None of the parent codes are billable by themselves. A claim submitted at S72, S72.1, or S72.11 comes back as non-specific. The full seven characters are what make the code valid, and the 7th is not optional padding.

Displaced or nondisplaced: the split is the 6th character

Both options live under the same subcategory. S72.11 covers displaced and nondisplaced fractures of the greater trochanter, and the 6th character separates them. S72.14 is a different injury altogether, an intertrochanteric fracture, so it is not the nondisplaced counterpart to anything in S72.11.

That distinction still needs explicit physician documentation. A radiology report noting a fracture, without characterizing displacement, does not support either branch on its own.

The ICD-10-CM Official Guidelines for Coding and Reporting settle the ambiguous case for you. A fracture documented without displacement status is coded to displaced.

So S72.111P is more often the correct pick than S72.114P when the note is thin. Querying the physician still beats defaulting, because the default is a fallback rather than a finding.

The siblings coders confuse with S72.111P

The S72.111 stem shares its 7th character options with the left-sided and unspecified variants. Picking between them is a documentation-matching exercise, not a clinical judgment call.

Malunion healed badly, nonunion never healed

That one line is the whole distinction, and mixing the two up is the most consequential error on an S72 claim. The two states take different 7th characters, and they can trigger different payer review paths.

Neither state can be inferred from how the patient feels. A coder cannot read pain or a limp as malunion. The treating physician has to write the healing status down, usually with imaging behind it, before either character goes on a claim.

What the note must say before you code S72.111P

Six elements have to be traceable to the record, one for each decision the code makes. Work down the list and the code either holds up or it does not.

• Displacement status: the physician or operative note states “displaced fracture” outright. An imaging report that describes a fracture line without characterizing displacement needs a query first.
• Anatomical site: the note names the greater trochanter, not “proximal femur” or “hip”. The greater trochanter is the bony prominence at the top outer femur, and a vague hip-region note does not reach this subcategory.
• Laterality: the record documents the right side. Bilateral fractures take a separate code for each side. S72.113P is for cases where the side stays unknown after a query.
• Encounter type: the visit is follow-up care, not the initial injury evaluation. Subsequent encounters cover cast changes, rehabilitation supervision, and review after surgical repair.
• Closed fracture confirmation: the original injury had intact skin over the fracture site. An open fracture moves you to Q or R instead.
• Malunion confirmation: the physician documents healing in abnormal alignment. Follow-up imaging usually shows angular or rotational deformity with callus, which confirms that union happened.

How an S72.111P claim moves from visit to payment

The path is short, and only two steps involve any judgment.

1. The visit. The physician reviews the patient, orders follow-up imaging, and documents that the right greater trochanter has united out of alignment.
2. The 6th character. The coder reads the displacement statement and picks 1, for displaced and right-sided.
3. The 7th character. The healing statement supplies P, because the fracture was closed and has now healed with malunion.
4. The procedure code. Whatever happened that day gets its own CPT code, whether that was an office visit, a radiograph, or therapy.
5. Submission. The claim leaves the practice with the diagnosis and the procedure linked on the charge line.
6. The response. The payer pays, or returns a claim adjustment reason code that usually points at documentation rather than at the code itself.

A worked example makes the sequence concrete. A patient returns a few months after a fall, and imaging shows the right greater trochanter united out of position. The physician writes “malunion” in the note.

The claim then carries S72.111P alongside the procedure code for the radiograph. The original injury was closed, so P stays correct no matter how much time has passed.

Before you submit, five quick checks catch almost every avoidable rejection:

• The note says displaced in the physician’s own words, not just “fracture”.
• The note names the greater trochanter, rather than the proximal femur or the hip.
• The side on the claim matches the side in the imaging report.
• The original fracture was closed, which rules out Q and R.
• The word malunion appears in the note, with imaging behind it.

The CPT codes that pair with S72.111P

S72.111P is a diagnosis code, so it needs a paired procedure code before the claim is complete. Which one depends on what happened at that visit, not on the fracture history.

Our reference library of CPT codes carries the full descriptors if you need to check one.

Two rows in that table are easy to swap by accident. 27244 is the plate and screw option, while 27245 is the intramedullary implant, so the operative note decides which one you bill.

Imaging is the usual companion at a malunion visit, and CPT code 73502 covers it. Payer coverage policies can still change which procedure codes are reimbursable next to S72.111P, so treat the rows above as typical rather than settled.

Longer-term help at home after a malunion falls outside CPT altogether. HCPCS code T1020 covers personal care services on a per diem basis, and state Medicaid programs are the usual payer.

The errors that get S72.111P denied

Most of these are pattern errors rather than knowledge errors. They happen when a coder reaches for the code that was right last time.

• The wrong healing character: using D for routine healing when the physician documented malunion. That understates the complexity of the visit and invites medical review.
• Malunion coded as nonunion: P means healed in poor alignment, K means never healed. Reaching for K when the note says “healed with deformity” is a straightforward coding error.
• Initial-encounter A at a follow-up: once the patient has had active treatment, the subsequent characters take over. A belongs to the acute encounter only.
• A made-up unspecified code: S72.119P does not exist. When the side truly is unknown, the displaced unspecified code is S72.113P.
• Unspecified laterality when the record is clear: payers compare the claim against the imaging report, and a side mismatch is quick to spot.
• P on an open fracture: the P character specifies a closed injury. An open fracture history takes Q for Type I or II, and R for Type IIIA, IIIB, or IIIC.

How claims management software keeps S72.111P claims clean

None of that judgment disappears when the workflow goes digital. Coders still read the note in the physician’s language and turn it into ICD-10-CM specificity. What software can remove is the retyping, and retyping is where digits get transposed.

Practice management software like Pabau moves the lookup inside the record. Pabau’s claims management software carries ICD-10-CM, CPT, and HCPCS libraries of more than 20,000 codes, refreshed with each official release.

The claim form then pre-fills from the encounter itself. The procedure code attached to the service lands on the charge line, and the diagnosis slots are seeded from the patient’s recorded problem list.

Pabau also checks that the fields the payer requires are filled before the claim can be sent, including membership and authorization numbers.

In the US it routes through the Claim.MD clearinghouse, which adds eligibility checks, electronic remittance posting, and claim-status tracking. So fewer claims bounce on a blank field, and you see the reason faster when one is rejected.

One boundary is worth stating plainly. No part of that pipeline decides whether P is the right 7th character for your patient. It checks the claim for completeness, not the coding for clinical accuracy. The malunion call stays with the physician and the coder.

Send fracture claims without retyping a code

Pabau’s claims management software puts ICD-10-CM and CPT lookup inside the patient record. It pre-fills the claim from the encounter and checks required fields before you submit. See how it fits an orthopedic or physical therapy workflow.

Book a demo

Conclusion

S72.111P rewards a habit more than it rewards a lookup. Read the 6th character off the displacement statement, take the 7th from the healing statement, and the code assembles itself. Guess at either one and you have described a patient the note does not support.

The trade-off worth remembering is speed against a query. Sending a defaulted code today is quicker than asking the physician one question. A denial three weeks later costs far more than that question would have. Ask it.

If retyping codes between systems is where your fracture claims lose time, that is a fixable problem. Book a demo to see how Pabau keeps coding and claim submission inside the patient record.

Continue your research

Need a system for handling fracture claim denials? Denial management in healthcare covers the common rejection patterns and how practices build a response workflow.

Want to know what makes a claim clean the first time? Clean claim breaks down the fields a payer checks before it accepts a submission.

Curious how a clearinghouse routes ICD-10 claims? Claim.MD clearinghouse explains electronic routing, eligibility checks, and remittance processing.

Looking for a billing compliance framework? Medical billing compliance outlines the documentation standards and audit risk areas behind fracture claims.

Frequently asked questions