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

Code Issues

Trading Post

Last Post by Anonymous 1 second ago

8 Posts

2 Users

0 Reactions

61 Views

RSS

mcarlo

(@mcarlo)

Posts: 66

Trusted Member

Topic starter

Hi,

We purchased a form several years ago that had a simple code that would flag when the global period expired. Starting a week ago the warning appears randomly when no date has been entered. This is causing a lot of confusion among the staff. Does anyone know what could be causing this. We made no changes to that form. Thanks

Code behind visibility region:

{ADDDATES(OBSNOW("POSTOPINST2"),"0","0","90")<._TODAYSDATE}

Posted : November 11, 2013 12:49 am

gibsonmi

(@gibsonmi)

Posts: 827

Prominent Member

I cant explain why something like that would have just started. If patients dont have that observation in the current update though it will display the visibility field. When no date has been entered and the observation is blank it returns NULL. NULL is always less than todays date, is there a change in workflow or the way that observation is recorded that could have caused this?

Posted : November 11, 2013 4:31 am

mcarlo

(@mcarlo)

Posts: 66

Trusted Member

Topic starter

No I have been testing it for three days to see if it was operator error but now several teams are reporting the issue. We have a similar code that shows when the patient is within the global period (different form) and it's not working either. Cry

Posted : November 11, 2013 4:35 am

gibsonmi

(@gibsonmi)

Posts: 827

Prominent Member

Just try this -

{ADDDATES(OBSNOW("POSTOPINST2"),"0","0","90")<._TODAYSDATE and

OBSNOW("POSTOPINST2") <> ""}

It's just for a visibility field to display, correct?

Posted : November 11, 2013 4:38 am

mcarlo

(@mcarlo)

Posts: 66

Trusted Member

Topic starter

Yes it just triggers a visibility region. I will try that. Thanks

Posted : November 11, 2013 4:41 am

mcarlo

(@mcarlo)

Posts: 66

Trusted Member

Topic starter

That makes the warning show whenever someone adds the date of surgery instead of calculating from it. Cry

Posted : November 11, 2013 4:46 am

gibsonmi

(@gibsonmi)

Posts: 827

Prominent Member

{DURATIONDAYS(ADDDATES(OBSNOW("POSTOPINST2"),"0","0","90"),str(._TODAYSDATE))>0 and OBSNOW("POSTOPINST2") <> ""}

Posted : November 11, 2013 4:57 am

mcarlo

(@mcarlo)

Posts: 66

Trusted Member

Topic starter

That appears to work. Thanks Smile

Posted : November 11, 2013 6:28 am

Share:

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