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

VFE File Size Question

Trading Post

Last Post by Anonymous 1 second ago

3 Posts

2 Users

0 Reactions

72 Views

RSS

Verna Lewis

(@vbl_chug)

Posts: 12

Eminent Member

Topic starter

Good afternoon,

Background:

We are working to build VFE forms to customize CPOE order content per specialty within our practice plan. It was suggested that we use button forms in order to accomplish this. After starting the development, we learned of the 64K file size limit for using a VFE form within the C-EMR. That being said, we have imported forms far larger than 64K without any adverse results. But we have also imported larger files that cause a total abort when we try to access the form in C-EMR.

Questions:

1. Has anyone worked with VFE forms that were greater than 64K? Have you been successful?

2. Does anyone have knowledge about what form elements affect the file size? Are buttons size-intensive?

If you have any VFE experience that you believe is associated with file size issues, we would be grateful for your feedback and willingness to share information.

Thank you.

Verna Lewis

Project Manager

Rowan University

Posted : November 1, 2013 4:21 am

gibsonmi

(@gibsonmi)

Posts: 827

Prominent Member

I know VFE gives you a warning when you get to either 60K or 64k per file, but there are different files for each page, two for functions, one for the printed version of the form and one clinical kit to keep them organized. I think the limit is a historical limit that older versions of Centricity had, I dont know what the current limit is and Im not sure if there even is one, I have one function file for an assessment form the is 117k and it imports and runs on CPS10.

The thing that really sucks up space from my experience is visibility fields, especially if you have a lot of items inside the visibility fields and stack a few of them up and use supression blocks for the translations. The way VFE writes those files is not very efficient. I have an all button problems page on a form, each button contains a function and an enable expression, about 120 buttons in all and the page is only 18k, so I think that plan should work for you. If you really want to know what it is doing you can open the efm file in notepad or the xlt or xlw in excel and get a good idea what makes up the file size

Posted : November 1, 2013 5:17 am

Verna Lewis

(@vbl_chug)

Posts: 12

Eminent Member

Topic starter

Michael,

Thank you so much for your detailed reply. I will share that with the team here.

Verna

Posted : November 1, 2013 5:18 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