Has anyone experienced any trouble using custom forms from 9.5 in 9.8. We currently still only have the Eval copy to play with and I'm having trouble with many of our custom forms acting up, not sure if I should jump into panic mode or not. We have a planned test upgrade system/server going up sometime this month. Just wondering if anyone out there has experienced any trouble with the way 9.8 reads code.
We have not yet done the 9.5 to 9.8 upgrade, but have had a test 9.8 system up for a while. And while we have many custom forms, we have not experienced any issues.
What kind of problems? What is it that the forms are supposed to do?
I am not aware of any MEL command reductions (commands no longer supported). Perhaps you are calling something shared, and it is not in the same location?
Thats what I'm hoping, a sharing issues at least. A few that stood out a simple inj-med form we have uses multiple display regions stacked on top of one another i'd say 20+. It simply displays the corresponding area when something is choose on a radio button, for example "x" is selected display area "x" appears. Well in the Eval copy of 9.8 won't display any of the regions with any of the choices selected.
Another is a custom HPI form that mimics the functionality of CCC. I have it set up to populate 7 list boxes from text components in Centricity per what problem is selected. I imported everything and made sure all the pieces where in. I get nothing in the form during an update. Also gives a error: Bad symbol type OBSNOW("HPI")..... Where as the form works flawlessly in 9.5.
So far that's all I've tested, a little worried to see anything else wrong.
I would run a trace on anything based on problems, With the introduction of ICD-10 those functions changed a bit. Im on CPS but when I went from 10 to 12, the only problem I had was problem listboxes used to add billing. It depends on how your functions are setup though
If you are running a standalone demo version of 9.8, see if you are getting warning messages in VFE before you import your forms, based on size….
I am currently in EMR 9.5, not yet on 9.8.
I was having troubles (weird behaviors) with a large form, and the MEL TRACE ERROR was Bad symbol type… on items that were just document variable assignments, straight up valid code - such as your OBSNOW(...) statement.
Turned out I was getting VFE warning messages based on size…
So I moved some of my functions into a function library, voila…form worked.
- Beverly