Skip to content

Moraph for clients

Sign in

Getting started

Getting started with Single Sign-On

What Single Sign-On is for, who uses it, what you need before you start, and your first steps.

Applies to Single Sign-On as it works today. Moraph updates the platform continuously, and this page is reviewed when it changes.

Last reviewed 2 min readReport a problem
On this page
  1. What it is for
  2. Who uses it
  3. Before you start
  4. Steps to get started
  5. Where to go next

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.

What it is for

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

Before you start

  • Your organization uses Single Sign-On as a managed platform from Moraph, under an agreement that covers it.
  • Licences for Imprivata, bought through Moraph or under your own agreement with the vendor.
  • A Moraph account in your organization for each person who works with Moraph on the service.
  • Named technical and security contacts, recorded in the Moraph Portal.

Steps to get started

  1. Agree the scope of the managed service for Single Sign-On with Moraph, including which environments and teams it covers.

  2. Name your administrators, technical contact and security contact in the Moraph Portal under People and access.

  3. Review the configuration baseline Moraph proposes for your regulations, and record any changes you need.

  4. Confirm how users will sign in, through your identity provider where the platform supports it.

  5. Agree the pilot group and the cut-over plan with your Moraph delivery lead.

Where to go next

Was this page helpful?

Report a problem with this page
What’s the problem?
Quote the step or heading if you can. Don’t include passwords or personal records.
Only if you’d like a reply. We use it for this report and nothing else.

Need help with your own setup rather than this page? Raise a support ticket.