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

Suppressing the Keyboard 'Enter' key

MEL, SQL, Oracle

Last Post by Anonymous 1 second ago

4 Posts

3 Users

0 Reactions

78 Views

RSS

jwhite-uams

(@jwhite-uams)

Posts: 15

Eminent Member

Topic starter

On our Vital Signs form we have a Height, Weight and Temperature field and the correct workflow is to enter the information in the field and then click into the next one. Unfortunately, our users keep hitting the ‘Enter’ key on their keyboard which causes the form to “disappear”. The data is still entered but to get back to the form the user must click on the form itself on the forms list for the encounter. Let me know your thoughts on how I can possibly restrict/suppress this action from happening.

Posted : February 4, 2019 3:40 am

caswelljm

(@caswelljm)

Posts: 80

Trusted Member

I don't think their is a suppress option for VFE.

We have been training our staff to use Tab.

-James

Posted : February 4, 2019 7:12 am

Lee

(@lee-cooper)

Posts: 348

Reputable Member

This is a core encounter form architecture issue with the EMR. VFE has no control over it because the EMR does not include a hook for it. Complicating issues is the multi-line edit field which does accept input from the enter key. I think for consistency sake, a decision was made long ago to not permit enter to jump fields. Makes sense, if it is thought about, but less sense in today's data entry environs. I do not think this will be changed in the current builds, but it may be something that self corrects once North-Star is fully implemented.

Jim is correct, the tab key is the preferred method of navigating fields on an encounter form. Training and reinforcement are the tools in your toolbox.

Posted : February 4, 2019 10:20 am

jwhite-uams

(@jwhite-uams)

Posts: 15

Eminent Member

Topic starter

Thank you caswelljm and Lee for the answers to my question. Looks like "Training and Reinforcement (using the tab key instead of the Enter key)" is the best method with this version of CPS - were on 12.3 SP2.

Posted : February 5, 2019 2:22 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