penguin8r wrote on Monday, September 19, 2016:
New 2017 ICD10 codes will be effective in the US on October 1st. Anybody tried importing the 2017 code data into OpenEMR? CMS has discontinued some of the files , and changed the naming structure on others it seems.
cmswest wrote on Monday, September 19, 2016:
Brady helped me bring the new files in:
penguin8r wrote on Monday, September 19, 2016:
That’s a good start, thanks! The next trick will be figuring out how to back port those into existing installations.
cmswest wrote on Monday, September 19, 2016:
The external data load tool under admin->other should handle it,
penguin8r wrote on Friday, September 30, 2016:
Just an FYI for anyone else who might be following this since tomorrow is October 1st, do NOT try to import the 2017 ICD10 data load files into existing version 4.X installations of OpenEMR. You will regret it.
Troubleshooting now, will report back if/when a solution is found.
teryhill wrote on Saturday, October 01, 2016:
What exactly is the issue? I already have users using them. Have not noticed an issue.
Terry
cmswest wrote on Monday, October 03, 2016:
this change prevents the addenda file from being loaded from 2017-ICD10-Code-Descriptions.zip which added invalid records
when upgrading to 2017 the entire new codeset will be appended on to the icd10_dx_order_code table and the previous revision is made inactive
this could be a problem for adjudication of claims with dates of service prior to 10-1-16 if the old code is now deleted (can’t be added in fee sheet) or a new code is selected (wasn’t a valid code at the time of service)
penguin8r wrote on Monday, October 03, 2016:
Yup, as Stephen pointed out, anything other than a brand new install with Version 5.0.0-dev code will choke on the addenda files and butcher your ICD10 data table, and could cause billing problems when working with data entered using the previous ICD10 data set. Have to either patch the .inc file, or substitute a new zip file with the erroneous addendum files removed when working with older established production systems.
teryhill wrote on Monday, October 03, 2016:
Not if you make the requred code changes.
cmswest wrote on Monday, October 03, 2016:
right, make the small edit to library/standard_tables_capture.inc bring in the new files and you can upgrade with 4.X.
mkup wrote on Monday, October 31, 2016:
Not being able to work on pre-update claims is a problem in itself, because there is usually a sizable number of claims aged more than 2 months. Plus, some icd10 codes are missing after the update. For example, N92.0 is present in both old and 2017 CM files, but it’s not visible after the update
cmswest wrote on Tuesday, November 01, 2016:
hi Mark, N92.0 should be present. Did you edit library/standard_tables_capture.inc as referenced in the above commit?
also, you can search for codes and modify them in Administration->Codes if need be.
mkup wrote on Wednesday, November 02, 2016:
I’ve modified the library/standard_tables_capture.inc. I can’t modify ICD10 codes in the Administration, because ICD10 is “External”
cmswest wrote on Wednesday, November 02, 2016:
did you modify standard_tables_capture.inc before you imported? either way it sounds like you may have to empty the tables and re-import.
ps please see attached screen shot for how to modify icd10 even though they are external.