Codes / ICD10CM / S36.499D

S36.499D Other injury of unspecified part of small intestine, subsequent encounter

ICD10CM code

ICD10CM

Chat with GenHealth to automate any coding or chart task.

Name of the Condition

  • Other injury of unspecified part of small intestine, subsequent encounter (ICD-10-CM Code: S36.499D)

Summary

Other injury of the unspecified part of the small intestine, subsequent encounter, refers to documented damage to the intestinal tissue that is not classified into more specific categories (e.g., laceration, contusion) and is being evaluated or treated during a follow-up visit. This code applies when the injury was initially documented and the patient is now receiving care for ongoing or residual effects. The condition may involve partial or complete disruption of the intestinal wall, with potential complications like bleeding, infection, or obstruction if untreated.

Causes

Injuries to the small intestine can result from blunt or penetrating abdominal trauma, including motor vehicle accidents, falls, or penetrating wounds (e.g., stab or gunshot injuries). Iatrogenic injury during surgical procedures is another possible cause. Non-traumatic mechanisms, such as severe abdominal compression or sudden forceful impact, may also lead to this type of injury.

Risk Factors

  • Engaging in high-risk activities without protective gear.
  • Pre-existing conditions that weaken abdominal organs (e.g., prior surgery or inflammatory bowel disease).
  • Lack of seatbelt use or improper safety precautions during travel.
  • Occupational exposure to trauma risks (e.g., construction or combat).

Symptoms

  • Acute abdominal pain or tenderness.
  • Nausea, vomiting, or abdominal distention.
  • Signs of internal bleeding (e.g., dizziness, fainting, or low blood pressure).
  • Abdominal rigidity or guarding.
  • Blood in stool or vomit (in severe cases).

Diagnosis

Physical examination to assess abdominal tenderness, rigidity, or bruising. Imaging tests, such as CT scans or ultrasounds, to visualize intestinal damage and bleeding. Blood tests to evaluate for anemia or infection. Diagnostic laparoscopy may be used in uncertain cases to directly inspect the intestine.

Treatment Options

Treatment depends on the severity of the injury and may include observation, supportive care (e.g., IV fluids, pain management), or surgical intervention to repair or remove damaged tissue. Antibiotics may be prescribed to prevent or treat infection. Follow-up care focuses on monitoring for complications and ensuring healing.

Prognosis and Follow-Up

Prognosis varies based on the extent of the injury and timely treatment. Most patients recover with appropriate care, but severe cases may require prolonged recovery or additional interventions. Follow-up visits are essential to assess healing, manage symptoms, and detect complications like infection or obstruction.

Complications

  • Infection of the abdominal cavity (peritonitis).
  • Intestinal obstruction or perforation.
  • Chronic pain or adhesions.
  • Delayed healing or fistula formation.

Lifestyle & Prevention

  • Use seatbelts and proper safety gear during travel or high-risk activities.
  • Avoid situations with increased risk of abdominal trauma.
  • Maintain overall abdominal health through regular check-ups, especially if pre-existing conditions exist.

When to Seek Professional Help

Seek immediate medical attention for severe abdominal pain, signs of internal bleeding (e.g., dizziness, fainting), or persistent vomiting. Follow-up care is necessary if symptoms worsen or new complications arise.

Tips for Medical Coders

Use this code for subsequent encounters (D) when the patient is receiving care for an unspecified small intestine injury that was previously documented. Ensure the encounter is classified as "subsequent" and that the injury is not further specified. Document the nature of the follow-up care (e.g., evaluation, treatment) to support code assignment.

Book a walkthrough

S36.499D policy automation walkthrough

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