ICD10 from the Front-Lines: Day #1

Today is the first day we are forced to use the ICD10 coding system. It rolled out and we are now learning some of the deficiencies on the system in real-time as we treat patients. I do not know how other practices are being affected because I am knee-deep in my own ICD10 quagmire.

What went wrong with ICD10 Day #1?

1. Navi-net has been down for a portion of the day. This is the site that we use to do many referrals and check eligibility for some patients. It is an important tool in our practice and now unavailable.

2. We are not able to do on-line referrals for some patients. The payers on-line referral site is not accepting ICD10 codes. Yet, if we revert back to ICD9, those referrals will not be approved. This is a big tech deficiency in the system that is particularly hard for primary care physicians.

3. Payers may be IT ready for ICD10 but their personnel not so much. For one thing, we cannot get through to them because of the large call volume. When we do get through, the staff on the phone cannot give us clear or accurate answers. My biller called about a previously denied claim and was told that she needs to resubmit it using an ICD10 code. This is completely wrong because ICD10 does not apply to patients seen before the date of service of October 1, 2015. Those patients still fit under the ICD9 codes.

4. “Just submit it and we will see” is the most common answer we are hearing today. This is an unacceptable answer. I do not “wait and see” if I will get paid before seeing a patient. The payers should train their employees to be aware of ICD10 and how to answer questions. Doctors’ livelihoods depend on it.

As Day #1 winds down, I am sure these glitches will be resolved and we will see more order on subsequent days. And we shall truly see what happens because there are no guarantees. Anyone else seeing any ICD10 problems?

Digiprove sealCopyright secured by Digiprove © 2015 Linda Girgis, MD, FAAFP

Related Posts

Please add your voice to the discussion

%d bloggers like this: