Hello, My name is mac, new to openemr and been building various systems over the past 30 years. I have forked the github repo and grepped the tree for ICD and see only references to ICD 9. I have all raw data files (dx & sg) for ICD 10 and wanted to see if you have effort to implement ICD 10 already underway. Let me know when your have a minute. Thanks.
The recommended strategy to do this is discussed in that thread. Not sure if there has been any progress by garcianc, though. Let us know if you want to work on this and we’ll be happy to provide guidance.
Brady,
Yes I am going to start working with the project and I’ll be focusing on ICD 10 upfront so any pointers will be helpful. I did take a look that those other threads today and noticed the two wikis. Will that be where to put discussion / design topics or would the project prefer those in developer threads? In reviewing the ICD 10 code base it is much more robust than ICD 9 in terms of specificity and was wondering about the UI ramifications. I am *really new* to the code so I’ll doing a lot of finding and grepping for a while. My background has been quite varied with a focus on data acquisition/analytics over the past 15 years SQL web type applications so the DB side of the ICD 10 is straightforward but the design might become worth reviewing if the ICD 10 model affects the UI. I have limited php exposure but am very familiar and experienced with other web frameworks. Also a github question: Nelson in Kenya has a tree that i want to collaborate with him on - does he branch 4.1.0 and push his changes to his branch then i merge to his branch? Anyway, let me know what the next steps are in terms of coming online with the project. Thanks.
Regarding GUI, don’t know how this will be affected; guessing not a really big issues. The main issue is that the ICD9 code has simply been hard-coded in many places and will need to replace these instances with more flexible code.
Collaborating with git/github is very straightforward once you have a handle on git. We are all very aware of git’s steep learning curve so always feel free to ask for advice/guidance. My suggestion is that the work be based on the ‘master’ branch rather than the 4.1.0 branch. Point us to the github branch you want to collaborate on with Nelson, and then it will be easier for us to suggest the best way to collaborate.
Recommend not touching the master branch; this should only be updated from the sourceforge or github official openemr repos. To set this up correctly, suggest following this tutorial: http://www.open-emr.org/wiki/index.php/Git_for_dummies
So, you will want to work on other branches, which is very easy. For example, if you are on your master branch, type:
git checkout -b mynewbranch
(this will now create a new branch for you to work in)
And you can then push this branch to your public github repo:
git push origin mynewbranch
Then a way Nelson can test and begin to work on your branch is:
git remote add mcaloon git://github.com/mcaloon/openemr.git
git fetch mcaloon
git checkout mcaloon/mynewbranch
git checkout -b nelson_mynewbranch
(then nelson can begin working off your branch)
(Note there are other ways to collaborate via ‘merge’ or ‘cherry-pick’, which will become more clear as you begin using git)