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

obsnow assigning date and time

MEL, SQL, Oracle

Last Post by Anonymous 1 second ago

4 Posts

3 Users

0 Reactions

60 Views

RSS

kalevine

(@kalevine)

Posts: 70

Estimable Member

Topic starter

Hello

I am trying to assign a value to an obs term as follows

obsnow("obsterm",calculation,LASTOBSDATETIME("obsterm2"))

It creates the obs term with the appropriate value and the appropriate date. The time is correct if the lastobsdatetime is prior to today, but if it's today, it puts in the time of the current update, rather than the actual time associated with obsterm2 Is this a known issue or is there a legit reason for this behavior?

Posted : May 8, 2017 9:08 am

jfitzmd

(@jfitzmd)

Posts: 419

Reputable Member

Not a bug. You can't enter an obs term date/time later than the time of opening of the encounter. This is also a problem when accessing information input after the encounter is opened, e.g. a scanned document. There is a workaround for this problem if anybody is interested.

Posted : May 8, 2017 12:31 pm

kalevine

(@kalevine)

Posts: 70

Estimable Member

Topic starter

I am not using a date/time later than when the encounter is opened. I am trying to assign the last signed datetime for a different but related obs to the datetime of this obs. That datetime is earlier the same day, but it seems to put in the time I opened the encounter instead of that earlier time

Posted : May 8, 2017 2:44 pm

Lee

(@lee-cooper)

Posts: 348

Reputable Member

Date and time are locked to the current update date/time unless otherwise specified.

When specifying a different date/time, always ensure that you allow it to be populated only once or it will add each time the command is executed.

Note:

Due to the duplication issue, GE removed the 'time' consideration for 'current date' obsnow quite a while back. There simply were too many support tickets regarding database overload where obsterms were entered literally hundreds of times per update due to lax code. Personally, I loved it for serial captures like blood glucose, oxygen saturation, even blood pressure. Alas, 'tis gone, ne'er to be seen again...

Posted : May 9, 2017 2:23 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