Imprivata Confirm ID

Name: Imprivata Confirm ID
Brand: Imprivata
Rating: 4.5 (58 reviews)

Simple and secure access management for mission-critical industries

Est 2000|Valuation $492.5M|Raised $2.6B

LinkedIn 28K|Website|Web traffic 466K|FTEs 833|HQ Waltham, Massachusetts, US

MarketsIdentity Provider (IdP) & Single Sign-On (SSO)

Published Jul 15, 2026

01Common complaints

- If the requirement is only generic MFA for VPN/SaaS without shared-workstation clinical workflows: cloud-first MFA/SSO products may be cheaper and faster to deploy. - If the organization is highly cost-sensitive and does not need extensive clinical workflow integration: hardware and licensing can increase total cost. - If transparent, per-user list pricing and simple cloud procurement are primary procurement criteria: Confirm ID/EAM pricing is typically quote-based. - If the workforce relies heavily on heterogeneous Android devices and push notification reliability cannot be tolerated: community reports indicate some device/OS combinations have inconsistent push delivery. - If the organization lacks expertise in VDI (Citrix/VMware) and Kerberos configuration but requires deep VDI integration: implementation and troubleshooting may require external expertise.

Deal disqualifiers (poor fit)

Small organizations that only need basic MFA for a small number of SaaS applications
Environments that cannot support endpoint agents/appliances or will not deploy badge hardware
Teams that require modern, self-serve QR/link enrollment flows and minimal helpdesk involvement

Known limitations evidenced in reviews/community

Administrative enrollment limitations reported by some reviewers (for example, constrained options to enroll users from the admin console or to use QR/link-based registration for certain deployments).
Password synchronization and credential update edge cases after password changes.
Browser and compatibility concerns in legacy environments.
VDI integration complexity (Citrix StoreFront behaviors, Kerberos/keytabs), as discussed in community threads.

Vendor-documented constraints

Confirm ID API access can be disabled by default and requires explicit enabling; a ‘Restricted’ API mode blocks certain password-related resources and returns 403 responses, which can constrain integrations.
Product lifecycle matrices and end-of-maintenance notices are published by the vendor; buyers should confirm they are deploying supported versions.

Roadmap / forward-looking

A February 2026 press release for the broader EAM portfolio described context-aware passwordless authentication, identity verification, and analytics added to the product family; that messaging applies to EAM generally and is not a Confirm ID–only roadmap commitment unless otherwise specified by the vendor.

Why some customers leave / churn reasons (signals)

Public signals and reviewer comments suggest potential churn drivers such as higher total cost relative to simpler MFA-only solutions, administrative friction with enrollment and method changes, and mobile push reliability issues on certain devices.

02Why they buy

Key differentiators described in vendor and review materials (rewritten in neutral terms): - Authentication workflows tailored to healthcare contexts, including badge-based re-authentication and shared-workstation scenarios. - EPCS-oriented identity proofing and enrollment workflows, and reporting capabilities intended to support controlled-substance prescription audit requirements. - A vendor feature described as automating OTP retrieval from the Imprivata ID application to reduce manual entry in some workflows. The vendor frames this as a convenience feature for clinical contexts. Balanced caveat: - Some vendor marketing language about workflow performance and speed should be validated in pilot testing under production conditions (for example, in the presence of RF/Bluetooth constraints and device management policies).

03Field reports

Review-platform sentiment (G2, TrustRadius)

Because Confirm ID is now commonly folded into Imprivata Enterprise Access Management branding, most public review content is under EAM/OneSign rather than Confirm ID alone. G2 (Imprivata Enterprise Access Management): - Overall rating shown on the vendor's review page: a high score with a modest review sample. - Positive themes noted by reviewers: time savings in clinical settings and SSO convenience across multiple applications. - Negative themes noted by reviewers: administrative enrollment limitations (for example, inability to enroll a user directly from the admin console in certain configurations), password synchronization challenges after password changes, and difficulties obtaining historical activity reporting in some deployments. Some reviews referenced browser compatibility issues in older environments. TrustRadius (Imprivata Enterprise Access Management): - TrustRadius lists EAM (formerly OneSign & Confirm ID) with a score presented on the site and a set of reviews; detailed review text requires examining individual entries.

Community / social feedback (Reddit)

Reddit threads and other community posts highlight operational issues observed by administrators and end users: - Push notification reliability problems reported on certain Android devices, which can affect remote access workflows. - Perceived high cost for smaller organizations that only need a subset of the full EAM capabilities. - Complexity in VDI environments (Citrix/VMware Horizon) with configuration and troubleshooting tasks that require specialized knowledge.

Gartner Peer Insights

A Gartner Peer Insights page exists for Imprivata Enterprise Access Management; access to full content is often restricted. Snippets for the reviews page were visible during this research run.

Why customers choose it (inferred from reviews and positioning)

Fit for healthcare workflows: badge tap and faster re-authentication for clinicians, reducing reliance on passwords in patient-care workflows.
Compliance orientation: reviewers reference HIPAA-focused security and features designed for healthcare contexts.

Vendor-published case study (example)

Imprivata publishes customer case studies that describe outcomes such as increased e-prescribing activity after implementing Confirm ID for EPCS.

Critical evaluation:

Vendor-published case studies provide useful examples but may not supply full methodological detail. Buyers should request supporting measurement definitions, time windows, number of sites/providers, and confirmation of whether concurrent workflow or policy changes affected the outcomes.

Notable gap: independent case studies

No independent third-party case study with audited metrics was identified in the sources accessed during this research session.

04Best fit

Company sizes

Typically best fit for mid-market to enterprise healthcare organizations — often larger, multi-site hospitals and clinic networks where shared workstations and VDI are common.

Industries / verticals

Hospitals and health systems
Ambulatory clinics with EPCS requirements
Healthcare IT and managed clinical environments

Roles and personas

Decision makers: CIO, CISO, VP IT, Director of Clinical Informatics, Identity & Access Management leads
End users: clinicians (physicians, nurses, pharmacists), registration staff, revenue-cycle staff
Implementers: VDI engineers (Citrix/VMware), endpoint engineering, IAM administrators

Pain points addressed

Password fatigue and frequent re-authentication in patient-care workflows
Need for DEA-compliant, auditable EPCS authentication
Securing remote access while attempting to minimize user interruption

Qualification criteria (good fit)

Organizations with a high volume of shared workstations and roaming users
Need for badge-based tap-and-go workflows
EPCS is a driving use case or other high-assurance signing workflows are required

05The pitch

What the product does (core value proposition)

Imprivata Confirm ID is an enterprise identity and strong authentication capability historically positioned for healthcare—notably for DEA-compliant electronic prescribing of controlled substances (EPCS) and other high-assurance clinical workflows. In current packaging, Confirm ID is commonly discussed as part of (or formerly alongside) Imprivata OneSign under the broader Enterprise Access Management (EAM) product family, combining SSO, MFA, and workflow-oriented authentication for shared workstations, virtual desktops (Citrix/VMware), and EHR/clinical applications. Imprivata has published product rename guidance indicating OneSign/Confirm ID were rebranded into Enterprise Access Management. Key Confirm ID capabilities evidenced in documentation and datasheets include: - MFA/strong authentication methods (push, OTP/soft token, integrations) and workflow-specific policies. - Identity proofing and enrollment paths for EPCS, including integration with certificate authorities. - Clinical workflow integrations (e.g., Epic/Cerner contexts highlighted on vendor pages and datasheets). - Remote access MFA integrations such as VMware Horizon guidance in product documentation.

Target market and positioning

- Primary: Mid-to-large healthcare delivery organizations (IDNs, hospitals, large clinics) with shared endpoints, clinician roaming, EHR re-authentication, and EPCS needs. - Secondary: Other regulated environments needing shared-device SSO/MFA and badge-based workflows—though many market signals and customer discussion emphasize healthcare as the core. Market positioning themes (restated in neutral terms): - Authentication designed to reduce interruptions to clinician workflows compared with generic MFA products. - Audit trails intended to support compliance requirements for controlled substance prescribing and clinical access.

Get a comprehensive analysis of Imprivata Confirm ID including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published Jul 15, 2026

01Common complaints

If the requirement is only generic MFA for VPN/SaaS without shared-workstation clinical workflows: cloud-first MFA/SSO products may be cheaper and faster to deploy.
If the organization is highly cost-sensitive and does not need extensive clinical workflow integration: hardware and licensing can increase total cost.
If transparent, per-user list pricing and simple cloud procurement are primary procurement criteria: Confirm ID/EAM pricing is typically quote-based.
If the workforce relies heavily on heterogeneous Android devices and push notification reliability cannot be tolerated: community reports indicate some device/OS combinations have inconsistent push delivery.
If the organization lacks expertise in VDI (Citrix/VMware) and Kerberos configuration but requires deep VDI integration: implementation and troubleshooting may require external expertise.

Deal disqualifiers (poor fit)

Small organizations that only need basic MFA for a small number of SaaS applications
Environments that cannot support endpoint agents/appliances or will not deploy badge hardware
Teams that require modern, self-serve QR/link enrollment flows and minimal helpdesk involvement

Known limitations evidenced in reviews/community

Administrative enrollment limitations reported by some reviewers (for example, constrained options to enroll users from the admin console or to use QR/link-based registration for certain deployments).
Password synchronization and credential update edge cases after password changes.
Browser and compatibility concerns in legacy environments.
VDI integration complexity (Citrix StoreFront behaviors, Kerberos/keytabs), as discussed in community threads.

Vendor-documented constraints

Confirm ID API access can be disabled by default and requires explicit enabling; a ‘Restricted’ API mode blocks certain password-related resources and returns 403 responses, which can constrain integrations.
Product lifecycle matrices and end-of-maintenance notices are published by the vendor; buyers should confirm they are deploying supported versions.

Roadmap / forward-looking

Why some customers leave / churn reasons (signals)

02Why they buy

Key differentiators described in vendor and review materials (rewritten in neutral terms):

Authentication workflows tailored to healthcare contexts, including badge-based re-authentication and shared-workstation scenarios.
EPCS-oriented identity proofing and enrollment workflows, and reporting capabilities intended to support controlled-substance prescription audit requirements.
A vendor feature described as automating OTP retrieval from the Imprivata ID application to reduce manual entry in some workflows. The vendor frames this as a convenience feature for clinical contexts.

Balanced caveat:

Some vendor marketing language about workflow performance and speed should be validated in pilot testing under production conditions (for example, in the presence of RF/Bluetooth constraints and device management policies).

03Field reports

Review-platform sentiment (G2, TrustRadius)

Because Confirm ID is now commonly folded into Imprivata Enterprise Access Management branding, most public review content is under EAM/OneSign rather than Confirm ID alone.

G2 (Imprivata Enterprise Access Management):

Overall rating shown on the vendor's review page: a high score with a modest review sample.
Positive themes noted by reviewers: time savings in clinical settings and SSO convenience across multiple applications.
Negative themes noted by reviewers: administrative enrollment limitations (for example, inability to enroll a user directly from the admin console in certain configurations), password synchronization challenges after password changes, and difficulties obtaining historical activity reporting in some deployments. Some reviews referenced browser compatibility issues in older environments.

TrustRadius (Imprivata Enterprise Access Management):

TrustRadius lists EAM (formerly OneSign & Confirm ID) with a score presented on the site and a set of reviews; detailed review text requires examining individual entries.

Community / social feedback (Reddit)

Reddit threads and other community posts highlight operational issues observed by administrators and end users:

Push notification reliability problems reported on certain Android devices, which can affect remote access workflows.
Perceived high cost for smaller organizations that only need a subset of the full EAM capabilities.
Complexity in VDI environments (Citrix/VMware Horizon) with configuration and troubleshooting tasks that require specialized knowledge.

Gartner Peer Insights

A Gartner Peer Insights page exists for Imprivata Enterprise Access Management; access to full content is often restricted. Snippets for the reviews page were visible during this research run.

Why customers choose it (inferred from reviews and positioning)

Fit for healthcare workflows: badge tap and faster re-authentication for clinicians, reducing reliance on passwords in patient-care workflows.
Compliance orientation: reviewers reference HIPAA-focused security and features designed for healthcare contexts.

Vendor-published case study (example)

Imprivata publishes customer case studies that describe outcomes such as increased e-prescribing activity after implementing Confirm ID for EPCS.

Critical evaluation:

Vendor-published case studies provide useful examples but may not supply full methodological detail. Buyers should request supporting measurement definitions, time windows, number of sites/providers, and confirmation of whether concurrent workflow or policy changes affected the outcomes.

Notable gap: independent case studies

No independent third-party case study with audited metrics was identified in the sources accessed during this research session.

04Best fit

Company sizes

Typically best fit for mid-market to enterprise healthcare organizations — often larger, multi-site hospitals and clinic networks where shared workstations and VDI are common.

Industries / verticals

Hospitals and health systems
Ambulatory clinics with EPCS requirements
Healthcare IT and managed clinical environments

Roles and personas

Decision makers: CIO, CISO, VP IT, Director of Clinical Informatics, Identity & Access Management leads
End users: clinicians (physicians, nurses, pharmacists), registration staff, revenue-cycle staff
Implementers: VDI engineers (Citrix/VMware), endpoint engineering, IAM administrators

Pain points addressed

Password fatigue and frequent re-authentication in patient-care workflows
Need for DEA-compliant, auditable EPCS authentication
Securing remote access while attempting to minimize user interruption

Qualification criteria (good fit)

Organizations with a high volume of shared workstations and roaming users
Need for badge-based tap-and-go workflows
EPCS is a driving use case or other high-assurance signing workflows are required

05The pitch

What the product does (core value proposition)

Key Confirm ID capabilities evidenced in documentation and datasheets include:

MFA/strong authentication methods (push, OTP/soft token, integrations) and workflow-specific policies.
Identity proofing and enrollment paths for EPCS, including integration with certificate authorities.
Clinical workflow integrations (e.g., Epic/Cerner contexts highlighted on vendor pages and datasheets).
Remote access MFA integrations such as VMware Horizon guidance in product documentation.

Target market and positioning

Primary: Mid-to-large healthcare delivery organizations (IDNs, hospitals, large clinics) with shared endpoints, clinician roaming, EHR re-authentication, and EPCS needs.
Secondary: Other regulated environments needing shared-device SSO/MFA and badge-based workflows—though many market signals and customer discussion emphasize healthcare as the core.

Market positioning themes (restated in neutral terms):

Authentication designed to reduce interruptions to clinician workflows compared with generic MFA products.
Audit trails intended to support compliance requirements for controlled substance prescribing and clinical access.

Get a comprehensive analysis of Imprivata Confirm ID including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →