GNU Health Upgrade
GNU Health is in constant development. Upgrades fix bugs and keep your system with the latest functionality. Therefore, you are advised to keep your production system with the latest version.
GNU Health will always provide the scripts and tools for you to keep your health center updated.
- Get the latest GNU Health versions and announces : A key point to keep your GNU Health environment in good shape is to become part of the community. We publish GNU Health version updates and other relevant news in different media. Make sure you subscribe at least to the General users and to the health announce mailing lists.
- Verify your current GNU Health version. You can check your current GNU Health database version from the client, via Administration -> Modules
- Always upgrade all the GNU Health modules : When we release a version, we always pack all the official modules on it. This is important, because we test the integrity and cross-functionality among modules. So, you should never use modules from different versions. For example, you should not use health_genetics version 1.6.3 with health 1.6.2 . This is not supported and can create serious inconsistencies on your database !
Prepare your upgrade
Plan your upgrade process, resources and downtime: Upgrading a Hospital Information System requires careful planning. Make sure you choose the right time, and notice your colleagues about the new release.
Test the upgrade process in another computer : It is highly recommended that you count with a separate server, where you can test your upgrade process in a controlled environment, without impacting your production installation. Write down all the steps and issues that you run into.
The upgrade process
This section summarizes the upgrade process steps for a standard installation, using the modules included in the official release at GNU.org ftp site. Any version specific information will sent via the firstname.lastname@example.org mailing list, along the new release announcement, so make sure you are subscribed !
- Backup your database and kernel : Before starting the upgrade, you should backup both your database, your GNU Health modules.
- Stop your tryton server
- Backup your database . You can use postgresql pg_dump command : pg_dump your_database_name > your_database_name_backup.sql
- Backup your GNU health modules. All the GNU Health modules start with "health" and they reside in the "modules" directory in the Tryton server. If you use want to be even more cautious, backup the whole tryton server directory.
- Download the new GNU Health version. The official GNU Health tar file contains all the modules.
- Extract the kernel and follow the instructions as in a new Installation . This is for the standard GNU health package (gnuhealth_version.tar.gz from GNU.org ). For other type of versions, like PIP or specific operating system release, use the corresponding command.
- Upgrade the database to your latest GNU Health version, go to the tryton server directory and execute the upgrade the database upgrade command : ./trytond --database=your_database_name --update=all
- Start the tryton server
You should be now in your new GNU Health version !