Codes / ICD10CM / S62.659D

S62.659D Nondisplaced fracture of middle phalanx of unspecified finger, subsequent encounter for fracture with routine healing

ICD10CM code

ICD10CM

Chat with GenHealth to automate any coding or chart task.

Name of the Condition

  • Nondisplaced fracture of middle phalanx of unspecified finger, subsequent encounter for fracture with routine healing (ICD-10 Code: S62.659D)

Summary

A nondisplaced fracture of the middle phalanx of an unspecified finger, with routine healing during a subsequent encounter, refers to a break in the middle bone segment of a finger where the bone fragments remain aligned and are progressing normally without complications. This code is used when the patient is being seen for follow-up after the initial injury, and healing is proceeding as expected.

Causes

Direct trauma or impact to the finger, such as from falls, sports injuries, or accidents. Crushing injuries or severe bending forces applied to the finger can also result in this fracture. Repetitive stress or overuse may contribute in some cases, though acute trauma is more common.

Risk Factors

  • Participation in contact sports or activities with a high risk of hand injuries.
  • Occupations involving manual labor or handling heavy equipment.
  • Prior history of hand or finger fractures.
  • Osteoporosis or other conditions that weaken bone density.

Symptoms

  • Pain, swelling, and tenderness in the affected finger.
  • Bruising around the injury site.
  • Limited range of motion or difficulty moving the finger.
  • Possible stiffness or discomfort with movement.

Diagnosis

Physical examination by a healthcare professional to assess pain, swelling, and mobility. Imaging tests, such as X-rays, to confirm the fracture and evaluate healing progress. Documentation of routine healing and the nature of the subsequent encounter is required for accurate coding.

Treatment Options

  • Immobilization with a splint or cast to support the finger during healing.
  • Pain management with over-the-counter or prescription medications.
  • Physical therapy to restore range of motion and strength once healing allows.
  • Monitoring of healing progress through follow-up appointments.

Prognosis and Follow-Up

With proper care, nondisplaced fractures of the middle phalanx typically heal well, and most patients regain full function. Follow-up care is important to ensure healing is progressing without issues. The duration of follow-up depends on the severity of the fracture and the patient’s overall health.

Complications

  • Delayed healing or nonunion if the fracture does not mend properly.
  • Stiffness or reduced range of motion in the finger.
  • Infection, though rare, can occur with open fractures or surgical intervention.
  • Nerve or tendon damage, which may affect sensation or movement.

Lifestyle & Prevention

  • Use protective gear during activities with a high risk of hand injuries.
  • Practice proper ergonomics and take breaks during repetitive tasks to reduce strain.
  • Maintain bone health through a balanced diet rich in calcium and vitamin D.
  • Avoid putting excessive force on the fingers to prevent trauma.

When to Seek Professional Help

Seek medical attention if there is severe pain, swelling, or deformity that does not improve, or if there are signs of infection such as redness, warmth, or pus. Additionally, consult a healthcare provider if there is numbness, tingling, or difficulty moving the finger after an injury.

Tips for Medical Coders

This code is specific to a subsequent encounter for a nondisplaced fracture of the middle phalanx of an unspecified finger with routine healing. Coders must ensure documentation supports the "subsequent encounter" and "routine healing" criteria. The code is not used for initial encounters or fractures with delayed healing, malunion, or nonunion. Accurate documentation of the encounter type and healing status is essential for correct coding.

Book a walkthrough

S62.659D policy automation walkthrough

Walk through the policies, prior authorization requirements, and workflow automation opportunities connected to this code.