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.

« How is the health reform going to pan out? | Main | HIPAA 5010 transition – building a case for automation »

ICD 10 – dual processing issue

Provider contracts (among other things) are written using ICD and DRG codes. As a result of the increase in number of codes in ICD-10, a new set of DRG’s will have to be created – to take advantage of the increased granularity of information for payments. Eventually every provider and payer will move to contracts based on ICD-10 and related DRG codes. But the switch will not take place overnight. There will be a transition period, during which contracts will be gradually migrated to ICD-10 world. It is this period that will require dual storage and processing of data.

Let’s first look at the issue from a provider standpoint. Providers will start capturing the ICD-10 codes for clinical purposes on Nov 1st 2014. But in most likelihood, contracts would be on ICD-9 and so the charges will need to be submitted on ICD-9 based DRGs. Later, at some point in time, few contracts will be on ICD-9 and remaining on ICD-10 – the charges will need to be submitted on both code-sets during this period. To be able to submit the charges on both code-sets the providers will need the ability to capture and store both code-sets based on the payer that the claim needs to go to. At the point of service, capturing both codes for the same service might not be a big challenge.   

The problem is more severe on the payer side. Payers have no easy way of knowing the ICD-9 as well as ICD-10 codes for the same service. Payers will need to pay claims and send remittances on the codes they receive. They’ll need to pay claims based on a code-set that’s in the contract. Maintaining one set of adjudication rules wouldn’t work. Crosswalks wouldn’t work either, partly because crosswalks can’t guarantee 100% conversion. The other reason is that practically speaking, crosswalks can’t be used in every rule of the adjudication process. So, dual adjudication platforms will need to be maintained for the transition period.

Given these complexities, the dual processing issue is at the top of my list of challenges with the ICD-10 transition. Backward compatibility and historical data support requirements make the issue more convoluted. And now I’m beginning to wonder if the so called “neutral strategy” for ICD-10 transition is practically feasible at all.

TrackBack

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

Comments

Providers will start capturing ICD 10 from Nov 1st 2013.

http://www.icd10codingtraining.com

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