Documentation, Consent & the Clear-to-Treat Handoff

The Readiness Standard never clears a patient — it only makes sure the clinician who does has complete, honest documentation to stand on.

⚑ Draft for review. This safety-critical module carries a Clinician sign-off — a named licensed Medical Director must sign it before use in continuing education credit.

🎖️ Bottom line for a busy clinician

The Readiness Standard and your certification never clear a patient — that call is always yours, and it always will be. Your job is to make sure the paperwork behind that call is complete: screening, medication reconciliation (especially CYP2D6 interactions for ibogaine and serotonergic/MAOI interactions for MDMA), contraindication review, consent, and the right modality annex, all signed and dated by you. Contributing de-identified outcomes to the registry is voluntary, separately consented, and never a condition of certification — and your certification can never be tied to buying Operation Whole Health products, full stop. If a no-go happens, document it as carefully as a yes — a declined treatment is still a clinical decision that needs a record.

The one rule this whole module sits on

Everything else in Module P8 is downstream of a single sentence from Protocol v1: "The go/no-go decision is the treating clinician's alone — this standard documents readiness; it does not clear anyone." The Readiness Standard, the certification, and the registry all exist to make that decision better-informed and better-documented. None of them make it for you, and none of them substitute for your own program's screening and consent process.

Why this framing matters for you personally: OWH's certification model deliberately mirrors a diving-certification body, not a treatment provider — it certifies that a program screens, informs, and documents to a defined bar. It never certifies that a substance is safe or effective, and it never certifies a specific patient as medically cleared. That distinction is what lets a non-treatment standard carry real authority — and it's also your liability firewall: the paperwork you generate is what shows, after the fact, that the process behind your decision was sound.

The Clear-to-Treat packet: what has to be in it

Phase 3 of the Common Core defines the Clear-to-Treat handoff as a documentation packet the treating clinician personally reviews and signs before proceeding. It is not a form the patient fills out alone, and it is not complete just because every box has an entry — you are attesting that you reviewed it.

Screening results — general medical history/exam/vitals/labs, cardiovascular baseline, psychiatric history and suicidality screen, pregnancy screen where applicable.
Medication & substance reconciliation — the complete list (prescription, OTC, supplement, substance), explicitly screened for serotonergic agents, QT-prolonging agents, and relevant CYP interactions.
Contraindication review — an explicit statement that the universal stop-criteria domains (cardiovascular disease/arrhythmia, uncorrected electrolyte abnormality, hepatic/renal impairment, active psychosis or unmanaged bipolar disorder, acute suicidality, pregnancy, unmanageable drug interactions) were checked and either cleared or addressed.
Consent completed — documented informed consent, supported by (not replaced by) the patient/caregiver education modules.
Education completed — confirmation the patient and caregiver finished the honesty-graded education track.
Modality annex applied — the medicine-specific safety annex (cardiac workup for ibogaine, serotonergic taper documentation for MDMA, urinary/dependence screen for ketamine, etc.) was used, not just the universal core.

Clinical pearl: a Clear-to-Treat packet with every field populated but no clinician signature, date, and legible rationale for edge-case judgment calls is functionally incomplete. If a case is later reviewed — by a state board, a plaintiff's attorney, or your own quality-assurance process — the packet has to show your reasoning, not just your checkboxes.

A no-go is a valid, and fully documentable, outcome

The standard's contraindication framework flags the domains; you set the exact thresholds and make the call. When screening surfaces a stop criterion — an abnormal QTc, an active psychotic disorder, a dangerous drug interaction that can't be safely managed — declining to clear the patient is the correct use of the process, not a failure of it.

Document which specific criterion triggered the no-go, referencing the screening data point (e.g., "QTc 478 ms on repeat ECG, above program threshold").
Document what remediation path, if any, was offered (referral, medication adjustment by the prescriber, re-screen timeline) — and if none, why not.
Never leave a no-go undocumented because the session didn't happen. The absence of treatment is still a clinical decision that needs a record.

Where the pharmacology has to be airtight in your notes

Two interactions illustrate why "medication reconciliation" can't be a checkbox — it has to be a documented clinical judgment.

Ibogaine + CYP2D6 status Established — Ibogaine is metabolized primarily by CYP2D6 to its active metabolite noribogaine. In a controlled pharmacokinetic study, pre-treatment with the CYP2D6 inhibitor paroxetine produced roughly double the active-moiety (ibogaine + noribogaine) exposure compared to placebo, leading the authors to recommend genotyping/phenotyping and at least halving the dose in poor metabolizers (Glue et al., J Clin Pharmacol, 2015). Ibogaine also directly blocks the cardiac hERG potassium channel, prolonging the QT interval; a toxicology review documented QT prolongation, ventricular arrhythmia, and 27 reported fatalities associated with ibogaine, including cases without pre-existing cardiac disease (Litjens & Brunt, Clin Toxicol, 2016; mechanism detailed in Thurner et al., J Pharmacol Exp Ther, 2013). What this means for your chart: the Clear-to-Treat packet for ibogaine needs a legible statement of CYP2D6 status (or documented rationale for proceeding without it), a baseline and pre-dose ECG/QTc, corrected electrolytes, and an explicit note on any CYP2D6-interacting medication and how it was handled.

MDMA + serotonergic/MAOI medications Established — MDMA is strongly serotonergic; combining it with SSRIs/SNRIs or especially MAOIs risks life-threatening serotonin toxicity (hyperthermia, rigidity, autonomic instability), a mechanism well described in the anesthesia and toxicology literature (Gillman, Br J Anaesth, 2005; Chiew et al., Br J Clin Pharmacol, 2024) and demonstrated as synergistic and highly lethal in preclinical MAO-A-inhibition models (Alves et al., Addiction Biology, 2009). What this means for your chart: any planned serotonergic-medication taper must be ordered and documented by the prescriber — never inferred from an education module or assumed complete because a date passed — and the reconciliation record must show the taper was verified, not just recommended, before the annex is marked satisfied.

Regulatory note for your documentation language: esketamine (Spravato) is FDA-approved for treatment-resistant depression; MDMA-assisted therapy is not FDA-approved (the agency declined Lykos Therapeutics' application in August 2024, citing safety and methodology concerns) — do not let a patient's chart or consent language imply otherwise. Ibogaine, psilocybin, LSD, and DMT remain Schedule I; ketamine is Schedule III.

Contributing to the registry: consent, not compliance

Registry participation sits on top of, not inside, your clinical documentation — and it has its own consent layer.

It is human-subjects research. Collecting outcomes to learn what works requires its own IRB oversight and informed consent — separate from treatment consent — and, for any digital record, a HIPAA-compliant platform with a signed Business Associate Agreement.
It is voluntary, de-identified, and portable. A clinic or patient can decline, and a clinic that later leaves the registry takes its own data with it.
Analyses are pre-registered and methods are open — the governance point of a registry is that nobody can quietly reshape the question after seeing the answer.
Contribution is a higher certification tier, not the floor. Universal readiness screening and the Clear-to-Treat process are required for any certified program; registry participation is required for the higher tier and is where compliance documentation becomes shared evidence.

Clinical pearl: because the minimum dataset schedule (screening → baseline → day-of → weekly check-ins → follow-up out to 12 months) overlaps heavily with what you already collect for good clinical care, the marginal documentation burden of registry participation is mostly a matter of using the same validated instruments (PCL-5/PHQ-9/GAD-7, C-SSRS, WHODAS 2.0) your program should be using anyway — not a second, separate paperwork system.

Certification, the COI firewall, and what it does and doesn't say about you

As an individual, you are eligible for Certified Provider status — a portable, CE-style credential earned by completing this training and passing an assessment on readiness, screening, informed consent, and crisis response. Your program (if it is one) is eligible separately for Certified Program status, and family/support persons for Certified Caregiver status. None of these tiers, including your own, is medical clearance of any patient — that stays with the treating clinician of record, case by case.

The firewall is explicit: certification — of a program, a provider, or anyone — is never contingent on purchasing Operation Whole Health products, and the certification/standards function is organizationally walled off from any commercial arm.
Disclose the conflict, don't hide it. OWH develops nutritional preparation protocols and products and also helped convene this standard; that dual role is disclosed rather than concealed, and it is exactly why the certification and registry functions are kept structurally separate.
A named Medical Director owns the clinical content. All thresholds and clinical language in the standard are signed by a licensed clinician-of-record and version-controlled with a public change log — if a threshold in your annex changes, you'll see it in that log, not hear about it informally.

Ongoing quality assurance: this is a living standard, not a plaque on the wall

Annual renewal, not a one-time credential. Program certification is renewed annually with review; spot review applies as the certifying body matures from attestation-based to audit-based.
Version control is your responsibility to track. Because thresholds and annexes are revised as evidence accrues, your documentation should reference which version of the standard a given Clear-to-Treat packet was completed under.
The registry is itself a QA loop. Any safety flag in the shared check-ins — a positive C-SSRS screen, a serious adverse event — triggers immediate escalation to the care team; it is never allowed to sit as a passive data point.
Honest sequencing applies to you too. The standard states plainly that its authority is earned, not declared, until it is clinician-authored, board-governed, and adopted with real outcomes data. Representing your certification to patients or referrers as more than a documented preparation-and-screening process — as if it were medical-board accreditation or a safety guarantee for any substance — misstates what you hold.

Honest limit Hypothesis: whether standardized documentation and readiness certification actually improve patient outcomes is not yet proven — it is the open question this registry exists to test, not a claim this module is making about your own practice.

Operation Whole Health — Patriot-founded 501(c)(3). Provider Track — prototype, DRAFT v0.1. Continuing education content; not medical, legal, or regulatory advice. Content marked Clinician sign-off is pending a named licensed physician / Medical Director’s review before use with patients. In crisis? Veterans Crisis Line: dial 988, then press 1.