Specifications include, but are not limited to:UCLA Health is requesting vendors of Single Sign-On solutions to submit their responses to this Request for Proposal (hereafter referred to as “RFP”) for the UCLA Health hospitals and affiliated clinics. The purpose of the RFP is to select vendors of such solutions using the criteria described herein. UCLA Health anticipates the deployment of the new solution to replace its aging resources serving the Ronald Reagan UCLA Medical Center (466 beds), the Santa Monica-UCLA Medical Center and Orthopaedic Hospital (265 beds) and their affiliated clinics and ambulatory care facilities. It is anticipated that the legacy systems will be replaced in a swift project commencing in fiscal year 2016.Single sign-on (SSO) is a property of access control of multiple, related, but independent software systems. A user logs in once and gains access to authorized systems without being prompted to log in again at each of them. At UCLA this translates into hundreds of hours saved per provider each year. Single Sign-On allows UCLA providers to sign into their workstation without typing a username or password. Instead, with just a tap of their badge, they are automatically authenticated into the system. This would potentially decrease the number of calls to the help desk to reset lost or forgotten passwords. This integration offers the fastest and most reliable method of providing streamlined secure access to the Epic environment and all other applications; this provides an added level of security. Vendors shall provide a detailed description of their Single Sign-On solution that will act as an integral part of a security identity authentication and management portfolio that will pass credentials to systems that UCLA Health supports and maintains as well as systems that UCLA Health does not own or support for network, workstation and application access (i.e., Microsoft Windows, Novell, Web, Java™, UNIX Telnet, in-house developed, off the shelf software and mainframe applications). The solution must recognize and respond to password requests from any system or application and must support different and multiple types of user authentication besides tap badges (i.e., ID tokens, smart cards, proximity cards and/or biometric technologies). It should: 1. Integrate with existing UCLA Health Active Directory. 2. Provide a method of “fast user switching” for all supported operating systems for shared, multi-user computers in a Windows domain. 3. Provide a method for users to resume their session at a later time, even if other users have accessed the workstation. 4. Reduce login delay where possible.
