Tuesday, September 28, 2010

Make Smooth Transition from ICD 9 to ICD 10

Having issue while upgrade medical coding from ICD 9 to ICD 10. Use ICD 10 Bridge tool make smooth transition.
ICD 9 to ICD 10, ICD-10 bridge, ICD-9 codes, ICD 10 codes

2013 is still to come, but it's certainly not too early to start your ICD-10 preparations. Here are three things to keep in mind while making the change from ICD 9 to ICD 10.
Do not stall preparation as you expect a delay
Today isn't too early to gear up for the ICD 9 to ICD 10 transition. The more familiar you are with the changes, the easier the transition will be. You shouln't begin your intensive, in-depth ICD-10 training until six to nine months before implementation, but you can gear up in other ways now.

Get your physicians ready now

Presently, CMS publishes about 14,000 ICD-9 codes, however there'll be over 69,000 ICD-10 codes. These codes will make it possible for you to provide greater detail in describing diagnoses and procedures. As because ICD 10 codes will often be more detailed and specific than the ICD-9 codes you and your ophthalmologist are used to, you may need to encourage your doctor to begin being more detailed in his documentation.

Begin by speaking with your physicians now about improving their clinical documentation detail which will be the most important aspect for them and should be started before the change.

Reach out to vendors to ensure readiness

You should be involved when practices communicate with information system vendors about their plans for the new code set implementation.

You will need to work with your software vendors before time to confirm that no issues will exist with claims submissions using ICD-10. First you should check whether your vendors are ready for the transition to the new 5010 form, which is making way for the ICD-10 code set.

For more tips on ways to make the ICD 9 to ICD 10 transition, sign up for a one-stop medical coding update. Such a site comes stocked with an ICD-10 bridge to make the transition much easier!

No comments:

Post a Comment