ICD code S82.161P – Torus fracture of upper end of right tibia with malunion

Key takeaways

ICD-10 Code S82.161P is a billable 7-character code, while the parent S82.161 is not billable on its own.

The 7th character P means a subsequent encounter for fracture with malunion, not nonunion (K) or delayed healing (G).

Coding P rests on provider documentation of malunion, usually supported by imaging.

Pabau, our practice management platform, connects to Claim.MD for electronic claim submission, eligibility checks and denial tracking.

ICD-10 Code S82.161P: definition and code details at a glance

ICD-10 Code S82.161P identifies a subsequent encounter for torus fracture of the upper end of the right tibia where the fracture has healed with malunion. The code is valid for use in the current fiscal year and is billable as a complete 7-character code under the CDC/NCHS ICD-10-CM classification system.

ICD-10-CM code hierarchy for S82.161P

S82.161P sits at the bottom of this chain. Every level above it is a chapter, block, category or subcategory. As a result, none of them is billable on its own.

• S00-T88: Injury, poisoning and certain other consequences of external causes
• S80-S89: Injuries to the knee and lower leg
• S82: Fracture of lower leg, including ankle
• S82.1: Fracture of upper end of tibia
• S82.16: Torus fracture of upper end of tibia
• S82.161: Torus fracture of upper end of right tibia (non-billable parent)
• S82.161P: Subsequent encounter for fracture with malunion (billable)

Clinical definition: torus (buckle) fracture of the upper end of the right tibia

A torus fracture is an incomplete fracture in which one cortex of the bone buckles without breaking through the opposite cortex. The terms torus fracture and buckle fracture are synonyms in ICD-10-CM and in orthopedic texts. Both describe the same injury pattern.

These fractures occur at the tibial metaphysis, the flared region just below the growth plate at the upper end of the tibia. This is because cancellous bone there is softer than mature cortical bone.

Torus fractures mostly affect children because growing bone is more porous and flexible. The cause is usually a force along the length of the bone, such as a fall onto an outstretched leg. However, adults can sustain torus-type injuries too, though far less often.

Understanding the 7th character “P” in S82.161P: subsequent encounter with malunion

The 7th character P means the patient is presenting for a subsequent encounter for fracture with malunion. Per CMS ICD-10-CM Official Guidelines Section I.C.19.c, a subsequent encounter covers any visit after the patient has received active treatment for the fracture. Malunion means the fracture has healed in a non-anatomical position, as documented by the provider and usually supported by imaging. Therefore, both conditions must be present before you select P over any other 7th character.

P, K, and G cause the most confusion in this code family. In particular, P (malunion) and K (nonunion) are often mixed up because both describe complications, yet they are clinically distinct. Malunion means the bone did heal, in the wrong position. By contrast, nonunion means the bone failed to heal at all. The flow below sets out the six options in the order a coder can test them.

7th character options for S82.161: full reference table

S82.161P vs. similar and easily confused codes

ICD-10 Code S82.161P is most often confused with its immediate siblings in the S82.161 family and with the left-tibia equivalent S82.162P. The table below shows the key differences.

Documentation requirements for S82.161P

Supporting S82.161P on a claim takes the six elements below. If any one is missing, the claim is open to denial or audit recoupment. For this reason, a grounding in medical billing fundamentals helps coders read the record the way a payer reviewer will.

• Confirmed laterality: The clinical note and any imaging report must specify the right tibia. Left-side notes cannot support S82.161P.
• Confirmed anatomical site: Documentation must place the fracture at the upper end (proximal region, metaphysis) of the tibia, not the shaft or distal end.
• Torus or buckle morphology: The original fracture diagnosis or the treating physician’s note must describe the fracture as torus, buckle, or incomplete cortical buckling. ICD-10-CM treats these terms as equivalent.
• Provider documentation of malunion: The treating provider must document that the fracture has healed in a non-anatomical position. An X-ray, CT, or MRI report usually supports that finding. However, suspicion of malunion without that note does not justify the P character.
• Subsequent encounter designation: The visit must be a follow-up after active treatment has been received. By contrast, if the patient is presenting for active treatment, use A instead.
• External cause code: An external cause code from the V00-Y99 range is reported when the payer or state requires it. Even so, reporting it is encouraged to capture the mechanism and place of occurrence.

Coding guidelines and official guidance

CMS ICD-10-CM Official Guidelines Section I.C.19.c governs fracture 7th-character assignment. According to CMS, a subsequent encounter is any encounter after the patient has received active treatment for the condition. For example, active treatment includes surgical treatment, an emergency department encounter, and evaluation and treatment by a new physician.

Good medical billing compliance means recording the basis for each 7th-character choice in the patient record. In particular, this matters most for the complication characters P, G, and K.

The CMS ICD-10-CM coding guidelines also clarify that providers should code the most specific diagnosis supported by the record. For that reason, using the non-billable parent S82.161 when S82.161P is the correct code is itself a compliance issue.

Commonly paired CPT codes for S82.161P encounters

ICD-10 Code S82.161P most often appears at follow-up visits, alongside orthopedic evaluation, imaging, and sometimes corrective procedure codes. The table below lists CPT codes often billed with S82.161P, based on AAPC coding guidance and standard orthopedic billing practice. However, you should verify all pairings against the relevant payer LCD before submission.

For example, a typical malunion follow-up pairs an office visit, such as 99213, with a knee X-ray series such as 73560 to document the healed alignment.

Common claim denial reasons for S82.161P and how to avoid them

ICD-10 Code S82.161P draws a predictable set of denial reasons. Most trace back to the notes or to a check that was skipped before submission. For this reason, a structured approach to denial management helps a billing team spot the pattern and fix it at the source.

Knowing the common denial codes helps billing teams read payer remittance advice and write targeted appeal letters. A 7th-character denial can often be fixed with a corrected claim, backed by the provider’s note of malunion. In fact, getting a clean claim out the first time takes far less effort than working a denial queue.

Payer requirements and prior authorization considerations

Medicare and most commercial payers do not require prior authorization for the follow-up office visit itself. However, authorization comes into play when S82.161P supports a procedure claim, such as corrective osteotomy for the malunion. Since requirements vary by payer and plan, verify them with each payer before scheduling any surgery.

Likewise, post-operative physical therapy claims after a malunion correction should carry S82.161P to support medical necessity.

For Medicare claims, consult the relevant MAC Local Coverage Determination for tibial fracture care. CMS does not publish a National Coverage Determination specific to tibial malunion correction, so coverage is set at the MAC level. Also, reimbursement amounts change every year, so always use the current CMS Physician Fee Schedule for rate lookups rather than prior-year figures.

How Pabau supports S82.161P claim submission and denial tracking

Without a connected system, an S82.161P claim passes through several hands. A coder first keys the diagnosis into a billing tool, and then someone uploads the claim to a clearinghouse portal. Finally, a denial surfaces weeks later in a remittance file.

In Pabau’s claims management software, the appointment, the chart note and the claim sit in the same patient record. Pabau also connects to Claim.MD for electronic claim submission, eligibility checks and denial tracking.

When a payer rejects a claim over the 7th character, the denial shows up against the visit it came from. As a result, your billing team can correct the code and resubmit from that record instead of rebuilding the claim by hand.

Submit and track S82.161P claims in one system

Pabau connects to Claim.MD for electronic claim submission, eligibility checks and denial tracking. Malunion follow-up claims leave from the same patient record as the visit note.

Book a demo

Conclusion

Before you assign ICD-10 Code S82.161P, the chart has to show three things. The provider documents malunion, the note names the right tibia, and the visit meets the ICD-10-CM definition of a subsequent encounter. If one is missing, query the provider before the claim goes out, not after the denial comes back.

Most of all, the call that matters is malunion versus nonunion. A bone that healed out of alignment takes P, while a bone that never united takes K instead. In the end, only the provider’s note can tell the coder which one applies.

Pabau connects to Claim.MD for electronic claim submission, eligibility checks and denial tracking. In addition, a corrected malunion claim goes back out from the same patient record. Book a demo to see how it fits your orthopedic follow-up billing.

Continue your research

Need to track denial patterns across your orthopedic claims? Denial management in healthcare covers the workflows billing teams use to track, appeal, and prevent recurring denials.

Want to understand the clearinghouse behind your electronic submissions? How the Claim.MD clearinghouse works explains real-time eligibility, ERA processing, and 837P submission through Pabau.

Looking for a framework to reduce claim errors before submission? What makes a clean claim outlines the checklist billing teams use to maximize first-pass acceptance rates.

Frequently asked questions