Codes / ICD10CM / T50.Z13D

T50.Z13D Poisoning by immunoglobulin, assault, subsequent encounter

ICD10CM code

ICD10CM

Chat with GenHealth to automate any coding or chart task.

Name of the Condition

  • Poisoning by immunoglobulin, assault, subsequent encounter

Summary

This condition describes poisoning resulting from exposure to immunoglobulins due to assault, with subsequent encounter indicating follow-up care after the initial event. Immunoglobulins are therapeutic agents used for immune deficiencies or autoimmune conditions, but forced exposure can lead to adverse clinical effects. The presentation depends on the dose, route, and individual sensitivity, and subsequent encounters focus on monitoring and managing ongoing effects.

Causes

Exposure may result from forced ingestion, injection, or other means of administration of immunoglobulin preparations during an assault. Assault-related poisoning involves intentional harm by another party, which can include misuse of therapeutic agents or access to unregulated sources. Subsequent encounters address residual toxicity or complications from the initial exposure.

Risk Factors

  • Proximity to immunoglobulin preparations during an assault
  • Underlying conditions affecting drug metabolism or sensitivity
  • Previous adverse reactions to immunoglobulins or related products
  • Delayed or inadequate initial medical intervention post-exposure
  • Ongoing exposure to contaminated materials or residual agents

Symptoms

  • Persistent nausea, vomiting, or abdominal pain
  • Recurrent headache, dizziness, or confusion
  • Lingering allergic reactions (rash, itching, swelling)
  • In severe cases, chronic respiratory distress or organ toxicity
  • Delayed anaphylaxis or systemic inflammatory responses

Diagnosis

Diagnosis is based on patient history (e.g., assault-related exposure) and clinical evaluation during follow-up. Laboratory tests may assess ongoing organ function or allergic markers, while toxicology screening can confirm residual exposure. Imaging or specialized tests may be used to evaluate persistent complications.

Treatment Options

  • Ongoing supportive care (e.g., hydration, monitoring)
  • Long-term management of allergic or inflammatory responses
  • Rehabilitation for organ damage or functional impairment
  • Psychological support for assault-related trauma
  • Adjustments to therapy for underlying conditions, if applicable

Prognosis and Follow-Up

Prognosis depends on the severity of initial exposure and timeliness of initial care. Subsequent encounters aim to monitor for delayed complications, such as organ dysfunction or chronic allergic reactions. Regular follow-up is essential to assess recovery and adjust treatment as needed.

Complications

  • Chronic organ damage (e.g., renal or hepatic impairment)
  • Persistent allergic sensitization or anaphylaxis risk
  • Psychological sequelae from assault
  • Delayed toxic effects from prolonged exposure
  • Interference with future immunoglobulin therapy due to sensitization

Lifestyle & Prevention

  • Secure storage of immunoglobulin preparations to prevent misuse
  • Education on recognizing and avoiding assault-related risks
  • Prompt reporting of exposure to healthcare providers
  • Adherence to prescribed follow-up schedules
  • Support for mental health and trauma recovery

When to Seek Professional Help

Seek immediate medical attention if symptoms worsen, new symptoms develop, or there are signs of severe allergic reactions (e.g., difficulty breathing, swelling). Follow-up care is critical for managing long-term effects and preventing complications.

Tips for Medical Coders

Document the assault-related nature of the exposure and specify that this is a subsequent encounter. Include details on the type of immunoglobulin involved, route of exposure, and any ongoing clinical effects. Ensure the encounter aligns with the "subsequent" modifier to reflect follow-up care after the initial poisoning event.

Book a walkthrough

T50.Z13D policy automation walkthrough

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