The Looming Problem in Healthcare EDI: ICD-10 and HIPAA 5010 migration

On Jan. 15, 2009 the United States Department of Health and Human Services released the final rules for the updated X12 Electronic Data Interchange (EDI) transaction definitions, version 005010 to be used in conjunction with HIPAA and completed by January 2013. At the same time, the International Classification of Diseases (ICD) standard has been bumped from ICD-9 to ICD-10 with a compliance date of October 2013. These aggressive compliance mandates, coupled with the close relationship between HIPAA transaction sets that can directly refer to ICD-9 or ICD-10 codes have health industry IT professionals scrambling. A huge fiscal burden has been placed on payers and providers as they look to redesign business processes and systems to handle hundreds of thousands of new codes at an estimated cost of more than $14 billion.

From the viewpoint of the people who use the data, there are many good reasons for this change. HIPAA 4010 and 5010 compliance has taught us a lot about who needs what data and when. However, the actual changes to the data format are more of the evolutionary and not revolutionary type.

The ICD-9 to ICD-10 change is truly a radical step:

  • It’s been 30 years since the ICD-9 list was first developed. ICD-9 is embedded much deeper into systems. The 36 years from 1977 to 2013 means that a junior programmer who wrote ICD-9-related code at the start of his career is probably now the CTO facing the consequences of a change he never planned for.
  • The list for ICD-10 is far more detailed, at almost 10× the length. The numbering system has changed, the number of diagnostic codes increased, individual codes are more detailed.
  • There are generally no 1:1 mappings between ICD-9 and ICD-10. Although some codes in the old classification map directly to codes in the new, most don’t. Sometimes there are a series of codes, sometimes there are alternatives that will take external information to choose from, and sometimes there are no direct alternatives.

There are several challenges for those working with these standards, and since the “HI” segment of several HIPAA transaction sets can directly refer to ICD-9 or ICD-10 codes, these problems actually intersect. How can we account for the changes when data has been moved, or where new data must be extracted from other sources to augment the existing feed?

The hardest part about writing a book is that first sentence. It is similar with data conversion projects. When there is so much to convert, where do you begin? Transforming data in HIPAA 4010 X12 files and translating ICD-9 codes has been covered by blogs like XML Connections. Now, software developers and architects can consult the HIPAA/ICD Upgrade Toolkit, created by the XML and data integration experts at Progress DataDirect. The kit includes the following information:

  • XQuery source for upgrading each of the 10 transaction sets from the 4010 version to the equivalent 5010 version
  • 50 sample 4010 files to use with the above
  • The ICD-9 to ICD-10 maps
  • A sample tool to compare the changes between ICD-9 codes and their closest ICD-10 analogs, with HTML output
  • An XQuery program which will read a HIPAA file containing ICD-9 codes and report on any potential conversion troubles with ICD-10
  • An XQuery program to read a HIPAA EDI file, and convert it from 4010 to 5010 and from ICD-9 to ICD-10 simultaneously

What does XQuery have to do with HIPAA? Well, EDI to XML converter technologies make EDI behave like XML. And XQuery is really good at augmenting, splitting and rearranging XML. The two together let a relatively small XQuery program do big things. The XQuery programs including in the HIPAA/ICD Upgrade Toolkit are sufficient to convert all of the samples that come with the 4010 documentation into valid 5010 files.

Your mileage may vary, but the examples available in the HIPAA/ICD Upgrade Toolkit provide a good starting point. No doubt your specific application will need some tweaking, but isn’t it a whole lot easier to change a working program than to start from scratch?

Newsletter Sign Up


7 thoughts on “The Looming Problem in Healthcare EDI: ICD-10 and HIPAA 5010 migration

  1. Hello Shahid,
    I am enjoying your blog a lot, thank you!
    I am a computer scientist who just started getting acquaintance with Health IT. I have been in the Healthcare industry since 2005, so I am learning and processing as I go, and noticing for example, that many computer science standards are not applied in the Health IT industry, can’t understand why. For example, computer science processes demand a flow chart of some sort. I see many explanations of systems processes, lacking one.
    Maybe it’s pointing to the need of more Computer Scientist to look into it!? 😉

    Now, since HIPAA is intended to save billions of dollars by simplifying the complex process of claims administration and payment through a single standard for healthcare transactions. I wonder who is tracking those savings? Also what is the cost of a transition to full HIPAA compliance and full business process integration?
    I also see a tremendous challenge to integrate hardware, software, services, support and training
    for healthcare organizations with high-performance computing requirements.
    Where are the standards for these challenges? who is drafting them? Any success stories you can share with us?
    Cheers!
    Luigi

  2. a good post, I see a tremendous challenge to integrate hardware, software, services, support and training
    for healthcare organizations with high-performance computing requirements.

  3. Pingback: Health Wonk Review: Killer viruses and the undead public option « Boston Health News

  4. Having worked many years in data conversion, the efforts required to convert the volumes of existing health record data is jaw dropping. However, that will be significantly overshadowed by the need for validation of the data once it has been converted. More than once have I seen remnants of incorrectly converted data long after the conversion activities have supposedly been completed. With the age and lack of standardization of some of the systems, I perceive this effort as quite a challenge.

  5. The Edifecs 5010™ Migration Solution is an integrated set of products, services and resources designed to help you successfully upgrade your organizational infrastructure to meet the new HIPAA 5010 requirements. The Edifecs5010™ Migration Solution leverages our vast client-focused expertise and deep industry experience for improved systems development, claims management & transaction visibility. More on Edifecs – 5010 Migration

  6. The Edifecs 5010™ Migration Solution is an integrated set of products, services and resources designed to help you successfully upgrade your organizational infrastructure to meet the new HIPAA 5010 requirements. The Edifecs5010™ Migration Solution leverages our vast client-focused expertise and deep industry experience for improved systems development, claims management & transaction visibility. More on Edifecs – 5010 Migration

  7. Hi Shahid

    , this article is super! 
    It clearly identifies and outlines the realities of the upcoming EDI
    / ICD-10 / HIPAA 4010 to 5010 conversion challenges. I work with
    a U.S. based strategic services company (headquartered in NY and
    with operations in India).  At the moment we are working
    with over 20 payer/provider companies, most of which we have
    already successfully converted them to 5010.  Even with our
    10+ years of experience in the healthcare back office space, I’ve
    seen that with each conversion that new lessons are learned by our
    team on client specific peculiarities…and our process is now well
    matured. However, as time is growing short I think we are all
    starting to see more and more companies literally rushing now to
    ensure that they are ready to start submitting their claims
    electronically using the X12 Version 5010 and NCPDP Version D.0
    standards by the January 1st 2012 deadline.  We’ll keep
    checking back to see if you have any updates and suggestions for the
    industry.  Cheers, Angela Carson, Head of Communication at Vee
    Technologies 

     

Add Comment