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

Orders not populating if the form was on HOLD during its lifetime

MEL, SQL, Oracle

Last Post by Anonymous 1 second ago

1 Posts

1 Users

0 Reactions

144 Views

RSS

[email protected]

(@wschuttccao-net)

Posts: 1

New Member

Topic starter

We have a form that ultimately creates orders after a button press where it runs about 300 lines of code. Normally everything flows fine, however if the form was on hold in its lifetime without many document variable changes afterwards some of the orders do not create while other will. The super strange part is that the document variable that the order is based on is still populated (as verified through a userOK box and what I understand of a MEL trace) right before the Mel_Add_order function:
if (DOCUMENT.TOTAL_KENALOG > 0) then
if (MEL_ADD_ORDER("S","Office Supplies","Kenalog, 40mg/1ml vial","",
kenalogcodes,kenalogdescr,"",str(DOCUMENT.TOTAL_KENALOG * 4))
< 0) then .....

The if statement appears to never kick off after the document is on hold even though DOCUMENT.TOTAL_KENALOG still holds the expected value as displayed using userOK which does still kickoff. Wondering first if this is any kind of known issue or basic thing I'm missing. Can get into more detail if desired. I did go through the post in CHUG | Is there any way to prevent multiple entries of orders even after the document is opened from hold? (centricityusers.com) which was almost opposite of my problem but this is on button press and no watcher variables in play to activate the orders so I don't think my concern is related. Thank you.

Posted : July 1, 2021 9:01 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