ECSA101 Chapters 7 & 8 Test Questions with Correct Answers

ECSA101 Chapters 7 & 8 Test Questions with Correct Answers Public/Patient-Centric - Answer-Public, AKA shared, workstations are named as such as the user typically changes frequently, such as in a patient exam room. However, these names can actually be a misleading. A public workstation is any workstation where the user does not log into the OS and only Hyperspace, or supporting applications launched from Hyperspace, are used. A user won't be using the Office suite to check their email for example. The two primary examples of a public workstations are exam rooms and track boards. Track boards may also be called status boards or grease boards. Private / User-Centric - Answer-A private workstation is a workstation that is generally used by a single user during a shift. However, as with public workstations the name can actually be misleading. A private workstation is any workstation where the user logs into the operating system and uses applications other than Hyperspace. Examples of private workstations include physician offices and front desk registration desks. Is it okay for a published application session of Hyperspace to disconnect before Hyperspace shuts down? - Answer-Yes, but only if the session remains in a disconnected state and doesn't shut down. Servers should never shut down a session before Hyperspace closes due to its own timeouts. What are the benefits of using Warp Drive? - Answer-Warp Drive can initially open Hyperspace so that users don't need to wait for a Citrix or RDSH login and Hyperspace startup. This is most useful when paired with auto-login PCs. Warp Drive can keep Hyperspace open while still allowing for maintenance windows. Warp Drive provides access to ICA virtual channels when paired with the ICA Wrapper. This allows for more direct integration with Hyperspace from the end-point machine when Hyperspace is delivered via XenApp. What Hyperspace icons should production users always have access to? - Answer- Production (PRD), which references the MEC environment entry, and Supports Read Only (SRO) which references the RPT environment entry. CCOW (Clinical Context Object Workgroup) - Answer-Organizations with multiple software solutions may wish to achieve a higher degree of integration by implementing Clinical Context Object Workgroup, CCOW, also known as context management. CCOW can provide the same capability as SSO, however, CCOW can go beyond managing the context of which user is in the system. CCOW can also manage the context of the patient and encounter. This greater degree of context tracking allows a user to be in Hyperspace looking at a patient's chart for a particular encounter, launch a 3rd party application, such as a PACS imaging solution, and open the radiology images for the same patient, from the same encounter, without having to supply any additional credentials. This can be a powerful time saver and can ensure the users are looking at the correct information when working in multiple systems. SSO (Single Sign-On) - Answer-Single Sign On, SSO, solutions can reduce or, depending on setup, eliminate the need to enter credentials. Epic publishes an API that allows SSO vendors to communicate with the Hyperspace client. Some vendors may also teach the software about the various login/logout/secure screens. Every SSO solution is different. Many organizations also integrate their SSO client with devices such as tap cards, proximity cards, or biometric devices. These allow users to access the environment without providing a password. In these types of configurations, the user will occasionally need to enter their password as a second form of authentication or to renew their session. Pass-Through Authentication - Answer-Organizations usually use pass-through authentication in conjunction with LDAP integration, though LDAP is not a prerequisite for using pass-through. If a user has already authenticated to Windows or Citrix, why prompt them for their credentials again? Pass-through authentication, PTA, can be a simple alternative to CCOW or SSO. Auto-Login PCs - Answer-For workstations shared by several users (Public, AKA Shared, workstations), asking the users to log in and log out of Windows with each change is unreasonable. These machines should automatically log in during system startup.