What's New in Imprivata PatientSecure 6.12

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

New Features

Client UI Updated with Palm Enrollment Quality Score

Added a palm quality score to inform registrars whether the palm scan quality is high, medium, or low. Some patients with lower palm quality scores may occasionally have trouble with authentication depending on hand placement at the time of authentication.

The palm quality score appears on the Patients Enrolled Details Report and Patient Details page in the PatientSecure Admin Console, so that managers and administrators can consider this information during troubleshooting.

Client UI Notifies Registrar when a Left Palm is Scanned During Enrollment

New messaging in the Enrollment and Verify workflows that detects when a patient's left palm is being enrolled or verified.

BEST PRACTICE:

Imprivata recommends always using the patient's right palm, unless it is permanently unusable. In this case, the left palm is acceptable.

Improvements

Application Settings to Allow Manual Capture of Palm Scan

Added a setting to allow the registrar to manually start the patient's palm scan, so they can assist the patient with proper hand placement during enrollment.

Improved Messaging when Enrollment Scans Don't Match

Updated the Client UI with improved messaging when the enrollment scans don't match and the registrar needs to restart the enrollment process. The updated screens include tips for the registrar to help improve the palm scan quality.

Upgrade

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

Technology Updates

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 Application Servers

    • 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.12 (or later) environment, you must update the Linux Hub to version 2.0.0.42. No other Linux Hub releases are compatible with a PatientSecure 6.12 or later environment.

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