Codes / ICD10CM / S36.252D

S36.252D Moderate laceration of tail of pancreas, subsequent encounter

ICD10CM code

ICD10CM

Chat with GenHealth to automate any coding or chart task.

Name of the Condition

  • Moderate laceration of tail of pancreas, subsequent encounter (ICD-10-CM Code: S36.252D)

Summary

Moderate laceration of the tail of the pancreas, subsequent encounter, refers to a partial tear or cut in the pancreatic tissue at the tail region during a follow-up visit for an injury that occurred previously. The tail of the pancreas, the leftmost portion of the organ, may sustain such damage, potentially leading to localized complications like bleeding, infection, or ductal injury if not fully resolved. This code is used for encounters after the initial injury to document ongoing management or recovery.

Causes

Moderate lacerations of the pancreatic tail are typically caused by blunt abdominal trauma, such as motor vehicle accidents, falls, or direct blows to the abdomen. Penetrating injuries, including stab wounds or gunshot wounds, can also damage the pancreas. Iatrogenic injury may occur during surgical procedures involving the abdomen, particularly those near the pancreatic tail.

Risk Factors

  • Lack of seatbelt use in vehicles.
  • Participation in high-impact sports without protective gear.
  • Environments with a high risk of physical trauma.
  • Pre-existing conditions that alter pancreatic anatomy or increase fragility.

Symptoms

  • Persistent or recurrent upper abdominal pain, often in the left upper quadrant.
  • Nausea, vomiting, or loss of appetite.
  • Abdominal tenderness or swelling.
  • Signs of internal bleeding, such as dizziness, fainting, or low blood pressure.
  • Elevated heart rate or shock in severe cases.

Diagnosis

Diagnosis involves a physical examination to assess abdominal tenderness and swelling, followed by imaging studies like a CT scan or MRI to visualize the pancreatic tail and identify residual damage. Laboratory tests, including amylase and lipase levels, may be used to evaluate pancreatic function. The subsequent encounter context confirms the injury is being managed after the initial event.

Treatment Options

Treatment depends on the severity of the laceration and may include observation, pain management, and monitoring for complications. In some cases, surgical intervention may be required to repair the pancreatic tail or address ductal damage. Nutritional support and pancreatic enzyme replacement may be necessary if function is impaired.

Prognosis and Follow-Up

Prognosis is generally favorable with appropriate treatment, though complications like infection or pseudocyst formation can occur. Follow-up care focuses on monitoring for healing, assessing pancreatic function, and addressing any ongoing symptoms. Regular imaging or lab tests may be used to track recovery.

Complications

  • Infection at the injury site.
  • Pancreatic pseudocyst formation.
  • Ductal damage leading to chronic pain or dysfunction.
  • Recurrent bleeding or abdominal pain.
  • Long-term pancreatic insufficiency.

Lifestyle & Prevention

  • Use seatbelts and protective gear during high-risk activities.
  • Avoid situations with a high risk of abdominal trauma.
  • Follow post-injury care instructions to support healing.
  • Maintain a balanced diet to support overall pancreatic health.

When to Seek Professional Help

Seek immediate medical attention if you experience severe abdominal pain, signs of internal bleeding (e.g., dizziness, fainting), or persistent vomiting. Follow up with a healthcare provider if symptoms worsen or new complications arise during recovery.

Tips for Medical Coders

Use this code for subsequent encounters related to a moderate laceration of the pancreatic tail. Document the encounter type (subsequent) and ensure the injury is linked to a prior event. Verify that the laceration is moderate and localized to the tail of the pancreas, with no indication of more severe disruption or additional injuries.

Book a walkthrough

S36.252D policy automation walkthrough

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