Your platform already holds the patient record. The modules add what the record doesn't do on its own — interpreting the data in it, generating personalized protocols from that interpretation, and writing the encounter note — inside the workflow your practitioners already use.
Practitioner-supervised. Rule-anchored. Evidence-cited. HIPAA (Health Insurance Portability and Accountability Act)-compliant, BAA (business associate agreement)-ready.
15+ hours
saved per practitioner per week across documentation, interpretation, and plan building
No
forklift integration — modules attach to the workflow you already have
9
modules, activated individually as your roadmap allows
Your practitioners document in your system, then do the interpretation and the planning outside it — which is where their time goes and where your platform stops adding value.
TODAY
The chart holds labs, history, and notes. Turning that into a clinical picture and a plan is the practitioner’s own work, done from memory and experience, and the platform has no part in it.
Building that capability in-house means a clinical knowledge base, an evidence pipeline, and a safety architecture your compliance team will accept — years of work outside your core product.
WITH TERA MODULES
Clinical Reasoning interprets the data already in the chart and returns findings with citations. The protocol builders generate a personalized plan the practitioner edits and signs.
The AI Scribe writes the encounter note in structured form, ready for your record. Every module is a feature you ship without a clinical build behind it.
The shift
Keep the record. Add the intelligence on top.
Clinical stack
Documentation, interpretation, and protocol generation — the three manual steps that sit on top of the record.
Module 01
Real-time clinical note generation from patient encounters. Structured output ready for your EHR (electronic health record) or encounter surface.
Module 02
Maps biomarkers and patient context to possible conditions deterministically. The LLM (large language model) summarizes findings; the rules engine produces them.
Module 03
Biomarker-driven meal plans, foods used as medicine, eliminations, and macronutrient targets personalized to the patient’s diagnostic and goal context.
Module 10
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 nine modules are available — these are the ones this use case starts with.
From record to action
Modules attach to your existing workflow — activate one, or the whole set.
Step 01
Patient data flows to the modules by REST API, or the SDK renders them natively in your interface.
Step 02
Clinical Reasoning maps biomarkers and context to possible conditions, deterministically and with citations.
Step 03
Protocol builders produce a personalized, evidence-cited plan in the practitioner’s existing workflow.
Step 04
The AI Scribe generates the structured encounter note, ready to write back to your record.
Clinical safeguards
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.
Pillar 01
Supervision
Tera AI generates; the licensed clinician approves. Every condition hypothesis, every protocol, every adjustment is reviewed and signed off before it reaches the patient.
Pillar 02
Reasoning
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.
Pillar 03
Evidence
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.
Clinical AI architecture
Rules produce the findings. AI communicates them.
Integration
Pick the integration depth that matches your engineering capacity and brand requirements. All three deliver the same clinical AI underneath.
API ONLY
You build the UI (user interface) inside your own application. Authentication via OAuth or API key. Modules return structured JSON your app renders natively.
EMBEDDED SDK
Your brand, your styling, our clinical logic. Embed the modules as React components in your existing application without building the interface from scratch.
WHITE-LABEL HOSTED
Tera hosts the full practitioner portal and Patient Copilot. Custom domain, custom theme, our infrastructure — no engineering work on your side.
Integration spectrum
Choose how much of the experience you want to own.