What's New in Imprivata PatientSecure 6.13

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

Improvements

Opt-Out Workflows

The opt-out workflows have been updated to allow registrars a quick and easy process to specify why the patient or registrar opts out of using PatientSecure.

  • The Admin Console has been updated to allow the creation of additional opt-out reasons and a method for selecting an appropriate category of opt-out reasons.

  • The PatientSecure user interface has been updated to allow registars to view the last opt-out reason and date on the Verify screen during scheduled patient workflows.

Application Settings for Emergency Search

Added Emergency Search application settings to the PatientSecureAdmin Console to allow administrators to tune the behavior of Emergency Search to their organization's needs.

  • Age range - The number of years Emergency Search will scan looking for potential matches.

  • Candidate pool size - The number of potential match candidates analyzed per server request.

CAUTION:

Changing the settings for Emergency Search may impact the performance of your environment. Contact Imprivata Support for guidance.

Upgrade

For more information about upgrading to Imprivata PatientSecure 6.13, see the Imprivata Upgrade portal.

Technology Updates

The following changes have been made to the system requirements and supported configurations.

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

System Requirements

  • PatientSecure Server Console

    • ASP.NET Core Runtime 8.0.6 Runtime Hosting Bundle for Windows or later

    • .NET Framework 4.8

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

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

  • PatientSecure Database Server

    • Support for Windows Server 2025

  • PatientSecure Application Servers

    • Support for Windows Server 2025

    • ASP.NET Core Runtime 8.0.6 Runtime Hosting Bundle for Windows or later

    • .NET Framework 4.8

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

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

  • PatientSecure Application Server - PatientSecure Emergency Search & Palm Vein Authentication Service

    • In addition to the Application Server requirements above, the Emergency Search component requires the installation of ASP.NET Core Runtime 6.0.29 Hosting Bundle for Windows or later, from the 6.0.x long term servicing (LTS) branch.

      Failure to install the ASP.NET 6.0.29 or later will prevent the Palm Vein Authentication Service from starting.

      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.

  • PatientSecure Desktop Clients and Kiosks.

    • ASP.NET Core Runtime 8.0.6 Runtime Hosting Bundle for Windows or later

    • .NET Framework 4.8

    • 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

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 several new features.

If your Linux Hub will connect to a PatientSecure 6.13 (or later) environment, you must update the Linux Hub to version 2.0.0.43. No other Linux Hub releases are compatible with a PatientSecure 6.13 or later environment.