ICDcodes.org
FY2027

S82.312KTorus fracture of lower end of left tibia, subsequent encounter for fracture with nonunion

BillableCC

Is S82.312K billable?

Yes — S82.312K is billable for FY2027. S82.312K is a valid, billable ICD-10-CM code at the highest level of specificity in its branch. S82.312K may be submitted for encounters from October 1, 2026 through September 30, 2027.

S82.312K at a glance

CodeS82.312K
DescriptionTorus fracture of lower end of left tibia, subsequent encounter for fracture with nonunion
BillableYes
Code setICD-10-CM FY2027
Valid for encountersOctober 1, 2026 – September 30, 2027
7th character "K"subsequent encounter for fracture with nonunion

What does the 7th character "K" mean in S82.312K?

In S82.312K, the 7th character K means subsequent encounter for fracture with nonunion. The 7th character is required for S82.312K to be a valid, complete code.

Same condition, different episode of care — switch the 7th character:

Which MS-DRGs does S82.312K group to?

S82.312K sits in MDC 08 and helps define the logic of 3 MS-DRGs (version 44, FY2027). Which one a stay actually groups to also depends on procedures and secondary diagnoses.

  • 564Other Musculoskeletal System and Connective Tissue Diagnoses with MCCmedical
  • 565Other Musculoskeletal System and Connective Tissue Diagnoses with CCmedical
  • 566Other Musculoskeletal System and Connective Tissue Diagnoses without CC/MCCmedical

As a secondary diagnosis, S82.312K is a complication or comorbidity (CC), which can move a stay into a higher-paying DRG.

How is S82.312K listed in the Alphabetic Index?

The Alphabetic Index lists these routes under S82.31, the nearest indexed parent of S82.312K. Use them to find the family, then select the specific code.

  • Fracture, traumatictibialower endtorus (abduction) (adduction) (separation)

Excludes1 — never code together — inherited from S82

The conditions below can never be reported together with S82.312K on the same claim. An Excludes1 note means the two conditions cannot occur in the same patient, so reporting both is a coding error.

  • traumatic amputation of lower leg (S88.-)

Excludes1 — never code together — inherited from S82.3

The conditions below can never be reported together with S82.312K on the same claim. An Excludes1 note means the two conditions cannot occur in the same patient, so reporting both is a coding error.

  • bimalleolar fracture of lower leg (S82.84-)
  • fracture of medial malleolus alone (S82.5-)
  • Maisonneuve's fracture (S82.86-)
  • pilon fracture of distal tibia (S82.87-)
  • trimalleolar fractures of lower leg (S82.85-)

Use additional code — inherited from Chapter 19

Report an additional code alongside S82.312K to fully describe the condition. S82.312K is sequenced first.

  • code to identify any retained foreign body, if applicable (Z18.-)

Excludes2 — not included here — inherited from Chapter 19

The conditions below are not part of S82.312K, but a patient may have both at the same time. When documentation supports it, S82.312K and the excluded code may both be reported.

  • birth trauma (P10-P15)
  • obstetric trauma (O70-O71)

Excludes2 — not included here — inherited from S80-S89

The conditions below are not part of S82.312K, but a patient may have both at the same time. When documentation supports it, S82.312K and the excluded code may both be reported.

  • burns and corrosions (T20-T32)
  • frostbite (T33-T34)
  • injuries of ankle and foot, except fracture of ankle and malleolus (S90-S99)
  • insect bite or sting, venomous (T63.4)

Excludes2 — not included here — inherited from S82

The conditions below are not part of S82.312K, but a patient may have both at the same time. When documentation supports it, S82.312K and the excluded code may both be reported.

  • fracture of foot, except ankle (S92.-)
  • periprosthetic fracture around internal prosthetic ankle joint (M97.2)
  • periprosthetic fracture around internal prosthetic implant of knee joint (M97.1-)

How long has S82.312K existed?

S82.312K has been in ICD-10-CM since at least FY2016, the earliest fiscal year on record here.

Derived from the official order files for FY2016–FY2026. FY2017 and FY2020 publish no order file, so those years are not covered.