Notifications
Clear all
Topic starter
We are experiencing an error "Obsolete Diagnosis" when providers select a Diagnosis from the Smart List and then place a Lab Order. We are noticing that certain Diagnosis' in the Smart List are greyed out, for example, Gouty Arthropathy and we believe this is the reason. Is anyone else experiencing this? Does anyone have an SR open?
Posted : March 24, 2015 7:27 am
Have you applied the monthly/quarterly updates for ICD-9's? I am assuming that in the absence of running these updates, these obsoleted diagnoses would still be available to be selected even though they are obsoleted.
Posted : March 24, 2015 8:34 pm
We are experiencing the same thing. The "Smart List" will capture and keep a diagnosis after 3 search attempts for it. Even if inactive/obsolete. I did open a ticket with GE to confirm this and was told there is not a way to get this removed from the Users "Smart List" once it is on. As all users "Smart List" differs based on their search of diagnosis codes, not everyone will have the inactive/obsolete code which is good in a way, just not helpful for those who have a bad one already displaying.
Hope this helps!
Posted : March 25, 2015 2:05 am
Currently there is no way to remove and inactive/outdated code from the smart list. It has been an enhancement request from many since going live on 9.8 The smart list initially was the same for everyone and was taken from the previous years most orderd and did include some outdated problems at that time. As user add to their "personalized" list it learns their preferences. We do not allow uncoded problems to be added, so I now our users aren't adding these to their smart list.
Posted : March 25, 2015 2:27 am
We're having an issue only with two providers where they are getting an obsolete dx notification, except the codes are not obsolete. The two codes in question are v06.1 and v70.0. The warning even pops up if the users grab the problem from the reference list instead of their smart list.
GE can't even figure out what is going on. Has anyone else seen this issue?
Posted : June 2, 2015 8:07 am
I have seen this same issue, esp since preloading ICD10's, even though there is an icd9 cross walked and our date isn't until oct 1 to use the icd10.... opened a SR and have yet to get a resolution on it.
Posted : September 30, 2015 8:16 am
