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

Page close handler issues with CPS 10

Trading Post

Last Post by Anonymous 1 second ago

4 Posts

4 Users

0 Reactions

68 Views

RSS

redde

(@redde)

Posts: 115

Estimable Member

Topic starter

I am having an issue with page close handler in CPS 10. Apparently the page close handler doen not work unless you click the close button (which is no longer in CPS 10), or you click the next form button. Clicking the right or left arrow to move between forms, or clicking a navigation button in the form will not process the page close handler, only clicking the next form button works. Even ending the update doen not work. This is a real issue with having only one form in an update. I can not get it to work at all since the next form button is greyed out. Even with multiple forms in an update it is possible for it not to work depending how the user navigates to other forms. Does any one else have this issue and what possible workaround there might be? This is the code I am using:

{if DOCUMENT.WORK_COMP<>"" then ADD_DOCUMENT_SUMMARY('Ofc Visit W/C') else ""

endif

closepage("FALSE")}

This just changes the summary line if the patient is work comp.

Posted : June 8, 2012 4:37 am

schinn

(@schinn)

Posts: 23

Eminent Member

I've been told that GE is working on a solution for this in the future (but I recommend reporting it anyway to keep it on their radar).

For the example you provided, I would either set it up as a button for the user to click and add the summary, or you can set it up as a global variable in the form, and create a text component to evaluate continuously and calls the global variable you created.

In the form, add this:

{!global workcomp = IF DOCUMENT.WORK_COMP<>"" then ADD_DOCUMENT_SUMMARY("Ofc Visit W/C") else "" endif}

Create a text comp with this: {'{workcomp}'}

Add the text comp to the document template with that form.

Hope that helps!

Posted : June 12, 2012 5:52 am

justinbelcher

(@justinbelcher)

Posts: 130

Estimable Member

You are correct. In CPS 9.5 page close handlers would ALWAYS get executed. In CPS 10 they do NOT always get executed. I had to recode a form because of this. If you have done anything clever with page close handlers you will have to recode your forms also.

There is no event in CPS 10 that fires prior to the end of an update. The only events you can capture are changes to OBS terms, DOCUMENT variables, and global variables.

Posted : June 18, 2012 8:59 am

kalevine

(@kalevine)

Posts: 70

Estimable Member

does anyone know if any of the CCC forms are affected by this? We can't see the source so there is no way to know for sure

Posted : August 24, 2012 5:58 am

Share:

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