An open, noncommercial educational resource
Contributors to OpenCausation.orgSM
The people behind the method.
OpenCausation is developed and reviewed by clinicians, causation methodologists, and technologists who share one commitment: to apply the same neutral, evidence-based method regardless of who asks the question or where the evidence leads.
Within each section, individuals are listed chronologically according to when they became involved with OpenCausation.orgSM.
CTR-01
Medical & methodology advisors
Medical and Methodology Advisors
J. Mark Melhorn, MD, FAAOS, FABOS, FACOEM, FACS, FASSH, FAAHS, FIAIME, CMLE
Founder and Medical Methodology Lead
Clinical Professor, Department of Orthopaedics, University of Kansas School of Medicine–Wichita
Leads the clinical framework, medical-causation methodology, and editorial review.
Barry J. Gelinas, MD, DC, FIAIME, CMLE
Co-Founder and Medical Methodology Advisor
International Academy of Independent Medical Evaluators
Contributes expertise in medical causation and musculoskeletal assessment, informed by formal training in medicine and chiropractic and his current licensure as a chiropractor.
Christopher R. Brigham, MD, MMS, FACOEM, FIAIME
Co-Founder and Medical Methodology Advisor
International Academy of Independent Medical Evaluators
Contributes expertise as an occupational medicine physician in evidence-based evaluation, independent medical assessment, and medical-causation analysis.
Waqas Ahmad Buttar, MBBS, B.Sc., MHA, CIR
Medical Advisor
International Medical Evaluator
Provides an international clinical perspective and medical-evaluation review.
CTR-02
Technology & platform
Technology and Platform
Ben Wen
Chief Technology Officer
MIT Electrical Engineering and Computer Science
Formerly at IBM and MongoLab
Formerly at IBM and MongoLab
Leads platform architecture, technical strategy, engineering oversight, and implementation standards.
Joseph Llanes
Principal Software Engineer
M.S., Crime Analysis, Arizona State University
Leads software implementation across AI workflows, backend, frontend, DevOps, and quality assurance.
Contributor roles reflect participation in platform design, methodology, review, and development; they do not imply case-specific review or endorsement.