Add a surface, remove a surface buttons
Posted: Wed Apr 09, 2008 12:32 pm
Maybe I'm the only one that this happens to, but whenever I have a tooth treatment planned for say a DO, and it turns out to be just an O, it sure would be nice to have a button to simply allow us to remove a surface. Likewise, if it turns into an MOD, it would be nice to have a shortcut button to add a surface.
What we're doing right now is going into the chart, double clicking on the procedure, clicking "Change", changing the code, correcting the surfaces, and clicking OK. Is there an easier way ?
I'm thinking that you could double click the appointment, single click that particular procedure, single click "Add a surface", and a window would open with the tooth number listed on top, and all of the surfaces listed with check boxes next to them. The currently scheduled surfaces would be checked, and the other surfaces would not be checked. The user could then toggle the check boxes to reflect the change, and the program would automatically change the code to the appropriate code for the new number of surfaces, and if it was planned as an amalgam, it would update to the appropriate amalgam code, and if planned as a composite it would use the new composite code.
Doesn't this sound like it would be SO much easier ?
Thanks,
Mike
What we're doing right now is going into the chart, double clicking on the procedure, clicking "Change", changing the code, correcting the surfaces, and clicking OK. Is there an easier way ?
I'm thinking that you could double click the appointment, single click that particular procedure, single click "Add a surface", and a window would open with the tooth number listed on top, and all of the surfaces listed with check boxes next to them. The currently scheduled surfaces would be checked, and the other surfaces would not be checked. The user could then toggle the check boxes to reflect the change, and the program would automatically change the code to the appropriate code for the new number of surfaces, and if it was planned as an amalgam, it would update to the appropriate amalgam code, and if planned as a composite it would use the new composite code.
Doesn't this sound like it would be SO much easier ?
Thanks,
Mike