From v3.x

To v4.x

Upgrading from v3.x to v4.x is a major upgrade and the following points need consideration. If you have any queries or concerns please contact ARANZ Medical Limited before upgrading, at: support@aranzmedical.com

• For versions prior to v3.10 of the software, it is recommended that a customer support representative be contacted to assist with this process.
• Tissue Type Classification feature is not available in v4.14. Any tissue type outlines need to be segregated in the data before upgrading.
• The storage format of the image captured date is converted based on the Default Timezone specified in the Organization Settings. As such, you should verify that the Default Timezone setting is correct prior to starting the upgrade. If an adjustment has to be made, sync the change to all SilhouetteConnect devices before proceeding with the upgrade.

The automatic upgrade process assumes that all image capture dates are from a single timezone. If data should be split into multiple timezones this needs to be performed by a customer support representative.

• Data consistency issues may cause upgrades to fail. These data consistency issues must be fixed before an upgrade can complete.
• The v3 integration component SilhouetteLink is replaced in v4 with NextGen Connect (formally Mirth Connect). Not all integrations can be supported in v4 but reconfiguration is required.
• LDAP Sync is replaced with SSO integration. LDAP sync'd user accounts in v3 will be disabled on upgrade.
• Once upgraded review the user groups and permissions granted as the permissions model has changed significantly.

From pre-v4.3

To v4.3+

Upgrading to v4.3, or beyond, requires that a synchronization instance of SQL Server be available on SilhouetteCentral to support the SilhouetteConnect synchronization process. The synchronization instance of SQL Server needs read and write access to the appropriate files\mdfcreation directory.

It is also recommended to modify the SilhouetteCentral web site configuration in IIS to set Preload Enabled to True and to set the Application Pool Start Mode property to Always Running. The optional IIS Application Initialization feature is required to enable these properties.

See the following topics for more details:

• Server Prerequisites and Dependencies
• Preparing a SQL Server Database.
• SilhouetteCentral Web Application Installation.

From pre-v4.4

To v4.4+

Upgrading to v4.4, or beyond, changes the way assessment dates are stored. Assessment creation dates are changed to record the local time plus an offset from UTC, as well as recording the time zone name of where they were created.

The time zone database used by Silhouette is the IANA time zone database. Information on the IANA time zone database can be found on the website https://www.iana.org/time-zones.

During the upgrade to v4.4, the upgrade will ask you to select an appropriate time zone to use for historical assessments. Selecting the correct time zone is important as the offset from UTC applied is dependent on any seasonal clock changes for that time zone.

The upgrade will ask you to specify a time zone per unit configured in Silhouette. The upgrade assumes is that the patients seen in different time zones will be in different units. If that is not the case for your system, contact ARANZ Medical for support while upgrading.

From pre-v4.6

To v4.6+

Version 4.6 reintroduces the concept of Wound State which was part of version 3 Silhouette but had previously been missing from the version 4 product.

If you are upgrading from a v3 Silhouette, the wound state records will be upgraded. These upgraded entries will appear as wound state changes on the relevant patient and wound time lines. The time given to the wound state records is 00:00 (midnight), in some case if a wound was healed on the same day as an assessment was completed for that wound then the healed state will show earlier than the assessment on the time line.

All wounds created in previous v4 versions of Silhouette are given an Open state based on the creation date and time of the wound.

This wound state upgrade requires the time zone mappings mentioned above in the v4.4 upgrade. If the time zone to unit mappings are not present, or are incomplete, then you will be asked to specify them during the upgrade of SilhouetteCentral.

Version 4.6 wound state also allows you to update the current wound state as part of a wound assessment. When upgrading any assessments will have a blank associated wound state record.

v4.8 upgrade removes previous blockers upgrading v3 systems, specifically systems with multiple patient identifiers and with duplicate wound indexes can now be upgraded. v3 systems with these properties should be directly upgraded to v4.8 without any intermediary steps.

When upgrading v3 systems with Multiple Patient Identifiers, you will be asked to identify a single identifier for use within Silhouette during the upgrade process. All other identifiers will be migrated to standard note fields as part of the patient details.

In some rare cases this upgrade can leave some patient records without patient identifiers to display within Silhouette. Contact ARANZ Medical support if you require some data migration other than that provided by the standard upgrade script.

v4.9 introduces the concept of a wound baseline date. The wound baseline date is used to identify the wound baseline measurement when calculating area reduction. The upgrade sets the baseline date for wounds created in v3 based on the baseline assessment date from v3, otherwise the baseline assessment date is set the same as the wound open date.

Area reduction was previously shown in Silhouette v3. when upgrading from v3, the area reduction values seen pre-upgrade vs post upgrade may change slightly as the calculation has been modified to remove the rounding errors from the display of area reduction.

v4.9 re-introduces the persistent note feature that was available in v3, but does not include support for persistent conditional expression. The v3 to v4.9 upgrade will keep notes that were persistent in v3, however all upgraded notes should be reviewed for their applicability.

v4.11 introduces the SilhouetteTokenService as a separately installed Web Application using .Net Core 3.1 runtime. When upgrading to v4.11 you will need to follow the upgrade instructions for SilhouetteCentral and the installation instructions for the SilhouetteTokenService provided in this manual.

Once updated to v4.11, you will need to be operating with a HTTPS binding on SilhouetteCentral. This may require updating the RootURL in SilhouetteCentral and the SyncURL in the associated SilhouetteConnect installations.

During the SilhouetteCentral upgrade, you will be asked to enter the ODIC Authority. Enter the URL for the new SilhouetteTokenService web application, e.g. https://<domain>/silhouettetoken.

v4.11 enables integration of Silhouette with an external identity provider using the SSO SAML 2.0 protocol. Silhouette v3 had a similar feature through direct LDAP queries to an external user directory. There is no upgrade of the v3 identity integration to the v4.11 identity integration. The v4.11 upgrade will disable any external user accounts previously sync'ed using LDAP and the SSO feature can be configured.