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

Adding a problem from a button - can it prompt the user if problem already loaded

Trading Post

Last Post by lkeith 12 years ago

3 Posts

2 Users

0 Reactions

92 Views

RSS

lkeith

(@lkeith)

Posts: 457

Honorable Member

Topic starter

We have a form that is using the Mel_Add_Problem function for one of our specialties and they have expressed a concern that it lets them add a problem even if it already is in the patient's problem list. We added a data display of the existing problems, but they said that with some of their patients, it would be a pain to have to scroll down to make sure that it isn't already there. So, is it possible to program it to prompt the user if the diagnosis they clicked on is already on the problems list????

Posted : March 7, 2013 12:50 am

gibsonmi

(@gibsonmi)

Posts: 827

Prominent Member

For my problem page I placed these in the enable expression box in the advanced section of each button -

match(PROB_AFTER(),"951.4")<1

This keeps the button from being available, you could also do something like -

This in the white space -

{fn CHECK_ADD_PROB(icd, description){

if match(PROB_AFTER(),code)>1 then

if USERYESNO("Prompt to add probelm anyway here") == "Yes" then

MEL_ADD_PROBLEM(‘DX OF’,description,icd,str(._todaysdate),’’,’’,’N’,’’)

else return "" endif

else

MEL_ADD_PROBLEM(‘DX OF’,description,icd,str(._todaysdate),’’,’’,’N’,’’)

endif

}}

In each button just add {CHECK_ADD_PROB(icd code here, description here)}

Mike

Posted : March 7, 2013 1:55 am

lkeith

(@lkeith)

Posts: 457

Honorable Member

Topic starter

Thanks so much...will give it a try! Smile

Posted : March 7, 2013 2:04 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