ICD10 Installation Error

Hello I’m using OpenEMR
Version Number: v5.0.1 (7)

OS: Mint 19.1
Browser, Firefox and Chromium

Hello I did a fresh install of OpenEMR on Mint and found that I could not search for ICD 10 or CPT codes in Fee Sheet. Do I have to enable anything to make it work?

Update. It seemed that I didn’t install ICD10.

However I have trouble when trying to install

Admin -> External Load Data -> ICD10 -> Install

icd10_querry_error

I followed the link and downloaded the 4 files.

Went to phpmyadmin and copy and paste the following into sql

INSERT INTO supported_external_dataloads (load_type, load_source, load_release_date, load_filename, load_checksum) VALUES ("ICD10", "CMS", "2017-10-01", "2018-ICD-10-PCS-Order-File.zip", "264b342310236f2b3927062d2c72cfe3"); INSERT INTO supported_external_dataloads (load_type, load_source, load_release_date, load_filename, load_checksum) VALUES ("ICD10", "CMS", "2017-10-01", "2018-ICD-10-CM-General-Equivalence-Mappings.zip", "787a025fdcf6e1da1a85be779004f670"); INSERT INTO supported_external_dataloads (load_type, load_source, load_release_date, load_filename, load_checksum) VALUES ("ICD10", "CMS", "2017-10-01", "2018-ICD-10-Code-Descriptions.zip", "6f9c77440132e30f565222ca9bb6599c"); INSERT INTO supported_external_dataloads (load_type, load_source, load_release_date, load_filename, load_checksum) VALUES ("ICD10", "CMS", "2017-10-01", "2018-ICD-10-PCS-General-Equivalence-Mappings.zip", "bb73c80e272da28712887d7979b1cebf");

Output

Back to External Load_data and this came up


I also tried to use command

mysql -u root -p openemr -e "INSERT INTO supported_external_dataloads (load_type, load_source, load_release_date, load_filename, load_checksum) VALUES ('ICD10', 'CMS', '2017-10-01', '2018-ICD-10-PCS-Order-File.zip', '264b342310236f2b3927062d2c72cfe3'); INSERT INTO supported_external_dataloads (load_type, load_source, load_release_date, load_filename, load_checksum) VALUES ('ICD10', 'CMS', '2017-10-01', '2018-ICD-10-CM-General-Equivalence-Mappings.zip', '787a025fdcf6e1da1a85be779004f670'); INSERT INTO supported_external_dataloads (load_type, load_source, load_release_date, load_filename, load_checksum) VALUES ('ICD10', 'CMS', '2017-10-01', '2018-ICD-10-Code-Descriptions.zip', '6f9c77440132e30f565222ca9bb6599c'); INSERT INTO supported_external_dataloads (load_type, load_source, load_release_date, load_filename, load_checksum) VALUES ('ICD10', 'CMS', '2017-10-01', '2018-ICD-10-PCS-General-Equivalence-Mappings.zip', 'bb73c80e272da28712887d7979b1cebf');"

It still gives me the same problem

Additional information
root@test-pc:/home/test# sudo ls -lrt /var/www/openemr/contrib/icd10
total 6712
-rw-rw-r-- 1 www-data www-data 126 Sep 29 2018 README
-rw-rw-r-- 1 www-data www-data 1640538 Jul 7 16:56 2018-ICD-10-PCS-Order-File.zip
-rw-rw-r-- 1 www-data www-data 1114989 Jul 7 16:56 2018-ICD-10-CM-General-Equivalence-Mappings.zip
-rw-rw-r-- 1 www-data www-data 2775671 Jul 7 16:56 2018-ICD-10-Code-Descriptions.zip
-rw-rw-r-- 1 www-data www-data 1327378 Jul 7 16:56 2018-ICD-10-PCS-General-Equivalence-Mappings.zip

Here is the folder of contribution

hi @cornutaurus ,
See this thread:
New php default setting of mysqli.allow_local_infile that will be causing issues

1 Like

Thank you. Got it to work

Heads up for anybody who’s looking at the new 2020 ICD10 code release, the existing file importer in OEMR does not successfully update the system to the 2020 ICD10 codes. Looks like something stops it from processing the new txt data files from CMS. Will need to find a solution to that before 10/1/2019 for U.S. based systems.

ETA: CMS changed their file/folder naming conventions, you will need to re-zip the bundle ‘2020-ICD-10-CM-Codes.zip’ , to make it work correctly. As it comes from CMS , the folder name includes spaces, which basically makes it invisible to the data parsing routine.

1 Like

thank you @Penguin8R, 2020 I10 dx update with a work around for nested folder (#2630) · openemr/openemr@53b8ae6 · GitHub

Actually, there’s 2 problems there, 1st one is due to spaces in the file bundles from CMS.
2nd problem is that if you follow the normal conventions and make both the ICD10-PCS and ICD10-CM data files available, the External Data Load utility will ignore the CM codes and import only the PCS Order codes. Unless you’re a hospital, probably best to just omit the PCS zip bundles altogether and load only the necessary CM codes so you’re up to date for 10/1/2019.

the PR above loads both no prob, the problem was the subfolder which is now handled

That is good to know, thanks! I had tried with version 5.0.0 , 5.0.1 , and the 5.0.2 release over the last few days and none of it worked until I made the workaround for the goofy CMS folder names, but even then it was still skipping the CM if PCS zip file was present. This will be a big deal in about 30 days, thank you for fixing.

thanks for the early warning :slight_smile: