Home▸Medical Cannabis Cannabinoid Pharmacology▸Medical Cannabis Dosing Titration Simulator

🌿 Medical Cannabis Dosing Titration Simulator

This simulation guides users through the process of titrating medical cannabis dosages. It provides detailed information on how to safely and effectively adjust doses based on patient response and individual needs.

Medical Cannabis Cannabinoid Pharmacology2DModerate60 FPS
medical-cannabis-dosing-titration-simulator ↗ Open standalone

Start Low — The First Dose in a Cannabis-Naive Patient

Individual response to THC varies widely, so treatment begins at the smallest plausible dose.

  • 1–2.5 mg: Typical starting dose (THC, cannabis-naive)
  • CB1: Endocannabinoid receptor (primary psychoactive target)
  • High: Inter-patient variability (metabolism, tolerance differ)
  • Elevated: Naive ED-visit risk (without slow titration)

Why start this low

Placeholder: narrow therapeutic index makes small starting doses safer.

Patient factors considered

Placeholder: age, weight, prior use, and comorbidities shape the starting dose.

Setting expectations

Placeholder: patients are told effects build slowly across visits, not one dose.

Assessing Effect — Route-Specific Onset Timing

Adequate observation time must pass before judging whether a dose worked.

  • 2–10 min: Inhaled onset (peak ~30 min)
  • 30–120 min: Edible onset (peak 2–4 hours)
  • 6–8 hr: Edible duration (longer than inhaled)
  • Re-dosing early: Common error (before onset completes)

Inhaled route timing

Placeholder: fast onset allows quick, incremental effect checks.

Edible route timing

Placeholder: delayed onset risks impatient, stacked re-dosing.

Why waiting matters

Placeholder: judging too early causes accidental overdose later.

Gradual Dose Increase When Relief Is Inadequate

Small stepwise increases are made only when relief is insufficient and no side effects appeared.

  • 1–2.5 mg: Typical step size (per increase)
  • Days: Minimum interval (between increases)
  • No relief AND no effects: Rule (both required to raise dose)
  • Slow convergence: Goal (toward effective dose)

Step-wise increase logic

Placeholder: raise dose only in small, spaced increments.

Monitoring between steps

Placeholder: patient logs relief and any psychoactive symptoms.

When to pause increases

Placeholder: any unwanted effect halts further dose increases.

Careful Titration Toward the Therapeutic Window

Titration continues while watching the gap between relief and unwanted psychoactive effects.

  • Narrow: Therapeutic window (relief vs. side effects)
  • Anxiety: Key side effect (most reported at high dose)
  • Weekly: Monitoring cadence (typical follow-up)
  • Bidirectional: Adjustment direction (up or down as needed)

Balancing two curves

Placeholder: relief and side-effect curves are tracked together.

Signs of overshoot

Placeholder: anxiety, sedation, or impairment signal reducing dose.

Route switching

Placeholder: some patients change route to ease titration control.

Individualized Optimal Dose Within the Therapeutic Window

Titration ends once a stable dose delivers relief without excessive psychoactive effect.

  • Optimal dose found: Outcome (individualized, stable)
  • Edible overdose: Common ED cause (delayed-onset re-dosing)
  • No relief: Under-dosing risk (patient discontinues therapy)
  • Excess psychoactivity: Over-dosing risk (anxiety, impairment, ED visits)

What success looks like

Placeholder: consistent relief at the lowest effective, tolerated dose.

Avoiding both failure modes

Placeholder: neither under-dosed nor over-dosed extremes serve the patient.

Maintaining the window

Placeholder: periodic reassessment keeps dosing within the sweet spot.

Placeholder highlight: edible overdoses are a leading avoidable ED visit cause.
⚙ Under the hood

This simulation guides users through the process of titrating medical cannabis dosages. It provides detailed information on how to safely and effectively adjust doses based on patient response and individual needs.

CanvasBiomedicine

2D · HTML5 Canvas 2D · 60 FPS target · runs fully client-side, no install

What did you find?

Add reproduction steps (optional)