From treatment plan to patient decision: organize estimates, questions and follow-up
There can be a decision stage between presenting treatment and beginning care. The system should retain exactly what was presented, which questions remain and what the next action is without turning follow-up into aggressive selling.
Present an identifiable version
Treatment plans and estimates are related but can change for different reasons. Version, date and status make it clear what information the patient received.
This also prevents later changes from silently rewriting the earlier proposal.
Represent partial decisions
A patient may accept one phase, postpone another or need time. A single accepted/declined state can lose important context.
The platform should reflect real decisions without turning software into a pressure mechanism.
Record questions and next action
Another consultation, additional documentation, a follow-up date or no immediate action are all possible outcomes. Explicit next steps prevent duplicate outreach.
Frequency and channel should respect preferences and applicable rules.
Connect acceptance to scheduling and finance
When a phase is confirmed, teams may need to schedule, record a deposit or prepare lab work. Those workflows can connect without assuming payment and acceptance are identical.
Clinical and financial decisions remain with people; software organizes the workflow.
Frequently asked questions
Does accepting one phase mean the whole plan is accepted?
Not necessarily. Partial decisions may need to be represented separately.
Are payment and acceptance the same?
No. A financial event and a treatment-plan decision are related but distinct.
Should practices follow up?
Follow-up can be useful when it has context and a reasonable next action, without repetitive messaging or pressure.
Put the workflow into practice
Odontomy connects these workflows to the patient record and the practice's daily operations.
