HIMSA makes use of the Microsoft SQL CE 4.0 database for the Noah patient database, activity log, and the Noah configuration settings database. The SQL CE database has been discontinued by Microsoft and the end of support for CE 4.0 was reached in July of 2021.
HIMSA expects no problems with the SQL CE database as a result of Microsoft’s end of support and has had no reports of any problems. This was seen as well when Microsoft discontinued support for the 3.5 version of the CE database. Many thousands of locations continued using this version and no problems occurred as the result of the end of support.
HIMSA has a project underway to provide our Noah customers with an updated reliable replacement database. HIMSA has selected the SQLite database product and implementation has begun. This project is scheduled to be included in Noah System 4.15, no date for release has been set. Updated information will be presented here as progress is made.
Q: Can I remove the CE databases if I use the integration option with Microsoft SQL Server?
A: No, Noah relies on the presence of the CE databases to function. Noah cannot run in their absence.
Database file details
Noah 4 makes use of the following database files:
- NOAHDatabaseCoreSqlCompact (c:\program files(x86)\Common Files\HIMSA Shared) – This database stores all patient and Noah action data
- Noah4ActivityLog (c:\programdata\HIMSA\Noah\ActivityLog – This database stores all activity within a Noah System 4 installation
- NoahCfgDatabase (c:\program files(x86)\Common Files\HIMSA Shared) – A database of settings and configuration settings
- NOAHBSIntegServerdatabase (c:\programdata\HIMSA\NoahBS) – This database is only present and used if the Noah System 4 installation has been integrated with a business system making use of the WSI API. This database is used to temporarily store data being exchanged between Noah and the Business System.
Q: Is it possible for other applications to interact with these database files?