it’s a common part of openemr setup to allow a local data load, here’s a post describing the step
Can I manually add to database ? Is there a procedure ?
you have to restart the service too
I’m on a shared server .How do I do that ?
maybe you can ask them for assistance?
It’s interesting that this is still a problem after all these years.
The ICD10 import utility did briefly work on some of the version 5 releases.
Now on Version 6.1, it’s broken again.
“The number of staged files is incorrect. Only place the files that you wish to install/upgrade to.”
There is of course only 1 ICD10 Code Description zip file in place. I have to say, as someone who’s been building and deploying OpenEMR installs in medical practices for over a decade now, it’s pretty dang embarrassing that we can’t get something as basic and fundamental as an ICD10 data load to work.
ETA: I went back and checked on a 6.0 test install, the ICD10 import works there. Apparently somebody decided to “upgrade” it for the 6.1 release.
What if the practice doesn’t want the PCS codes?
(Since 99.9% of them will only ever need or use the CM codes)
I mean, I love OpenEMR, but let’s be realistic, it’s not being used in hospitals…
ICD10-PCS has to be activated in Admin->Forms->Lists->Code Types so the load just needs it’s zip file to the load the DX and PCS tables in case at some point someone would like to use the PCS.
So, am I understanding this correctly, we have to load both ICD10-CM and ICD10-PCS simultaneously, even though the ICD10-PCS will never be used? So then all future ICD10 updates will have to include both as well?
I will spin up another 6.1.1 install & test if that’s the case, just making sure we know what to expect.
I don’t recall us having to add that for FHIR support, but we may have needed it to handle the receiving of CCD-A imports when we are receiving a file that is referred to a clinical installation from a hospital.
We’ve had to add a lot more code set supports in order to meet ONC certification. There will be some additional code-sets that that will have to be executed for the 7.0 release. 6.1 was a stepping stone to the 7.0 ONC certified release so that’s possibly the problem you are running into.
As for things breaking, as volunteers we are trying to do the best we can, we’d love to have more development help as it sounds like you and your team have experience in this space. Feel free to help us fix some of these bugs 
1 Like
The code loader in 6.1.0 is broken.
One awkward workaround is to use a temporary installation of 6.0 to load the current CMS ICD-10 release, then dump the table and import it into the working 6.1.0 environment.
Doesn’t work on a local test installation of 6.1.0. A version 6.0 installed on the same LAMP stack has no trouble loading the ICD-10 CM codes.
Ran into the same issue twice in the last month helping 3rd party sites set up laboratory interfaces.
Most labs require DX codes as part of the order requisition, so it’s a critical component.
I have a dev working on a LOINC code loader, so I’ll see if he can fix the ICD10 bugs too.
ETA: The 2 lab installs were on brand new 6.1 OpenEMR environments that were being prepped for first use, with no existing ICD10 data present, so it’s not just updates that don’t work, even the initial load of the ICD10 codes on a clean system can’t be executed.
Ok, good luck, am unable to reproduce the fail on my local tests and the demos.
It just hit me, is this a new feature for ONC, so the system will recognize ICD10-PCS codes when receiving data from a hospital or HIE in future? If that’s the reason, then it would make some sense, but that is the only logical explanation I can think of for defaulting to loading both code sets…
Stephen, thanks for the tips, I understand how it works now, after creating a clean 6.1.1 environment to test in.
I have been updating ICD10s the same way for over a decade, this change definitely caught me by surprise, have never even bothered to download the PCS code sets before.
1 Like
There’s another OpenEMR user @mdsupport who is looking at integrating a LOINC code importer. See this github issue. The two of you may want to coordinate: LOINC codes · Issue #5411 · openemr/openemr · GitHub
1 Like