rdh61 wrote on Thursday, August 25, 2011:
Hi,
I am using version 3.2.0 on Ubuntu 10.10. I have made substantial changes in some of the forms (e.g. the system review form), and added my own layout based forms.
If I update to the latest version of OpenEMR, is it straightforward to import my modified forms and databases?
bradymiller wrote on Thursday, August 25, 2011:
Hi,
If you are you proficient at git or able to spend time learning git? If so, I’d rec. using git to hold your modifications in a git branch, which can then be used to develop a patch from the original 3.2 version. You could then upgrade to the original 4.0 (soon to be 4.1), and then apply this patch (also may need to do some manual fixing up (ie. merge work)). Knowing this is a nice way to maintain your mods (and add additional mods) into future version.
It does sounds like your changes to the codebase may be minimal, so could also simply manually make the changes again after the upgrade (note all the layout based forms are within the database, so you don’t need to worry about this in the upgrade).
For the upgrade. When crossing over 4.0, there are some special issues that arise. Depends on the following:
1) Do you have an ‘admin’ user?
2) Are you using php-gacl?
3) Are you using sql-ledger?
And, of course, whenever doing this kind of stuff important to test it out on a testing version of your instance of OpenEMR (ie. do not do it to your production instance until you are sure it will work)
-brady
bradymiller wrote on Thursday, August 25, 2011:
Hi,
Strike all my talk above regarding crossing over 4.0. I had a brain fart; it’s actually when crossing over 3.0, so does not apply to you at all. Upgrade manuals for you can be found here:
http://www.openmedsoftware.org/wiki/OpenEMR_Upgrade_Guides
-brady
sunsetsystems wrote on Thursday, August 25, 2011:
The Layout Based forms should survive an upgrade, as they are intended to be custom built. Changes to system forms should be reviewed by your programmer, in light of possibly conflicting changes in the community code between the two releases.
I suggest that in the future you open a discussion in the Developers forum and/or tracker when planning changes to the code, as others may have suggestions and/or be interested in getting them integrated into the project. Integration is to your advantage as it avoids this upgrade problem in the future.