HIFIS 4.0.60.4.4 Release Notes

Warning:

Before implementing this release, a backup of your database is necessary. Taking a snapshot of your application tier before implementing this update is also important in the event that a roll back of the changes are required.

Please be advised that the upcoming update to the HIFIS application may require an extended amount of time to process.

This update contains the changes that were implemented in HIFIS 4.0.60.4.4, including a major change where all Client State records are recalculated to align with the new 90-day inactivity policy standard. As a result, clients who have not engaged with services within the last 90 days may be flagged as inactive.

This could impact their status on your Coordinated Access list (including versions generated through custom reporting).

Key Recommendations:

• Create a copy of your production environment and deploy it to your sandbox or testing site.
• Perform the update on the sandbox/testing environment first to evaluate the impact of the recalculation and the overall duration of the process.
• Verify that all key functionalities and client data behave as expected after the update in the sandbox environment before proceeding with the production update.

It is important to understand how this change will influence your Coordinated Access list and plan accordingly to avoid any disruptions in service delivery and changes to data reporting.

If you have any questions or require assistance, please contact the HIFIS Client Support Center.

Note: When updating to release 4.0.60.4.4 of HIFIS, communities will have the opportunity to apply coordinated access consent to every client that currently has explicit consent on their installation. This is for communities who have already “bundled” consent using the existing explicit consent functionality. Choosing to opt-out of this option means that the community will need to manually add the coordinated access consent for each client separately, as applicable. The option will not present itself again in the future.

Please note that Microsoft has ended its support of SQL Server 2014 effective July 9th, 2024. As a result, the lowest version of SQL Server supported by HIFIS will be SQL Server 2016.

We strongly recommend upgrading to SQL Server 2016. Moving forward versions and releases of HIFIS require SQL Server 2016, and Microsoft will not be able to assist with any server related problems experienced using SQL Server 2014. For more information on SQL Server 2014 support, you can visit the Microsoft website. 

For communities that have not yet implemented HIFIS releases 4.0.58.1 or above, note that updating to HIFIS release 4.0.60.4.4 may have an impact on custom reports. This is due to changes to the database's underlying structure that were introduced in HIFIS release 4.0.58.1. Please consult release notes 4.0.58.1. for additional information on the affected tables.. Consult your report service provider if you have any issues.