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

VFE Mel Add Prob ICD 10 issue

CPS, C-EMR, PM

Last Post by Anonymous 1 second ago

9 Posts

6 Users

0 Reactions

79 Views

RSS

hbias

(@hbias)

Posts: 83

Estimable Member

Topic starter

I am trying to make a few easy buttons for ICD 10 and have run into an issue. Currently I have button to add hypertension and diabetes. When it is pushed in the problem list it shows both ICD9 and ICD 10. But if I update the button to add the ICD 10, it only shows the ICD 10 and doesn't map back to ICD 9. I have checked and the ICD10 codes are back mapped to the ICD9 codes. Anyone have any ideas? I want to always have both codes when at all possible.

just when I think I am getting to the bottom of my to do list 🙂

Hilary

Posted : September 20, 2015 10:42 am

gibsonmi

(@gibsonmi)

Posts: 827

Prominent Member

From the help -

Optional. ICD-9 code for the problem. If no ICD-9 code is present, the problem is added as uncoded. See the Comment below for more details.

ICD-9 codes should be formatted as "ICD-XXX" and ICD-10 codes should be formatted as "ICD10-XXX". If you provide the ICD-9 code and the system has a unique ICD-10 code that it can map to, the ICD-10 code will be provided automatically

Two codes can be specified by separating them by a pipe ‘|’ character, "ICD-XXX|ICD10-XXX". If this is used the second parameter must be an ICD10 code. The first parameter can be an ICD9, ICD10 or custom code.

It doesn't say it will back map 10 to 9, only 9 to ten. I always add both codes with the pipe like the bolded string above, never had a problem with the add_problem using that method.

Posted : September 21, 2015 3:05 am

blackmanb

(@blackmanb)

Posts: 268

Reputable Member

Question, when you do your ADD_PROBLEM using icd9|icd10, which problem description do you use ? Icd-10 problem description ? - B

Posted : September 21, 2015 7:59 am

gibsonmi

(@gibsonmi)

Posts: 827

Prominent Member

I use the ICD10 description, in almost all cases it has more specificity and therefore better represents both codes.

Posted : September 21, 2015 8:14 am

Lee

(@lee-cooper)

Posts: 348

Reputable Member

When adding a problem, you can specify both the ICD9 and ICD10 codes.

Unfortunately, when the MEL_CHANGE_PROBLEM data symbol was coded, it was coded so that only one ICD code could be specified. This presents an obvious issue knowing what we know now (that both 9 and 1o codes are needed for the foreseeable future).

The trick is to change the problem using the 10 code and all the arguments desired. You then execute a second change statement with only the PRID and 9 code. This will make the change you want and keep both codes.

I would suggest everyone report the data symbol as a defect and get them to accept a pipe delimited string instead of placing the burden of the change process on the user layer of MEL.

If you do not want to code 2 change statements, understand that the only other option will be to remove and add again (where both codes can be specified). While 'cleaner' in theory, it is not because a remove entry will be added to the problem list and when the problem history is reviewed, it will have needless 'removed' entries in it.

The above applies to Change too, which is why I strongly suggest that users report it as a defect in an effort to avoid needless clutter in the problems table (which could adversely affect performance down the road).

Posted : September 21, 2015 10:12 am

gibsonmi

(@gibsonmi)

Posts: 827

Prominent Member

@Lee I noticed that too and use the same workaround. Do you have an SPR for it? We are CPS 12.0.10

Posted : September 21, 2015 10:29 am

hbias

(@hbias)

Posts: 83

Estimable Member

Topic starter

Thank you for the help! The | was the answer

Posted : September 21, 2015 11:39 am

JenWagaman

(@jenwagaman)

Posts: 74

Trusted Member

We've had a case open with GE for a couple weeks now about this. SR 1-720571965.

Posted : September 22, 2015 8:55 am

dubsterne

(@dubsterne)

Posts: 55

Trusted Member

When we were working on this issue, this is information that I found really helpful:

The problem with the ICD-9 vs. ICD-10 here is the position number used within the function. ICD-9 codes are in position 3 of the PROB_AFTER(“delimited”) array, ICD-10 codes are new and are in position 8.

So, everywhere your function refers to GETPROB[3], you just need to change it to GETPROB[8]. If you want either/or, then you would need to check for both using a conditional expression.

You may also want to check any other functions in the form that use the 3rd array position of any of the PROB data symbols and update those as well. Also, all of the ORDERS data symbols now have the ICD-10 in position 26 of the array, while ICD-9 remains in the 7th position, so you might want

Posted : August 30, 2016 8:36 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