Healthcare · Managed platform (Imprivata)

Single Sign-On

Badge tap sign-on for clinicians on shared workstations, configured and run for you

Book a demonstrationRequest a technical briefingFactsheet

Overview

What you are buying

Moraph resells, implements and runs Imprivata so clinicians can sign in to shared workstations and clinical applications by tapping their badge, instead of typing passwords at every stop. Imprivata OneSign handles badge enrollment, application sign-on profiles and fast user switching, and where licensed, Imprivata Confirm ID supports two-factor signing for e-prescribing of controlled substances. Moraph's service team maintains the profiles as applications change, watches the service, and gives your security team the access records it needs.

The problem it solves

Clinicians move between workstations all day, and each one asks for a username and password, sometimes several times for different applications. Staff share sessions or leave them open to save time, which undermines unique user identification and makes it hard to say who looked at a record. Password resets fill the service desk. Hospitals that buy badge sign-on often find that application profiles break when an EMR or other application is upgraded, and that the people who set it up have moved on.

  • Repeated password entry slows clinicians and encourages shared or open sessions
  • Application sign-on profiles break when applications are upgraded
  • Password resets take up a large share of service desk calls
  • Evidence of unique user access and automatic logoff is hard to produce

Who uses it

  • Hospital IT and identity teams responsible for clinical workstation access
  • CMIOs, CNIOs and clinical informatics teams who hear about sign-on friction first
  • HIPAA security officers who answer for unique user identification and automatic logoff
  • Pharmacy and prescriber leadership managing e-prescribing of controlled substances
  • Health systems with an Imprivata deployment that needs an owner

Requirements it supports

HIPAA Security Rule (45 CFR Part 164, Subpart C), including access control and person or entity authentication at 45 CFR 164.312HIPAA Privacy Rule (45 CFR Part 164, Subpart E)DEA electronic prescriptions for controlled substances (21 CFR Part 1311)NIST SP 800-63B, Digital Identity Guidelines: Authentication and Lifecycle ManagementHIPAA Breach Notification Rule (45 CFR 164.400 to 164.414)

The product supports these requirements; meeting them remains your organization’s responsibility.

Responsibilities

Who is responsible for what

Imprivata provides the software and its support, Moraph configures and runs your deployment, and your organization makes the access policy decisions and owns the directory and workstations.

AreaMoraphImprivataYour organization
LicensingResells Imprivata licenses and keeps counts aligned with your usersSets license terms and product availabilityAgrees the users and products to license and pays under the order
Platform softwareInstalls and maintains servers or appliances and agents to the supported versionsDevelops, releases and supports the software under its own commitmentsProvides the infrastructure and workstation images it runs on
PoliciesConfigures authentication, timeout and lock policies to the approved baselineProvides the policy featuresDecides and approves policies and exceptions
Application profilesBuilds, tests and maintains profiles as applications changeProvides profile tools and guidanceTells Moraph about upgrades and joins user testing
IdentityConnects Imprivata to your directoryProvides directory integrationOwns accounts, groups, joiners, movers and leavers
BadgesMaintains enrollment processes and removes lost badges on requestSupports the readers and badge types listed by ImprivataIssues badges and buys readers
MonitoringWatches service health and works sign-on incidentsSupports escalated issuesReports clinical impact and runs the service desk
UpdatesPlans and applies Imprivata updates in agreed windowsReleases updates and security fixesApproves maintenance windows
IncidentsLeads incident handling for the service and reports cause and fixResolves product defects and provides root cause where availableDecides on any regulatory or patient notification
Regulatory obligationsProvides evidence of configuration and changesProvides product documentation under its termsRemains responsible for HIPAA access controls and EPCS requirements

See how it works

A short walkthrough

Illustrative screens of how Moraph runs the service, with fictional sample data. They are not screens of Imprivata itself, which belongs to its vendor.

  1. Step 1

    Onboarding tracker

    During onboarding, each area moves from policy approval to live badge sign-on, with the owner of each step visible.

    AreaWorkstationsPolicy approvedAgent deployedBadge enrollmentStatus
    Example Medical Center, 3 East40YesYesFloor support completeLive
    Example Medical Center, ED65YesYesIn progressPilot
    Example Medical Center, Perioperative52Timeout exception pendingYesNot startedOn hold
    Example Clinic, Primary Care18YesImage update waiting on client ITNot startedPlanned
    During onboarding, each area moves from policy approval to live badge sign-on, with the owner of each step visible.

  2. Step 2

    Profiles ahead of an upgrade

    Before an application upgrade, Moraph tests each affected profile and shows what still needs work.

    ApplicationCurrent versionUpgrade versionProfile testUser testReady
    EMR (fictional sample)Version AVersion BPassedPassedYes
    Lab results viewer3.23.4Failed: new sign-in screenNot startedNo
    PACS viewer11.011.1PassedScheduledPending
    Scheduling application8.5No changeNot neededNot neededYes
    Before an application upgrade, Moraph tests each affected profile and shows what still needs work.

  3. Step 3

    A timeout exception request

    Exceptions to the timeout policy are requested, justified and approved by the security officer before Moraph applies them.

    Change CR-2043 · Longer lock timeout in operating rooms

    Requested by
    CNIO
    Area
    Perioperative, Example Medical Center
    Current policy
    Lock after standard inactivity period
    Requested
    Longer period during procedures, with tap to lock
    Reason
    Workstations used intermittently during cases
    Status
    Awaiting security officer

    Approvals

    • Clinical informatics: approved
    • Client IT identity team: approved
    • !HIPAA security officer: pending
    Exceptions to the timeout policy are requested, justified and approved by the security officer before Moraph applies them.

  4. Step 4

    Working a sign-on incident

    When clinicians report sign-on problems, the incident record shows each step from report to fix.

    Incident IN-0877 · Lab results viewer asks for password after tap

    1. Several reports from 3 East loggedService desk
    2. Linked to lab viewer patch applied overnight by vendorMoraph service team
    3. Profile updated in test and checkedMoraph service team
    4. Emergency change approvedClient IT identity team
    5. Updated profile releasedMoraph service team
    6. Clinicians confirm sign-on workingClinical informatics lead
    When clinicians report sign-on problems, the incident record shows each step from report to fix.

  5. Step 5

    Administrator access review

    Periodically, the security officer reviews everyone who can change sign-on configuration, including Moraph staff.

    Imprivata administrator access review · Example Health System

    Accounts reviewed
    12
    Client IT administrators
    5
    Moraph service team
    6
    Help desk enrollment role
    1 group
    Reviewer
    HIPAA security officer

    Findings

    • !One client IT account belongs to a person who changed roles
    • All Moraph accounts used only for approved changes in the period
    • Help desk group limited to enrollment status
    Periodically, the security officer reviews everyone who can change sign-on configuration, including Moraph staff.

  6. Step 6

    Monthly service review

    Each month, Moraph and your IT team review sign-on use, failures, resets and changes, using fictional figures here.

    MeasureThis monthLast monthNote
    Active users with enrolled badge6,1205,980ED rollout
    Profile failure reports1431Lab viewer fixed
    Password reset tickets212260Self-service reset promoted
    Changes applied86All approved
    Open incidents12Printer sign-on in clinic
    Upgrades ahead21Testing scheduled
    Each month, Moraph and your IT team review sign-on use, failures, resets and changes, using fictional figures here.

Workflows

The principal workflows

  1. Enroll badges

    Each clinician links their badge to their network account once, usually at first sign-in or at the badge office, and from then on a tap identifies them.

    • New staff receive their badge and network account through your existing processes
    • At first tap, the clinician enters their password once to link the badge
    • Imprivata records the enrollment against their directory account
    • Lost or replaced badges are re-enrolled and the old badge removed
    • Leavers lose badge sign-on when their directory account is disabled

  2. Tap in, tap over

    On shared workstations, a tap signs the clinician in, and a tap by the next clinician switches the session, so nobody works under someone else's sign-in.

    • Clinician taps their badge at a shared workstation or virtual desktop
    • Imprivata signs them in to Windows or their virtual desktop session
    • Application profiles fill in their credentials for the EMR and other applications
    • A tap by another clinician locks or switches the session
    • Inactivity locks the session as your timeout policy sets

  3. Maintain profiles

    When an application is upgraded or added, Moraph tests and updates its sign-on profile before the change reaches clinicians.

    • Client IT or the application team tells Moraph about an upgrade or new application
    • Moraph tests the existing profile against the new version in your test environment
    • Profiles are updated or built and checked with a small group of users
    • The change is applied against an approved change request
    • Profile failures reported after release are worked as incidents

  4. Prove access

    Moraph keeps the configuration baseline and access records your security team needs to show unique user identification, automatic logoff and two-factor signing where it applies.

    • Timeout, lock and authentication policies are documented in the baseline
    • Sign-in and badge enrollment records are kept in Imprivata
    • Administrator access is reviewed with your security officer
    • Two-factor signing setup for controlled-substance prescribing is documented where Confirm ID is licensed
    • Evidence is produced for audits and the monthly service review

Roles and permissions

Who does what in the product

Each role below is a starting point. During implementation we set them up to match your teams, and every action anyone takes is recorded in the audit trail.

Clinical informatics lead

CMIO, CNIO, clinical informatics manager

Represents clinicians: decides which applications need sign-on profiles first and reports where sign-on gets in the way of care.

Sees

  • Applications with sign-on profiles and their status
  • Profile failures reported by clinicians
  • Planned application upgrades that affect sign-on

Does

  • Requests profiles for new applications
  • Sets priorities for profile work
  • Joins user testing of profiles before release
  • Raises clinician feedback at the monthly service review

Cannot

  • Change authentication or timeout policies
  • Make changes directly in Imprivata
Approvals
Approves profile changes that affect clinical workflows; policy changes need the HIPAA security officer.
Notified about
Profiles ready for testing, upgrades scheduled, and profile incidents affecting clinicians.

Client IT identity team

Identity and access manager, Active Directory engineer, end-user computing manager

Owns the directory, workstations and virtual desktops that Imprivata depends on, and is Moraph's technical counterpart.

Sees

  • The full Imprivata configuration and its health
  • The configuration baseline and change history
  • Service reports and open incidents

Does

  • Approves technical change requests
  • Maintains directory accounts and groups that drive sign-on
  • Deploys the Imprivata agent through workstation images
  • Tells Moraph about application upgrades and new workstations
  • Joins the monthly service review

Cannot

  • Change authentication policy without the HIPAA security officer
  • Edit the change record after the fact
Approvals
Approves technical changes; policy changes also need the HIPAA security officer.
Notified about
Incidents, vendor notices affecting you, and change requests waiting for approval.

HIPAA security officer

HIPAA security officer, CISO, identity governance lead

Sets authentication, timeout and lock requirements and uses the service's records as evidence of access controls.

Sees

  • Authentication and timeout policies and every change to them
  • Administrator accounts, including Moraph staff
  • Two-factor signing setup for EPCS where it applies
  • Sign-in records within the service's retention

Does

  • Approves authentication, timeout and lock policies
  • Approves exceptions such as longer timeouts in specific areas
  • Reviews administrator access periodically
  • Requests sign-in records for investigations
  • Uses service reports for risk analysis and audits

Cannot

  • Edit or delete sign-in or change records
  • Make configuration changes directly in Imprivata
Approvals
Approves policy changes and exceptions.
Notified about
Policy exceptions requested, administrator access reviews due, and security-relevant incidents.

Badge office

Security badging coordinator, HR onboarding staff

Issues badges and helps clinicians enroll, replace or remove them.

Sees

  • Badge enrollment status for a person they are helping
  • Badges reported lost

Does

  • Issues and replaces badges
  • Helps clinicians enroll a new badge
  • Removes enrollment for lost badges

Cannot

  • Change policies or profiles
  • See sign-in history
Approvals
None; badge issuance follows your existing identity verification process.
Notified about
Enrollment problems routed back from the service desk.

Moraph service team

Moraph identity engineers and service managers

Runs Imprivata on your behalf: configuration, profiles, monitoring, updates and incidents.

Sees

  • Imprivata configuration, server or appliance health and agent status
  • Profile failures and sign-on incidents
  • Change requests and their approvals

Does

  • Configures policies and profiles to the approved baseline
  • Tests and updates profiles ahead of application upgrades
  • Applies Imprivata updates in agreed maintenance windows
  • Works sign-on incidents and escalates to Imprivata where needed
  • Pulls sign-in records when your security officer requests them
  • Prepares the monthly service review

Cannot

  • Change policies without an approved change request
  • Use privileged access outside approved, time-bound work
  • Sign in to clinical applications as a clinician
Approvals
Every configuration change is made against a change request approved by the owner you name.
Notified about
Health alerts, profile failures, vendor notices, and scheduled application upgrades.

Service desk

IT service desk analyst, tier 1 support

Takes clinician calls about sign-on and badges and routes them.

Sees

  • Whether a user's badge is enrolled
  • Known issues and planned changes

Does

  • Logs sign-on and profile problems
  • Guides clinicians through badge re-enrollment
  • Routes tickets to Moraph or client IT

Cannot

  • Change profiles or policies
  • See sign-in history
Approvals
None; tickets are worked by Moraph or client IT.
Notified about
Planned changes and known issues.

Auditor (read-only)

Internal auditor, compliance analyst, external assessor under temporary access

Reviews evidence of access controls without changing anything.

Sees

  • Policies, the configuration baseline and change history
  • Administrator access reviews
  • Sign-in records within the scope granted

Does

  • Reads and exports evidence within their scope, with each export logged
  • Requests further evidence through the HIPAA security officer

Cannot

  • Change, approve or delete anything
  • Keep access after the agreed end date
Approvals
Access is approved by the HIPAA security officer with a scope and an end date.
Notified about
Nothing by default.

Permissions at a glance

ActionInformaticsClient ITSecurityBadge officeMoraph teamService deskAuditor
Request a new application profileFullFullView onlyNo accessView onlyNo accessNo access
Build and update sign-on profilesApprovesApprovesNo accessNo accessFullNo accessView only
Change authentication policiesNo accessView onlyApprovesNo accessFullNo accessView only
Change timeout and lock rulesView onlyApprovesApprovesNo accessFullNo accessView only
Enroll or remove a badgeNo accessFullNo accessFullFullOwn work onlyNo access
Configure two-factor signing for EPCSView onlyApprovesApprovesNo accessFullNo accessView only
Apply Imprivata updatesView onlyApprovesView onlyNo accessFullNo accessNo access
View sign-in recordsNo accessView onlyFullNo accessOwn work onlyNo accessView only
View the configuration baselineView onlyView onlyView onlyNo accessFullNo accessView only
Manage Imprivata administrator accessNo accessApprovesApprovesNo accessFullNo accessNo access
View service reportsView onlyView onlyView onlyNo accessFullNo accessView only
  • Full
  • Own work only
  • Approves
  • View only
  • No access

How access is controlled

  • Moraph changes policies and profiles only against a change request approved by the owner you name, and each change is recorded with the request it came from.
  • Moraph's staff pull sign-in records only when your security officer requests them, for example for an investigation, and each request is recorded.
  • Imprivata administrator roles are agreed with you during onboarding and reviewed with your security officer at each access review.
  • Auditors receive temporary read-only access to evidence with a defined scope and an end date, rather than shared accounts.

Features

What it does

Badge tap sign-on

Imprivata OneSign signs clinicians in to workstations with a tap of their proximity badge, after a one-time badge enrollment.

Fast user switching

On shared workstations, a tap by the next clinician locks or switches the session, so each person works under their own sign-in.

Application sign-on profiles

Imprivata fills in credentials for the EMR and other applications so clinicians do not retype passwords in each one.

Virtual desktop roaming

Where you use virtual desktops, the clinician's session can follow them from one workstation to the next.

Self-service password reset

Where licensed and configured, staff reset forgotten passwords themselves after answering enrollment questions, without calling the service desk.

Two-factor signing for EPCS

Where Imprivata Confirm ID is licensed, prescribers sign controlled-substance prescriptions with two factors, and the setup is documented for your EPCS controls.

Timeout and lock policies

Inactivity timeouts and lock behavior are set by area, so an operating room and a registration desk can follow different rules.

Profile testing before upgrades

Moraph tests sign-on profiles against new application versions before upgrades go live, and updates them through change requests.

Badge enrollment management

Moraph maintains badge enrollment processes with your badge office and service desk, including lost and replaced badges.

Configuration baseline

Policies, profiles and appliance settings are documented, checked against the live configuration and reviewed with you each quarter.

Service monitoring

Moraph watches the health of Imprivata servers or appliances and agents, and follows up sign-on failures reported by the service desk.

Service reporting

A monthly service review covers sign-on use, profile failures, password resets, changes, incidents and open issues.

Integrations

How it connects to your systems

Connects toHowWhat flows
Active Directory or your directoryImprivata uses your directory for user accounts and groups, so joiners, movers and leavers follow your existing processes.In: user accounts, group membership and account status.
EMR and clinical applicationsSign-on profiles fill credentials into your EMR and other applications; profiles are maintained as those applications change.Out: credentials entered into applications on the user's behalf.
Virtual desktopsWorks with Citrix and Omnissa Horizon virtual desktop environments so sessions can follow clinicians between workstations.In and out: session connect and disconnect.
Badge readers and badge systemsProximity badge readers at workstations read the same badges your physical access system issues.In: badge identifiers read at enrollment and sign-in.
E-prescribingWhere Imprivata Confirm ID is licensed, two-factor signing is connected to your EHR's controlled-substance prescribing workflow.In and out: signing requests and authentication results.
IT service managementSign-on tickets flow between your service desk and Moraph's service team, including Moraph's IT Service Management service where you use it.In and out: tickets, status and resolution.
Identity governanceAccount status and roles from your identity governance process, including Moraph's Identity Governance service, drive who can sign in.In: account provisioning and removal.

Each integration is confirmed in discovery and specified in the design. See how an engagement progresses.

Security and privacy

How your data is protected

Multi-factor administration

Your administrators and Moraph's staff sign in to Imprivata administration with multi-factor authentication, and access is removed when people leave.

Role-based access

The badge office manages enrollments, the service desk sees enrollment status, and Moraph's service team works on configuration rather than clinical data.

Recorded changes and record requests

Every configuration change and every request for sign-in records is recorded with the person, time and request it served.

Controlled privileged access

Moraph staff use administrative access only for approved work, with keys and credentials they cannot use without explicit, time-bound authorization.

Independent audits

Moraph's operations are audited under SOC 2 Type II and ISO/IEC 27001. Imprivata's own assurance documentation is available from Imprivata under its terms.

Business associate agreement

Where the service involves PHI, Moraph signs a business associate agreement, and Moraph's service tooling uses the United States region.

Company-wide controls, independent audits (SOC 2 Type II and ISO/IEC 27001) and data residency are described in our Trust Center, where you can request the evidence pack.

Reporting

What you can report on

10 standard reports, grouped by who uses them. Each shows who it is for, how it can be broken down, how it is delivered and what it is used for. The data behind them is also available to your own reporting tools.

Operational

Profile failures

For moraph service team, client IT, clinical informatics

Application sign-on profiles reported as failing, with the application, version, number of reports and status.

Break down by
Application, Version, Site, Status
Delivered as
Live view; weekly email
Used for
Fixing profiles that make clinicians type passwords again.

Badge enrollment

For client IT and the badge office

Active users with and without an enrolled badge, and badges replaced or removed in the period.

Break down by
Department, Site, Enrollment status
Delivered as
Monthly; CSV export
Used for
Finding staff who still sign in by password and following up.

Upcoming application upgrades

For client IT and clinical informatics

Planned application upgrades with the sign-on profiles they affect and the status of testing.

Break down by
Application, Planned date, Test status
Delivered as
Live view
Used for
Making sure profiles are ready before an upgrade reaches clinicians.

Service health

For moraph service team and client IT

Health of Imprivata servers or appliances and agents, with alerts raised and resolved.

Break down by
Component, Site, Alert type, Period
Delivered as
Live view; monthly summary
Used for
Spotting problems before they stop sign-on.

Security and compliance

Authentication and timeout policy

For hIPAA security officer and auditors

The policies in force by area, with approved exceptions and their reasons.

Break down by
Area, Policy, Exception
Delivered as
Quarterly review pack; PDF export
Used for
Evidencing unique user identification and automatic logoff controls.

Administrator access review

For hIPAA security officer

Everyone with administrative access to Imprivata, including Moraph staff, with their role and last use.

Break down by
Organization, Role, Last sign-in
Delivered as
At each access review; PDF export
Used for
Certifying that only the right people can change sign-on configuration.

Sign-in record extract

For hIPAA security officer and privacy officer

Sign-in and session events for a person, workstation or period, within Imprivata's retention.

Break down by
User, Workstation, Date range, Event type
Delivered as
On request; CSV export
Used for
Supporting privacy investigations and access questions.

EPCS two-factor setup

For hIPAA security officer and pharmacy leadership

Where Confirm ID is licensed, the prescribers enrolled for two-factor signing and changes to that setup.

Break down by
Prescriber group, Enrollment status, Period
Delivered as
On request; PDF export
Used for
Supporting your organization's controls for electronic prescribing of controlled substances.

Service

Monthly service review

For client IT and service owners

Sign-on use, profile failures, password reset volume, changes, incidents and open issues for the month.

Break down by
Month, Site, Category
Delivered as
PDF; review meeting
Used for
Reviewing the service with Moraph and agreeing priorities.

Change request log

For client IT, clinical informatics, security officer

Every change request with its requester, approver, status and the date it was applied.

Break down by
Status, Requester, Change type, Period
Delivered as
Live view; CSV export
Used for
Tracking what is changing in sign-on and who agreed it.

Exports, access and evidence

  • Reports come from Imprivata's own data and Moraph's service records. Moraph assembles the monthly review and evidence packs; your administrators can also use Imprivata's reporting where their role allows.
  • Every report can be exported to CSV, and review and evidence reports to PDF.
  • Sign-in record extracts are produced only on a request from your security or privacy officer, and each request is recorded.
  • What is available depends on the Imprivata products you license and how long Imprivata keeps each kind of record in your configuration.
  • Evidence reports can be run for a past period for audits, and producing them is recorded.

Deployment

Where and how it runs

Imprivata in your data center, managed by Moraph

Imprivata servers or virtual appliances run in your environment, and Moraph configures and runs them remotely under a managed service agreement.

Moraph-managed with your existing licenses

If you already license Imprivata, Moraph can take over configuration and operations, subject to Imprivata's terms.

Alongside other Moraph services

Run with Moraph's Identity Governance, Enterprise Mobility or Network Access Control services so identity, devices and network access are managed together.

Security controls, independent audits and data residency are set out in our Trust Center. Engagement models and what drives a quotation are on Working with Moraph.

Implementation

What a rollout involves

The general phases are on Working with Moraph. For this product, they involve the following.

Current-state review

We review your workstations, virtual desktops, applications, badges and any existing Imprivata deployment, and agree which areas and applications come first.

Policy design

Your security officer, client IT and clinical informatics agree authentication, timeout and lock policies by area, and record any exceptions.

Infrastructure and agents

Imprivata servers or appliances are installed or reviewed, connected to your directory, and the agent is added to your workstation images.

Profiles

Sign-on profiles are built and tested for the applications in scope, starting with the EMR and the applications clinicians use most.

Pilot and rollout

A pilot area goes live with badge enrollment support on the floor, then remaining areas follow in an agreed order.

Handover to service

Monitoring, profile maintenance, change requests and the monthly service review begin, and your contacts are confirmed.

Limitations

What it does not do

Worth knowing before you evaluate it.

  • Moraph is not Imprivata. The software belongs to Imprivata, and Imprivata's own support commitments, roadmap and product defects apply to it.
  • Licenses are subject to Imprivata's terms. Features such as two-factor signing for EPCS and self-service password reset depend on the products you license.
  • Some applications cannot be profiled, or need rework after each upgrade. Moraph tests profiles before upgrades but cannot guarantee every application version will work with badge sign-on.
  • Badge sign-on depends on your directory, network, workstations and readers. Moraph does not supply badge readers or workstations.
  • Moraph does not issue badges or verify identity; your badge office and onboarding processes do that.
  • Your organization remains responsible for HIPAA access controls, its EPCS obligations under DEA rules, and decisions about timeouts and exceptions.
  • Where Imprivata runs in your data center, its availability depends on your infrastructure as well as Moraph's monitoring.

Evaluation checklist

What to test in a demonstration or pilot

Questions worth putting to us, and to any other vendor you are considering.

  1. Pick a busy unit and walk through a clinician's sign-ins over one shift, before and after badge sign-on
  2. List your top applications and ask which can be profiled and what testing each upgrade needs
  3. Review the draft timeout and lock policies with your security officer and clinical informatics
  4. Walk through what happens when a badge is lost
  5. Ask to see how a sign-on incident would be logged, worked and closed
  6. Confirm who at your organization approves policy changes and requests sign-in records

Questions

Frequently asked questions

Do clinicians still need passwords?

They enter their password to enroll their badge and periodically as your policy requires. Day to day, a tap signs them in and application profiles fill in credentials for them.

What happens when the EMR is upgraded?

Moraph tests affected profiles against the new version in your test environment before the upgrade and updates them through a change request. Tell us about upgrades as early as you can.

Does this satisfy the DEA two-factor requirement for EPCS?

Imprivata Confirm ID is designed to support it, where you license it. Your organization remains responsible for its EPCS controls, including identity proofing and access control set out in 21 CFR Part 1311, and Moraph documents the setup to support that.

We already have Imprivata. Can Moraph take it over?

Usually, subject to Imprivata's terms. We start with a review of your current configuration, profiles and versions, and agree what needs to change.

Can Moraph see what clinicians do in applications?

No. Moraph's team works on the sign-on configuration. Sign-in records are pulled only when your security officer requests them, and each request is recorded.

How is it priced?

Imprivata licenses are priced under Imprivata's terms, usually per user, and Moraph's managed service is priced separately. See Working with Moraph for what drives a quotation.

Next steps

Evaluate Single Sign-On

Book a demonstration

See the product working with sample data, focused on your workflows.

Request a demonstration

Request a technical briefing

Architecture, integrations, security and hosting, with our engineers and your technical team.

Request a briefing

Factsheet

This page on two sides, to share with colleagues or add to your evaluation file.

Open the factsheet

Buying through a formal procurement? See How to buy for purchasing routes, accessibility conformance reports and company information. Documentation: Single Sign-On guides on docs.moraph.com (getting started and security guides are public; setup, administration and integration guides are for client accounts). Support: Single Sign-On support guide.

Related products