Updating of SPM or PHM applications
Posted by Sinclair Hughes, Last modified by Sinclair Hughes on 25 January 2022 03:43 PM

These instructions are only to be used for Minor-Updates, as specified by Incisive.

There are three parts to the update process, which can be run independently.

  1. Downloading the update file to the onsite ‘server’ and preparing the files for deployment to the workstations
  2. Updating the program files in the \SPMWIN directory on the server and updating the database structure
  3. Deploying the updated program files to the application terminal servers, workstations and laptops

Downloading to the Server

This process should only be performed by either Incisive staff or IT technicians who are familiar with the Incisive update process.

  1. Notify Incisive of when you wish to apply an update.
  2. Go to the Downloads page and download the correct update installation file.  You need to login or register.  Check that the file size is correct.
  3. Find the \Spmwin directory on the server.
  4. Rename the  Updates directory to PrevUpdates
  5. Delete any existing folder called NxtUpdate
  6. Right-mouse-click on the downloaded updates installation file and choose ‘Run As Administrator’.
  7. Ensure the location of the \Spmwin directory on the server is correct
  8. Complete the installation process to the NxtUpdate directory

Updating the Server

Just before the terminal server, workstation update process is about to be performed, the following steps need to be conducted.  It is preferable that the server is restarted before this process is performed.

This process should only be performed by either Incisive staff or IT technicians who are familiar with the Incisive update process.

  1. Backup the databases and all of the associated image and document files.
  2. Create a Snapshot or Restore Point on the server.
  3. If possible, restart the server.  If a restart is not feasible, use Task Manager and make sure that xpmmenu.exe is not running nor any other processes that start with spm*.*
  4. On the server, login using local admin or domain administrator rights.
  5. Rename the directory called NxtUpdate to  Updates
  6. Copy all the files from the Updates directory to the \Spmwin program directory on the server.  Overwrite the existing files.
  7. Update the copy of SPM on the server by copying all of the files from the Updates directory into the Spmwin directory
  8. In the \Spmwin directory use the Run-As-Administrator option on the following three files:
    • mdbUpdate.exe
      This process will update the data structure of the database.
      It can be performed ahead of the workstation update process and even if staff are still using the SPM/PHM database.
    • reregister.bat
    • XPMMenu.exe
      Log into SPM and test that it has updated correctly.
  9. Check the version numbers at the login screen.
  10. Go to Setup -> Personnel -> Permissions and modify the menu permissions for each of the Roles
  11. Go to Patient -> Notes and check that you can display the Notes for a patient.
  12. Go to Appointment Book and display the appointment list for a specialist.
  13. Complete any other acceptance testing you require.

Deploying & updating Application servers, Workstations & Laptops

If the Workstation has been setup correctly then updating to the latest Version should only take two easy steps.
Incisive staff may assist with the updating of a single application server, workstation or laptop.  Thereafter it is your responsibility to perform the task on the other devices.

  1. Restart the application server or workstation/laptop
  2. Temporarily disable the virus-checker (if possible)
  3. Login using either a Local Administrator login or the Domain Administrator login

    If installing to an application Terminal Server
    - Create a Restore Point or Snapshot
    - Exit to a Command Prompt (as Administrator) and execute the following command
             Change User /install
    - Use Task Manager and make sure that xpmmenu.exe is not running nor any other processes that start with spm*.*

  4. Find the Incisive folder on the Desktop and double-click on the ‘Update Program Files’ icon.
    This should cause a command window to appear and display the files that are being copied from the Updates directory on the server to the \Spmwin directory on the local device.
    Note: If the command window flashes up quickly and disappears, then something is not quite right with your setup and you will need to rectify the batch-file instruction or remedy the network connection.  Call the Incisive Helpdesk for assistance.
  5. In the \Spmwin directory use the Run-As-Administrator option on the following three files:
    • mdbUpdate.exe (only if it hasn't been run already on a different server)
    • reregister.bat
    • XPMmenu.exe
      Log into SPM and test that it has updated correctly.
  6. Check the version numbers at the login screen.
  7. Go to Patient > Notes and check that you can display the Notes for a patient.
  8. Go to Appointment Book and display the appointment list for a specialist.

    If updating an application terminal server
    - go to the command prompt (as Administrator) and execute the following command:
         Change User /execute

  9. Enable the virus-checker
  10. Make sure all of the workstations and laptops have been updated to the correct version.

Troubleshooting

If you are unsure at any stage during the update process, please call the Incisive helpdesk for assistance.

If you have tried to register files without using the Run As Administrator option and are getting errors during the file registration process, you may need to perform the following:

  1. Exit to a Command Prompt window
  2. Change to the SPMWIN directory
  3. Type in and execute the following command (which deletes three text files)
       DEL   spm_*.txt
  4. Exit from the Command prompt window.
  5. Right-mouse-click on XPMmenu.exe and run using the Run As Administrator option

If serious problems with the deployment and updating of the program files to the applications servers, workstations or laptops is encountered, you may need to perform a roll-back to the previous version.  Contact the Incisive Helpdesk.