Problem with recall types

[drtech]

1)I can't get my prophy recall type to hold the "Special type" of prophy in the setup window. If you select it from the drop down box it doesn't save it....so my "schedule recall" button isn't working at all because no recall type has a type of prophy.

Also, is there a way to get rid of a recall type? I made some that I think are overkill and don't want to use them, but just removing the triggers does not remove it from pt's recally types.

[drtech]

i figured out it does set it, the prefs information just doesn't get reloaded from the database and therefore it doesn't take effect until it is reloaded or you restart OD.

Second problem is that if a pt has perio and prophy recalls (because they have had prophies in the past as well as perio tx) then their recall appt gets double procedures added (eg, 2 exams, perio maint, & prophy on one appt) Maybe it should default to use perio info and disable the prophy (or not use it for recall appt scheduling) if the pt has both.

betaV6.0.2

[drtech]

also, it does not seem that the times are synchronized properly on non prophy/perio types. I set a follow up recall for endo pt for 1 day after for call backs, and then i changed the date to 6 month follow up to check if they have a crown down, then resycronized. It didn't reset the date to 6 months, but kept it at 1 day later after synchronization.

[jordansparks]

2. The patient should never have both prophy and perio recall. They are mutually exclusive. So how were you able to add them both to one patient?

[jordansparks]

Recalls persisting even after removing the triggers is considered a bug.

[drtech]

not sure, how they both got added, but they did...i think maybe my "special types" for prophy was removed to none and that might have messed it up before i put it back.

Also, I have a existing pt who had prophy's before, but who just had SRP tx. The code is listed as a trigger in the perio recall, but he still has a prophy recall even after sycro. Not sure what is going on there...i will look into it more...

[jordansparks]

Normally, this is the sort of thing I would fix immediately. But I lost a hard drive yesterday, and I'm still not fully functional. So maybe I'll get to this bug tomorrow.

[drtech]

HD failure is never fun...