Decide whether to update your existing database or to start with a new database

The 2009 SIR method provides a completely new set of user fields to be used with incident reporting, to accommodate altered system rules and lookup code and description changes. The previous user field structure must be removed from the system to allow the new user field structure to be established. Any optional user fields your department has created are also removed by the update.

Due to the user field changes and to sweeping changes in codes and their descriptions, you need to decide whether to start with a new database for 2009 incident reporting, or whether to archive data in the Incident reporting module and update your current database.

1. Review the information below about updating your database and using a new database.

   Update your existing database

   Before updating your existing database, you must archive your current incidents. Archiving incidents generates a secondary database containing the incidents you want to archive, and then deletes the incidents from the live database.  This process produces a clean environment for the new recording method.

   Note: Alternatively, you can create a copy of the existing FH database components to retain your historical data.

   Install a new database

   Starting with a new installation of FH produces a clean environment and database for the new recording method. However, you may need to re-enter master record information such as staff master records, inventory, necessary lookup codes.

2. Decide whether you want to update your existing database or to start with a new database.

   Note: If you have any questions while making this decision, contact FH^® technical support for assistance.

3. Depending your decision, continue with one of the following: 

   If you decided to	Do this
   Update your existing database	Continue with Archive your database.
   Install a new database	Continue with Copy your database.