At Infosys, our Insurance, Healthcare and Life Sciences teams strive for holistic, better and safer healthcare through the technology we create. In this blog, we will discuss healthcare IT, obstacles, successes, new ideas and much more, with the aim of improving healthcare technology, and quality of life as a result.

« Analytics for Accountable Care Organizations | Main | ICD-10 - is there sufficient time for integration? »

Think..... Before you Crosswalk...

While the Payer industry is maturing with their knowledge of ICD-10 & crosswalks, there is no new surprise that most of them have realized that CMS GEMs are not magic bullets and aren't the only solution for their ICD-10 Crosswalk. With thorough analysis, the industry today has found the backward GEMs to be less challenging (with almost 75% 1:1 mapping relationship) over the forward. Many of the payers have therefore decided to go for it with a mindset to override rest of the backward GEMs complexities with creation of simplified custom map/maps. But, let's be honest in understanding that any crosswalks/custom map is not going to be 100% reliable. A crosswalk is not all about mapping a set of source code to its targets. It's a meaningful and logical translation of one code set to other by keeping the underlying concept of the codes all the same in the course. In the exercise of mapping, there is potential risk that information can either be completely lost or will get added by an assumption about the condition or care provided that may or may not be true. Validation of code set translation will be based on skilled human judgment and will hugely require significant modeling and testing to ensure financial and clinical transparency.

Understanding the gravity of the associated risk as per me, payers should start their crosswalk solutioning with definition of High Level Requirements and the business need assessment. Understanding that forward crosswalk is challenging simple adoption of backward crosswalk will not mitigate the problem. Scenarios in backward map where more than one ICD-9 code is required to translate the ICD-10 code, determine if a 1:1 mapping is possible or to analyze the ICD-10 codes that do not have an ICD-9 map or even decide if a suitable ICD-9 alternative is available will always be a daunting task to accomplish. Above and all to reduce the substantial financial risk out of crosswalk there is an inherent need to identify DRG variations between original and mapped data. Pointing out areas where a more detailed analysis of the CMS maps is required and/or if an alternative map is required is also not that easy. The criticality will further lie in ensuring that the new ICD-10 mappings does not affect their existing benefit policy, pricing, care management or reimbursements to providers.

Honestly, significant work is left to the payer to analyze and determine how best to map the ICD-10 codes with the precursors to reach financial neutrality and clinical equivalency. Payer organization better answer the following before they decide to crosswalk, irrespective of the mapping direction they opt -
• Where in the business process is the need to go to find the ICD-10 equivalent for frequently used ICD-9 codes?
• How best can the GEMs be used and in what different business scenarios?
• What direction of GEMs (forward, backward or reimbursement) serves the transition goal?
• Will an enterprise level map serve the purpose? Or there is need of different maps across the functional areas?
A successful crosswalk implementation will invariably depend on right planning, assessment and analysis. Crosswalk though an intermittent solution, can cause some real catastrophe by defeating the purpose of the transition to ICD-10 which is more specific, accurate and complete to provide improved, effective and efficient healthcare. I would therefore suggest to take the time to do the hard work now instead of paying later!

 

TrackBack

TrackBack URL for this entry:
http://www.infosysblogs.com/apps/mt-tb.cgi/4144

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

Please key in the two words you see in the box to validate your identity as an authentic user and reduce spam.

Subscribe to this blog's feed

Follow us on

Blogger Profiles

Infosys on Twitter