Codes / ICD10CM / T46.0X1D

T46.0X1D Poisoning by cardiac-stimulant glycosides and drugs of similar action, accidental (unintentional), subsequent encounter

ICD10CM code

ICD10CM

Chat with GenHealth to automate any coding or chart task.

Name of the Condition

  • Poisoning by cardiac-stimulant glycosides and drugs of similar action, accidental (unintentional), subsequent encounter

Summary

This code describes an accidental (unintentional) poisoning by cardiac-stimulant glycosides or related drugs, with a subsequent encounter indicating ongoing care for the condition. Cardiac-stimulant glycosides affect heart function, and accidental exposure can lead to adverse effects. The "subsequent encounter" modifier signifies that the patient is receiving follow-up care after the initial poisoning event.

Causes

Accidental poisoning may result from incorrect dosing, consumption of contaminated products, or environmental exposure to these drugs. Common scenarios include medication mix-ups, improper storage, or unintentional ingestion by individuals unaware of the substance's presence. The "subsequent encounter" modifier applies when the patient is being seen for ongoing management of the poisoning.

Risk Factors

  • Presence of cardiac-stimulant glycosides in the home (e.g., certain plants or medications).
  • Lack of awareness about the toxicity of these substances.
  • Poor medication storage practices.
  • Age-related factors, such as children exploring their environment or older adults with cognitive impairments.
  • Previous history of accidental poisoning, increasing the likelihood of recurrence.

Symptoms

  • Nausea, vomiting, or abdominal pain.
  • Irregular heart rhythms (arrhythmias).
  • Dizziness or fainting.
  • Visual disturbances (e.g., blurred vision, yellow-green halos around lights).
  • Weakness or fatigue.
  • Ongoing symptoms requiring follow-up care.

Diagnosis

Diagnosis involves a patient history to identify potential exposure, physical examination, and laboratory tests (e.g., drug levels, electrolyte panels). The "subsequent encounter" modifier is used when the patient is being seen for follow-up after the initial poisoning event, and the provider documents the ongoing nature of the condition.

Treatment Options

Treatment focuses on managing symptoms and preventing further complications. This may include monitoring heart function, correcting electrolyte imbalances, and providing supportive care. The "subsequent encounter" modifier indicates that the patient is receiving ongoing care, such as follow-up visits or adjustments to treatment plans.

Prognosis and Follow-Up

Prognosis depends on the severity of the poisoning and the timeliness of care. Follow-up care is essential to monitor for lingering effects or complications. The "subsequent encounter" modifier is appropriate for visits where the provider documents the patient's progress or adjusts management strategies.

Complications

  • Persistent arrhythmias or heart failure.
  • Kidney damage from prolonged exposure.
  • Neurological effects, such as confusion or seizures.
  • Worsening of underlying heart conditions.

Lifestyle & Prevention

  • Store medications securely to prevent accidental ingestion.
  • Educate patients and caregivers about the risks of cardiac glycosides.
  • Use childproof containers and clear labeling.
  • Avoid mixing medications to reduce the risk of dosing errors.

When to Seek Professional Help

Seek immediate medical attention if symptoms of poisoning recur or worsen, or if new symptoms develop. Follow-up care is necessary for ongoing management, as indicated by the "subsequent encounter" modifier.

Tips for Medical Coders

Use this code for accidental poisoning by cardiac-stimulant glycosides with a subsequent encounter. Document the ongoing nature of the condition and the reason for follow-up care. Ensure the encounter is not the initial treatment for the poisoning. The code is specific to accidental (unintentional) exposure and subsequent care.

Book a walkthrough

T46.0X1D policy automation walkthrough

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