Codes / ICD10CM / T36.5X1D

T36.5X1D Poisoning by aminoglycosides, accidental (unintentional), subsequent encounter

ICD10CM code

ICD10CM

Chat with GenHealth to automate any coding or chart task.

Name of the Condition

  • Poisoning by aminoglycosides, accidental (unintentional), subsequent encounter

Summary

This condition represents accidental poisoning by aminoglycosides during a subsequent encounter. It applies to cases where unintentional exposure to these antibiotics results in harmful effects, and the patient is receiving follow-up care. Documentation should clarify the aminoglycoside involved, the accidental nature of the exposure, and the encounter context (subsequent).

Causes

Accidental poisoning may occur due to dosing errors, misadministration, or unintended access to aminoglycosides. This can include incorrect dosing calculations, confusion between similar medications, or patient self-administration errors. Underlying factors might involve inadequate labeling, lack of supervision, or environmental hazards.

Risk Factors

  • Prior renal or auditory impairment increasing susceptibility to toxicity.
  • Concurrent use of other nephrotoxic or ototoxic medications.
  • Pediatric or elderly patients with altered drug metabolism.
  • Limited health literacy or misunderstanding of medication instructions.
  • Unsupervised medication handling in home or institutional settings.

Symptoms

  • Gastrointestinal: Nausea, vomiting, abdominal cramping.
  • Renal: Reduced urine output, elevated creatinine, or electrolyte imbalances.
  • Auditory: Tinnitus, hearing loss, or vertigo.
  • Neurological: Dizziness, confusion, or muscle weakness.
  • Systemic: Fever, hypotension, or allergic reactions (rash, itching).

Diagnosis

Diagnosis relies on clinical assessment, medication history, and laboratory tests. Serum aminoglycoside levels may be measured to confirm exposure. Renal function tests (creatinine, BUN) and auditory evaluations help assess organ impact. Documentation must specify the accidental nature and subsequent encounter timing.

Treatment Options

Management focuses on supportive care, discontinuing the aminoglycoside, and addressing complications. Renal support (e.g., hydration, dialysis) may be needed for toxicity. Auditory monitoring and symptomatic treatment (antiemetics, antihistamines) are common. In severe cases, specific antidotes or interventions target organ dysfunction.

Prognosis and Follow-Up

Prognosis depends on the extent of toxicity and timely intervention. Most patients recover with appropriate care, but permanent renal or auditory damage is possible. Follow-up includes monitoring renal function, auditory tests, and medication reconciliation to prevent recurrence.

Complications

  • Acute kidney injury or chronic renal impairment.
  • Permanent hearing loss or vestibular dysfunction.
  • Electrolyte imbalances (e.g., hypokalemia, hypomagnesemia).
  • Allergic reactions progressing to anaphylaxis.
  • Delayed toxicity from cumulative exposure.

Lifestyle & Prevention

  • Ensure clear medication labeling and storage.
  • Educate patients and caregivers on proper dosing and administration.
  • Avoid polypharmacy with nephrotoxic/ototoxic drugs when possible.
  • Implement safeguards in institutional settings (e.g., double-checking doses).
  • Regularly review medication lists to minimize interaction risks.

When to Seek Professional Help

Seek immediate care for symptoms like severe vomiting, reduced urine output, dizziness, or hearing changes. Contact a healthcare provider if accidental exposure is suspected, even without immediate symptoms, to assess potential toxicity.

Tips for Medical Coders

Use this code for accidental aminoglycoside poisoning during a subsequent encounter. Document the aminoglycoside type, accidental intent, and encounter context clearly. Differentiate from intentional poisoning or initial encounters using the appropriate code. Ensure clinical details support the "subsequent encounter" designation.

Book a walkthrough

T36.5X1D policy automation walkthrough

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