When we release updates they are either
- new features,
- non-critical fixes,
- or critical fixes.
All of these software fixes are available free of charge, for immediate download.
Critical / Security fixes
We provide notifications of critical fixes (which are often security fixes, but they can also be fixes that could prevent your software from working).
To be notified of these updates, we have two forums which you can opt-in to, by subscribing with your email address:
- Public notification of critical updates
- Vetted notification of critical updates
The vetted notification is for known customers/partners, who require updates before a public security notification, to allow them to update their software before this information is released to a wider group. This forum requires password access, and you will need to contact us to get access.
To subscribe to one of these forums: go into the forum (click the large start button, if it hasn’t automatically gone into the chat box), click on the ‘Settings’ button on the bottom left corner, and enter your email address. If you download the free AtomJump Messaging app (available for iPhone and Android), you can also get live ping notifications on your phone.
MedImage Server Upgrade Notes
For Windows platforms :
If there is a suitable patch for uploading, this is a better approach than upgrading, as only the altered files will be installed.
Unless warned otherwise, upgrading the MedImage Server is a case of downloading the new .exe file, and installing it over the top of the current MedImage Server. If you have add-ons installed, we recommend backing up the C:\MedImage\public\components\header.html file beforehand, as a MedImage Server will overwrite the menus that those add-ons add (see the comment above about ‘Patches’ being an easier approach). You can generally copy this back over after the MedImage Server installation. But otherwise, a MedImage Server install should retain all of your configuration files, add-ons, and add-on configuration files. We always advise to take a manual back-up of your current C:\MedImage folder before upgrading, however, in case you have any issues and wish to roll back.
We also suggest doing this upgrade out-of-office hours.
For Linux/Mac platforms :
If there is a suitable patch for uploading, this is a better approach than upgrading, as only the altered files will be installed.
There are upgrade scripts available for each of these platforms on their respective download pages.
If you have add-ons installed, we recommend backing up the [MedImage-Server-Path]\public\components\header.html file beforehand, as a MedImage Server will overwrite the menus that those add-ons add (see the comment above about ‘Patches’ being an easier approach). You can generally copy this back over after the MedImage Server installation.
Specific Version Notes
If you are using a version of the MedImage Server < 1.9.0 and you are upgrading to Ver >= 2.0.0, you will also need to upgrade your add-ons, e.g. the EHR Connector, to their matching 2.0 versions.
We recommend that you upgrade MedImage Servers prior to 1.6.1 (and >= 1.5.3) to version 1.6.1 via the version 1.6.1 patch. MedImage Servers <= 1.5.3 should be reinstalled/upgraded to 1.6.1 to fix this issue.
If you are upgrading from a Windows MedImage Server prior to 1.0, we recommend you back-up the following files/folders, uninstall the MedImage Server, and remove the folder C:\MedImage, before installing MedImage Server > 1.0, and then installing any add-ons once more.
C:\MedImage\config.json C:\MedImage\photos\
If you are updating MedImage Server 1.4 versions to >= 1.5 versions, and want to take advantage of additional file types e.g. .pdf files, you should add a ‘fileWritten’ event into your C:\MedImage\addons\config.json file, in the same location as the ‘photoWritten’ event. Please refer to a technical person to do this, or reinstall your server again after backing up the files/folders above.
EHR Connector Upgrade Notes
Please take a backup of the C:\MedImage\addons\ehrconnect\config\ehrconnect.json file before upgrading. You may also like to back up your log files in C:\MedImage\addons\ehrconnect\log\*
Special Note: For version <= 0.8.4 of the EHR Connector being upgraded to 1.x you should uninstall the EHR Connector via the Windows Programs before installing the new package.
A core EHR Connector upgrade usually involves installing the .exe file over the existing installation. This will clear the existing settings for the connection. You then need to install your EHR specific configuration installer (a .zip add-on), once more. You can either reconfigure the connection, or assuming there were no new additions to the configuration, copy back your old ehrconnect.json file into it’s original location.
If you are only upgrading the EHR specific configuration installer, you can do so, but keep in mind that you will need to reconfigure the connection manually afterwards.
Please do this upgrade out-of-office hours, to ensure that no live users are affected.
Wound Mapp Upgrade Notes
You should install over your current installation.
Before upgrading the Wound Mapp Add-on, you should stop the ‘MedImage’ service (and restart it afterwards). Please keep in mind that if you upgrade the MedImage Server, you will lose the ‘See Photos’ link on the main menu, so you will need to reinstall the Wound Map Add-on afterwards. It is often a good idea to back-up the C:\MedImage\config.json file before any upgrades.
App Upgrade Notes
Depending on the settings on you individual phone, app updates can be set up to occur automatically, when in Wifi range, or on user confirmation.
We will let you know if there are any critical updates via the forums above, but we recommend allowing automatic updates on the app.