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

Identifying Temporary Variables

MEL, SQL, Oracle

Last Post by Anonymous 1 second ago

2 Posts

2 Users

0 Reactions

80 Views

RSS

bhoover

(@bhoover)

Posts: 360

Honorable Member

Topic starter

Hello All,

I am trying to fix some issues with form slowness in a visit. Some button presses are slow particularly when there are other forms present. Specifically, one of the functions that runs when the button is clicked may add a problem to the problem list. This in turn makes everything that uses PROB_AFTER() run. I am looking at where I have PROB_AFTER() in forms in the visit and modifying or removing if I can. In my mel trace I have something like this:

MelTrace] Fire trigger: {global F03376158922416588048=PROB_AFTER() ""}
MelTrace] execute>>call PROB_AFTER()
MelTrace] results>>[PROBLEM LIST IS RETURNED HERE]
MelTrace] execute>>end
MelTrace] results>>""
MelTrace] execute>>Done with trigger

So it looks like somewhere I have defined a global variable that gets the value of PROB_AFTER(). The temporary variable name the emr uses isn't very helpful. Short of looking through every form in the visit is there a way for me to identify what the temporary variable F03376158922416588048 is actually called?

Thanks,

Brad

Posted : May 13, 2020 2:20 am

gibsonmi

(@gibsonmi)

Posts: 827

Prominent Member

That's just how VFE compiles the form into a kit, in your form in VFE you would just find a reference to PROB_AFTER().

I would search for it by query, you should be able to run this and identify the form

SELECT * FROM FORMSET WHERE WATCHERS like '%F03376158922416588048%' and Active = 'D'

Posted : May 13, 2020 2:36 am

Share:

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