Notifications
Clear all
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
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
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. 
Posted : November 11, 2013 4:35 am
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
Topic starter
Yes it just triggers a visibility region. I will try that. Thanks
Posted : November 11, 2013 4:41 am
Topic starter
That makes the warning show whenever someone adds the date of surgery instead of calculating from it.
Posted : November 11, 2013 4:46 am
{DURATIONDAYS(ADDDATES(OBSNOW("POSTOPINST2"),"0","0","90"),str(._TODAYSDATE))>0 and OBSNOW("POSTOPINST2") <> ""}
Posted : November 11, 2013 4:57 am
Topic starter
That appears to work. Thanks
Posted : November 11, 2013 6:28 am
