Skip to content Skip to navigation

ICD10: Ready! Set! Crawl...

March 17, 2011
by Pete Rivera
| Reprints
Still think ICD10 is not an IT project? Eventually it will be IT's to fix

For such a large initiative as ICD10 and 5010, the HIT buzz still seems to be focused on HIE and Meaningful Use. Maybe it’s the long lead times or the fact that it’s a “coding thing,” so why should IT drive it?

The ugly truth about ICD10 was revealed during a session at HIMSS “Implementing ICD10: Lessons Learned from Canada.” The productivity loss associated with coding and chart review was alarming. Workload increased since coders were now looking for more information and granularity. Average number of charts reviewed per hour dropped by 50% for day surgery and emergency room. All areas suffered a productivity loss that has yet to be recovered since 2002.

Now keep in mind that coding speed directly impacts Lag Days. This also will impact the quality (learning curve) of the coders, which impacts denials. The knock on your door will be from operations wondering what went wrong with your 5010 conversion that is causing such a large reimbursement delay. You can point to interface schemas, crosswalk tables and 5010 plans all you want, but the root ICD10 code will be the crux of the issue.

Still think ICD10 is not an IT project? Eventually it will be IT's to fix

Topics

Pete Rivera

Director Informatics, Hayes Management Consulting

Pete Rivera

@Gator_Pete

www.Hayesmanagement.com

 

 

 

 

 

 

 

...