Notifications
Clear all
Topic starter
After a recent update to 12.3 my vital signs form is producing OBSNOW in the fields instead of the values entered. It is not a form I created. I remember this happening in the past with other forms but cannot remember the solution. If I go to the next form and back it populates the correct data. Any ideas? Thank you!
Posted : June 30, 2020 5:27 am
We are on 12.2.2 and this happens to some of our users occasionally. For us to resolve it we replace the usrlib and vitallib files within the Client folder. Even though the replacement files appear identical to the files that are already in the Client folder, this has always worked as a resolution for us.
Posted : June 30, 2020 5:50 am
Topic starter
Thank you Jessica! I will give it a try.
Posted : June 30, 2020 8:16 am
For further understanding, the typical culprit of this presentation is a MEL error in linked code. The error can range from any number of syntax and command errors such as unpaired suppression blocks, unpaired parenthesis, unpaired curly braces, missing an endif or endfor or endcond, etc. Sometimes, hidden characters can also be the cause, or even a simple misspelling (i.e. ednif vs endif) or a comma in place of a period making them rather difficult to isolate.
The good news is a MEL trace is often useful for narrowing down the general area of the error making fixing it easier. If it is being driven, as suggested, by a .txt file, it can be a bit more difficult to capture in a trace, but sometimes one gets lucky. This difficulty is introduced due to how the .txt files function - they are loaded on EMR start-up and reside in memory before a trace can even be started.
If swapping the files does not work, you might consider running a MEL trace to see what the issue could be. Over the past 20 years, the EMR has become less 'tolerant' of MEL syntax issues, which is probably not a bad thing.
Posted : July 7, 2020 2:58 am