Healthcare // Analytics
Commentary
4/30/2012
08:50 AM
Paul Cerrato
Paul Cerrato
Commentary
Connect Directly
Twitter
RSS
E-Mail
50%
50%

So What Was Wrong With ICD-9?

As your IT team makes the transition to the ICD-10 medical coding system, doctors will insist that the older system worked just fine. Here's your comeback.

The Great ICD-10 Debate: Healthcare Coding Transforms
The Great ICD-10 Debate: Healthcare Coding Transforms
(click image for larger view and for slideshow)
We're admonished to avoid cliches and platitudes, but some contain too much wisdom to ignore. "Not seeing the forest for the trees" is one of the best.

As IT departments struggle to put the ICD-10 coding system in place in various health information systems, CIOs and chief medical information officers (CMIOs) should prepare for a barrage of complaints about all the extra work that clinicians will be required to do.

ICD-10, which stands for International Classification of Diseases, 10th Edition, contains the codes used to bill insurers for a variety of diagnoses and inpatient medical procedures. The currently used ICD-9 contains 13,000 diagnostic codes, while version 10--due to be implemented by October 1, 2014, if the feds don't change their minds again--has 68,000. ICD-9 has 11,000 procedure codes, compared with 87,000 in ICD-10. That sure sounds like a lot more work.

Critics of the new system complain that it's so granular it's almost laughable. According to a Wall Street Journal article, in an attempt to refine the billing process for patient injuries, there are now specific codes depending on whether the injury occurred in an opera house, in an art gallery, around a mobile home, even in a chicken coop. There are also codes to specify if the patient was hurt while sewing, ironing, playing a brass instrument, or knitting.

Clinicians scoff at such granularity. What difference does it make to Dr. Jones if he's treating a bump on the head that occurred while the patient was listening to Don Giovanni or viewing a Picasso painting? This gets back to the trees and forest analogy.

[ For additional insights on the ICD-10 debate, see our new slideshow The Great ICD-10 Debate: Healthcare Coding Transforms. ]

Clinicians' top priority has always been to treat individual patients--the trees. But as the role of medical informatics and data analytics grows, doctors must start thinking not just about the patients in front of them, but about the population as a whole--the forest.

Much of the granular data generated from ICD-10 can be analyzed and used to do population surveillance. It can help policymakers determine public health campaigns and detect epidemics before they get out of hand. And the new coding system will also provide a treasure trove of data for public health researchers as they try to understand patient behavior and attitudes about risk taking. So, yes, knowing where specific types of injuries occur on a farm, for example, has merit.

Of course, some physicians will object to the fact that they now have to not only provide care for their patients, but also take on this public health role. They can take some comfort in knowing their IT counterparts are in the same boat.

IT managers now must make major adjustments to a host of programs, despite the fact that their organizations aren't public health agencies. They must make sure their financial applications are ICD-10-compliant. Other applications must be able to extract these codes, moving them through the system so that providers will be reimbursed.

Still, the really scary part of ICD-10 implementation, according to George Brenckle, CIO for UMass Memorial is: "Does my clinical documentation have enough detail in it to support the appropriate coding?" In other words, are my doctors providing enough detail in the electronic health record (EHR) system to meet the demands of ICD-10? "Our clinicians are just not used to providing that level of detail in their notes," Brenckle says.

Obviously, there's lots of angst to go around as hospital and medical practices struggle with ICD-10. And stakeholders will likely debate the merits of the system for some time.

The 2012 InformationWeek Healthcare IT Priorities Survey finds that grabbing federal incentive dollars and meeting pay-for-performance mandates are the top issues facing IT execs. Find out more in the new, all-digital Time To Deliver issue of InformationWeek Healthcare. (Free registration required.)

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
justaskjul
50%
50%
justaskjul,
User Rank: Apprentice
5/4/2012 | 6:55:32 PM
re: So What Was Wrong With ICD-9?
My favorite new ICD10 codes are:
W58 Contact with crocodile or alligator
W58.0 Contact with alligator
W58.01 Bitten by alligator

W58.11 Bitten by crocodile,
W58.12 Struck by crocodile
W58.13 Crushed by crocodile

Really? I guess maybe these could be useful in Florida?
pbug
50%
50%
pbug,
User Rank: Strategist
5/29/2012 | 3:48:36 AM
re: So What Was Wrong With ICD-9?
9 was not granular enough, 10 takes it beyond absurdity, as justaskjul points out below. An example of 9 - 283.0, Autoimmune Hemolytic Anemia. There are several types - each treated very differently. Warm, Cold. Variations that work better with gamma globulin, or corticosteroids, or rituximab. Etc. And it would be a lot easier to match symptoms to treatments with better diagnostic codes, at least as a starting point. And when you look these up online, the different types often get mixed together, which can easily lead to poor choices by patients and doctors (who are not experts and are not in contact with experts). Better coding would help.
Big Love for Big Data? The Remedy for Healthcare Quality Improvements
Big Love for Big Data? The Remedy for Healthcare Quality Improvements
Healthcare data is nothing new, but yet, why do healthcare improvements from quantifiable data seem almost rare today? Healthcare administrators have a wealth of data accessible to them but aren't sure how much of that data is usable or even correct.
Register for InformationWeek Newsletters
White Papers
Current Issue
InformationWeek Tech Digest September 18, 2014
Enterprise social network success starts and ends with integration. Here's how to finally make collaboration click.
Flash Poll
Video
Slideshows
Twitter Feed
InformationWeek Radio
Archived InformationWeek Radio
The weekly wrap-up of the top stories from InformationWeek.com this week.
Sponsored Live Streaming Video
Everything You've Been Told About Mobility Is Wrong
Attend this video symposium with Sean Wisdom, Global Director of Mobility Solutions, and learn about how you can harness powerful new products to mobilize your business potential.