What's New in Imprivata PatientSecure 6.7 SP1

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

Improvements

Support for Language Country Codes

Support for Polish, Russian, and Chinese in Epic Kiosk using language-country codes.

Windows Kiosk Option to Disable Biometric Addition Workflow

Added a Windows Kiosk option to disable biometric addition workflow so that patients can quickly check in after they are successfully identified.

Streamline the Windows Kiosk Authentication Workflow

Modified the existing Windows Kiosk authentication workflow to eliminate one palm scan (the "hover" palm scan) so that patients can more quickly check in.

There will still be a hover palm scan if you set the Use old (I-Format) biometric scan to identify patients setting to OFF.

Retry Authentication in Cerner before Search and Create

When an authentication attempt fails, allows the registrar to try scanning the hand again before they enter the Search and Create workflow.

Upgrade

For more information about upgrading to Imprivata PatientSecure 6.7 SP1, 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

    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

    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.

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