Treatment Planning

Executive summary

Treatment Planning is a versioned plan aggregate: options, phases, steps with dependencies, safety checks, fees, patient acceptance and scheduling. The plan itself is deterministic code — sequencing rules, fee calculation and safety checks — and makes no model calls; AI enters only as draft options the clinician may adopt. Acceptance records the exact plan version and fee schedule the patient agreed to.

Overview

ProductionProduce · Treatment Planning
Hold the plan the patient actually agreed to — version, steps, fees and consent — and drive scheduling from it.

Pipeline

A plan is created from the clinician’s choices, Copilot drafts or studio proposals.
Steps are sequenced by dependency rules into phases; safety rules check each step against the patient’s confirmed facts.
Fees are calculated from the clinic’s fee schedule; estimates are versioned with the plan.
The patient accepts a specific version; the acceptance freezes plan and fees for documents and billing.
Accepted steps link to appointments and to Clinical Documents.

Data owned

Plans, versions, options, phases, steps, dependencies
Holds
The plan aggregate
Step evidence and safety overrides
Holds
Why a step is there, and any clinician override of a safety rule
Acceptances
Holds
The exact version and fees a patient agreed to
Fee schedule and appointment–step links
Holds
Pricing and scheduling

Store	Holds
Plans, versions, options, phases, steps, dependencies	The plan aggregate
Step evidence and safety overrides	Why a step is there, and any clinician override of a safety rule
Acceptances	The exact version and fees a patient agreed to
Fee schedule and appointment–step links	Pricing and scheduling

Models and engines

Draft plan options
Model or engine
Gemini 3 Flash (pro tier)
Notes
Decision options are drafts; the plan aggregate itself is deterministic

Step	Model or engine	Notes
Draft plan options	Gemini 3 Flash (pro tier)	Decision options are drafts; the plan aggregate itself is deterministic

Guardrails

Sequencing, fees and safety rules are code.
Safety overrides are explicit, attributed and audited.
Acceptance binds a version; a later edit creates a new version rather than changing what was accepted.

Rollout and status

ProductionPlan aggregate
Enabled in the production configuration
ShadowPlan safety rules
Evaluated and recorded; never blocks yet
PilotPlan options, consent, scheduling
Per clinic; options gated on a clinician-authored evaluation set

Interfaces

Consumes
What
Confirmed facts
Consumes
What
Studio proposals and Copilot drafts
Consumes
What
Clinic fee schedule
Emits
What
Accepted plan versions
Emits
What
Appointment links
Emits
What
Plan sources for Clinical Documents
Emits
What
Billing inputs

Direction	What
Consumes	Confirmed facts
Consumes	Studio proposals and Copilot drafts
Consumes	Clinic fee schedule
Emits	Accepted plan versions
Emits	Appointment links
Emits	Plan sources for Clinical Documents
Emits	Billing inputs

SOURCE OF TRUTH

server/services/clinical/treatmentPlan/
server/routes/private/treatmentPlan*.ts
docs/treatment-planning-tier1-implementation-plan.md