I am building a VFE form and when i import it into EMR, enter data on one of the fields it like flutters through the rest of the form. I cant make any changes until it gets to the last field. I am not sure if this has something to do with my suppression blocks. I never experienced this before. Any suggestions??
Usually this happens if you have a ton of obsterms (100+)
You can also get this if you have several watcher expressions or enable/disable fields.
-James
This is likely due to the amount of data that is being pulled into the form itself. The functions that are being run have to go in order in which they are called, so the more data being pulled in or the more functions being run will be additive to the loading completion time.
Any thoughts on how to prevent this from happening? I moved items into sections and that helped a bit bit it is still happening. I have about 50 custom obs terms in the form but that's about it.
Do you have many watcher expressions trying to evaluate on form load? Often times when you create custom functions and you try to run everything at once, you will see some lag time because the different expressions are trying to evaluate to a condition all at once. If you have your form setup this way, it may be better to have certain buttons that call a process, such as a mel calcuation or another specific set of functions that do the same job. It's not automatic, but it will still pull the relevant info for the user. I realize it may not be the perfect scenario, but it might help alleviate some issues with load times. I know that in my own personal development environment, when I am evaluating a ton of data at once, I make use of an extra tab on my forms that I switch to in order to "refresh" the data on the form. It's not perfect, but it does the job.
I'm sure some other users here may have some input that could potentially help speed things up for you. Hope this helped a little.
No watcher expressions. It is actually a pretty straight forward form with a couple visibility regions and data fields. Nothing crazy, that's why I am surprised it is having this behavior.
I am hoping it's just a setting i need to change somewhere or change how I formatted something. I never had this happen.
I happened to be creating a form last week with the same irritating behavior. It has 137 OBSTERMS. I ended up "solving" the problem by changing all fields to document variables, then using a Run Process button to assign the values to the appropriate OBSTERMS. Much faster to input data!
Bentley
Cascade Eye Center
Oregon