Upgrade Noah 4.15.2. Guide - for Noah ES customers
Please read the below information before continuing. The software download is found at the end of this page
Noah ES Client 4.15.2
Noah System 4.15.2 was released March 22, 2024. This version was released to address an issue with internet browser updates interfering with Noah ES communication.
Background Details
In Noah System 4.15, the local Microsoft CE Database is replaced by a SQLite database.
For Noah ES customers, the Noah database is hosted in the cloud by HIMSA, but the update of the local Noah database from CE to SQLite still needs to occur. This local Noah database may be used if seeing a patient at a location with no internet access for example.
In many cases, there is no patient data in the local Noah database for Noah ES users, so the Noah update will move quickly.
The migration mentioned in the following steps is just from the old CE database to the new SQLite database, there is no patient data being moved or migrated to Noah ES.
Installation Guidelines
Please follow the below procedure to upgrade to Noah System 4.15.2 on your computer.
Launch the installation
Click through the prompts and Install
Read and accept the notes on Migrating the Noah CE Database from Microsoft SQL CE database to SQLite database.
IMPORTANT: Please note that the migration can take time depending on the size of the local Noah database. If time is a concern check the size of the local database in the Noah Console before you begin. If the local database is over 1 GB know that it can take more than an hour to complete the migration and update.
If your PC already using Noah 4.15.0 or 4.15.1 the migration topic presented below does not apply. Your installation will go a bit quicker.
Many Noah ES locations will have an empty local Noah database and update will be very quick.
Before the database is migrated from CE to SQLite, a database backup will be made, and the DB Maintenance tool will run.
After the DB Maintenance tool has run, the migration to SQLite will begin, and progress will be displayed. The migration goes table by table so the progress bar will start over for each table.
Expected Migration Time for computers with patients in the local database: HIMSA’s testing indicates that a mid-range machine should expect 30 minutes per gigabyte in the database. As an example, a 2GB database would take an hour to migrate, whereas a 4GB database would take 2 hours. HIMSA advises you start the migration when there is more time available than anticipated.
Once the migration is successful, the update to Noah 4.15.2 will continue. Noah Basic Modules will be installed. At the end of the update, you will be presented with the Noah login screen. You can log in to Noah ES at this time if you desire.
