Chat with GenHealth to automate any coding or chart task.
Name of the Condition
- Nondisplaced fracture of distal phalanx of left little finger, subsequent encounter for fracture with routine healing (ICD-10 Code: S62.667D)
Summary
A nondisplaced fracture of the distal phalanx of the left little finger, with routine healing during a subsequent encounter, refers to a break in the tip bone of the finger where the bone fragments remain in their normal anatomical alignment and are healing as expected. This type of fracture involves minimal displacement, meaning the bone does not shift out of place. The distal phalanx is the most distal segment of the finger, and this injury typically results from direct trauma or impact to the fingertip. The "subsequent encounter" modifier indicates follow-up care after the initial injury, while "routine healing" confirms the fracture is progressing normally without complications.
Causes
Direct trauma or impact to the fingertip, such as from crushing injuries, falls, or accidents. Severe bending forces applied to the finger, often seen in sports or manual labor, can also cause this fracture. Repetitive stress or overuse is less common but may contribute in some cases.
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 at the fingertip.
- Bruising around the injury site.
- Possible deformity or misalignment, though less pronounced than in displaced fractures.
- Limited range of motion or difficulty moving the fingertip.
- Numbness or tingling if nerves are involved.
Diagnosis
Physical examination by a healthcare provider to assess pain, swelling, and range of motion. Imaging studies, such as X-rays, are typically used to confirm the fracture and evaluate alignment. The provider will also review the patient's medical history and mechanism of injury to determine the cause.
Treatment Options
- Immobilization with a splint or buddy taping to support the finger and promote healing.
- Pain management with over-the-counter or prescription medications, as needed.
- Follow-up appointments to monitor healing progress.
- Occupational or physical therapy to restore function and strength once the fracture has healed.
Prognosis and Follow-Up
With proper treatment and routine healing, most nondisplaced fractures of the distal phalanx heal within 4-6 weeks. Full recovery of function is common, though some stiffness or sensitivity may persist temporarily. Follow-up care is essential to ensure the fracture heals correctly and to address any ongoing symptoms.
Complications
- Delayed healing or nonunion if the fracture does not heal as expected.
- Infection, particularly if there was an open wound.
- Stiffness or reduced range of motion in the finger.
- Nerve damage, leading to numbness or tingling.
Lifestyle & Prevention
- Use protective gear, such as gloves, during activities with a high risk of hand injuries.
- Practice proper ergonomics and technique when engaging in manual labor or sports.
- Maintain bone health through a balanced diet rich in calcium and vitamin D.
- Avoid repetitive stress on the fingers when possible.
When to Seek Professional Help
Seek immediate medical attention if you experience severe pain, swelling, or deformity after an injury. Contact a healthcare provider if symptoms worsen, or if you notice signs of infection, such as redness, warmth, or pus at the injury site.
Tips for Medical Coders
When coding for S62.667D, ensure the documentation specifies a subsequent encounter for fracture with routine healing. The code requires confirmation that the fracture is healing normally and that the encounter is for follow-up care. Verify that the laterality (left little finger) and fracture type (nondisplaced) are clearly documented to support accurate coding.
S62.667D policy automation walkthrough
Walk through the policies, prior authorization requirements, and workflow automation opportunities connected to this code.