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

CANNOT FIND MATCH FOR SPECIFIED ITEM

MEL, SQL, Oracle

Last Post by Anonymous 1 second ago

3 Posts

2 Users

0 Reactions

73 Views

RSS

bhoover

(@bhoover)

Posts: 360

Honorable Member

Topic starter

Hello All,

I am having trouble with the error below. Users are reporting issues with a form, but not all the time. In the form I put PROB_AFTER("delimited") in a global variable for use in multiple spots rather than calling PROB_AFTER("delimited") repeatedly. So basically this:

{! GLOBAL gprobupdate = PROB_AFTER("delimited")}

The users who are seeing the problem are seeing this in the note text:

{global F03376155248268017054=PROB_AFTER("delimited") "" <-CANNOT FIND MATCH FOR SPECIFIED ITEM

Does anyone have any thoughts?

Thanks,

Brad

Posted : March 13, 2019 4:23 am

mthompso

(@mthompso)

Posts: 54

Trusted Member

The expression shown above is automatically generated by Visual Form Editor to do something similar to what you are trying to do. However, that reference is only used in watcher expressions. I would recommend either:

1. Try removing the ! in your watcher expression. When Visual Form Editor updates the global variable your watcher will be executed automatically.

2. In the Program Options->Build->Speed Optimizations section uncheck the Clinical function references item.

Posted : March 18, 2019 1:10 pm

bhoover

(@bhoover)

Posts: 360

Honorable Member

Topic starter

Thank you for your suggestions. I ended up resolving this in two steps:

First, I removed the global variable and simply used PROBLEM_AFTER() instead.

This fixed some of the problem areas that users were having but at less frequency they reported that they were getting the <-CANNOT FIND MATCH FOR SPECIFIED ITEM error. After looking through MEL traces of a couple of charts it looked like it was getting caught on using LIST_ASSESSMENTS(). In this case I am asking for a list of assessments that are 'DX of'. The patients where the error was occurring where when there was a problem in their problem list with an old 'HX of'. GE removed HX of as an option a little while ago and updated the problem table. It seems that there some of these older problems that didn't get updated. You can resolve this problem by simply updating the problem with out changing it (i.e. adding a space to the description and then removing it).

Posted : March 20, 2019 3:38 am

Share:

24 Forums
9,942 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.1