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

OBSPREV not working on some OBS terms

MEL, SQL, Oracle

Last Post by Anonymous 1 second ago

5 Posts

3 Users

0 Reactions

73 Views

RSS

AChess

(@achess)

Posts: 4

Active Member

Topic starter

We recently started pushing new information to a previously unused OBS term and we have been working on getting either the quicktext or patient banner code to display the latest entry in that obs term.

I've tried OBSPREV, LAST_OBS_SIGNED_VALUE, OBSANY, and LIST_OBS, but so far nothing works. The code will work for any other OBS term, just not the one we are interested in. It simply displays a blank.

To your knowledge, is there some additional requirement for pulling the OBS term in this way? I did make sure the value in the OBSHEAD table was changed to active, but maybe something else?

Thank you!

Posted : July 20, 2018 4:19 am

joeg1962

(@joeg1962)

Posts: 843

Noble Member

Nothing comes to mind, however:

Are you signing the update that is pushing the OBS term?

Do you check prior to saving, and review the 'Clinical Changes' to see if it is written?

Could it be a spacing issue?

Posted : July 20, 2018 4:32 am

bhoover

(@bhoover)

Posts: 360

Honorable Member

Is this a custom obs term? We have multiple systems (test, production, etc.) and I have run into issues in the past where I forgot to import the clinical kit to add the custom term into all of the databases. If you don't do that you code won't work because it can't find the term.

Posted : July 20, 2018 5:25 am

AChess

(@achess)

Posts: 4

Active Member

Topic starter

It was an existing but inactive and unused OBS term. All I did to activate it was change the 'Active' field in the OBSHEAD table from 'I' to 'A'.

Posted : July 20, 2018 6:07 am

AChess

(@achess)

Posts: 4

Active Member

Topic starter

I figured out the problem.

I was inserting into the OBS table but I left the 'Change' field and the 'ABNORMAL' field as NULL, the former should have been 2 and the latter, ''

Posted : July 20, 2018 6:37 am

Share:

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