No report here in the Fora of a converter within OE thus far.
This webpage is the closest we have to a mechanism for mapping.
For most practices, only about 10 to 20 diagnosis codes are used on a daily basis; therefore it is unnecessary & time poorly spent to map all ICD-9 codes to ICD-10.
For example, we’ve never had the occasion to use this code, with or without eye involvement, in many decades of practice.
It would be more efficient to convert a cheat sheet worth of codes, be done with it, rather than having to repeat the conversion each time the Fee Sheet is used.
Hello fsgl
Yes as you said, for a specialized clinic, they may use 10 - 20 codes on a daily basis. But when considering a general clinic, where it serves lot of specialities, they may need a wide range of codes. In this case, this enhancement could be helpful for them to map the ICD 9 codes to ICD 10 and find the appropriate match very easily without much manual matching.
Just exploring out to find, whether this could be a useful enhancement to OpenEMR.
I think that it still would be easier for each specialty in a multi-discipline setting to have its own cheat sheet. Ophthalmology is not going to use Urology’s codes. If we are talking about a huge clinic owned by the local hospital, it is more likely that another EHR would be used.
The billing clerk for each specialty should learn the new ICD-10 subset to complete the transition. After a few months she should know that H25.10 is the old 366.16 & hopefully key it in without resorting to the cheat sheet.
Clients may request a built-in converter; but in terms of work flow, it will not help staff gain proficiency in coding.
Since at this time chances of anyone actively updating ICD9 are minimal and relationship between ICD9 to ICD10 are available from the source (CMS), wouldn’t it make sense to update the search function such that when user enters partial text :
If code type is set to ICD10, look up only ICD10 tables
If code type is set to ICD9 AND tables for ICD10 have been updated, LEFT JOIN ICD10 results with ICD9 matches. The results can either be displayed as all ICD10 hits followed by ICD9 suggestions OR each ICD10 hit followed by ICD9 alternatives.
To @fsgl’s point, when a practice is working with handful of codes they would probably recall them from memory or have a cheat sheet. But when dealing with unusal situation or in our case where our practices will be replacing the ICD9 codes associated with issues as they come up during appointments, these tables are real timesavers.
You must know those 2 cards are a bit over simplified. With ICD9 we were coding the visit in the exam room and dropping the bill that evening. With ICD10, the billing flow will now require a “coding competent” person to review each record before coding and billing the visit (after the dictated note is typed) with the accompanying delay in reimbursement. All in the name of progress. (I actually had 2 patients with pheochomocytoma in my 40 years :>) )
If the physician is in solo practice & can check off the ICD-10 code on the Superbill, the index cards can be kept to a reasonable size.
Things become more complicated in a group practice & if/when we are mandated to code for laterality/severity/comorbidities.
Fortunately the young folks don’t know about the “good old days” (& they can’t retire even if they want to); otherwise no physicians will be left to care for patients.
I’m curious about cost/ benefit: how long would it take to develop such a tool /vs/ how long would it be in use? Can it be deployed quickly enough to be worthwhile? Plus, wouldn’t people change their workflows to use the crosswalk tool, then have to change them again after ICD-9 disappears? Just convert, learn the new system and be done with it!
This Implementation can be done quickly and deployed to usage. Yes, of course this maping will not be needed down the road, when the ICD 9 is completely obselete. But, we can implement the search to function(both way),
search ICD 9 (code/description) and that shows ICD 10 mappings (from which we can choose an appropriate one).
or can search only ICD 10 (code/description) and can select.
When ICD 9 is no longer needed, we can disable that from the configurations, so that the search will function purely for ICD 10 search. The main idea is, to make the physicians life easier to find the appropriate ICD 10 mapping, instead of by hearting or searching for the match. This may save the time, which is very crusial in an Healthcare field.