Today is going to be the last day looking at other people’s “Top Health IT Lists” since tomorrow I think I’ll create my own Top 10 Health IT 2011 List and then for the New Years I’ll see about doing a Top 10 Health IT in 2012 list. However, today let’s look at something that will likely make the Top 10 2012 Health IT issues: ICD-10. Government Health IT recently wrote an article what they call the Top 5 ICD-10 Pitfalls.

1. Reporting: I’m sure that many think that ICD-10 is just going to happen and be fine. They’ll assume that their reports are just going to work with ICD-10 since they worked with ICD-9. Don’t be so sure. Test the reports so you know one way or another. Diving a little deeper beforehand is a lot better than learning about the problems after.

2. Overlooking impacted areas: Much like an EHR implementation, don’t forget the other people that are affected by ICD-10. Involve everyone in the process so that they can share their concerns so they can be addressed. Plus, by having them involved you’ll get much better buy in from the staff.

3. Teaching old dogs new tricks: ICD-10 is a different beast and will require significant training even if you have an expert ICD-9 coder with years of experience. Don’t underestimate the cost to train your coders on ICD-10.

4. Preparing for impact on productivity: The article mentions Canada’s loss of productivity during their implementation of ICD-10. Do we think we’re going to be any different? Remember also that productivity loss can come in a lot of different places (which is kind of a repeat of number 2 above).

5. Communicating with IT vendors: It’s one thing to trust that your EHR and other health IT vendors are prepared to deal with ICD-10. It’s another to blindly follow whatever you’re being told. Remember at the end of the day it’s your organization that will suffer if your health IT vendor is not ready. I like to use the phrase, trust but verify.

Be sure to read the rest of my Health IT Top 10 as they’re posted.

Next up in our evaluation of the various end of 2011 Health IT lists series is one that takes a bit of a look back at 2011. In this list, PwC lists what they consider the Top Health Industry Issues of 2011. The list starts with an interesting comment about the health IT spending in 2011:

More than $88.6 billion was spent by providers in 2010 on developing and implementing electronic health records (EHRs), health information exchanges (HIEs) and other initiatives. This surge is a sign of technology’s critical place in health system improvement.

$88.6 billion is a lot of health IT spending and larger than most numbers I’ve seen. Although, most numbers I’ve seen are only the EMR and EHR market and doesn’t include HIE spending and other healthcare IT initiatives. It’s quite clear that the health IT spending is up, and up Big!

Their list of top Health issues isn’t that surprising, except possibly one of them:

Meaningful Use – This has to be topic number one for health IT in 2011. It’s had a trans formative effect on healthcare IT and EMR and EHR as we know them. Pretty much every EHR vendor I’ve talked to basically had to take an entire software development life cycle to meet the meaningful use and certified EHR requirements. This is the dramatic effect of meaningful use on EHR development.

PwC actually focuses on how meaningful use will encourage patient participation in their healthcare or “shared medical decision-making.” To be honest, I’m not sure meaningful use has done much to help this goal, yet(?). Possibly meaningful use stage 2 and meaningful use stage 3 will help to further these goals. MU stage 1 has done little to encourage this. Regardless of the impact of meaningful use, shared medical decision-making is going forward fast and furious.

HIPAA 5010 and ICD-10 – The interesting issue for 5010 and ICD-10 is that they’ve basically been overwhelmed by meaningful use and EHR incentive money. Either of these changes alone would have been a reasonable challenge for a normal year. However, clinical organizations are battling through 5010, ICD-10 and meaningful use all at the same time. Are there any other IT projects going on that don’t involved these three things? I’d say probably very few.

Electronic medical device reporting (eMDR) – I found this point quite interesting. There’s been a lot of movement in 2011 in regards to what constitutes a medical device and who should take care of tracking and collecting the adverse events that occur on these devices. I don’t think we’ve come to a final conclusion on what will be considered a medical device and how we’re going to deal with reporting adverse events, but finally getting electronic reporting of adverse events is a good step in the right direction.

Be sure to read the rest of my Health IT Top 10 as they’re posted.

The Wall Street Journal put out an interesting article about the switch from ICD-9 coding to ICD-10. The title mocks the ICD-10 codes, Walked Into a Lamppost? Hurt While Crocheting? Help Is on the Way”, and the subtitle is funny as well, “New Medical-Billing System Provides Precision; Nine Codes for Macaw Mishaps”

I must admit that I’m not very well steeped in the history of ICD-9 and ICD-10. Nor am I that familiar with the process that was used for creating the voluminous ICD-10 coding system. I’m more of a practical person and so I’ve been more interested in EHR’s ICD-10 preparedness and the timeline for ICD-10 implementation. Seems like we won’t have much choice.

I guess I should have known that going from 18,000 codes (which doctors can’t even stay up with as is) to 140,000 codes would offer some crazy and hilarious codes. Here’s some examples from the article linked above:

There are codes for injuries in opera houses, art galleries, squash courts and nine locations in and around a mobile home, from the bathroom to the bedroom.

And the appropriate follow up question from a family physician, “Really? Bathroom versus bedroom? What difference does it make?”

Some other interesting codes mentioned in the article:
R46.1 is “bizarre personal appearance”
R46.0 is “very low level of personal hygiene”
W22.02XA, “walked into lamppost, initial encounter
W22.02XD, “walked into lamppost, subsequent encounter”
V91.07XA, “burn due to water-skis on fire”

There are codes for injuries received while sewing, ironing, playing a brass instrument, crocheting, doing handcrafts, or knitting—but not while shopping. There are codes for injuries from birds such as: a duck, macaw, parrot, goose, turkey or chicken. I’d hate for my doctor to choose the “bitten by turtle” versus “struck by turtle” code. My insurance company might not reimburse the second.

Do people know of any other off the wall ICD-10 codes?

While this has me a little concerned to see ICD-10 in action, hopefully it will give all of you a good laugh going into the weekend. I can’t say I saw a code for any sort of Friday inefficiency, but there probably should be.

Chuck Podesta is Fletcher Allen Health Care’s chief information officer.

ICD-10 would not be so daunting if the deadline was not occurring during the rush to get EHRs for meaningful use. Add in value-based purchasing, bundled payments and transitioning to ACOs, and you can see why many CIOs are retiring early or migrating to the vendor or consulting world. We are just over two years away from the October 2013 deadline, and there is much work to be done. ICD-10 contains 68,000 codes, as opposed to the 13,000 currently used in the ICD-9 world. There is a code for every condition that exists on the planet.

The revenue cycle system, which includes registration, HIM and billing/AR, will be the lynch pin to ICD-10 readiness. Having a solid vendor partner and a strong product is key to a successful transition. Many solution providers – like GE Healthcare, who recently launched the 5.0 version of their Centricity Business product – are updating their systems to better comply with ICD-10. GE Healthcare also allows existing Centricity Business customers to retrofit the new ICD-10 functions to the 4.6 version of the product. Strong vendor partners take the burden off you by being ahead of the game and delivering the appropriate technology in time so you are not racing to the finish line.

By now, you should have at least a steering committee in place. Your IT shop should have completed an inventory of all applications that are impacted by ICD-10, including reporting systems. You will be surprised by the number of applications, even if you have taken the one-vendor approach for most of your IT needs. You will need to contact all affected application vendors to see what the plans are for ICD-10 compliance. Most likely, upgrades will be required that will need to be scheduled.

Training of coders will be critical, along with implementing clinical documentation improvement programs. Documentation improvement programs are difficult to implement and will be viewed by providers as more work on top of an already busy schedule. New technologies such as computer-assisted coding will definitely help, but success will be a combination of process improvements and technology.

Lastly, remember that the deadline is for Medicare and Medicaid patients only. Unless the rest of the payer industry follows the same deadline (highly unlikely), you will need to run both ICD-9 and ICD-10 systems.