Notifications
Clear all
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
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
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
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
