We have a custom form for Health Maintenance that works great in our Office Visit. We recently learned that it does not seem to load correctly in the Clinical List Update, however, if we remove it from the Clinical List Update and Add it back in, then it loads fine. We have tried removing it from the Document Template for the Clinical List Update saving it and then adding it back into the Document Template and saving it again, but when we launch a new Clinical List Update it does not load correctly. We have to Remove it and Add it back in for it to work, but like I stated it works fine in our Office Visit Document Template.
Any ideas what could be going on and what can be done with this so that it loads correctly in the Clinical List Update?
My best guess without dissecting the form itself is that your custom form has references to variables that conflict with the other form(s) in the Clinical List Update template. Behavior of forms with conflicting variables can be difficult to isolate, but this is where I would look first. A best practice I use when doing custom form development is to use a prefix before any variable I utilize in the function view of the form. The purpose of the prefix is to ensure that the variable will be unique if my form component is ever added to a different encounter template or "on the fly" through the Add Form button while in an encounter. The prefix I use is often a short abbreviation of the form name itself. This makes the variable names longer but it helps prevent future conflicts.