We had this at the start of the 5.1.3 beta testing and had the developement team logged and and gave them multiple exams of patients and our database but we never did seem to get it completely fixed but it slowed down with subsequent versions of 5.1
and we have had it happen much less and with every user in the office.