Home User Manual Discussion Forum Search

Bug 1086 

Bug #1086 was discovered on 3/24/10. 

Description
If a procedure is already complete, but the date does not match the appointment it's attached to, then attempting to set it complete again should give an error message.

Detailed Explanation
This only happens when the user is confused about which appointment the procedure is attached to.  The confusion can happen if:
1. Users are setting procedures complete instead of appointments (this is the biggest problem).
2. Users do not notice that a procedure attached to an appointment is already complete with a previous date.
3. Users are scheduling the next appointment before the current appointment is marked complete, accidentally moving procedures from today to the future.

This is a bug.  Although unanticipated user behavior is a factor, the program should anticipate such behavior and block it.

To determine how many procedures are affected, run this report:

SELECT * FROM procedurelog WHERE ProcStatus=2 AND DATE(DateEntryC) < DATE(ProcDate)

This may return a number of false positives.  It will also show all procedures that were set complete and future dated, something that is sometimes allowed, but less now than in previous versions.

To find procedures that are significantly mismatched in date

SELECT * FROM procedurelog WHERE ProcStatus=2 AND DATE(DateEntryC) < DATE(ProcDate - INTERVAL 2 DAY)
or
SELECT * FROM procedurelog WHERE ProcStatus=2 AND DATE(DateEntryC) < DATE(ProcDate - INTERVAL 60 DAY)

We are in the process of tightening down the user interface to prevent such issues in the future.  But for procedures that already have a date that does not match the appointment, we are reluctant to attempt any sort of automatic fix.  There is no way to exclude false positives. But using the queries above, the most significant problems can be manually addressed.

 

 

Open Dental Software 1-503-363-5432