Notifications
Clear all
Topic starter
Hello All,
I have a provider who wants to pull his entire past visit forward on a relatively data intensive form. I am in the process of developing what he wants and have found that the form behavior works fine at first (click a button and the previous populates) but will eventually freeze CPS. When CPS freezes the visit module disappears. On the chart module the visit is there to click and open but does nothing when you try to do so. Also there isn't a listing for the visit with a pencil next to it in the list of documents.
I am thinking this is because of the number of obs needed (~ 240) since the form was working fine as I was going along converting document variables to obs terms and testing. Once I had about 175 obs on the form I started noticing this problem. I know ideally I shouldn't be using this many obs on the form because of the overhead they bring. Is there a maximum limit for obs term on a single form? Has anyone else noticed this type of issue? I am seeing this on our test environment where we are on CPS 12.3
Thanks,
Brad
Posted : January 4, 2018 8:48 am
Obsterms are time and resource intensive. I would suggest splitting your encounter into multiple forms. I have had forms with probably 50 obsterms. Depending on your network, they may be very slow in loading and in function. If you are committed to a similar number, then consider loading obsterms into document variable on form load, writing the document variables back to obsterms on update or form exit. The form loading may be slow, but the speed from the user perspective is fine. If you are going to have obsterm translation to document variables on form load, be aware, you need to monitor completion of initialization as multiform timing issues can totally sabotage the form load. Contact me if you have further questions.
Posted : January 4, 2018 9:34 am
