For clinic directors
Choosing clinical software for an ibogaine or psychedelic treatment clinic
Most clinics start on a mix of spreadsheets, paper observation charts and a general practice record system. That works until the first audit, insurance review, adverse event or regulator enquiry, at which point the questions are about attribution, thresholds and timestamps — the things a general-purpose system was never asked to hold.
Where general-purpose systems fall short
- Timed observation charts: a treatment session needs vitals at defined intervals against a named protocol, not free-text notes.
- Threshold review prompts: a clinician-entered QTc of 502 ms can be marked against a fixed built-in threshold for review. In most general systems it is just a number in a field.
- Attribution: every reading, decision and acknowledgement needs a person and a time attached to it.
- Structured screening: contraindication and interaction screening needs fields and rules, because a narrative note cannot be queried or audited.
- Assessment scoring: PHQ-9 and GAD-7 collected as PDFs cannot be charted against treatment milestones.
- Delivery-mode protocols: one observation template cannot serve IV flood dosing and telehealth microdosing.
A requirements checklist
| Requirement | Why it matters |
|---|---|
| Row-level access control | Patients must see only their own record, and clinical editing must be restricted to clinicians. Enforced at the data layer, not by hiding a menu item. |
| Recorded threshold prompts | When a clinician-entered value crosses a fixed built-in threshold, the record stores a prompt and acknowledgement status for clinician review whether or not a browser remains open. |
| Immutable audit trail | Who changed which vital, alert or setting, and when. This is the artefact an insurer or regulator asks for. |
| Protocol engine | Each combination of route, formulation, dosing strategy and setting maps to its own checklist, vitals interval and observation window. |
| Interaction rule governance | Rules carry a source, an evidence level, a named reviewer and a review date, and can be updated without a software release. |
| Scored, charted assessments | Instruments auto-scored and banded, plotted against milestones, so change over the arc of care is visible without a chart review. |
| Adverse event register | Events recorded against the session that produced them, with the action taken. |
| Exportable clinical reports | One-click PDF for referral, insurance, handover and the patient's own file. |
| Jurisdictional configuration | Country, timezone, locale, currency, units and regulatory wording as configuration, so one platform serves clinics in different countries. |
| Multi-language interface | The full clinician and patient interface in ten languages, including right-to-left, so international teams and non-English-speaking patients work in their own language. |
| Patient-facing surface | Patient-entered daily check-ins and readings taken with separate home equipment appear in the same record the prescriber reviews, rather than a second system to reconcile. |
Build, adapt or licence
Building in-house gives exact fit and costs a development team indefinitely. Adapting a general EHR is fast to start and slow to live with, because the screening structures and protocol logic end up as free text. Licensing purpose-built software trades some flexibility for the clinical model already being there.
Whichever route a clinic takes, the deciding question is the same: when someone asks who cleared this patient, on what evidence, and what clinicians measured and recorded, can the system answer in one place?
How Treatment Companion App is set up
Treatment Companion App was built for this specific pathway rather than adapted to it: structured contraindication screening, medication and psychedelic readiness on every tier, timed clinician-entered vitals and QTc records with fixed built-in review prompts, delivery-mode protocols across oral, IV, sublingual, total alkaloid, root bark, flood, titrated, booster and microdose, auto-scored assessments, an adverse event register, integration follow-up to six months, a full audit trail, and PDF clinical reports. It licences per practitioner, per clinic or per provider network, and deploys in any jurisdiction with metric or imperial units, local regulatory wording and a ten-language interface for clinicians and patients.
Run this in one clinical record
Treatment Companion App organises clinician-entered screening findings and measurements, assessments, adverse events and follow-up records for clinics and prescribers in any jurisdiction. 21-day trial, no card required.