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

/par not displaying correctly

Trading Post

Last Post by Anonymous 1 second ago

6 Posts

3 Users

0 Reactions

132 Views

RSS

SLHV

(@slhv)

Posts: 478

Honorable Member

Topic starter

First let me apologize, coding is not my forte so if the issue isn't detailed enough please let me know I will provide as much info as needed.

Since we have upgraded to CPS 9.5 from 9.0, we have been having an issue with a VFE form. The issue is that when the particular form is edited in any way, an extra "/" is added to our "/par" variable. Resulting in it looking like this: "//par". This then causes the form to display all of the MEL code and messes with the format. I've tried researching but am lost so far. Has anyone experienced any issues such as this?

Edit: Here is a visual, step by step, of what I'm referring to. Paint still comes in handy every now and then Laugh

1

2

3

4

Posted : October 12, 2012 3:29 am

schinn

(@schinn)

Posts: 23

Eminent Member

Is this a custom form you created? If it is, attach the source file for the form and I'll take a look at it and see if I can help!

Posted : October 12, 2012 7:35 am

SLHV

(@slhv)

Posts: 478

Honorable Member

Topic starter

schinn said:

Is this a custom form you created? If it is, attach the source file for the form and I'll take a look at it and see if I can help!

It's a custom form, but not one that I created. Trying to edit this to work with CPS 9.5 is my first time working with VFE or MEL code. I've been trying to wrap my head around it but it's been slow going thus far unfortunately. Finally, I figured an outside perspective could shine some light on the problem.

What is the easiest way to view the source code? I opened it in Notepad++ but notice there's a lot of giberish characters so I'm assuming it wasn't read correctly. Also there may be some sensitive information in there so I'd like to censor that first.

Thanks for your help. Very much appreciated.

Posted : October 12, 2012 12:08 pm

cwhite

(@cwhite)

Posts: 28

Eminent Member

Can you upload the .dlg file associated with the form to the forum so that we could take a look and maybe figure out the coding error?

Do you have VFE installed, and if so, are you able to open the form in VFE?

Thanks,

Chris

Posted : October 17, 2012 4:25 am

SLHV

(@slhv)

Posts: 478

Honorable Member

Topic starter

Yep.

Posted : October 22, 2012 7:14 am

SLHV

(@slhv)

Posts: 478

Honorable Member

Topic starter

For anyone interested, I was able to resolve this issue by removing the returns between lines and inserting the command "+HRET+" between each line.

For example, before the code for a button looked like this:

{CFMT(LASTOBSVALUE("EF MUGA"), "", "1. Normal Bruce protocol exercise tolerance test.

2. Normal left ventricular size and function with a calculated ejection fraction of ", "", "%.

3. Myocardial scintigraphy is normal without evidence for previous myocardial infarction or reversible ischemia.")}

I then changed each to read like this:

{CFMT(LASTOBSVALUE("EF MUGA"), "", "1. Normal Bruce protocol exercise tolerance test.” + HRET + “2. Normal left ventricular size and function with a calculated ejection fraction of ", "", "%.” + HRET + “3. Myocardial scintigraphy is normal without evidence for previous myocardial infarction or reversible ischemia.")}

After making this change to every button within the form, the /par went away for good.

Posted : November 28, 2012 2:51 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