|
Post by Kraig on Aug 9, 2018 10:37:26 GMT -6
This is a problem with version 4.6.35. Finalizing a prescription may not populate the diagnosis codes. Leaving the tab, coming back, and finalizing again will typically prompt for the proper codes. This issue has been brought to development and should be resolved in the next update. Unfortunately, at this time, we have no ETA for the update.
|
|
|
Post by williamgrichey on Aug 27, 2018 8:17:39 GMT -6
It's not that it doesn't populate the diagnosis codes, it populates incorrect ones. It automatically enters bilateral astigmatism for everyone which has to be deleted when not appropriate and re-finalizing the SRx to get accurate codes. I hate to be a complainer but this is a big waste of time.
|
|
|
Post by Kraig on Aug 27, 2018 11:29:52 GMT -6
Your issue does appear to be related and is also fixed in the next update which is currently in beta testing.
|
|
|
Post by Heather Nelson on Mar 14, 2019 12:43:34 GMT -6
Hi, Has this issue been updated yet?
|
|
|
Post by bwhite on Apr 3, 2019 6:50:50 GMT -6
Having the same issue- every medical record gets populated with bilateral astigmatism automatically as the first diagnosis code. Have to manually delete and enter properly-would prefer that Crystal does not populate any information into the medical record.
|
|
|
Post by erica on Apr 3, 2019 7:19:12 GMT -6
Having the same issue- every medical record gets populated with bilateral astigmatism automatically as the first diagnosis code. Have to manually delete and enter properly-would prefer that Crystal does not populate any information into the medical record. Please see attached: disable auto coding clinical decision supp....docx (35.41 KB)
|
|