Child Fluoride
Posted: Wed Mar 03, 2010 1:23 pm
I would like to discuss the current behavior of the program as relates to child fluoride. Child vs adult fluoride is actually handled in three entirely separate parts of the program:
1. Recall. See the recall types section under setup. Open the child prophy window. As you can see, it automatically uses adult if 12 or older.
2. Manual entry. If not recall, then the user manually enters either adult or child. For example, from the appointment edit window, or in the Chart module.
3. Insurance benefit estimating. Lets you set the age limit for fluoride coverage. The behavior was recently changed in version 6.8 in response to this discussion:
viewtopic.php?f=1&t=2304&p=9446
It only limits estimates for child fluorides, typically at 18 or 19.
So here's my question for everyone. What does everyone think of the current behavior? I think #1 is right because everyone I know bills it as adult if over age 12, but maybe everyone I know is doing it wrong. I think the behavior of #3 is about as good as it's going to get for the reasons explained in that discussion. But #1 and #3 behaviors do not seem to work together well. They are different. So I guess my question is mostly about #1, the recall. If we let users set the age, would a global default age setting be acceptable, or do we need to allow setting it per plan? Also, should we crank up the automation and turn it into an autocode so that the user has to think less about which one to use?
1. Recall. See the recall types section under setup. Open the child prophy window. As you can see, it automatically uses adult if 12 or older.
2. Manual entry. If not recall, then the user manually enters either adult or child. For example, from the appointment edit window, or in the Chart module.
3. Insurance benefit estimating. Lets you set the age limit for fluoride coverage. The behavior was recently changed in version 6.8 in response to this discussion:
viewtopic.php?f=1&t=2304&p=9446
It only limits estimates for child fluorides, typically at 18 or 19.
So here's my question for everyone. What does everyone think of the current behavior? I think #1 is right because everyone I know bills it as adult if over age 12, but maybe everyone I know is doing it wrong. I think the behavior of #3 is about as good as it's going to get for the reasons explained in that discussion. But #1 and #3 behaviors do not seem to work together well. They are different. So I guess my question is mostly about #1, the recall. If we let users set the age, would a global default age setting be acceptable, or do we need to allow setting it per plan? Also, should we crank up the automation and turn it into an autocode so that the user has to think less about which one to use?