This presentation will describe the process Oklahoma State Department of Health went through to upgrade from PHIN-MS 2.1 to PHIN-MS 2.8. The operating environment of PHINMS 2.1 will be discussed including; Operating system, admin privileges, party ID, certificates, passwords, CPA files where and what, location of sender files and receiver files, and databases. Once the current PHINMS 2.1 installation was understood we begin a discussion of what is needed for upgrading. You can not upgrade directly from 2.1 to 2.8, you must do an intermediate upgrade to 2.7 and this will be discussed. Most of the bare bones instructions are available for these upgrades but we will provide time line and personal antidotes and observations that OSDH went thru for the upgrade.
We will discuss the actual upgrade process. How you should request and download the software from CDC. Who to seek for help. Once you have the software, the next step. What are “partyID's” , how do they work and why they are important. We will discuss digital certificates, what they are and how to get them. This is not a trivial task and what do you do with certificates once you have them. We will walk you through installation of PHINMS 2.7 necessary to upgrade to PHINMS 2.8 and any pitfalls that we encountered. To use PHINMS 2.7 you must download and insert certain jar files before you can create the SQL database. Once these jar files are in place you can create the necessary tables in the SQL database. We will describe the scripts necessary to create required tables and queues, and how to run these scripts. Once software installation is complete we will discuss configuration and testing of the PHINMS 2.7 application. The next step is upgrading from PHINMS 2.7 to PHINMS 2.8.