Scope
This guide covers the upgrade process of OSCAR 15 to OSCAR 19. OSCAR 15 is not easily defined due to the fact that many users have done updates since the original release (build 361, Feb 12, 2016). Although some users may be starting the upgrade from different points in time, the process remains the same.
Database Updates
Database updates must be performed in order to upgrade the schema and perform essential data migrations to support the updated codebase. The update files are available from the OSCAR source code tree under the database/mysql/updates subfolder and each file's release date is encoded within it's name. The files can also be seen and downloaded using the following link
https://bitbucket.org/oscaremr/oscar/src/stable/database/mysql/updates/
The user should choose the starting file which is most appropriate, for example, if one is updating from OSCAR 15~build-361, the first file to load into the database engine would be update-2016-02-16.sql. All files should be run in order up until the the date of the build you are running.
If you are not sure the corresponding date of your build, you can find it from one of the following links.
https://demo.oscarmcmaster.org:11042/job/oscar15BetaMaster/ (for builds up to and including 533)
http://jenkins.oscar-emr.com:8080/job/oscar-stable/ (for builds 534 and up)