Codes / ICD10CM / T62.93XA

T62.93XA Toxic effect of unspecified noxious substance eaten as food, assault, initial encounter

ICD10CM code

ICD10CM

Chat with GenHealth to automate any coding or chart task.

Name of the Condition

  • Toxic effect of unspecified noxious substance eaten as food, assault, initial encounter

Summary

This condition describes adverse health effects resulting from the ingestion of food contaminated with an unspecified noxious substance due to assault, during the initial encounter. The effects arise from exposure to harmful agents in food, which may include chemicals, toxins, or other materials not classified under more specific toxic categories. The severity of symptoms depends on the nature and amount of the substance ingested.

Causes

Toxic effects occur when food is contaminated with substances such as industrial chemicals, pesticides, heavy metals, or other non-biological toxins. These contaminants may enter the food supply through intentional adulteration or exposure to harmful agents. The specific agent determines the nature and severity of the toxic response.

Risk Factors

  • Consumption of food from unregulated or poorly monitored sources.
  • Exposure to environments with high levels of industrial or agricultural contaminants.
  • Inadequate food safety practices during preparation or storage.
  • Consumption of wild or foraged foods with unknown toxic properties.

Symptoms

  • Gastrointestinal distress, including nausea, vomiting, or diarrhea.
  • Neurological symptoms like dizziness, confusion, or weakness.
  • Respiratory issues, such as shortness of breath or coughing.
  • Cardiovascular symptoms, such as rapid heart rate or low blood pressure.
  • Skin reactions, including rashes or irritation.

Diagnosis

Diagnosis involves a thorough patient history to identify potential exposure to contaminated food, including details about the assault. Clinical evaluation assesses symptoms and may include laboratory tests to detect toxins or contaminants. Imaging or other diagnostic tools may be used to rule out other conditions or assess organ damage.

Treatment Options

Treatment focuses on stabilizing the patient, removing the toxic substance (e.g., through induced vomiting or activated charcoal), and managing symptoms. Supportive care, such as intravenous fluids or medications for pain or nausea, may be necessary. In severe cases, specialized interventions like dialysis or antidotes may be required.

Prognosis and Follow-Up

Prognosis depends on the type and amount of toxin ingested, as well as the timeliness of treatment. Most patients recover with appropriate care, but severe cases may lead to long-term complications. Follow-up care includes monitoring for delayed effects and addressing any underlying trauma from the assault.

Complications

  • Organ damage (e.g., liver, kidney, or neurological impairment).
  • Severe dehydration or electrolyte imbalances.
  • Respiratory failure or cardiovascular collapse.
  • Psychological trauma related to the assault.

Lifestyle & Prevention

  • Avoid consuming food from untrusted sources or in unsafe environments.
  • Practice strict food safety measures, such as proper storage and cooking.
  • Seek help if exposed to situations involving potential food tampering or assault.
  • Report suspected food contamination to authorities to prevent further incidents.

When to Seek Professional Help

Seek immediate medical attention if you experience symptoms of food poisoning, especially if linked to an assault. Contact emergency services if symptoms are severe (e.g., difficulty breathing, loss of consciousness) or if you suspect intentional contamination.

Tips for Medical Coders

Document the assault context and initial encounter clearly. Ensure the code T62.93XA is used for the initial encounter of toxic effects from an unspecified noxious substance eaten as food due to assault. Verify that the documentation supports the assault-related exposure and initial visit to justify the code.

Book a walkthrough

T62.93XA policy automation walkthrough

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