Imprivata PatientSecure Supported Configurations and System Requirements

This section includes information about the system requirements for Imprivata PatientSecure®. Any limitations are noted in the support details or footnotes.

If a component is not listed, then its official status is "Not Supported".

• System Requirements

  • Database Server

  • Application Server

  • Load Balance Server

  • Communication Ports

  • Clients

• Supported Configurations

Related Documents

• Product Lifecycle Matrix — contains the lifecycle status of released versions of Imprivata products.

• Imprivata Maintenance and Support agreement — Items marked as no longer supported by the vendor have reached the end of their primary or mainstream support.

Maintained Versions

The following table includes all currently maintained versions of Imprivata PatientSecure. A listed version includes all service packs and hotfixes for each release.

For a complete accounting of release versions, see the Product Lifecycle Matrix.

Imprivata PatientSecure Version
PatientSecure 6.12 SP1
PatientSecure 6.12
PatientSecure 6.11
PatientSecure 6.10
PatientSecure 6.9
PatientSecure 6.8
PatientSecure 6.7 SP1

System Requirements

This section includes information about the system requirements for Imprivata PatientSecure®. Any limitations are noted in the support details or footnotes.

If a component is not listed, then its official status is "Not Supported".

Before you begin your Imprivata PatientSecure installation, review the hardware and software requirements for the server and client machines.

Database Server Requirements

The following requirements apply to Test and Production database servers:

Hardware

Item	Description
Operating System	Recommended: Windows Server 2016, Windows Server 2019, or Windows Server 2022
Processor	Recommended: 2x 64-bit Quad-Core Intel Xeon Processor (x64 processor) or greater Minimum: 1x 64-bit Quad-Core Intel Xeon Processor (x64 processor)
	Test Server	Production Server
Memory	Recommended: 32 GB RAM or greater Minimum: 4 GB RAM	Recommended: 64 GB RAM or greater Minimum: 16 GB RAM
Available Disk Space	Solid-state drives (SSD) highly recommended Recommended: 500 GB or greater (data partition) Minimum: 40 GB	Solid-state drives (SSD) highly recommended Recommended: 500 GB or greater (data partition) Minimum: 100 GB

Software

Item	Description
Software	Recommended: Microsoft SQL Server 2016 Enterprise edition Microsoft SQL Server 2017 Enterprise edition Microsoft SQL Server 2019 Enterprise edition Microsoft SQL Server 2022 Enterprise edition Minimum: Microsoft SQL Server 2016, 2017, 2019 or 2022 Standard Edition (64-bit), including SQL Server Management Studio (SSMS)
Environment	Can be part of Shared or Consolidated environment
Privileges	A user with Sysadmin privileges to install the PatientSecure database.

Application Server Requirements

There are two approaches to installing Imprivata PatientSecure application servers:

• Single-server configuration: all Imprivata PatientSecure services are installed on a single application server.

• Multi-server configuration: Imprivata PatientSecure services are installed over two or more application servers, with a Load Balance server handling access to the services and providing failover support.

  For more information, see Imprivata PatientSecure High Availability Support for Load Balancing in the PatientSecure Online Help.

The following requirements apply to application servers:

Hardware

Item	Description
Operating System	Recommended: Windows Server 2016, Windows Server 2019, or Windows Server 2022
Processor	Recommended: 2x 64-bit Quad-Core Intel Xeon Processor (x64 processor) or greater Minimum: 1x 64-bit Quad-Core Intel Xeon Processor (x64 processor)
	Test Server	Production Server
Memory	Recommended: 32 GB RAM or greater Minimum: 4 GB RAM	Recommended: 32 GB RAM or greater Minimum: 16 GB RAM
Available Disk Space	Recommended: 100 GB Minimum: 20 GB	Recommended: 100 GB Minimum: 50 GB

Certificates

Use third-party SSL certificates to encrypt the traffic when connecting to PatientSecure Application server components.

• The certificates must use a fully qualified domain name (FQDN).

• Production PatientSecure environments must use third-party SSL certificates. Self-signed certificates generated by PatientSecure should only be used in test environments.

Software

Item	Description
Microsoft .NET Framework	Microsoft .NET Framework 4.8
Microsoft Visual C++ Redistributable Packages	Microsoft Visual C++ Redistributable package 2015, 2017, 2019, 2022 (x64) Microsoft Visual C++ 2010 Redistributable Package (x64)
PowerShell	PowerShell 3
Additional Software	PatientSecure 6.10 and later: ASP.NET Core Runtime 8.0.6 Runtime Hosting Bundle for Windows (or later), from the 8.0.x long term servicing (LTS) branch. PatientSecure Emergency Search 6.10 and later: ASP.NET Core Runtime 8.0.6 Runtime Hosting Bundle for Windows (or later), from the 8.0.x long term servicing (LTS) branch. 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 Core Runtime 6.0.29 or later will prevent the Palm Vein Authentication Service from starting. NOTE: ASP.NET Core Runtime 7.0.x Runtime & Hosting Bundle is not supported. PatientSecure 6.7 to 6.9: ASP.NET Core Runtime 6.0.29 Runtime Hosting Bundle for Windows (or later), from the 6.0.x long term servicing (LTS) branch. NOTE: ASP.NET Core Runtime 7.0.x Runtime & Hosting Bundle is not supported. Microsoft URL Rewrite Module 2.1 for IIS
Roles and Features - Windows Server 2016, 2019, and 2022	Install the following IIS components from the Roles and Features Wizard: NOTE: Adding the Web Server (IIS) role adds many features by default; the following list indicates exceptions to the default features that you must configure. For more information on Web Server (IIS) features, see your Windows Server documentation. Web Server Common HTTP features NOTE: In Common HTTP features, ensure that the WebDAV Publishing feature is not enabled. Performance Security Application Development Management Tools .Net Framework 3.5 features .Net Framework 4.6 features Windows Powershell

PatientSecure Admin Console and Server Console Requirements

The following requirements apply to accessing the PatientSecure Admin Console and Server Console from a workstation. If a component is not listed, then its official status is "Not Supported".

Item	Description
Screen resolution	1400 x 900 or higher resolution
Browsers	Microsoft Edge Chromium Google Chrome

Load Balance Server Requirements

Supported Load Balancer Technologies

Item	Description
Microsoft IIS with ARR	All maintained PatientSecure releases
Citrix ADC (formerly NetScaler)	All maintained PatientSecure releases
F5 BIG-IP GTM/LTM	All maintained PatientSecure releases

Microsoft IIS with ARR

The following requirements apply to Microsoft IIS-based Load Balance servers in a multi-server load balanced Imprivata PatientSecure environment.

For other load balancer technologies, follow the system requirements of your manufacturer.

Hardware

Item	Description
Operating System	Recommended: Windows Server 2016, Windows Server 2019, or Windows Server 2022
Processor	1x 64-bit Quad-Core Intel Xeon Processor (x64 processor)
Memory	Recommended: 4 GB RAM Minimum: 2 GB RAM
Available Disk Space	Recommended: 50 GB Minimum: 20 GB
Peripherals	Uninterruptible Power Supply (UPS) highly recommended for Load Balance or VM hosts

Software

Item	Description
PatientSecure Server Console component	Imprivata recommends that the PatientSecure Server Console be installed on the Load Balancer server to keep it separate from the PatientSecure application servers, to ensure service reliability. Required software is listed below:
Microsoft .NET Framework	Microsoft .NET Framework 4.8
Microsoft Visual C++ Redistributable Packages	Microsoft Visual C++ Redistributable package 2015, 2017, 2019, 2022 (x64) Microsoft Visual C++ 2010 Redistributable Package (x64)
	PatientSecure 6.10 and later: ASP.NET Core Runtime 8.0.6 Runtime Hosting Bundle for Windows (or later), from the 8.0.x long term servicing (LTS) branch. PatientSecure Emergency Search - 6.10 and later: ASP.NET Core Runtime 8.0.6 Runtime Hosting Bundle for Windows (or later), from the 8.0.x long term servicing (LTS) branch. 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 Core Runtime 6.0.29 or later will prevent the Palm Vein Authentication Service from starting. NOTE: ASP.NET Core Runtime 7.0.x Runtime & Hosting Bundle is not supported. PatientSecure 6.7 to 6.9: ASP.NET Core Runtime 6.0.29 Runtime Hosting Bundle for Windows (or later), from the 6.0.x long term servicing (LTS) branch. NOTE: ASP.NET Core Runtime 7.0.x Runtime & Hosting Bundle is not supported.

Certificates in High Availability Environments

Third-party certificates used by the load balancer in a High Availability server configuration must have a Subject Alternative Name (SAN).

• Production PatientSecure environments must use third-party SSL certificates. Self-signed certificates generated by PatientSecure should only be used in test environments.

Active Directory

PatientSecure user access is determined by Active Directory groups on the Active Directory server.

Take note of the following Active Directory information for use during PatientSecure environment configuration.

Active Directory Information

Item	Description
Domain Name	The domain name of the Active Directory server.
Container	The container name for organization units (OU), if any.
AD Account Name	The name of the domain administrator on the Active Directory.
AD Account Password	The password for the Active Directory domain administrator account.

Active Directory Groups

In Active Directory, define one or more groups for PatientSecure administrative users. For more information on the user groups and how they are used in the PatientSecure Admin Console, see the PatientSecure help.

Active Directory Group	Permissions in Admin Console	PatientSecure Release
Owners	Full access to the PatientSecure Admin Console	All maintained PatientSecure versions
Administrators	System notifications Patient records Report data Configuring location permissions Edit scheduled reports View PatientSecure license.	All maintained PatientSecure versions
Users	Access to the Dashboard and report data.	All maintained PatientSecure versions

Communication Ports

Imprivata PatientSecure uses a variety of ports for communication between its components.

Database Server Ports

This port must be open on the database server:

Default Port	Direction	Description
1433	Inbound	SQL Server

Application Server Ports

These ports must be open on application servers:

Default Port	Description
7001	Communication between the PatientSecure Identity Server (PSIS) component and the client components - PatientSecure, PatientSecure Hub and Toolbar.
7002	Communication between the PatientSecure Web Services (PSWS) component and the client components - PatientSecure, PatientSecure Hub and Toolbar.
7003	Communication between the PatientSecure User Interface server component and the client components.
7004	Communication for the PatientSecure Reporting Service.
7005, 7006	Communication for the PatientSecure Emergency Search & Palm Vein Authentication Service.
7007	Communication for the PatientSecure System Health Service, that powers the PatientSecure System Health Dashboard in the Admin Console.
2244	PatientSecure HL7 Service

Ports for Optional Application Server Services

PatientSecure introduces several optional application server services that are dependent on your environment's integration with several external systems.

Reserve one or more ports in the 7000 range, after the required PatientSecure service ports listed above.

The port numbers are dependent on the order of component installation in your environment. Your PatientSecure environment may be different.

For more information, see the PatientSecure Online Help.

Example Port	Description
7008	PatientSecure FHIR Service - communication to the HL7 FHIR API.
7009	PatientSecure EMPI Service.

Website Application Server Ports

These ports must be open on the Website application servers.

Default Port	Direction	Description
80, 443	Inbound	PatientSecure Admin Console site. NOTE: You cannot configure alternate ports for Admin Console.
7000	Inbound	PatientSecure Server Console site.
443	Outbound	PatientSecure Site Monitor.

Client Ports

These ports must be open on client machines.

Port	Direction	Description
2244	Local	Communication with the PatientSecure Web Services (PSWS) and Identity Services (PSIS) components.
8081	Inbound	Communication between the PatientSecure Gateway on the client and the PatientSecure Web Services (PSWS) component.
8082	Outbound	Communication between the PatientSecure Gateway on the client and the PatientSecure Web Services (PSWS) component.
8083	Local	Communication between the PatientSecure Hub and the PatientSecure client on the local machine.

Client Requirements

The following requirements apply to client machines. If a component is not listed, then its official status is "Not Supported".

Registration Desktop Requirements

Item	Descriptions
Operating System	Windows 11 ( x64) - all versions Windows 10 (x32 or x64) - all versions through Windows 10, October 2022 Update / version 22H2
Processor	Recommended: Intel Quad Core i5 2.5 GHz or greater with 4 GB of RAM Minimum: Intel Pentium Dual Core - 2.0 GHz processor or faster with at least 2 GB of RAM
Available Disk Space	Recommended: 6 GB Minimum: 1.5 GB
Display and Peripherals	1400 x 900 or higher-resolution monitor Microsoft Mouse or compatible pointing device Keyboard USB 2.0 or 3.0 ports
Microsoft Visual C++ Redistributable Package	Microsoft Visual C++ Redistributable (x64) for Visual Studio 2015, 2017 and 2019. Microsoft Visual C++ Redistributable (x86) for Visual Studio 2015, 2017 and 2019.
Additional Software	PatientSecure 6.10 and later: ASP.NET Core Runtime 8.0.6 Runtime Hosting Bundle for Windows (or later), from the 8.0.x long term servicing (LTS) branch. PatientSecure 6.7 to 6.9: ASP.NET Core Runtime 6.0.29 Runtime Hosting Bundle for Windows (or later), from the 6.0.x long term servicing (LTS) branch. NOTE: ASP.NET Core Runtime 7.0.x Runtime & Hosting Bundle is not supported. .Net Framework 4.8

Registration Kiosk Requirements

Item	Description
Operating System	Windows 11 ( x64) - all versions Windows 10 (x32 or x64) - all versions through Windows 10, October 2022 Update / version 22H2
Processor	Recommended: Intel Quad Core i5 2.5 GHz or greater with 4 GB of RAM Minimum: Intel Pentium Dual Core - 2.0 GHz processor or faster with at least 2 GB of RAM
Available Disk Space	Recommended: 6 GB Minimum: 1.5 GB
Microsoft Visual C++ Redistributable Package	Microsoft Visual C++ Redistributable (x64) for Visual Studio 2015, 2017 and 2019. Microsoft Visual C++ Redistributable (x86) for Visual Studio 2015, 2017 and 2019.
Additional Software	PatientSecure 6.10 and later: ASP.NET Core Runtime 8.0.6 Runtime Hosting Bundle for Windows (or later), from the 8.0.x long term servicing (LTS) branch. PatientSecure 6.7 to 6.9: ASP.NET Core Runtime 6.0.29 Runtime Hosting Bundle for Windows (or later), from the 6.0.x long term servicing (LTS) branch. NOTE: ASP.NET Core Runtime 7.0.x Runtime & Hosting Bundle is not supported. .Net Framework 4.8
Display and Peripherals	1440 x 900 or higher resolution monitor Microsoft Mouse or compatible pointing device Keyboard USB 2.0 or 3.0 ports

Palm Scanner Requirements

Vendor	Driver	Device	PatientSecure Release
Fujitsu	Fujitsu F-Pro extended drivers	Keyo hand guide with the Fujtsu F-Pro palm vein scanner (Also known as the Fujitsu F-pro sensor or the M5 sensor)	All maintained PatientSecure versions

Supported Configurations

This section includes information about the supported configurations for Imprivata PatientSecure®. Any limitations are noted in the support details or footnotes.

If a component is not listed, then its official status is "Not Supported".

Electronic Medical Record Systems and Hospital Systems

Imprivata PatientSecure supports all electronic medical record (EMR) systems and hospital information systems (HIS) through either direct API-based integrations or third-party integrations.

API-based Solutions

Imprivata PatientSecure integrates with the following EMR and HIS solutions directly using an API.

Vendor and EMR/HIS	Versions Supported	PatientSecure Version
Cerner Millennium	2010, 2012, 2015, 2018	All maintained PatientSecure versions
Cerner Soarian	4.2.300	All maintained PatientSecure versions
Epic - Cadence and Prelude	Epic February 2019 and later1 New versions of Epic do not require updates to the PatientSecure API integration, and are therefore fully supported. Epic November 2018 Epic August 20182 In mid-2018, Epic altered its software distribution model from a yearly release to a quarterly release of new Epic and Epic Welcome Kiosk software. The PatientSecure client installation directory location defaults to the latest release of Epic and Epic Kiosk available at the time of the PatientSecure release. Epic 20183 PatientSecure includes client installation program options for installing the Epic Integration 2018 component.	All maintained PatientSecure versions
Epic - Cadence and Prelude	2012, 2014, 2015, 2017	All maintained PatientSecure versions
Epic Community Connect		All maintained PatientSecure versions
McKesson HealthQuest	18.x (minimum)	All maintained PatientSecure versions
McKesson Paragon	12.x (minimum)	All maintained PatientSecure versions
McKesson Practice Plus	13.0 (October maintenance, minimum)	All maintained PatientSecure versions
McKesson STAR	19.x (minimum)	All maintained PatientSecure versions
MEDITECH Expanse 2.1: Acute Environment - requires the use of the MEDITECH Client application REG and EDM MEDITECH Expanse does not have an integration in place for Ambulatory Environment	2.1	All maintained PatientSecure versions
MEDITECH 6.15 - ADM and EDM only	6.15.30	All maintained PatientSecure versions
MEDITECH 6.16 - ADM and EDM - Thick client	6.16	All maintained PatientSecure versions

EMPI Integrations

PatientSecure supports the following enterprise master patient index (EMPI) integrations:

Vendor and EMR/HIS	Versions Supported	PatientSecure Version
IBM Initiate	10.1 11.6	All maintained PatientSecure versions
Verato Universal MPI		All maintained PatientSecure versions

Third-party Integrations

Imprivata PatientSecure supports the following third-party integrations using Toolbar from IPeople:

Vendor and EMR/HIS	Versions Supported	PatientSecure Version
MEDITECH C/S	5.6.x, 6.0	All maintained PatientSecure versions
MEDITECH Magic	5.6x	All maintained PatientSecure versions

Kiosk Solutions

Imprivata PatientSecure supports the following kiosk systems:

Epic Welcome Kiosk

Versions Supported	PatientSecure Version	Notes
May 2019 February 2019 November 2018 August 20184 Beginning in 2018, Epic altered its software distribution model from a yearly release to a quarterly release of new Epic and Epic Welcome Kiosk software. The PatientSecure client installation directory location defaults to the latest release of Epic and Epic Kiosk available at the time of the PatientSecure release. 2018	All maintained PatientSecure versions 5 PatientSecure includes client installation program options for installing the Epic Kiosk 2018 component.
2014, 2015, 2017	All maintained PatientSecure versions	Support for Epic Welcome on 32-bit and 64-bit kiosks.

Language Support for Epic Welcome Kiosk

Language	PatientSecure Version
Chinese	All maintained PatientSecure versions
Polish	All maintained PatientSecure versions
Russian	All maintained PatientSecure versions
Spanish	All maintained PatientSecure versions

PatientWorks

Versions Supported	PatientSecure Version	Notes
	All maintained PatientSecure versions	Support for PatientWorks on 32-bit and 64-bit kiosks.

Vecna

Versions Supported	PatientSecure Version
	All maintained PatientSecure versions

Operating Systems

Imprivata PatientSecure supports the following operating systems. If a component is not listed, then its official status is "Not Supported".

Operating System	Support Information
Windows 11 (x64) - all versions	Yes
Windows 10 (x32 or x64) - all versions through Windows 10, October 2022 Update / version 22H2	Yes
Windows Server 2022	Yes
Windows Server 2019	Yes
Windows Server 2016	Yes

Browsers

The following browsers are supported for accessing the Imprivata PatientSecure Admin Console.

Browser	Support Information
Microsoft Edge Chromium version 85 or later	Yes
Firefox 48.0 and later	Yes
Google Chrome 52.0.2743.82 and later	Yes

Virtual Desktop Infrastructure Support

Imprivata PatientSecure supports the following client configurations:

• Full: Client machines with Windows running locally as the primary desktop.

• Thin: Client machine with Windows installed but not running as the primary desktop; instead, the client is leveraging a virtual desktop that is pushed to the endpoint.

• Zero: Client machine without a local operating system installed; instead, the client is leveraging a virtual desktop that is pushed to the endpoint.

The following sections describe the Virtual Desktop Infrastructure configurations for the Imprivata PatientSecure components :

• EMR: The source electronic medical records system.

• PatientSecure Hub: The point of integration between the biometric scanner and the client endpoints.

• PatientSecure Client: The user interface.

• PatientSecure Gateway: The service that exposes APIs for communication between PatientSecure and integrating applications.

• PatientSecure Toolbar: Imprivata PatientSecure icons that reside on the desktop for access to applications profiled with the Imprivata Application Profile Generator (APG).

Imprivata PatientSecure components may run on the client machine (Local), on the virtual desktop (Host), or on a virtual application.

Full Client

Palm installations support Full clients running Windows:

EMR	Hub	Client	Gateway	Toolbar
Local	Local	Local	Local	Local
Citrix Virtual Apps	Local	Local	Local	XenApp
Omnissa (VMware) Horizon published apps	Local	Local	Local	Horizon Published app

Thin Client

Palm installations support Thin clients running Windows:

EMR	Hub	Client	Gateway	Toolbar
Omnissa (VMware) Horizon	Host	Host	Host	Host
Citrix Virtual Apps and Desktops	Host	Host	Host	Host

Zero Client

Palm installations support the following Zero clients:

EMR	Hub	Client	Gateway	Toolbar
Omnissa (VMware) Horizon	Host	Host	Host	Host
Citrix Virtual Apps and Desktops	Host	Host	Host	Host

Virtual Desktop Infrastructure Systems

Citrix Virtual Environments

Citrix Virtual Apps and Desktops

Formerly known as XenDesktop and XenApp.

Version	PatientSecure Version
7 2411	All maintained PatientSecure versions
7 2402 LTSR	All maintained PatientSecure versions
7 2311	All maintained PatientSecure versions
7 2308	All maintained PatientSecure versions
7 2305	All maintained PatientSecure versions
7 2303	All maintained PatientSecure versions
7 2302	All maintained PatientSecure versions
7 2212	All maintained PatientSecure versions
7 2209	All maintained PatientSecure versions
7 2203 LTSR	All maintained PatientSecure versions
7 1912 LTSR	All maintained PatientSecure versions

Omnissa Virtual Environment Support

Omnissa Horizon

Formerly VMware Horizon.

All zero clients with the Tera2 chipset and the latest firmware are supported.

Omnissa Horizon Version	PatientSecure Version
8 2406	All maintained PatientSecure versions
8 2312	All maintained PatientSecure versions
8 2309	All maintained PatientSecure versions
8 2306	All maintained PatientSecure versions
8 2303	All maintained PatientSecure versions
8 2212	All maintained PatientSecure versions
8 2209	All maintained PatientSecure versions
8 2206	All maintained PatientSecure versions
8 2203	All maintained PatientSecure versions
8 2111	All maintained PatientSecure versions
8 2012	All maintained PatientSecure versions

Omnissa Horizon Client for Windows

Horizon Client for Windows Version	PatientSecure Version
8 2309	All maintained PatientSecure versions
8 2306	All maintained PatientSecure versions
8 2303	All maintained PatientSecure versions
8 2212	All maintained PatientSecure versions
8 2209	All maintained PatientSecure versions
8 2206	All maintained PatientSecure versions
8 2203	All maintained PatientSecure versions
8 2111	All maintained PatientSecure versions
8 2106	All maintained PatientSecure versions
8 2103	All maintained PatientSecure versions
8 2012 (8.1)	All maintained PatientSecure versions
3.5	All maintained PatientSecure versions
3.4	All maintained PatientSecure versions