What's New in Imprivata PatientSecure 6.9

Imprivata PatientSecure® 6.9 contains the following new features and technology updates.

New Features

RDP Support

Added RDP Support to allow PatientSecure to run on remote machines. Requires forwarding of the palm vein scanner. Supports Azure Virtual Desktop single-user sessions only.

Display of Patient Preferred Names

During self-service workflows, patients viewing the PatientSecure match found screen on a kiosk want to see the name they prefer, so that they feel comfortable and have a more satisfying check-in experience.

Registrars viewing the PatientSecure match found screen want to see the patient’s preferred name, so that they can address the patient in a way that makes them comfortable.

Added support for patient's preferred first and last names in the following areas:

  • Registrar-facing Match Found

  • Epic Welcome Kiosk Match Found

  • Administrator Console Patient Details

Improvements

Scheduled Reporting Enhancements

PatientSecure Administrators want to be notified by email when a scheduled report runs, but they may not want to receive the report itself. This enhancement provides the option to email a notification regarding the outcome of a scheduled report only.

When a scheduled report fails, PatientSecure Administrators need to re-run that report using the same parameters as when the report was originally run. Instead of requiring the admin to remember and re-enter report parameters, this release provides the option to re-run a scheduled report using the same configured parameters.

Database Performance Improvements

Database structure and data access changes have been incorporated to improve performance. Reports run significantly faster, decreasing the time it takes for Registration Managers and PatientSecure Administrators to get the information they need.

Upgrade

For more information about upgrading to Imprivata PatientSecure 6.9, see the Imprivata Upgrade Help.

Technology Updates

System Requirements

  • PatientSecure Server Console

    • .NET Framework 4.8

    • ASP.NET Core Runtime 6.0.29 Runtime Hosting Bundle for Windows (or later), from the 6.0.x long term servicing (LTS) branch.

      IMPORTANT:

      ASP.NET Core Runtime 7.0.x Runtime & Hosting Bundle is not supported. Use 6.0.29 or a later release in the 6.0.x LTS branch.

    • Microsoft Visual C++ Redistributable package 2015, 2017, 2019, 2022 (x64)

    • Microsoft Visual C++ 2010 Redistributable Package (x64)

  • PatientSecure Application Servers

    • .NET Framework 4.8

    • ASP.NET Core Runtime 6.0.29 Runtime Hosting Bundle for Windows (or later), from the 6.0.x long term servicing (LTS) branch.

      IMPORTANT:

      ASP.NET Core Runtime 7.0.x Runtime Hosting Bundle is not supported. Use 6.0.29 or a later release in the 6.0.x LTS branch.

    • Microsoft Visual C++ Redistributable package 2015, 2017, 2019, 2022 (x64)

    • Microsoft Visual C++ 2010 Redistributable Package (x64)

  • PatientSecure Desktop Clients and Kiosks.

    • .NET Framework 4.8

    • ASP.NET Core Runtime 6.0.29 Runtime Hosting Bundle for Windows (or later), from the 6.0.x long term servicing (LTS) branch.

      IMPORTANT:

      ASP.NET Core Runtime 7.0.x Runtime Hosting Bundle is not supported. Use 6.0.29 or a later release in the 6.0.x LTS branch.

    • Microsoft Visual C++ Redistributable (x64) for Visual Studio 2015, 2017 and 2019.

    • Microsoft Visual C++ Redistributable (x86) for Visual Studio 2015, 2017 and 2019.

High Availability Support for Load Balancing

Imprivata PatientSecure supports high availability configurations using the following load balancer technologies:

  • Application Request Routing (ARR) on Microsoft’s IIS web server

  • Citrix ADC (formerly Netscaler) appliance

  • F5 BIG-IP GTM/LTM load balancers

Windows Kiosks - Authentication Header Requires Vendor Token

Beginning in PatientSecure 6.4, the Windows Kiosk API was updated to require the vendor token in the authentication header when using the PatientSecure Hub and Gateway components on Windows kiosks.

For more information, contact your Imprivata representative to obtain the Imprivata PatientSecure Windows Kiosk API Guide, v.2.0.

Patient Identifier API Tags Cannot Contain Spaces

PatientSecure EMR patient identifier API tags cannot have spaces in them when using the TCP/IP API. If such a tag does contain a space, a warning level log message is logged, indicating that an invalid character was used and that the patient identifier is excluded from the API response.

Linux Hub Compatibility

The PatientSecure Linux Hub has been updated to support preferred patient names.

If your Linux Hub will connect to a PatientSecure 6.9 (or later) environment, you must update the Linux Hub to version 2.0.0.476. Older Linux Hub releases are not compatible with a PatientSecure 6.9 or later environment.

For more information on qualifications and certifications, see Imprivata PatientSecure Supported Configurations.