Download ECSM101 - Epic Client System Manger – Hyperspace and more Exams Health sciences in PDF only on Docsity!
ECSM101 - Epic Client System
Manger – Hyperspace
Hyperspace Client ✔ Ans - Hyperspace cannot be installed on a machine that hosts another of Epic's VB applications, such as HomeHealth or Analytics, due to resources that would end up being shared by these clients. Am I known? ✔ Ans - A Workstation Record or LSW must be identified in order for a connection to be successful. This LWS record can be specific to the machine establishing the connection, a generic LWS, or a record shared by multiple connections, depending on the connection being configured. Am I trusted? ✔ Ans - A fixed key is used to restrict access to the environment and to establish trust. The same fixed key must be defined in the Epic operational database environment as well as in the environment file. Who Am I? ✔ Ans - The Epic environment attempts to find an LWS record that matches the one specified by the Client or workstation ID in the connection configuration. If no match is found, a generic LWS can be used if enabled. Where am I going? ✔ Ans - Destination environments must also be defined in order for a connection to be successful. The connection must provide details such as the hostname of the Epic operational database and the communications port the environment uses. You can define connection information for multiple environments within the same environment file. What is an Administrative Image? ✔ Ans - You can think of the installation packages (*.msi files) as a collection of compressed files and a database that includes instructions on how to install those files.
An Administrative Image will be much larger than the original *.msi, because in an *.msi, the installation files have been decompressed. It is important to keep this large structure together when moving it from one location to another. Why is an Administrative Image Needed? ✔ Ans - You will install Hyperspace on many servers and workstations in your environment. To avoid customizing each installation manually, you should create and customize a single package so that, when deployed, it works without further configuration. Can you run Hyperspace on x86 (32-bit) Windows 7? ✔ Ans
- Yes, Hyperspace is technically compatible with 32-bit Windows 7; 32-bit Windows 7 is not, however, a Target Platform, and running Hyperspace on this platform caries some risk of running into previously undiscovered issues. How is trust established between an Epic client and the Epic operational database environment? ✔ Ans - A fixed key will be defined on the client, usually in some type of environment file, and imported into the Epic environment. Why does Epic recommend creating a Hyperspace Administrative Image? ✔ Ans - Using a script to copy files carries a high chance of failure and would be logged separate from the installation. By creating a customized Hyperspace Administrative Image, an administrator can be sure that all necessary files will be on any client built from that customized image. What documents should you reference prior to building a new Hyperspace server? ✔ Ans - Target Platform: Epic Client Systems Manager - Application Deployment Administrator and the Hyperspace Server Build Checklist EpicComm ✔ Ans - Hyperspace client uses a connection protocol called EpicComm over ECF to establish a connection
A ClientID is configured in Epic.cli to answer 'Who am I?', environmentconnection information is defined in EpicComm.env to answer 'Where am I going?', and a fixed key is defined in EpicComm.env to complete half of the 'Am I trusted?' configuration. What function does the Generic LWS record provide? ✔ Ans
- The Generic LWS record is used, if enabled, whenever no LWS with a Workstation Name or Workstation ID that matches the Client ID specified by the Hyperspace client can be found. This is primarily used to allow remote users (doctors completing notes at home) and build teams in nonproduction environments to access the environment without a unique LWS assigned to their workstation. What are the four questions that must be answered when configuring a connection to an Epic environment? How are these questions answered for Hyperspace? ✔ Ans - Who am I?' - Client ID in Epic.cli 'Where am I going?' - Connection information in EpicComm.env 'Am I trusted?' - Fixed key in EpicComm.env and Epic environment 'Am I known?' - LWS record created in Epic environment InstallMSP.exe ✔ Ans - InstallMSP.exe is the utility used by an ECSM to apply a Client Pack to Hyperspace installations. While the InstallMSP GUI makes it possible to directly apply a Client Pack to Hyperspace, Epic recommends creating batch file or leveraging your 3rd-party distribution system to deploy your Client Pack using a pre-built batch file. This process ensures that there are no issues with the Client Pack prior to update night, and helps to avoid any last minute scrambles as you update your environment. Validates that the Client Pack delivered by
Epic is cumulative and contains all Special Updates already installed on a representative client. This is also where you would specify SUs that were intentionally removed. To ensure you are always working with the latest version of InsatllMSP.exe favorite the InstallMSP Changelog document out on Galaxy. As indicated in the changelog you may always find the latest version of InstallMSP on EEDS in the (version) > Client Applications > InstallMSP folder. InstallMSP.vbs ✔ Ans - As previously mentioned, Epic recommends using a 3rd party distribution tool to apply Client Packs to your Hyperspace machines. When using this tool, a batch file like the one you just created would be the package you deploy. Applying Client Packs requires InstallMSP.exe. If your organization uses a tool such as System Center Configuration Manager (SCCM) to deploy this batch file as built above, InstallMSP would not provide return codes, and the distribution tool wouldn't know if installation succeeded. Registry and About Hyperspace ✔ Ans - When viewing Epic > Help > About Hyperspace > Extended Info, you saw the Client Pack and the individual Special Updates the Client Pack included that were on your Hyperspace client. You also saw a list of which server- side updates had been loaded into the Epic operational database environment. The client-side update information is pulled from the Hyperspace client's Windows registry and the server-side update information is pulled from the Epic operational database environment to which your client is connected. The registry information is found in the following path: HKLM\SOFTWARE\Wow6432Node\Epic Systems Corporation 81HotFix Why must the Epic environment be updated before a Client Pack is applied to your Hyperspace clients? ✔ Ans - The
CCOW ✔ Ans - 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 Pass-Through Authentication ✔ Ans - If a user has already authenticated to Windows, why prompt them for their credentials again when they've already successfully identified themselves with Active Directory? Pass-Through Authentication, PTA, can be a simple alternative to CCOW or SSO. Auto-Login on Shared Workstations ✔ Ans - For workstations shared by multiple users, where the individual using the machine frequently changes, asking the users to log in and log out of Windows with each change is a major dis-satisfier. These machines should automatically log in during system startup. Limit Sources of Slowness ✔ Ans - Limit Login Scripts Login scripts slow user access by their mere presence. Limit GPO Parsing Group Policy can also slow a user's access to the system. The more policies and the more rules in those policies, the longer logins will take. Limit Network Resources Accessed During Login Any item that is located on your network is a potential source of slowness during login. Epic recommends locating any files accessed during login on the machine with Hyperspace installed. Locating these files in the yperspace Administrative Image, as discussed in the Chapter 2 - Configure, will ensure loading these files is fast. Examples of files that shouldn't be located on the network include images use to brand the Hyperspace experience, environment files, and CLI files.
How can you ensure end-users only access your Production environment, PRD? ✔ Ans - Add the ENV=PRD command line argument to your Production Hyperspace shortcut and published applications. What is the difference between SSO and CCOW? ✔ Ans - CCOW is capable of tracking the user, patient, and encounter while SSO can only ensure the same user is supplied when launching a new application. Why should your shared workstations be configured to automatically login as a unique domain account during startup? ✔ Ans - This ensures users will not have to authenticate to Windows in addition to Epic. Users may secure or log out of Hyperspace but leave the Hyperspace window open for the next user. Using a unique domain account avoids issues with client printing and session stealing. EpicComm Problems ✔ Ans - Most errors seen after launching Hyperspace, before the login screen is presented, are caused by issues with the EpicComm configuration. When you see an error during connection ask yourself, "Which of the four environment connection questions does this sound like a problem with?" Restricted Environment Access ✔ Ans - If your organization has just upgraded the Epic environment, users may not be able to access the environment. This is intentional. To validate the environment, a small number of analysts and other technical staff need to access the environment before it is generally available for users. This is accomplished by flagging Employee records, EMPs, and Workstation records, LWSs, to allow Restricted-Mode Connections. Dependencies ✔ Ans - As discussed in Chapter 4, code in the Hyperspace client can depend on code in the Epic environment. If a Hyperspace client has been upgrade to a higher IU or
concurrency across multiple servers usually indicates a problem with the network or Epic environment. Workflow Tracer ✔ Ans - Workflow Tracer (WFT) can be used to capture screenshots of users' workflows and memory dumps of the Hyperspace process. WFT is a separate executable that runs next to Hyperspace and is included in the Hyperspace install. WFT can be presented to users in two ways. The first method is to provide Hyperspace and WFT to users with a different shortcut or published application that captures all data without any interaction from the user. The second is to provide a Capture Dump button to a user that allows them to capture the desired information on demand. WMI Corruption ✔ Ans - WMI corruption issues may be seen when attempting to install Hyperspace or when attempting to apply a ClientPack. If you see any of the following error messages refer to the How to Diagnose and Repair WMI Corruption knowledge base article. Missing Special Updates ✔ Ans - When attempting to validate a new ClientPack from a representative client as part of your InstallMSP.exe batch file build process, you may be presented with the following error: Client pack error: 'There is at least one SU missing from the remove list.' If you encounter this error consult the Client pack error: 'There is at least one SU missing from the remove list.' knowledge base article. This error is seen when a
ClientPack does not have all SUs that were already installed on your Hyperspace clients. This generally occurs as a result of SUs being removed because they have been identified as broken or when your application analysts have determined that a particular SU causes undesired changes to users' workflows at your organization. Leapfrog Packages ✔ Ans - A leapfrog package is a small update package, comprised of critical and urgent fixes. We deliver leapfrog package when you need to install the included SUs into production on an expedited timeline. Sysinternals Suite - Process Monitor ✔ Ans - Process Monitor Process Monitor, better known as Procmon, is a favorite for any Windows troubleshooting. Procmon shows, in detail, everything that is happening from file system and registry access, network traces and process and thread activity. Sysinternals Suite - Process Explorer ✔ Ans - Process Explorer gives a much more detailed look at what's running on your system than the built-in Windows Task Manager. Process Explorer displays the running tasks in a tree view, to show the parent/child relationship for all processes on your system. It can also display the fractional CPU usage and CPU history instead of just the current usage. Process Explorer can be useful to investigate which services are associated with individual svchost.exe processes, which processes are causing the greatest impact on CPU, and which program has a lock on a particular file or folder. ProcDump ✔ Ans - ProcDump can be used to monitor a particular process for a predefined event, such as reaching a certain percentage of CPU use or a hang and can then generate a dump of that processes. ProcDump can also be used to capture on demand dumps as the need arises.
