Codes / ICD10CM / T43.1X4D

T43.1X4D Poisoning by monoamine-oxidase-inhibitor antidepressants, undetermined, subsequent encounter

ICD10CM code

ICD10CM

Chat with GenHealth to automate any coding or chart task.

Name of the Condition

  • Poisoning by monoamine-oxidase-inhibitor antidepressants, undetermined, subsequent encounter
  • Technical term: T43.1X4D

Summary

This code applies to cases of poisoning by monoamine-oxidase-inhibitor (MAOI) antidepressants where the intent (accidental, intentional, or undetermined) is not specified, and the encounter is classified as a subsequent visit. MAOIs are a class of medications used to treat depression and other mental health conditions. The code is used when the documentation indicates poisoning with undetermined intent during a follow-up encounter, rather than the initial episode.

Causes

Poisoning may result from overdose of the medication, though the intent behind the exposure is not documented. This could involve taking more than the prescribed dose, but without clear evidence of accidental or intentional action. Adverse effects or interactions with other substances may also contribute, but the primary focus is on the poisoning event with undetermined intent during a subsequent encounter.

Risk Factors

  • Concurrent use of medications that interact with MAOIs (e.g., certain antidepressants, pain relievers).
  • Lack of clarity in medication history or dosing instructions.
  • Pre-existing conditions affecting drug metabolism (e.g., liver or kidney disease).
  • Situations where the circumstances of exposure are unclear or not fully documented during follow-up.

Symptoms

Symptoms may include:

  • Hypertensive crisis (severe headache, rapid heart rate, chest pain).
  • Altered mental status, confusion, or agitation.
  • Nausea, vomiting, or abdominal pain.
  • Seizures or tremors.
  • Flushing or sweating.

Diagnosis

Diagnosis relies on clinical evaluation, including patient history, physical examination, and laboratory tests to confirm MAOI exposure. Toxicology screens may detect the drug or its metabolites. Documentation must specify the poisoning event and undetermined intent, with the encounter classified as subsequent (e.g., follow-up visit after initial treatment).

Treatment Options

Treatment focuses on managing symptoms and preventing further harm. This may include supportive care (e.g., monitoring vital signs), administration of antidotes (if available), and addressing complications like hypertensive crisis. The approach depends on the severity of symptoms and the patient’s overall condition.

Prognosis and Follow-Up

Prognosis varies based on the dose, timing of intervention, and individual health factors. Subsequent encounters allow for monitoring of recovery, adjustment of treatment, and addressing any lingering effects. Follow-up care ensures stability and reduces the risk of recurrence.

Complications

Potential complications include organ damage (e.g., liver or kidney), persistent neurological effects, or cardiovascular issues. Severe cases may require long-term management or rehabilitation.

Lifestyle & Prevention

Patients should adhere to prescribed dosing and avoid interactions with other medications or substances. Education on proper storage and usage of MAOIs can reduce accidental exposure. Regular follow-ups help track progress and address concerns.

When to Seek Professional Help

Seek immediate medical attention for symptoms like severe headache, chest pain, confusion, or seizures. Follow-up with a healthcare provider for ongoing symptoms or concerns during subsequent encounters.

Tips for Medical Coders

Use this code when documentation specifies poisoning by MAOI antidepressants with undetermined intent during a subsequent encounter. Ensure the encounter is classified as "subsequent" (e.g., follow-up visit) and that intent remains unspecified. Verify that the code aligns with clinical notes and excludes cases with clear accidental or intentional intent.

Book a walkthrough

T43.1X4D policy automation walkthrough

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