Overview

Epic Electronic Health Record (EHR) systems are widely used in healthcare environments to manage patient data, clinical workflows, and hospital operations. Epic Hyperspace is the primary Windows-based client used by clinicians to access Epic applications.

Oloid Windows Login integrates with Epic EHR to provide fast and secure authentication for healthcare workstations. By using credentials such as Badge ID, Face, PIN, or NFC, clinicians can quickly authenticate to Windows devices and access Epic Hyperspace while maintaining strong identity verification.

When to Use This Integration

Epic EHR integration with Oloid Windows Login is typically used in healthcare environments where:

Clinicians need access to shared Windows workstations in hospitals or clinics.
Fast authentication is required to minimize disruption to patient care.
Organizations require secure passwordless authentication methods.
Badge-based or biometric authentication is preferred over traditional passwords.
Epic workflows require multi-user verification to complete sensitive actions.

Key Components of the Integration

This integration helps healthcare organizations reduce login time, improve clinical workflow efficiency, and maintain compliance with security requirements in shared workstation environments.

Oloid Windows Login

Oloid Windows Login enables passwordless authentication on Windows devices using credentials such as:

Face authentication
Badge ID
PIN
NFC / ID card

It securely verifies the user and grants access to the workstation.

Epic Hyperspace

Epic Hyperspace is the desktop client used by healthcare professionals to access Epic EHR applications on Windows systems.

After Windows authentication, clinicians can launch Hyperspace to access patient records and clinical workflows.

Epic Single Sign-On (SSO)

Epic SSO allows Epic applications to authenticate users through external authentication systems.

When integrated with Oloid Windows Login, clinicians can authenticate to Windows and access Epic workflows without repeatedly entering credentials.

Two-User Authentication

Certain clinical workflows require two-user authentication, where a second authorized user must verify a transaction using badge credentials.

Authentication Workflow

A typical Epic authentication workflow with Oloid Windows Login is as follows:

A clinician approaches a shared workstation.
The user authenticates to Windows using Oloid Windows Login (for example, using Badge ID or Face authentication).
Windows login is completed and the workstation session starts.
The clinician launches Epic Hyperspace.
The user must authenticate into Epic Hyperspace using Oloid Credentials.
The clinician can securely access Epic EHR functionality.

Deployment Architecture

The Epic EHR integration typically involves the following components:

Oloid Windows Login installed on Windows workstations
Epic Hyperspace client installed on the workstation
Epic SSO enabled in the Tenant Admin Portal
Epic EHR configuration completed in the Oloid platform

These components work together to enable secure and efficient authentication workflows for healthcare users.

Configuration Tasks

To deploy Epic EHR integration with Oloid Windows Login, complete the following configuration tasks:

Install Windows Authenticator (Healthcare).
Enable Epic SSO in the Tenant Admin Portal.
Install Epic Hyperspace on Windows workstations.
Configure Epic EHR integration settings in the Tenant Admin Portal.
Configure authentication workflows such as badge-based authentication and two-user authentication.