Single Sign-On for Non-Epic and EHR-less Hospitals

If your hospital doesn’t run Epic, or you’d like single sign-on without launching from inside an EHR, your staff can sign in with any standard OpenID Connect identity provider — Google Workspace, Microsoft 365, Okta, and similar. Connecting your identity provider is something your hospital sets up with your NEPA contact; there isn’t a self-service setup screen for it yet.

How staff sign in

Once your identity provider is connected, staff start from a sign-in link specific to your hospital rather than launching from inside an EHR. Everything after that works exactly like Epic-launched sign-in: the first time someone signs in this way, their request goes to your hospital’s administrators for approval (see EHR Sign-In Access Requests), and after that, signing in again takes them straight into the app, landing on the page for their role (see Role-Based Landing Page After Sign-In).

If a request is pending or declined, staff see the same Access requested, Access not available, or We couldn’t sign you in messages described for Epic sign-in (see Epic SSO Sign-In for Staff).

An option alongside invites, not a replacement

This is a convenience alongside your existing email-invite sign-in, not a replacement — if your hospital doesn’t have an identity provider, you can keep using invite-based accounts.