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

OBSANY() while a document is on hold, Used in handouts

Trading Post

Last Post by Anonymous 1 second ago

7 Posts

4 Users

0 Reactions

85 Views

RSS

Anonymous

(@Anonymous)

Posts: 0

New Member Guest

Topic starter

I'm also working on the Patient Instructions handout.

In my case, providers will enter clinical data while the patient is in the office, and then place that document on 'Hold.' While the document is on 'Hold,' we will print a handout, and the provider will sign off on the document some amount of time later.

My issue is that OBSNOW() returns "" inside the handout while the document is on hold, and OBSANY() returns the value entered during the previous update. OBSANY() does NOT return the value entered during the update that was placed on 'Hold.'

The help topic defines the return value for OBSANY() as:

"the most recent observation value up to and including the current update."

Am I correct in saying that updates placed on 'Hold' are not defined as being 'the current update,' and that OBSANY() will not return the value for an obs term entered before placing the update on 'Hold' ? Or, is there some issue with OBSANY() that only I am experiencing?

Posted : February 12, 2013 2:23 am

gibsonmi

(@gibsonmi)

Posts: 827

Prominent Member

That is correct, OBSANY will only evaluate signed documents and active chart updates.

This was a problem for us as well, so i created a function that would look up observations in the pencil status regardless of whether the document was active. It first checks the object "_PencilOnlyObs" then if it does not find a result looks in "SignedObs" and filters all results by date. It took me a bit to get it setup and we use it mostly for the CVS, if it is something you might be interested in send me an email and I can send some examples of what I did.

Mike

[email protected]

Posted : February 13, 2013 6:22 am

kalevine

(@kalevine)

Posts: 70

Estimable Member

I am experiencing this problem with obsnow with one obs term but not with any other, and I think it's a bug. obsnow should be the current value in the update regardless if it was assigned prior to putting the document on hold or not. Here is my code:

if obsnow("HPV VAX DOSE")<>"" then

if (obsnow("HPV VAX VIS")=="") then

obsnow("HPV VAX VIS","05/17/2013")

endif

if obsnow("HPV#1AD")=="" then

obsnow("HPV#1AD",sub(str(document.clinicaldate),1,10))

endif

When I first enter a value in the form for HPV VAX DOSE, it assigns 05/17/2013 to HPV VAX VIS and the document date for HPV#1AD. I change each of those dates. I then put the document on hold and view clinical list changes. Everything looks fine. Then I edit the document and see that, while HPV VAX DOSE still has the value I changed it to, HPV#1AD has been updated to the document date again. Any explanation or qworkaround would be appreciated!

Ken

Posted : December 3, 2013 5:29 am

jjordet

(@jjordet)

Posts: 545

Honorable Member

OBSANY will return a value, but you have to be in the chart, not necessarily the update, to get the value from the update that's on hold.

Posted : December 3, 2013 5:46 am

kalevine

(@kalevine)

Posts: 70

Estimable Member

I don't want to use obsany. I don't care what its value was prior to this update, only what it is during the update, and I don't care whether the value was set prior to going on hold or not.

Both HPV VAX DOSE and HPV VAX VIS retain the obsnow values from prior to going on hold, so I can't see a logical reason why the same is not the case for HPV#1AD, unless it is somehow executing this code prior to reloading the value of HPV#1AD. By the way, iof I do use if obsany("HPV#1AD")=="" then, the condition still evaluates to true and the date gets replaced by the current date. This at least seems consistent to me, albeit consistently wrong

Posted : December 3, 2013 6:00 am

gibsonmi

(@gibsonmi)

Posts: 827

Prominent Member

It is my experience that loading the observations tied to a document is one of the last things it does. It is quite plausible that it just hasnt loaded it before the code is executed. I have moved away from using observations for checking conditions for this reason. Almost all of my code and form fields use document variables, and then I save obsterms separately in the watcher pane with code like {OBSNOW("HEIGHT",document.height)}. You could also prevent the problem above by adding a document variable to check if the code had been executed already, like below, then it shouldn't overwrite your changes on form open.

if obsnow("HPV VAX DOSE")<>"" then

if document.execute == "" then

if (obsnow("HPV VAX VIS")=="") then

obsnow("HPV VAX VIS","05/17/2013")

endif

if obsnow("HPV#1AD")=="" then

obsnow("HPV#1AD",sub(str(document.clinicaldate),1,10))

endif

document.execute = "Done"

endif

Posted : December 3, 2013 6:18 am

kalevine

(@kalevine)

Posts: 70

Estimable Member

Thanks Michael, that's helpful, if not exactly the logic I want.

What's maddening is that it appears to have loaded the values for other obs terms on which the code that it wrongly executes is dependent. If it loaded them all at the beginning or end there wouldn't be this problem. It makes me wonder where else this issue may be lurking.

Thanks again

Ken

Posted : December 3, 2013 6:58 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