Linux Upgrade 4.2.2 to 5.0.0

From OpenEMR Project Wiki

Upgrade

  1. Move current (4.2.2) /openemr directory to a backup directory
   sudo mv /var/www/html/openemr ~/Documents/openemr.old
  1. Unpackage 5.0.0 openemr into web directory and rename the directory to openemr
  #: sudo tar -pxvzC /var/www/html/  -f ~/Downloads/openemr-5.0.0.tar.gz
  #: sudo mv /var/www/html/openemr-5.0.0 /var/www/html/openemr

3. Move following directories from old 4.2.2 version to /openemr directory:

#:openemr/sites/default/documents 
   sudo mv ~/Documents/openemr.old/sites/default/documents /var/www/html/openemr/sites/default/.
  1. openemr/sites/default/edi
   sudo mv ~/Documents/openemr.old/sites/default/edi /var/www/html/openemr/sites/default/.
  1. openemr/sites/default/era
   sudo mv ~/Documents/openemr.old/sites/default/era /var/www/html/openemr/sites/default/.
  1. openemr/sites/default/letter_templates
   sudo mv ~/Documents/openemr.old/sites/default/letter_templates /var/www/html/openemr/sites/default/.
  1. Record the openemr/sites/default/sqlconf.php file variables from your old 4.2.2 version, and type these into the openemr/sites/default/sqlconf.php file in new openemr version
   sudo joe ~/Documents/openemr.old/sites/default/sqlconf.php /var/www/html/openemr/sites/default/sqlconf.php
  1. In the openemr/sites/default/sqlconf.php file, set the $config variable (found near bottom of file within bunch of slashes) to 1 ($config = 1;).
  2. Open openemr/sql_upgrade.php (http://localhost/openemr/sql_upgrade.php) in web browser, choose 4.2.2 and click 'Upgrade Database'
  3. Configure optional settings in openemr/sites/default/config.php files

Download and install most recent patch

After finishing above upgrade, recommending getting the most recent patch for version 5.0.0. Instruction to do this can be found on the OpenEMR Patches page.


Meaningful Use 2 Specific Instructions


Using OpenEMR

See the OpenEMR 5.0.0 User Guide


Securing OpenEMR

See the Securing OpenEMR Guide


Calendar Glitch

If your calendar had not been properly set up and this message appears after the upgrade, "This appointment slot is already used. Use it anyway?"; see this forum discussionfor the solution.

Support:
http://sourceforge.net/projects/openemr/forums