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 remove problem WITHOUT PRID for a button to remove a particular problem

MEL, SQL, Oracle

Last Post by Anonymous 1 second ago

9 Posts

2 Users

0 Reactions

105 Views

RSS

Scott Forest

(@sforest)

Posts: 527

Honorable Member

Topic starter

I am trying to build a button that will resolve one particular problem, the issue with using the MEL_REMOVE_PROBLEM is that it requires the use of the PRID, it wouldn't be so bad IF the PRID didn't change every time it was added, however it does so I can't use it. Any other solution?

Posted : September 21, 2016 3:47 am

gibsonmi

(@gibsonmi)

Posts: 827

Prominent Member

We use that function successfully. I loop through PROB_AFTER() to find the PRID for a problem matching in description and ICD10 code and then pass it mel_remove.

Posted : September 21, 2016 4:05 am

Scott Forest

(@sforest)

Posts: 527

Honorable Member

Topic starter

That's probably a bit more programming than I know, can you share anything to try?

Posted : September 21, 2016 4:16 am

gibsonmi

(@gibsonmi)

Posts: 827

Prominent Member

Basic example where name is passed as the description of the problem and the reason is passed as a valid reason for removing problems (See reason list for removing problems in the GUI)

{fn Remove_Problem(name,reason){


	local hold = getfield(prob_after("delimited"),"|","")

	local temp
	for i = 1, i 0 then

			return MEL_Remove_Problem(temp[9],str(._todaysdate),false,reason)

		endif

	endfor

return rslt } }

Posted : September 21, 2016 4:35 am

Scott Forest

(@sforest)

Posts: 527

Honorable Member

Topic starter

yea, see, I would never have known. I don't get the "for i = 1, i 0" part, where does that come from? Mind you the last time I programmed was C++ in high school and I'll be damned if I can remember any of that from nearly 20 years ago.

Posted : September 21, 2016 5:07 am

gibsonmi

(@gibsonmi)

Posts: 827

Prominent Member

No idea.. It should say this, when I try to edit the post it still doesn't save right -

for i = 1, i <= size(hold), i = i + 1 do

temp = getfield(hold[i],"^","")

if match(toupper(name),toupper(temp[2]))>0 then
return MEL_Remove_Problem(temp[9],str(._todaysdate),false,reason)
endif
endfor

Posted : September 21, 2016 5:34 am

Scott Forest

(@sforest)

Posts: 527

Honorable Member

Topic starter

could I write this?

{
!if OBSNOW("PREGNANT") == "No"
THEN
Remove_Problem("Pregnant State, incidental", resolved)
local hold = getfield(prob_after("delimited"),"|","")
local temp
for i = 1, i <= size(hold), i = i + 1 do
temp = getfield(hold[i],"^","")
if match(toupper(name),toupper(temp[2]))>0 then
return MEL_Remove_Problem(temp[9],str(._todaysdate),false, resolved)
endif
endfor
return rslt
}

Posted : September 21, 2016 6:04 am

gibsonmi

(@gibsonmi)

Posts: 827

Prominent Member

{ !if OBSNOW("PREGNANT") == "No" and match(PROB_AFTER("delimited"),"Pregnant State, incidental")>0 THEN

Remove_Problem("Pregnant State, incidental", "resolved")

else "" endif}

{!fn Remove_Problem(name,reason){

local hold = getfield(prob_after("delimited"),"|","")

local temp

for i = 1, i <= size(hold), i = i + 1 do

temp = getfield(hold[i],"^","")

if match(toupper(name),toupper(temp[2]))>0 then

return MEL_Remove_Problem(temp[9],str(._todaysdate),false, resolved)

endif

endfor

return rslt }}

Posted : September 21, 2016 8:39 am

Scott Forest

(@sforest)

Posts: 527

Honorable Member

Topic starter

Michael,

thank you so very much, this was extremely helpful. I need to use this for several different items. I appreciate your time. Programming this was/is still way over my head at this point.

Posted : September 21, 2016 9:22 am

Share:

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