How the Clinical Reasoning Engine Works
The Clinical Reasoning Engine is the first layer of intelligence that runs when you generate a protocol. It analyzes your case intake data to identify the likely physiological themes behind the patient's presentation.
What It Does
Rather than reacting to symptoms one by one, the engine looks for patterns — the same way an experienced functional practitioner thinks.
For example, a patient presenting with fatigue, brain fog, hair loss, and low ferritin may be interpreted as: Iron deficiency affecting oxygen delivery and energy production. The protocol is then structured around correcting that driver.
Physiological Themes It Recognizes
The engine is trained to identify patterns across areas including:
Gut dysbiosis and digestive dysfunction
Inflammation (acute and chronic)
Blood sugar dysregulation
Hormonal imbalance
HPA axis and adrenal stress
Mitochondrial dysfunction
Nutrient deficiencies
Thyroid and metabolic patterns
Immune dysregulation
Detoxification burden
And more…
What It Uses
The engine analyzes symptoms, clinical notes, lab markers, age, sex, and primary complaint. The more complete the intake, the more accurate the reasoning output.
What It Does Not Do
The Clinical Reasoning Engine does not diagnose. It provides a structured clinical framework for protocol generation, which you review and adjust before finalizing.