Question | ProcTPs and 'Estimate as of'

[rinse-dental]

I noticed Open Dental saves ProcTPs with PriInsAmt and SecInsAmt calculated using the 'Estimates as of' date. Is the 'Estimates as of' date stored in the DB and available via another API?

For example, patient has a treatment plan that will exceed max or hit frequency limitations. Treatment plan #1 is saved using today's date for 'Estimates as of'. Treatment plan #2 is saved using a future date for 'Estimates as of'.

If this date is not stored or available, may I make a request to include 'Estimates as of' on the TreatPlan table and available through the TreatPlans API?

[justine]

I noticed Open Dental saves ProcTPs with PriInsAmt and SecInsAmt calculated using the 'Estimates as of' date. Is the 'Estimates as of' date stored in the DB and available via another API?

For example, patient has a treatment plan that will exceed max or hit frequency limitations. Treatment plan #1 is saved using today's date for 'Estimates as of'. Treatment plan #2 is saved using a future date for 'Estimates as of'.

If this date is not stored or available, may I make a request to include 'Estimates as of' on the TreatPlan table and available through the TreatPlans API?

Hello rinse-dental,

I'm going to research this for you, but if I recall correctly, these estimates are extremely complex and calculated in memory.

Thanks!

[rinse-dental]

I'm going to research this for you, but if I recall correctly, these estimates are extremely complex and calculated in memory.

Sorry if my question wasn't clear. I don't need the calculations. I'm referring to the ProcTP and TreatPlan tables. ProcTP already stores FeeAmt, PriInsAmt, PatAmt, Discount, etc. when the treatment plan is saved; however, those calculations are based on whatever the user has set in the 'Estimates as of' date in the GUI. The issue is, I can't find the 'Estimates as of' date stored in the DB.

Our practice is creating treatment plan options that reflect treatment if it were to be done in 2024 vs. 2025 (for example). Those treatment plans are saved and can be accessed via the API; however, I can't see a difference outside of the amounts and entry dates. Ideally the TreatPlan API would include the 'Estimates as of' date. Or, if you can point me to where the 'Estimates as of' date is being stored, I can write a ShortQuery.

Thank you!

[justine]

I'm going to research this for you, but if I recall correctly, these estimates are extremely complex and calculated in memory.

Sorry if my question wasn't clear. I don't need the calculations. I'm referring to the ProcTP and TreatPlan tables. ProcTP already stores FeeAmt, PriInsAmt, PatAmt, Discount, etc. when the treatment plan is saved; however, those calculations are based on whatever the user has set in the 'Estimates as of' date in the GUI. The issue is, I can't find the 'Estimates as of' date stored in the DB.

Our practice is creating treatment plan options that reflect treatment if it were to be done in 2024 vs. 2025 (for example). Those treatment plans are saved and can be accessed via the API; however, I can't see a difference outside of the amounts and entry dates. Ideally the TreatPlan API would include the 'Estimates as of' date. Or, if you can point me to where the 'Estimates as of' date is being stored, I can write a ShortQuery.

Thank you!

Hello rinse-dental,

The 'Estimates as of' date picker and the 'Refresh' button are not displayed in the UI unless PrefName.InsChecksFrequency is true.

When true, it appears that Open Dental does allow you to change that date picker to whatever date you'd like and recalculate estimates. These estimates are in memory, until the 'Save TP' button is clicked. However, Open Dental does not save the selected date picker value anywhere, UI or otherwise. I'll bring this up with our team and see if I'm missing something.

I'd recommend advising the office to add a note to the treatment plan indicating when the estimates were recalculated and saved.

Thanks!

[rinse-dental]

Got it. That was my worry. Thanks for checking in on it. To whatever extent this can be considered a feature request to the DB and API teams, I would appreciate it.