Planiranje terapije

Overview

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

Pipeline

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

Data owned

Models and engines

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