So, our ICD10 effort isn’t entirely going as planned. I suspect that is the case for nearly every complex health system.
We started our effort by surveying our key IT partners (vendors). The surveys asked a lot of question but the key information we wanted to ascertain was Which version of your application can we count on being ICD10 ready?
I believe the vendors were responding with the best knowledge they had at the time. But, their responses are proving to be incorrect. As we tested the supposed ICD10-ready versions of the applications we found bugs that had to be fixed. Many of these fixes are requiring a later version of the software. The unplanned upgrades are adding months and thousands of hours to our ICD10 plans.
While the ICD10 transition date is over a year away, I am feeling a lot of pressure. When we sequence the tasks that need to be completed we are running out of slack.
2 thoughts on “ICD-10 Nervousness”
Back in Idaho they (IDHW) started preparing for ICD 10 in 2011. Here in FL its a whole different story with some of the HMOs that think we don’t have to start our testing until the spring of 2014.
As a configuration analyst who maintains the benefits and MRDT tables I’m heads deep in my 3rd ICD 10 CM/PCS program (Started in 2009) I can only hope and cross my fingers that we move foward now before we find ourselves behind the eight ball.
Are you seeing the issues at initiation-points in the coding chain (e.g., Lab, Rad, EHR Documentation, EHR Orders, Pharmacy), mid-points (e.g., coding/abstracting, Computer Assisted Coding), in the core billing system(s), and/or in the revenue cycle bolt-on’s (e.g., claims scrubber, claims transmission)?
This makes integrated testing all the more critical but also more frequent which pulls critical user resources from their “day jobs” sooner than anticipated.