Automate the protocol your coaches deliver.
Your coaches are good at coaching. What slows them down is building a personalized plan for each member from that member's data — and doing it consistently across a roster. Clinical Reasoning interprets the data; the protocol builders generate the plan; your coaches do what they do best.
15+ hours
saved per practitioner per week on interpretation and plan assembly
6
protocol domains generated per member, not a single generic curriculum
Cited
evidence behind every recommendation a coach delivers
Coaching scales. Personalization is what doesn't.
A curriculum can be delivered to thousands. A plan built from one member's labs, session notes, health history and conditions has to be produced for each of them — which is where the model breaks.
A curriculum, lightly tailored
Members get a program with some branching, and coaches adapt it in conversation. The adaptation depends on the individual coach’s knowledge, and it isn’t reproducible across a roster.
Making it genuinely personalized would mean a clinician interpreting each member’s data and building each plan — which the unit economics of a coaching platform don’t support.
A generated plan per member
Clinical Reasoning interprets each member’s biomarkers, symptoms, and history, returning findings with citations rather than a coach’s recall.
The protocol builders generate a personalized plan across six domains. A practitioner approves it, and your coaches deliver it — the same quality bar for every member on the roster.
The modules this uses.
Interpretation and protocol generation, plus a patient surface where you want the plan delivered in-app.
Clinical Reasoning
Maps biomarkers and patient context to possible conditions deterministically. The LLM (large language model) summarizes findings; the rules engine produces them.
Nutrition Protocol Builder
Biomarker-driven meal plans, foods used as medicine, eliminations, and macronutrient targets personalized to the patient’s diagnostic and goal context.
Fitness Protocol Builder
Strength, cardiovascular, and mobility programs calibrated to functional capacity and recovery patterns.
Tera Patient Copilot
AI patient portal that coaches patients daily between visits. White-labeled (hosted by Tera) or embedded as an SDK (software development kit) in your patient app.
All ten modules are available — these are the ones this use case starts with.
How it works.
The plan is generated and approved; your coaches stay the relationship and the accountability.
Member data in
Labs, intake, symptoms logged and program data pass into Clinical Reasoning through the API.
Findings returned
Biomarkers and signals map to functional ranges and conditions deterministically, with citations.
Plan generated
Protocol builders produce a personalized plan across nutrition, fitness, sleep, stress, and the rest.
Practitioner signs, coach delivers
A clinician approves the plan; your coach runs it with the member and handles the accountability.
Safe AI you can embed.
Clinical defensibility is the precondition for embedding AI into any healthcare platform — three architectural pillars built to pass your compliance, legal, and clinical leadership reviews.
Practitioner-supervised by design
Tera AI generates; the licensed clinician approves. Every condition hypothesis, every protocol, every adjustment is reviewed and signed off before it reaches the patient.
Reasoning is rule-anchored, not improvised
Tera does not ask a language model to interpret biomarkers. A proprietary clinical knowledge base maps results and wearable metrics to functional ranges deterministically, then to conditions and protocols. The model only summarizes what the rules produced.
Every recommendation is evidence-cited
Three knowledge bases — biomarker to condition, condition to protocol, food to condition and health goal — with every mapping backed by peer-reviewed citations. Audit-ready and inspectable.
Three ways to deploy.
Pick the integration depth that matches your engineering capacity and brand requirements. All three deliver the same clinical AI underneath.
— I — API ONLY
Server-to-server REST API
You build the UI (user interface) inside your own application. Authentication via OAuth or API key. Modules return structured JSON your app renders natively.
— II — EMBEDDED SDK
Drop-in React components
Your brand, your styling, our clinical logic. Embed the modules as React components in your existing application without building the interface from scratch.
— III — WHITE-LABEL HOSTED
We host the interface; you brand it
Tera hosts the full practitioner portal and Patient Copilot. Custom domain, custom theme, our infrastructure — no engineering work on your side.