Welcome to the NEW CHUG— your ultimate destination for cutting-edge insights and discussions at the intersection of healthcare and technology.

Our platform is dedicated to exploring the dynamic landscape of healthcare technology, empowering professionals, enthusiasts, and innovators alike with the knowledge and resources to navigate the rapidly evolving field.

From telemedicine revolutionizing patient care to the transformative potential of artificial intelligence in diagnostics, we delve into a myriad of topics shaping the future of healthcare delivery. Whether you’re a seasoned healthcare IT professional, an aspiring entrepreneur in the digital health space, or simply curious about the latest innovations, our curated content, expert interviews, and thought-provoking articles provide a comprehensive exploration of healthcare technology’s most pressing issues.

Join us as we navigate the forefront of innovation, driving forward the transformation of healthcare for a healthier, more connected world.

Have questions or suggestions? Please use the contact button below.

Notifications

Clear all

HTML Forms

CPS, C-EMR, PM

Last Post by Anonymous 1 second ago

2 Posts

2 Users

0 Reactions

59 Views

RSS

dorotheatrusty

(@dorotheatrusty)

Posts: 148

Reputable Member

Topic starter

Is anyone using straight HTML forms? How's that going?

Thanks for your response.

Posted : March 17, 2016 5:24 am

mikeseale

(@mikeseale)

Posts: 344

Reputable Member

We use mostly HTML forms that I develop. There are some things you have to get around currently when using them, but the overall performance outweighs those issues. I don't think you will see too much of a performance/speed increase unless you have big forms.

We do a lot of checks in the background on the information typed in, and with the VFE forms this slowed them down a lot. We also write to many observation terms for reporting which also slows the forms down.

Development time is increased at first because you have to pretty much start from scratch, but I find maintaining the HTML forms is much easier. Not being able to use "find and replace" within the VFE forms really makes changing the bigger forms a tedious chore.

Some things that currently don't work with HTML forms:

ENTER key is blocked and will not trigger anything when pressed while on the HTML Forms. You have to use CTRL+M to go to the next line in <textarea>.
Form is not built in, so it is essentially a pop-up. This hasn't been such a big deal as we added more forms as HTML; however, when you only have a few, it is an inconsistent experience.
You can't close the window through code. The use has to press the X at the top right. This makes switching back to the VFE forms a little strange at times. Basically, you set the OPEN_FORM_COMP during window.unload to change to your desired form whenever the user clicks on the X.

Posted : March 17, 2016 8:23 am

Share:

24 Forums
9,940 Topics
39.9 K Posts
1 Online
6,470 Members

Forum Icons: Forum contains no unread posts Forum contains unread posts

Topic Icons: Not Replied Replied Active Hot Sticky Unapproved Solved Private Closed

Powered by wpForo Powered by wpForo version 2.4.0