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 Help to Auto Add Hypertension to Problem list

MEL, SQL, Oracle

Last Post by Anonymous 1 second ago

8 Posts

5 Users

0 Reactions

84 Views

RSS

akoen

(@akoen)

Posts: 144

Estimable Member

Topic starter

Below is MEL language we have been using for some time to automatically add hypertension or diabetes to a patient’s problem list if the either problem is in the patients past medical history:

{if match(obsany("PAST MED HX"), "Hypertension")>0 and

match(PROB_AFTER("LIST"), "ICD-401.1")==0 then MEL_ADD_PROBLEM("hx of", "Hypertension", "ICD-401.1", str(._TODAYSDATE),"","")

else "" endif}

{if match(obsany("PAST MED HX"), "Diabetes")>0 and

match(PROB_AFTER("LIST"), "ICD-250.00")==0 then MEL_ADD_PROBLEM("hx of", "Diabetes", "ICD-250.00", str(._TODAYSDATE),"","")

else "" endif}

Today, for some reason, both problems are being added to the problem list multiple times during the visit. It appears the diagnosis is being added each time the Office Visit is opened.

Not sure why this started happening out of the blue 🙁 Any thoughts?

Posted : October 21, 2015 1:14 pm

ErnieT

(@erniet)

Posts: 479

Honorable Member

Have you tried to change your match functions to the ICD10 code? That may be the issue.

Posted : October 22, 2015 6:12 am

akoen

(@akoen)

Posts: 144

Estimable Member

Topic starter

I did try changing the codes to an ICD10 code (that was my first thought) but still had the same issue. Do you know do we still use ICD- in front of the ICD10 codes?

Posted : October 22, 2015 7:04 am

blackmanb

(@blackmanb)

Posts: 268

Reputable Member

ICD-250.00 = Diabetes mellitus without mention of complication, type II or unspecified type, not stated as uncontrolled

ICD10-E11.9 = Type 2 diabetes mellitus without complications

Try adding both codes in your mel_add_problem, see if that helps

MEL_ADD_PROBLEM("hx of", "Diabetes", "ICD-250.00|ICD10-E11.9", str(._TODAYSDATE),"","")

Posted : October 22, 2015 8:25 am

ken.takenaka

(@ken-takenaka)

Posts: 212

Reputable Member

I think the issue might be your usage of Prob_after. Is this only happening when the clinical list changes are not signed when exiting the document?

Posted : October 27, 2015 8:21 am

ken.takenaka

(@ken-takenaka)

Posts: 212

Reputable Member

you would use ICD10-xxx.xxxx instead of ICD-xxx.xx

Posted : October 27, 2015 8:22 am

DavidShower

(@davidshower)

Posts: 1255

Noble Member

We have seen some similar things that result from some MEL functions evaluating to NULL when you enter or bring a document off hold. Look at your trace and see if that is what is happening. We are trying to figure out how to get around this.

Posted : November 17, 2015 7:45 am

akoen

(@akoen)

Posts: 144

Estimable Member

Topic starter

David,

We worked with another office and added the code below to the form.

{

! if (formStarted<>"" and obsany("PAST MED HX")<>"") then

if match(obsany("PAST MED HX"), "Hypertension")>0 and

match(PROB_AFTER("LIST"), "ICD-401.1")==0 then MEL_ADD_PROBLEM("hx of", "Hypertension", "ICD-401.1", str(._TODAYSDATE),"","")

else "" endif

if match(obsany("PAST MED HX"), "Diabetes")>0 and

match(PROB_AFTER("LIST"), "ICD-250.00")==0 then MEL_ADD_PROBLEM("hx of", "Diabetes", "ICD-250.00", str(._TODAYSDATE),"","")

else "" endif

if match(obsnow("SMOK ADVICE"), "yes")>0 and

match(PROB_AFTER("LIST"), "ICD-305.1")==0 then MEL_ADD_PROBLEM("dx of", "Disorder, tobacco use", "ICD-305.1", str(._TODAYSDATE),"","")

else "" endif

if val(OBSNOW("BMI"))>= "40" and

match(PROB_AFTER("LIST"), "ICD-278.01")==0 then MEL_ADD_PROBLEM("dx of", "Morbid obesity", "ICD-278.01", str(._TODAYSDATE),"","")

else "" endif

if match(obsany("PAST MED HX"), "HIV")>0 and

match(PROB_AFTER("LIST"), "ICD-042")==0 then MEL_ADD_PROBLEM("dx of", "Human immunodeficiency virus [HIV]", "ICD-042", str(._TODAYSDATE),"","")

else "" endif

if match(obsany("PAST MED HX"), "Hepatitis C")>0 and

match(PROB_AFTER("LIST"), "ICD-070.51")==0 then MEL_ADD_PROBLEM("dx of", "Hepatitis C, acute", "ICD-070.51", str(._TODAYSDATE),"","")

else "" endif

else

endif

}

We also added a visibility region within the form using the code:

false

Within that visibility form, we posted a date display with a MEL Expression of:

formStarted="COMPLETE"

That solved our issue! Magic Mike strikes again!!! 🙂

Posted : November 17, 2015 9:35 am

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