UPDATE TO 10.1.3

[mbusinelle]

A few issues we have had with the update

Our schedule keeps going half screen when exiting from images.  This does not happen all the time and is very hard to duplicate, but frustrating when it happens.  Hitting ALT + F, back arrow and then maximize to get back to full screen.

Our schedule also keeps disappearing. We have to then go to Appt book and select active appointments.  Its like this just randomly becomes unchecked on the computers.

Now, if we suspend a chart and then go back into it to check someone out it is not updating checkout cost correctly.  This is related to the frequency limitation in insurance.  So for instance if the D1110 has a frequency of 6 months, if the chart is suspended, then you right click to continue checkout, it will not update the correct check out amount. If i remove the frequency and put it to 0, it then works fine.  

Is there any thoughts on when these bugs might be worked out.  

[ma1q]

Was upgraded to 10.1.3 yesterday and can confirm that active appointments are intermittently visible/blank.  Selecting ApptBook--> View --> Active Appointments seems to reset it.

[jdowner]

Hello

The issue with the appointments not showing when PracticeWorks is first opened is a known issue in v10.1.3.  This is being addressed and will be in the next version of the CS PracticeWorks software. 

As for the issue with the appointment book Restoring down (going half screen), and the estimating issues at checkout. I would want to see if I can see those happening and see if it might just be something that needs a setting or workflow change or if it's something that needs to actually be reported as a potential issue. 

I'd be happy to reach out to you at your convenience, or you can give our support line a call and ask for either me or another Escalation team member. 

[mbusinelle]

@jdowner can you reach out to us again regarding these issues?  Thanks

[mbusinelle]

Please reach out to me. 256.329.8401 8-12 and 130-430 CST.

[jdowner]

Sorry, it would seem i missed the notification of your reply.  I'll reach out this afternoon. 

[tshaw]

@jdowner tagging you to see if you have had other reports of this and if you know if it has been turned in to development.