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

PRINTHANDOUT() Routes Visit?

Bugs, Known Issues, Open Cases

Last Post by Anonymous 1 second ago

9 Posts

4 Users

0 Reactions

67 Views

RSS

bhoover

(@bhoover)

Posts: 360

Honorable Member

Topic starter

Hello All,

I am seeing a weird issue with a limited number of users. We have a form where users click a button that calls the PRINTHANDOUT() function. For most users the function works as intended and prints the selected handout. Recently however a couple of MAs have found that when they click the button to print the handout it opens the window as if they ended the visit and populates the box to route the visit to one of the doctors.

I ran a MEL trace logged in as one of the MAs who was having the problem and the function to print the handout was called correctly. The users also have their printers setup correctly. I also temporarily modified their user groups in security to see if there was a missed setting and that did not change the behavior either.

Has anyone else run into this behavior? If so, how did you address it?

Thanks.

Posted : May 27, 2015 5:09 am

mkherman

(@mkherman)

Posts: 53

Trusted Member

What version are you on?

We just discovered this with an upgrade to CPS 12 (SP6).

If a user has the checkbox to 'Record handout printing in Chart' selected in the Handout dialog then an document is created in the chart (Internal Correspondence). If the user removes the check from the checkbox a document will not be created. If the MA's do not have signing privileges to that document type, they will get the route dialog, only after they route the document will the handout print.

We found a document may also be happening with providers, they just don't notice because they have signing privileges to that document type so do not get prompted to route the document.

I opened a ticket with GE asking about this functionality but have not yet heard back.

I was looking to see if there was a way to set this in the data symbol that is not documented in the Help file.

I hope this helps- it took us some time to figure it out.

Mary Kay

Posted : May 27, 2015 5:25 am

bhoover

(@bhoover)

Posts: 360

Honorable Member

Topic starter

Hello Mary Kay,

Thanks for you response. The issue that you found is interesting... but I think might be unrelated. We aren't using the 'I' button in this case. We are printing custom handouts using the PRINTHANDOUT function so it wouldn't record anything in the chart... at least that I am aware of.

Brad

Posted : May 27, 2015 7:38 am

mkherman

(@mkherman)

Posts: 53

Trusted Member

I know- same for us. We have a button on a form that calls the Printhandout() symbol to print a specific handout. In previous versions only the handout printed, now a document is sometimes created when printing a custom handout. The printhandout appears to take the 'sticky' setting from the handouts (not the i button but ctrl + H) to determine if a document should be created.

Mary Kay

Posted : May 27, 2015 9:17 am

bhoover

(@bhoover)

Posts: 360

Honorable Member

Topic starter

Mary Kay,

Thanks for the additional info. That's strange. I'll look further at our situation and see what I can find. Hopefully you find out something conclusive from GE.

Brad

Posted : May 27, 2015 9:52 am

jpack

(@jpack)

Posts: 20

Eminent Member

Hi all,

We also have an MA experiencing this. She is clicking a button that runs PRINTHANDOUT() and is getting the box to route a document. Her account setup and settings in Centricity are identical to all of her teammates, but only she is experiencing this; all other MA's have a handout sent to the printer with no dialog box presenting at all. I'd appreciate any added insights.

Thanks,

Posted : May 18, 2018 4:50 am

jpack

(@jpack)

Posts: 20

Eminent Member

Update:

After reading the other posts here, I had our MA Open the Print Patient Education Handout window with Ctrl H, select a handout to print, uncheck "Record handout printing in chart", and Close. Now the PRINTHANDOUT() button prints as expected. It is this box that seems to be affecting things for her. However, other users have that box checked...? I submitted a case to GE. Hopefully others do too.

Posted : May 18, 2018 5:07 am

gibsonmi

(@gibsonmi)

Posts: 827

Prominent Member

Its the user that's set for the print handout record. If you open the regular handouts window and have 'Record handout printing in Chart' checked and any user other then the logged in user selected, it will prompt the user to route the record of the handout printing anytime they print a handout with the PRINTHANDOUT() function. Just have the user switch the name back to themselves and it should stop. We have one or two instances of this a month across about 500 users.

Posted : May 18, 2018 6:33 am

jpack

(@jpack)

Posts: 20

Eminent Member

Ah ha! Thanks!

Posted : May 18, 2018 10:30 am

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