ICD-10 Code S72.021R: displaced fracture of right femur with malunion

Key Takeaways

S72.021R describes a displaced fracture of the epiphysis (separation) (upper) of the right femur, coded at a subsequent encounter for a closed fracture with malunion.

The 7th character R specifically indicates malunion: the fracture has healed in an abnormal anatomical position, distinct from nonunion (failed healing) or delayed healing.

Coders must not apply S72.021R at initial presentation: it is a subsequent encounter code, requiring imaging or clinical confirmation of malunion before use.

Pabau’s claims management software supports orthopedic billing workflows, including subsequent encounter and malunion coding validation.

ICD-10 Code S72.021R: definition and clinical description

S72.021R is the ICD-10 Code for a displaced fracture of the epiphysis (separation) (upper) of the right femur, subsequent encounter for closed fracture with malunion. Most orthopedic billing denials for this code trace back to one of three mistakes: using it at initial presentation, confusing malunion with nonunion, or missing laterality in the clinical note. This reference covers every element coders need to apply ICD-10 Code S72.021R correctly, from the 7th character system through documentation requirements and sibling codes. Like other ICD-10 diagnostic code references, getting each modifier right determines whether the claim pays first time.

Understanding the 7th character ‘R’ in ICD-10 Code S72.021R

The 7th character is the most consequential part of the S72.021x code. It encodes both the encounter type (initial vs. subsequent vs. sequela) and the healing status at the time of the visit. Getting this wrong is the fastest route to a denial or a compliance audit.

For S72.021R, the character R means: subsequent encounter, closed fracture, malunion. That triple condition must be satisfied simultaneously. Coders often treat subsequent-encounter coding as a detail rather than a threshold, but ICD-10 subsequent encounter coding rules require each element to be independently documented in the medical record.

What is malunion and why does it matter for coding?

Malunion means the fracture has healed, but in an incorrect anatomical position. The bone consolidates, but not where it should. That’s the key clinical distinction coders must understand before applying ICD-10 Code S72.021R.

Two closely related terms cause repeated coding errors. Understanding the difference protects both claim accuracy and audit defensibility. Checking this against solid ICD-10-CM diagnostic coding guidance helps coders frame each encounter type correctly.

• Malunion (7th character R): Fracture has healed, but in an abnormal position. Bone consolidation is complete. Clinical symptoms may include limb malalignment, shortened extremity, altered gait, or chronic pain. Imaging confirms bony union in a non-anatomic position.
• Nonunion (7th characters K, M, N, P, Q): Fracture has failed to heal within an expected timeframe. The fracture gap persists. No bony bridging on imaging. The patient may have persistent pain, instability, or movement at the fracture site.
• Delayed healing (7th characters G, H, J): Healing is occurring but is slower than expected. Radiographic callus formation is present but incomplete. The process is still active, not arrested.

Malunion requires a fundamentally different clinical note than nonunion. The physician must document bony consolidation in a malposition, not just persistent symptoms or slow callus formation. Without that explicit statement, a payer reviewing the claim has no clinical basis for approving 7th character R over G or K.

When to use S72.021R: subsequent encounter guidance

S72.021R is a subsequent encounter code. It cannot be used at the initial emergency department visit, urgent care presentation, or first fracture clinic appointment where the fracture is being actively managed for the first time.

Applying it too early is one of the most flagged patterns in orthopedic billing audits. Understanding when the encounter threshold genuinely shifts from initial to subsequent matters as much as knowing the code itself. Poor claim denial management often starts with encounter-type errors that could have been caught at the documentation stage.

1. Initial encounter (7th character A, B, or C): The patient receives active fracture treatment for the first time. This includes the emergency visit, initial surgical intervention, cast application, and the immediate postoperative period.
2. Transition point: Once the definitive treatment plan is established and the patient moves into routine follow-up, subsequent encounter codes apply. This is provider-defined, not time-defined.
3. Subsequent encounter (7th character D through R): The patient attends follow-up visits during which the physician assesses healing progress, manages complications, or adjusts treatment. The healing status at each visit determines which 7th character to select.
4. Malunion confirmed (use S72.021R): Imaging at a follow-up visit demonstrates bony consolidation in an abnormal position. The physician documents this finding explicitly as malunion. The code S72.021R applies from that visit forward.
5. Sequela (7th character S): Used when coding conditions that are the direct result of a healed fracture, not the fracture itself. Do not confuse sequela coding with subsequent encounter coding.

Documentation requirements for S72.021R

Each element of the code must be independently supported in the medical record. A single missing documentation element is enough to trigger a denial or an audit finding. Strong medical billing workflows build this checklist into the chart note review process before claim submission.

• Displacement confirmed: Documentation must state the fracture is displaced. “Displaced” is not implied by fracture type; it must be explicit. Undisplaced fractures use a different code series (S72.022x for left femur, and the equivalent non-displaced codes for right).
• Fracture location: Epiphysis (upper) of the femur must be specified. Neck of femur and epiphysis (separation) are anatomically distinct in ICD-10-CM. Confirm the physician’s note references the epiphyseal or growth plate region of the proximal femur.
• Laterality: Right femur must be documented. If the note says “femur” without laterality, use the unspecified code (S72.001x) rather than S72.021R. Never code laterality not explicitly stated.
• Fracture type: Closed fracture. If the fracture was open (skin integrity disrupted), different 7th characters apply (E, F, H, J, M, N, Q, or R depending on Gustilo-Anderson classification).
• Encounter type: Subsequent encounter must be documented. Active fracture management has concluded and the patient is in the follow-up phase.
• Malunion confirmed: This is the highest-risk documentation gap. The physician must explicitly state malunion or describe bone healing in an abnormal anatomical position. Imaging findings (X-ray or CT) showing bony union in a malposition should be referenced or described.

Practices that manage high volumes of orthopedic follow-up claims benefit from using medical billing compliance frameworks that integrate documentation checklists directly into the post-visit workflow.

Parent code and code hierarchy for S72.021R

Understanding where S72.021R sits in the ICD-10-CM hierarchy helps coders navigate the tabular list and cross-check code selection. Practices managing orthopedic billing at scale use orthopedic claims management software to validate code selections against the correct code hierarchy before submission.

Streamline orthopedic billing with Pabau

Pabau’s claims management tools help orthopedic and physical therapy practices submit cleaner claims, track subsequent encounter codes, and reduce denial rates on fracture follow-up billing.

Book a demo

Sibling and related codes for S72.021R

The S72.021x code family shares the same anatomical location (displaced epiphysis fracture, upper femur) and differs only by laterality (right vs. left vs. unspecified) and 7th character (encounter type and healing status). Coders also regularly cross-reference nearby codes within S72.0 for neck-of-femur fractures. Submitting claims through electronic claims via Claim.MD allows practices to validate these code families against payer edits before they reach the clearinghouse.

Common coding errors to avoid with S72.021R

Fracture malunion coding errors cluster around a small number of predictable patterns. Each one is avoidable with a structured pre-submission review. Practices that reduce denied claims on subsequent encounter codes typically standardize this review process at the point of note sign-off, rather than at the billing desk. Connecting to a medical claims clearinghouse with built-in edit checks can catch these errors before they reach the payer.

• Using the initial encounter code (A) for follow-up visits: The most common error in orthopedic fracture billing. Once the initial treatment phase ends, subsequent encounter codes apply. Using 7th character A at a 6-week follow-up visit is an automatic payer flag.
• Confusing malunion (R) with nonunion (K): These are distinct clinical conditions. Malunion means healed in the wrong position. Nonunion means failed to heal. The documentation must describe which condition applies; coders cannot infer one from the other.
• Using S72.021R for open fractures: ICD-10 Code S72.021R specifies a closed fracture. If the original injury involved a wound communicating with the bone, open fracture 7th characters (B, C, E, F, H, J, M, N, Q) apply instead, depending on Gustilo-Anderson classification.
• Missing laterality: Right femur documentation must be explicit. If the operative report or office note does not specify left or right, coders must use the unspecified laterality code (S72.023x). Coding right when the documentation says “femur” without side is a compliance violation.
• Coding S72.021R without imaging documentation of malunion: Payers increasingly request imaging reports to substantiate malunion claims. The chart note must reference X-ray or CT findings confirming bony union in an abnormal position. Symptom descriptions alone do not support the use of 7th character R.

Reviewing electronic remittance advice on denied S72 claims often reveals which of these patterns is driving rejections for a specific practice’s patient population.

Clinical context: displaced epiphyseal fractures of the upper femur

Epiphyseal fractures of the upper femur are injuries to the growth plate region at the proximal end of the femur. The Salter-Harris classification system defines the severity of growth plate involvement. These fractures are most common in the pediatric and adolescent population, typically following high-energy trauma such as motor vehicle accidents or significant falls from height.

Displacement matters both clinically and for coding accuracy. A displaced fracture means the bone fragments have shifted position relative to each other. Clinically, this raises the risk of avascular necrosis of the femoral head, growth disturbance, and, as captured by ICD-10 Code S72.021R, malunion. Practices managing orthopedic follow-up for this population, including those providing physical therapy EMR software workflows post-surgery, depend on precise subsequent encounter coding to reflect the actual healing trajectory.

Malunion in this anatomical location typically presents as limb length discrepancy, hip joint malalignment, or altered gait mechanics. Long-term outcomes depend significantly on how quickly the malunion is identified and whether corrective osteotomy or other intervention is warranted. The coding system reflects this clinical reality: ICD-10 Code S72.021R exists to capture follow-up care for a complication that carries distinct management and reimbursement implications compared to routine fracture healing.

Conclusion

Coding ICD-10 Code S72.021R accurately requires three conditions to align in the medical record: the fracture is displaced, the encounter is subsequent (not initial), and imaging confirms malunion as opposed to nonunion or delayed healing. Missing any one of these tips a clean claim into a denial or an audit finding.

Pabau’s claims management software supports orthopedic practices in validating subsequent encounter codes and managing the full billing lifecycle for fracture follow-up care. To see how it fits your workflow, book a demo.

Continue your research

Need to understand clean claim requirements for orthopedic billing? Clean claim best practices covers the documentation and submission standards that prevent first-pass denials.

Want to understand how remittance data identifies denial patterns? Electronic remittance advice explains how ERA files surface denial reasons and support appeal workflows.

Looking for a reference on medical billing fundamentals? What is medical billing covers the end-to-end revenue cycle process for healthcare practices.

Frequently Asked Questions