Welcome to the NEW CHUG— your ultimate destination for cutting-edge insights and discussions at the intersection of healthcare and technology.

Our platform is dedicated to exploring the dynamic landscape of healthcare technology, empowering professionals, enthusiasts, and innovators alike with the knowledge and resources to navigate the rapidly evolving field.

From telemedicine revolutionizing patient care to the transformative potential of artificial intelligence in diagnostics, we delve into a myriad of topics shaping the future of healthcare delivery. Whether you’re a seasoned healthcare IT professional, an aspiring entrepreneur in the digital health space, or simply curious about the latest innovations, our curated content, expert interviews, and thought-provoking articles provide a comprehensive exploration of healthcare technology’s most pressing issues.

Join us as we navigate the forefront of innovation, driving forward the transformation of healthcare for a healthier, more connected world.

Have questions or suggestions? Please use the contact button below.

Notifications

Clear all

Post-V20 Upgrade Signing Issues

General Discussion

Last Post by cstephenson 3 years ago

4 Posts

3 Users

0 Reactions

67 Views

RSS

cstephenson

(@cstephenson)

Posts: 33

Trusted Member

Topic starter

I just thought I would throw this out here to see if anyone has experienced this problem. We upgraded to V20 classic on Friday and today is our first day in production. Most of our users have lost the ability the sign documents. The "SIGN" document button is grayed out. All of the pre-upgrade permissions appear to be intact. I tried removing the signing permissions and adding them back and it did not correct the problem. Hoping someone has a solution!!

Posted : June 21, 2021 8:20 am

cjames

(@cjames)

Posts: 58

Estimable Member

We experienced the same. Here are a few options support offered us:

1) If it is an unsigned document, user can open the document itself and sign it from within.

2) If it is a signed document (that user needs to co-sign) or an unsigned document the user needs to sign without opening it, one of the two following workarounds can be utilized.

A. Give the user the "Lab Report" -Sign document signing privileges (NOT RECOMMENDED)

B. Sign the document via the "Route" option. From the Chart Desktop, highlight the document and choose "Route". Remove all "Route to" users and click "Sign". (RECOMMENDED)

Posted : June 21, 2021 8:30 am

jessicaw

(@jessicaw)

Posts: 434

Prominent Member

We encountered the same problem with the "Letter" document type and were offered the same suggestions mentioned by cjames. See link to knowledge article below.

KA 95736

https://athenaflex.athenahealth.com/s/article/kA06f000000NEuYCAW?lang=en_US

Posted : June 24, 2021 6:24 am

cstephenson

(@cstephenson)

Posts: 33

Trusted Member

Topic starter

I just want to follow up on this in case anyone is following this post. We discovered through our own testing that if you give users the "Lab Report - Sign" permission, it unlocks all of their other signing permissions (crazy I know). I eventually heard back from Quatris on this and they confirmed that this is a bug (KA 95736) and they are working on a fix. The options are to give all users the "Lab Report - Sign" permission (not recommended) or to have them sign the document using the routing box.

Posted : June 30, 2021 2:40 am

Share:

24 Forums
9,940 Topics
39.9 K Posts
0 Online
6,470 Members

Forum Icons: Forum contains no unread posts Forum contains unread posts

Topic Icons: Not Replied Replied Active Hot Sticky Unapproved Solved Private Closed

Powered by wpForo Powered by wpForo version 2.4.0