Upgrade icd10 code set

Management and Administration
#81

shouldn’t have spaces

#82

sorry, it looks like that but I double checked. There’s no space at all

#83

root@testbed:/home/med# ls -lrt /var/www/openemr/contrib/icd10
total 6708
-rw-r–r-- 1 www-data www-data 1640538 Mar 8 10:00 2018-ICD-10-PCS-Order-File.zip
-rw-r–r-- 1 www-data www-data 1114989 Mar 8 10:00 2018-ICD-10-CM-General-Equivalence-Mappings.zip
-rw-r–r-- 1 www-data www-data 2775671 Mar 8 10:00 2018-ICD-10-Code-Descriptions.zip
-rw-r–r-- 1 www-data www-data 1327378 Mar 8 10:00 2018-ICD-10-PCS-General-Equivalence-Mappings.zip

Just to be prove that it’s so

#84

edit: how did you create your 5.0.1 test system?

#85

a Fresh install of Ubuntu 16, Lamp server installed. Then, I install OpenEmr 4.2.2. Then I import and updated data from my 4.2.0. I used sql-upgrade.php to upgrade the database. After that, I installed OpenEMR 5.0. Then I patched it…

#86

did you run the sql upgrade for 5.0.0?

#87

yes I did…

#88

might want to try rebuilding the test server by installing 5.0.0, then drop the database, create a new blank one from the command line, then import your old database and run the 5.0.0 sql upgrade

#89

I will do it and get back to you. I hope it works this time. I have rebuilt the system 3 times already but never just install 5.0 directly.

#90

OK, just finished doing another fresh install of Ubuntu 16, update and upgrade everything, installed LAMP and OEM 5.0. I was able to log into admin account and see that the 2017’s ICD10 are available to install but not installed.

Installed Release
Not installed
Staged Releases
2017-GEM-DC.zip
2017-GEM-PCS.zip
2017-ICD10-Code-Descriptions.zip
2017-PCS-Long-Abbrev-Titles.zip

I have chown’ed www-data to the openemr folder and ready for the next step. I presume the next step would be to upload my 4.2.0 database into sql and then do sql_upgrade.php.

After that, download the new ICD10 from 2018, do the sql statement & then apply them through external database upgrade?

1 Like
#91

Nope, no good. I still can’t upgrade to the latest ICD10 2018. The database from 4.2.0 once uploaded to the 5.0 and went through sql_upgrade.php has md5s already in the database, the whole 6 sets from past attempts to upgrade.

I am so confused.

#92

sorry, at this point you probably need professional support, https://open-emr.org/wiki/index.php/Professional_Support#Care_Management_Solutions.2C_Inc.

#93

Thank you… Do you or anyone know how to delete all the md5’s from the database?