Difference between revisions of "Windows Upgrade 4.2.2 to 5.0.0"
From OpenEMR Project Wiki
Bradymiller (talk | contribs) |
Bradymiller (talk | contribs) |
||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
=== Upgrade === | === Upgrade === | ||
#Clear the log tables by going to Administration > Backup click the Create Eventlog Backup | |||
#Once Event log is done select backup again and click Create Backup | |||
# Move current (4.2.2) /openemr directory to a backup directory | # Move current (4.2.2) /openemr directory to a backup directory | ||
# Unpackage 5.0.0 openemr into web directory and rename the directory to openemr | # Unpackage 5.0.0 openemr into web directory and rename the directory to openemr | ||
| Line 7: | Line 9: | ||
#:openemr/sites/default/era | #:openemr/sites/default/era | ||
#:openemr/sites/default/letter_templates | #:openemr/sites/default/letter_templates | ||
# Record the openemr/sites/default/sqlconf.php file variables from your old 4.2. | # 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 | ||
# 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;). | # 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;). | ||
# Open openemr/sql_upgrade.php (http://localhost/openemr/sql_upgrade.php) in web browser, choose 4.2. | # Open openemr/sql_upgrade.php (http://localhost/openemr/sql_upgrade.php) in web browser, choose 4.2.2 and click 'Upgrade Database' | ||
# Configure optional settings in openemr/sites/default/config.php files | # Configure optional settings in openemr/sites/default/config.php files | ||
<br> | |||
=== Download and install most recent patch === | === Download and install most recent patch === | ||
:After finishing above upgrade, recommending getting the most recent patch for version | :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|OpenEMR Patches]] page. | ||
<br> | <br> | ||
=== Meaningful Use 2 Specific Instructions === | === Meaningful Use 2 Specific Instructions === | ||
*[[OpenEMR | *[[OpenEMR 5.0.0 MU2 Install Instructions]] | ||
<br> | <br> | ||
=== Using OpenEMR === | === Using OpenEMR === | ||
:See the [[ | :See the [[OpenEMR_5.0.0_Users_Guide|OpenEMR 5.0.0 User Guide]] | ||
<br> | <br> | ||
Latest revision as of 03:38, 26 September 2017
Upgrade
- Clear the log tables by going to Administration > Backup click the Create Eventlog Backup
- Once Event log is done select backup again and click Create Backup
- Move current (4.2.2) /openemr directory to a backup directory
- Unpackage 5.0.0 openemr into web directory and rename the directory to openemr
- Move following directories from old 4.2.2 version to /openemr directory:
- openemr/sites/default/documents
- openemr/sites/default/edi
- openemr/sites/default/era
- openemr/sites/default/letter_templates
- 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
- 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;).
- Open openemr/sql_upgrade.php (http://localhost/openemr/sql_upgrade.php) in web browser, choose 4.2.2 and click 'Upgrade Database'
- 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
