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

MEL Parse Error on Form with Multiple Visibility Regions

MEL, SQL, Oracle

Last Post by Anonymous 1 second ago

7 Posts

4 Users

0 Reactions

61 Views

RSS

jmf432

(@jmf432)

Posts: 15

Eminent Member

Topic starter

I have a form with 7 visibility regions ( different tests/orders appear based on location of care).

When I added the 7th visibility region, I started get a MEL parse error. There are approx. 80 document variables on each from.

Strange thing is that the IF statement that shows up in the MEL is not part of my code - is this something that is being created internally? I can't seem to get around this. The MEL vomit appears when the form is loads initially.

{IF (STR(DOCUMENT.PT_ROOM, DOCUMENT.EKG, DOCUMENT.INTR_DIAG_01, DOCUMENT.RYTH_STRP, DOCUMENT.INTR_DIAG_02, DOCUMENT.HEMOGLOBIN_A, DOCUMENT.INTR_DIAG_03, DOCUMENT.FINGER_STICK, DOCUMENT.INTR_DIAG_04,

......

DOCUMENT.INTR_DIAG_22, DOCUMENT.AMRRH_TST, DOCUMENT.INTR_DIAG_23, DOCUMENT.HEMOCCULT, DOCUMENT.INTR_DIAG_24, DOCUMENT.OTHER_TESTS_1, DOCUMENT.INTR_DIAG_25, DOCUMENT.RAPID_STREP_, DOCUMENT.INTR_DIAG_15, DOCUMENT.THROAT_CULT, DOCUMENT.INTR_DIAG_16, DOCUMENT.PEAK_FLOW, DOCUMENT.INTR_DIAG_14, DOCUMENT.EYE_EXAM, DOCUMENT.INTR_DIAG_17, DOCUMENT.HEAR_TST, DOCUMENT.INTR_DIAG_18, DOCUMENT.UP_GO_TST, DOCUMENT.INTR_DIAG_19, DOCUMENT.UA_DIP, DOCUMENT.INTR_DIAG_20, DOCUMENT.DYSURIA_UA, <-COMPILER ERROR NEARBY: Too many arguments after COMMA

Posted : November 28, 2016 3:26 am

evanstaden

(@evanstaden)

Posts: 31

Eminent Member

Then the code is either in the encounter or in a variable directly. If you send me the form I can help you fix it. Go to the bottom window of VFE where you would see the errors and Ctrl+F and type in part of the str and enter to search then double click and it will open the box that contains that code.

Hope this helps. If need be email it to me at [email protected] and I can find it for you.

Posted : November 28, 2016 3:41 am

jmf432

(@jmf432)

Posts: 15

Eminent Member

Topic starter

The error happens at run time....It compiles with no errors......

Posted : November 28, 2016 3:47 am

evanstaden

(@evanstaden)

Posts: 31

Eminent Member

You still need to identify where the code is and take it out then re-run it. Look in the encounter if you execute by dropping the form into a blank open encounter then the code is in the form.

Posted : November 28, 2016 3:49 am

jfitzmd

(@jfitzmd)

Posts: 419

Reputable Member

The if statement is created to process the visibility segment. Take it out, verify there are no errors, then look carefully at your syntax. It would be helpful if you could post your visibilitiy segment code.

Posted : November 28, 2016 3:55 am

jmf432

(@jmf432)

Posts: 15

Eminent Member

Topic starter

The code in the visibility region just checks the location of care.......

{DOCUMENT.LOCOFCARENAME == "XXXXX-Cardiology"}

Posted : November 28, 2016 4:01 am

Lee

(@lee-cooper)

Posts: 348

Reputable Member

Based on the information provided:

7 layers of 80 variables = 560 potential arguments.

MEL has undocumented argument count limits to various functions and I suspect that you might have hit the limit for the str() function.

Try to remove fields (variables) from the last layer until it works. Add a field back and see if it breaks again - you will have your answer regarding the limit.

Possible resolution:

Break the visibility layers up into multiple sections or tabs, ensuring you do not exceed the newly discovered limit. If you break it up using tabs, you could then use some additional MEL to jump the user to the appropriate tab containing the additional layers.

Alternatively, you could break the layers into multiple layers containing 20 variables each for each layer resulting in 4 layers per location of care 'visibility'. This would give you room to expand as well.

Hope this helps.

Posted : November 28, 2016 6:26 am

Share:

24 Forums
9,940 Topics
39.9 K Posts
0 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