Cardiac arrest
Reports may describe collapse, resuscitation attempts, timing after exposure, and whether a cardiac rhythm or prior risk factor was documented.
Safety standards hub
Adverse Event Registry
A transparent, aggregated digest of documented adverse events and fatalities linked to ibogaine, synthesized for clinicians, researchers, policymakers, families, and people seeking careful safety context.
Entries should be read across jurisdictions and care settings. This registry does not present original, unverified case reports or patient-identifying information.
Registry scope
Signals, not certainty
This page organizes what documented reports can and cannot show. It focuses on events described in published case literature, clinical accounts, and other attributable source material, while treating missing information as missing rather than filling gaps with assumptions. The broader ibogaine safety and policy context matters because legal status, access pathways, and clinical oversight differ substantially across locations.
Ibogaine has been associated in documented reports with serious cardiac complications and fatalities. Its pharmacology and safety questions are not reducible to a single exposure: indication, amount, co-medications, underlying conditions, electrolyte status, and the setting in which an event occurs may all matter. The published review of ibogaine-related fatalities is a useful example of why records must distinguish association from demonstrated causation.
For practical background, the ibogaine HCl guide can help clarify the terms that often appear in source descriptions, while the clinical protocol materials frame why screening, monitoring, and escalation capacity are central variables rather than incidental details.
Case categories
Four recurring areas for structured review
Categories are used to support comparison across reports. They do not establish that ibogaine alone caused a specific outcome, and one documented event may involve more than one category.
Arrhythmia
Rhythm disturbances, QT-related concerns, electrocardiographic findings, and concurrent agents require precise timing and source attribution.
Electrolyte derangement
Potassium, magnesium, dehydration, vomiting, and other metabolic factors should be recorded where source reports provide them.
Co-medication interactions
Prescription medicines, non-prescribed substances, and recent exposure history can be material confounders in a reported event.
Minimum dataset
Make future reports comparable
A useful registry needs enough context to identify patterns without publishing identifying information. The proposed dataset below is a reporting structure, not a claim that every field will be available in every historical record. It is especially important where people are comparing ibogaine treatment for addiction accounts that may describe different indications, settings, and pre-existing health circumstances.
Cardiac history and medication interactions need especially careful treatment. The FDA’s overview of drug interactions underscores that interactions can alter effects or risks; a registry should therefore document them without presuming which factor was decisive.
Regional interpretation
Jurisdiction changes what is visible
Different regions produce different kinds of records. Some events are reflected in clinical literature, others in coronial, toxicology, legal, or media documentation, and many may never enter a public source. Access questions also differ: ibogaine’s legal status in the United States is not a substitute for examining how another jurisdiction records, investigates, or publishes adverse events.
Cost and cross-border treatment pathways can shape the setting in which an event is reported. For example, discussions of the cost of ibogaine treatment in Mexico should not be used to infer a clinic’s safeguards, event rate, or reporting quality. Likewise, directories of top ibogaine treatment centers are not evidence that a provider has disclosed all adverse events.
Absence of a report is not evidence that an event did not occur; a report is not, by itself, proof of a single cause.
Terms themselves can obscure search and reporting. A source using a colloquial label may not be captured by formal searches, so the street names associated with ibogaine are relevant only as a documentation and retrieval issue—not as a measure of safety or prevalence.
Reading the record
Interpret statistical signals with restraint
Counts compiled from case reports, retrospective collections, and public records are not incidence rates unless the number and characteristics of people exposed are known. Denominators are often unavailable, reporting thresholds differ, and serious events are more likely to be documented than uneventful exposures. These are classic sources of reporting bias, a concept summarized in the reference overview of reporting bias.
- Ask what population is represented. A case series, a toxicology report, and a regulatory record may answer different questions and should not be pooled casually.
- Separate chronology from causality. An event occurring after ibogaine exposure may be clinically important while still having multiple plausible contributors.
- Check the missing fields. Dose, ECG data, electrolytes, co-medications, medical history, and response capacity can materially change interpretation.
- State the limit plainly. A pattern can justify further scrutiny, not a confident numerical claim unsupported by an exposure denominator.
People looking at potential outcomes should also distinguish a claimed benefit from a safety conclusion. Summaries of ibogaine therapy benefits do not resolve adverse-event risk, just as accounts of ibogaine therapy for PTSD cannot establish safety for an individual or setting.
Interpretation notes
Questions this registry should answer carefully
Does a reported event prove ibogaine caused it?
No. A report can identify temporal association and possible risk factors, but incomplete histories, co-exposures, underlying conditions, and variable monitoring make causal conclusions uncertain. This is why every entry should retain its citation and its stated limitations.
Why does setting belong in an adverse-event record?
Setting helps distinguish documented monitoring and response capacity from an unsupervised context. It is descriptive metadata, not a quality rating or a conclusion about causation. A provider directory such as ibogaine clinic information should likewise not be treated as an adverse-event database.
What makes a future report more useful?
A de-identified minimum dataset that records indication, approximate dose, timing, co-medications, comorbidities, setting, monitoring, interventions, outcome, and source citation makes reports more interpretable. Clearer methods and transparent limits are also part of the safety approach described on the site’s resource pathways.