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

When Are OBS Terms / Document Variables Loaded Into Memory?

MEL, SQL, Oracle

Last Post by Anonymous 1 second ago

4 Posts

2 Users

0 Reactions

59 Views

RSS

bhoover

(@bhoover)

Posts: 360

Honorable Member

Topic starter

Hello All,

I am trying to get a handout to autoprint on a a form without a button. I created a watcher function that takes the bmi and if it is over a certain range a handout is called with PRINTHANDOUT(). I also put a value into an obs term indicating that the printout occurred -- this way there isn't a duplicate handout printed. This works great as long as you don't put the document on hold.

I've noticed that bringing the document off of hold causes PRINTHANDOUT() to be called again even though there is a value in the obs term that should prevent this. I ran a mel trace and noticed that the obs term returned a null value. Even though a null value is returned in the mel trace the initial value before I put the visit on hold is returned on the form.

So, I think that obs terms (and document variables since I tried that too) are loaded after any watcher functions. Has anyone coded around this? I'd like to be able to have a flag persist if the visit is put on hold.

Thanks,

Brad

Posted : February 19, 2016 5:01 am

gibsonmi

(@gibsonmi)

Posts: 827

Prominent Member

Yes you are correct that observation terms are loaded much later, but I do this all the time with document variables. Just make sure that you are not setting the document variable with the observation term or you may have the same issue, I usually do something like this -

{!if DOCUMENT.ALREADYPRINTED == "" then IF DOCUMENT.CRITERIA == TRUE then

//do this

DOCUMENT.ALREADYPRINTED = "Yes"

ENDIF

endif}

{OBSNOW("OBSTERM",DOCUMENT.ALREADYPRINTED)}

Posted : February 19, 2016 5:49 am

gibsonmi

(@gibsonmi)

Posts: 827

Prominent Member

Yes you are correct that observation terms are loaded much later, but I do this all the time with document variables. Just make sure that you are not setting the document variable with the observation term or you may have the same issue, I usually do something like this -

{!if DOCUMENT.ALREADYPRINTED == "" then IF DOCUMENT.CRITERIA == TRUE then

//do this

DOCUMENT.ALREADYPRINTED = "Yes"

ENDIF

ENDIF}

{OBSNOW("OBSTERM",DOCUMENT.ALREADYPRINTED)}

Posted : February 19, 2016 5:51 am

bhoover

(@bhoover)

Posts: 360

Honorable Member

Topic starter

Thank you for the explanation. I looked at my attempt using a document variable again and found a type-o in the code that was preventing the document variable from being assigned. It is interesting that the obs terms load after other code. You would think all of the data that code might need to access would load first.

Posted : February 19, 2016 7:45 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