Home Forums Discussions Problems Entering ICD-9 codes in 6.5

Just upgraded to 6.5 and now when I search for ICD-9 codes it's all screwed up. in 6.3 I could type in the code and it enter and it would populate it to the note, now with 6.5 I enter the code and it enter and it pulls up a good search box. I do a lot of osteopathic manipulation so almost all of my new patients get codes 739.0 through 739.9. I used to be able to enter them in a matter of seconds, now it takes me minutes because I have to move between the keyboard and the mouse. Anyway to get it back to the way it was?

I'm not quite sure what you mean by "pulls up a good search box."

Sometimes the descriptive names change. If you are used to typing 3-4 letters and it used to pop up, check to see whether the descriptions have changed. If that isn't the reason, probably time to call support

lol, I meant google search box, not good.

Ok, let me rephrase this. Is there a way in 6.5 to rapidly enter ICD9 codes. aka, type the code, hit enter and it go into the chart? This was possible before and now it's not that I know of.

Dear Scott,

If you type the code into the box to the left of the search button the list matching should populate below the search window. Click the right code to add it to the chart. I don't thing this has changed. You may not even have to open up the search window where you see the options for starts with, contains and Google.

I am happy to log in and see what is happening if you like. My email is Claire@amazingcharts.com.


Claire

Claire, in the past from the search window I could type the icd9 code in (say 739.2) and hit enter and it would enter into the chart. Now when I do that, it pulls up a google web browser box instead. Very annoying.

So now in 6.5 I have to type in the code, mouse up to it, click it, then click add to chart, then go back and click the search box again and repeat the whole thing over. so when I'm entering like 12 codes in a row, this takes forever. Big time waste.

Dear Scott,

Thank you for the update. Our development team has been able to recreate the problem in their test environment. They are working on changing this work flow back to the old way. You should see this restored in version 6.6.

Claire

SWEET!!!!!!

Oh my goodness. I just upgraded to the new version 8, and this problem came back!!!! AC fixed this in version 6.6 and now they broke it again in version 8! Claire, anyway to fix this again on the next release????