Codes / ICD10CM / T40.714D

T40.714D Poisoning by cannabis, undetermined, subsequent encounter

ICD10CM code

ICD10CM

Chat with GenHealth to automate any coding or chart task.

Name of the Condition

  • Poisoning by cannabis, undetermined, subsequent encounter

Summary

This ICD code applies to cases of cannabis poisoning where the intent (accidental, intentional, or undetermined) is not specified, and the encounter is subsequent to the initial episode. It covers ongoing care or follow-up for patients with unresolved or continuing effects of cannabis exposure, regardless of the initial circumstances. The code is used when the focus is on managing residual symptoms or complications from the poisoning event.

Causes

Poisoning may result from exposure to cannabis products, including inhalation, ingestion, or other routes. The undetermined intent indicates that the circumstances of exposure (e.g., accidental, intentional, or therapeutic error) are not clearly documented. Subsequent encounters involve ongoing management of symptoms or complications from the initial poisoning episode.

Risk Factors

  • Prior history of cannabis use or exposure
  • Lack of clear documentation regarding the intent of exposure
  • Ongoing symptoms or complications from a previous poisoning event
  • Incomplete or unclear initial assessment of the poisoning incident

Symptoms

  • Persistent dizziness, confusion, or impaired coordination
  • Ongoing anxiety, panic attacks, or paranoia
  • Nausea, vomiting, or abdominal discomfort
  • Increased heart rate or palpitations
  • Profound drowsiness or lethargy
  • Respiratory distress or other systemic effects

Diagnosis

Diagnosis relies on clinical evaluation, including a history of cannabis exposure and assessment of residual symptoms. Toxicology screens may be used to confirm cannabinoid presence, though results may not correlate with symptom severity. The "subsequent encounter" designation indicates follow-up care for unresolved effects from a prior poisoning episode.

Treatment Options

  • Supportive care tailored to ongoing symptoms (e.g., hydration, rest)
  • Medications to manage anxiety, nausea, or other persistent effects
  • Monitoring for delayed complications or worsening symptoms
  • Referral to specialists (e.g., psychiatry, toxicology) if needed

Prognosis and Follow-Up

Prognosis depends on the severity of the initial poisoning and the presence of residual effects. Most patients recover with appropriate care, but some may experience prolonged symptoms. Follow-up is essential to assess resolution of symptoms, address underlying issues, and prevent recurrence. Regular monitoring ensures timely intervention for complications.

Complications

  • Prolonged cognitive impairment or confusion
  • Persistent psychiatric symptoms (e.g., anxiety, paranoia)
  • Cardiovascular issues (e.g., tachycardia, arrhythmias)
  • Respiratory problems or other systemic effects
  • Delayed recognition of intent (e.g., if self-harm is later confirmed)

Lifestyle & Prevention

  • Avoid cannabis use if intent of exposure is unclear or risky
  • Ensure proper labeling and storage of cannabis products to prevent accidental access
  • Educate users on safe dosing and potential risks
  • Address underlying substance use or mental health concerns to reduce future incidents

When to Seek Professional Help

Seek immediate care if symptoms worsen, new symptoms develop, or there is uncertainty about the cause of ongoing effects. Professional evaluation is critical for managing complications, adjusting treatment, or clarifying the intent of the original exposure.

Tips for Medical Coders

Use this code for subsequent encounters related to cannabis poisoning when the intent remains undetermined. Document the nature of the follow-up (e.g., symptom management, complication monitoring) and ensure the encounter is linked to the initial poisoning event. Verify that the "subsequent encounter" modifier is appropriate for the stage of care.

Book a walkthrough

T40.714D policy automation walkthrough

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