jenjhall wrote on Wednesday, January 19, 2011:
I don’t think the table would be any larger than the language translation tables. I bet you could find the ICD9 codes already in a sql file somewhere on the net if they are already in the public domain. - Jen
darstout wrote on Monday, January 24, 2011:
I am also having difficulty installing the ICD-9 codes.
I am using Ubuntu 10.04 Linux and have a fresh installation of version 3.2.
I modified the load_icd_desc.plx perl script by using the description at the link “www.openmedsoftware.org/wiki/Load_ICD9_Codes” and ran the script (as root) as instructed. This is the command and the output:
openemr1: perl /var/www/openemr/contrib/util/load_icd_desc.plx
Inserted 0 rows, updated 0 codes.
It looks like there may be some more modifications necessary? Please help.
Thanks!
Darius
tmccormi wrote on Monday, January 24, 2011:
I’ll be pushing a current icd9 file in SQL format out to the 4.0 release this week… Look for an announcement …
-Tony
darstout wrote on Monday, January 24, 2011:
Good news for all of those using Ubuntu Linux 10.04 and OpenEMR version 3.2. I was able to retrieve 14,012 rows of ICD codes by using the script supplied by OpenEMR (load_icd_desc.plx) AND by adding the single line of code that Ruben posted earlier on 1/12/2001. Thanks Ruben and thanks to everyone that participated in this thread.
Darius Stout
darstout wrote on Monday, January 24, 2011:
Sorry. In the last post I meant to list the year as1/12/2011 INSTEAD of 1/12/2001.
klassy wrote on Saturday, March 26, 2011:
Thank you all for a great post!
i followed each step to the letter - except one thing:
i am failing to install mechanize! i keep getting this error when i try to run the perl script
Can’t locate WWW/Mechanize.pm in @INC
i have tried countless forums with no luck
please help
brentosv wrote on Thursday, October 13, 2011:
Hello, I am having issues with this problem as well. I have followed all of the steps yet when i run the code in the cmd i get:
C:\Perl\bin\perl c:\xampp\htdocs\openemr\contrib\load_icd_desc.plx
Can’t open perl script “” no such file or directory
i’ve also tried:
C:\Perl\bin\perl c:\xampp\htdocs\openemr\contrib\util\load_icd_desc.plx
but the same thing happens.
I have tried countless forums as well with no luck also, please help. thank you.
tmccormi wrote on Friday, October 14, 2011:
These files are now included with the release, you don’t need to run that scripts every again. Look in the openemr/sql directory for a file call icd9-codes-insert.sql and use mysql or phpMyAdmin (from the Administration->Database) to import it.
-Tony
tmccormi wrote on Friday, October 14, 2011:
That should read … run that script ever again …
-Tony
klassy wrote on Friday, October 14, 2011:
Thanks tony! sorry i forgot to get back on the forum and congratulate you guys for including 1cd9 in the current release!
just one issue, how to do the same with ICD10? scrapping codes from the ICD10 web site has been a nightmare!
bradymiller wrote on Friday, October 14, 2011:
Hi,
Should we have these icd9 codes installed during the installation script (like is done with the cvx codes)?
-brady
brentosv wrote on Friday, October 14, 2011:
Thank you Tony!
One more question, this one may be a bit more difficult (i’m not sure-i’m pretty new at coding) but how would one go about populating the ICD9 codes into the CAMOS form of the openEMR? If a step-by-step or quick summary isn’t too difficult, it would be very much appreciated.
thanks!
-Brent V.
tmccormi wrote on Friday, October 14, 2011:
Brady - I think the setup script should have a section that allows the user to check off which supplied, extra tables to load. Not all users world wide want the full list of icd9 for instance and it would be nice to be able to include other table in the list. I’d suggest a sub-dir in the sql dir called “optional” that is parsed to produce a selection list.
Brent - CAMOS is a subject for an new topic. And I’m not a CAMOS user, so I won’t be any help with that.
-Tony
bradymiller wrote on Friday, October 14, 2011:
Hi Tony,
Issue is that many of the installations bypass setup.php (ubuntu and xampp packages). Since the code_type for ICD9 is hard-coded(ie. nothing else should ever use it’s defined ct_key and ct_id), don’t see how the existence of it would hurt users whom don’t want it:
http://open-emr.org/wiki/index.php/Code_Types
For example, ICD-10 codes would likely be akin to adding the CVX codes(ct_id is not hard-coded), which will likely require some code mods to support. Note i’m just thinking out loud here. Any thoughts here (for example, is it better to substitute the ICD-10 directly for the ICD-9 ct_id)?
-brady
bradymiller wrote on Friday, October 14, 2011:
Hi,
Regarding the issue of installing ICD9 codes by default, probably best to just leave this decision up to the community. If anybody feels the full ICD9 codes database should be included in a default installation, then chime in now. Otherwise, will plan to keep them not installed by default.
-brady
yehster wrote on Friday, October 14, 2011:
It is easier to add them if you want them than to remove them if you don’t, so I think the option of not installed by default is the better one.
nursejeff wrote on Saturday, October 15, 2011:
Its a basic need for a medical billing system. No ICD-9 codes= no pay.
It makes total sense to me to have them installed by default.
Jeff Guillory Jr.
NP Health Clinic
klassy wrote on Saturday, October 15, 2011:
Hi all!
Is it not possible to include both ICD10 and ICD9 on the install and make it an option for the user to select which module they’d like installed?
It will be good to turn off other options like cpt4 and hpsa codes because not everyone needs them!
blankev wrote on Tuesday, October 18, 2011:
For language translation we use an option that might be called a conversion table. Conclusion: What is the same in a different language can be used in that specific language otherwise is default into the orriginal).
Would it be an option to include ICD9 (17000 codes), ICD10 (155.000 codes) and ICPC (international Classification for Primary Care ??? codes) in some form of conversion table. There are readily available tables for this download through WHO. These tables could than be used interchangeable to ones likings.
This is a simplification of the problem, since there are huge differences between the tables, but also many similarities.
http://www.tdrdata.com/ipd/ipd_ICD10ToICD9List.aspx (a part of the conversion between ICD9 and ICD10)
I am not a programmer, but just wanted to toss in a long supported thought on this topic.
Pimm
blankev wrote on Tuesday, October 18, 2011:
Literature on ICD9 and ICD10 coding principals and difficulties in conversion
Pimm