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

Problems signing a Clinical Visit Summary

MU, CQR, PQRS, etc.

Last Post by Anonymous 1 second ago

5 Posts

5 Users

0 Reactions

68 Views

RSS

JBell

(@jbell)

Posts: 285

Honorable Member

Topic starter

I have a provider who is unable to sign a Clinical Visit Summary that has ended up on his desktop. Specifically:
'Cannot perform the action: Sign Documents (Clinical Visit Summary). You do not have the required privilege. '

I have checked and this permission is not granted within the normal documents signing area as there is not clinical visit summary that I can grant permissions to sign. The document type is CVS.

GE informed me that I need to upgrade to 12.3 to fix this.

Has anyone else experienced this and is there a way to grant permissions to sign this document?

Thanks in advance!!!

Posted : May 1, 2018 8:19 am

sborchardt

(@sborchardt)

Posts: 218

Reputable Member

We have had this happen a few times. We send in a support time and GE has to access the data base to sign the document.

Posted : May 1, 2018 8:30 am

mtooley

(@mtooley)

Posts: 62

Estimable Member

We had this happen and what worked for us was that I went into the person's privileges and gave him access to sign all documents (even though there is no CVS like you said) and the person was able to sign after that. I then went back in and removed what they weren't suppose to have.

Give that a shot!

Posted : May 1, 2018 8:36 am

DavidShower

(@davidshower)

Posts: 1255

Noble Member

That document type was probably applied manually at the start of an update. It is exposed in the UI but isn't supposed to be (think there are at least 3 others). That's why it isn't in the list of documents to sign/half-sign. Been a bug for a while. And you can't change it in the document properties because you have to have rights to sign the document type you are changing from as well as the one you are changing to. You would need to update the DOCTYPE field in the DOCUMENT table for that document to a document type (listed in the DOCTYPES table) that the provider can sign.

Posted : May 9, 2018 5:03 am

Sirna

(@sirna)

Posts: 384

Honorable Member

Call with GE and they jump on the server to sign manually. There is a PROG Note-exp and one other that I know of with the same glitch.

Posted : May 9, 2018 7:39 am

Share:

24 Forums
9,940 Topics
39.9 K Posts
1 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