Notifications
Clear all
Topic starter
I have a CPS12 test environment that I have changed the ICD10 implementation date to 10/1/2014. When I utilize the expanded search for problems (by clicking on the magnifying glass) the dropdown still defaults to ICD9 - I have to manually change this to ICD10. Is there a step I am missing in my setup to get this dropdown to default to ICD10? Thank you for any help.
Deb Durant
Director of EMR Systems
Posted : July 27, 2015 5:37 am
I believe GE stated that this would be fixed in SP10... Right...
This is taken from the ICD-10 community discussion on the service portal:
Hi, the best thing to do is move to Service Pack 10 where we will be removing the toggle where you have to select 9 or 10 and instead use a google like description search to find the problem in the chart module. At this time the ICD10 implementation date does not control this for you...in fact, it does nothing on the EMR side of the house. See here: EMR Enterprise Date Explained
Let me know if this addresses your question. Thank you for your engagement with our team! Amy Sebesta
Posted : July 27, 2015 6:15 am
While discussing with GE last week, there is a bug in this feature but I'm not sure if this problem IS the known bug. While they stated this would be fixed in SP10 they also said there was a script to correct. This is for CPS only, not EMR.
Posted : July 27, 2015 7:33 am
WHAT?!? What about those of us still on CPS 11? We can't upgrade to SP10. It's not just the drop down box either. I also have to check the box "Show Inactive Problems Codes", or no ICD10 codes will be returned for the search. Then when I try to link the new diagnosis to an order, I get "The Diagnosis ... is expired". Any screen that shows both ICD9 and 10 has the ICD9 in black and the ICD10 in light gray. It's as if ICD10 is not really activated at all. It makes me wonder which code will be pulled to the PM side when we do "Retrieve Charges", and which code will be sent in the HL7 message for lab orders.
Posted : September 18, 2015 6:32 am
WOW.....just wow!!!!!
Posted : October 22, 2015 7:49 am
I've heard that Service pack 10 didn't fix it like they intended and now you have to wait for SP11. Can anyone confirm or deny this?
Posted : October 22, 2015 7:58 am
