I am new to OpenEMR and unfortunately i wasn’t as active as I should have in this forum as well.
My basic doubt is if we make considerable code changes and design changes to the OpenEMR 4.1.1 version, how would it affect us when say a new version of OpenEMR is released.
I would guess in that case, to upgrade my customized version would be very tedious.
The code maintenance is depends upon the changes you are going to made in your OpenEMR, If you are made only small changes it would be easier to apply the upcoming patch in your OpenEMR, Other wise it becomes hard to maintain.Better you can use GIT for code revision,
Ismail,
FYI : If you maintain GIT properly,You can use OpenEMR patch for needed bug fixes(Not all) from community.please make sure that.As well please let us know for further help on OpenEMR services
The best way to avoid diverging your code is to consider contributing your improvements to the official OpenEMR codebase; then the upgrading/patching will work out of the box (of course this decision is up to you).
One of the things that we at ZH Healthcare is doing is making a code with which you can install new modules that run with OpenEMR. So, lets say, if you were to take the Calendar part and make substantial changes to it, you can code it as a separate Calendar module and run it with OpenEMR. So you will essentially have the original Calendar code and the changes you made.
You might have seen such module installer in almost all open source products like Drupal and such.
You dont need a module installer to do this. You can take the approach of creating your modifications as another module even without the module installer.
This way you get to retain the changes you made. Currently we are testing the module installer and will be contributing this code to the community.