ECSA101 Chapters 3 & 4 questions well answered
already passed latest update
1. 3 Types of
Published Application, Virtual Desktop and Full Client
Deploy- ment
Options
Deploying Hyperspace as a is the most
2. Published Applica-
widely used Hyperspace deployment option. VMware's Horizon
tion
RDS and Citrix's XenApp are the only platforms that
are Target Platforms. Microsoft's Remote App is currently
exploratory.
3. Virtual Desktop The community's use of VDI is growing. Physicians' desire to roam
their
entire desktop is often cited as a driving force behind VDI. VDI
may not be appropriate if you are only deploying Hyperspace. VDI
is more appropriate when your organization also needs to deploy
other applications. If your primary Hyperspace deployment method
is virtual desktops, your HDAs are likely your VDI administrators.
4. Full Client Installing Hyperspace locally on a PC is not usually an organization's
primary
method of deploying Hyperspace. Organizations that don't use full
clients as their primary deployment likely do have some full
clients. This is often the case with radiology PACS machines. Be
mindful of compatibility between your 3rd-party applications and
software that Hyperspace requires. IE and .NET versions can be
particularly problematic.
5. EPICComm The Hyperspace client uses a connection protocol called EpicComm
over ECF,
or EpicComm for short. Hyperspace uses this protocol to establish a
connec- tion to Epic operational database environments. EpicComm
configuration is backwards compatible. Some other Epic clients use
1/
17
,ECSA101 Chapters 3 & 4 questions well answered
already passed latest update
this protocol as well, such as HomeHealth.
6. Client The Hyperspace install includes a configuration tool known as the
Configuration Client Configuration Utility. You will use this utility to complete
Utility configuration that answers the questions of 'Who am I?,' 'Where am I
going?,' and half of 'Am I trusted?'
2/
17
, ECSA101 Chapters 3 & 4 questions well answered
already passed latest update
7. EPIC.cli File When a user launches Hyperspace, Hyperspace will locate the
file in
C:\ProgramData\Epic\Config. This file provides the client with a
Client ID and points to one or more environment files. The
best practice is
that points to only one environment file,
EpicComm.env.
8. LWS When you specify a Client ID in the Epic.cli file, you are indirectly
specifying which LWS record to look for in the Epic environment.
LWS records represent workstations or, more accurately, end-point
devices at which an end-user works. The device may be a terminal or
a full client workstation. LWS records are referred to as Workstation
records. There should be a one to one map- ping of an LWS record
and and end point device.
9. What are the three Published application, virtual desktops, and full clients.
targeted Hyperspace
deployment options?
10. When using VDI, Hyperspace should be installed locally in the VDI image. This will
where should you ensure peripherals on the end-point can be used by the
install Hyperspace? Hyperspace session. This also avoids unneeded complexity.
Why?
11. True or False? Hy- False. Users access Hyperspace Web from within Hyperspace.
perspace Web is in- Issues with Hyperspace can impact Hyperspace Web.
dependent of Hyper-
space.
12. %CLIENTNAME% Your organization ONLY uses full clients and virtual desktops as your
Hyper-
3/
17
already passed latest update
1. 3 Types of
Published Application, Virtual Desktop and Full Client
Deploy- ment
Options
Deploying Hyperspace as a is the most
2. Published Applica-
widely used Hyperspace deployment option. VMware's Horizon
tion
RDS and Citrix's XenApp are the only platforms that
are Target Platforms. Microsoft's Remote App is currently
exploratory.
3. Virtual Desktop The community's use of VDI is growing. Physicians' desire to roam
their
entire desktop is often cited as a driving force behind VDI. VDI
may not be appropriate if you are only deploying Hyperspace. VDI
is more appropriate when your organization also needs to deploy
other applications. If your primary Hyperspace deployment method
is virtual desktops, your HDAs are likely your VDI administrators.
4. Full Client Installing Hyperspace locally on a PC is not usually an organization's
primary
method of deploying Hyperspace. Organizations that don't use full
clients as their primary deployment likely do have some full
clients. This is often the case with radiology PACS machines. Be
mindful of compatibility between your 3rd-party applications and
software that Hyperspace requires. IE and .NET versions can be
particularly problematic.
5. EPICComm The Hyperspace client uses a connection protocol called EpicComm
over ECF,
or EpicComm for short. Hyperspace uses this protocol to establish a
connec- tion to Epic operational database environments. EpicComm
configuration is backwards compatible. Some other Epic clients use
1/
17
,ECSA101 Chapters 3 & 4 questions well answered
already passed latest update
this protocol as well, such as HomeHealth.
6. Client The Hyperspace install includes a configuration tool known as the
Configuration Client Configuration Utility. You will use this utility to complete
Utility configuration that answers the questions of 'Who am I?,' 'Where am I
going?,' and half of 'Am I trusted?'
2/
17
, ECSA101 Chapters 3 & 4 questions well answered
already passed latest update
7. EPIC.cli File When a user launches Hyperspace, Hyperspace will locate the
file in
C:\ProgramData\Epic\Config. This file provides the client with a
Client ID and points to one or more environment files. The
best practice is
that points to only one environment file,
EpicComm.env.
8. LWS When you specify a Client ID in the Epic.cli file, you are indirectly
specifying which LWS record to look for in the Epic environment.
LWS records represent workstations or, more accurately, end-point
devices at which an end-user works. The device may be a terminal or
a full client workstation. LWS records are referred to as Workstation
records. There should be a one to one map- ping of an LWS record
and and end point device.
9. What are the three Published application, virtual desktops, and full clients.
targeted Hyperspace
deployment options?
10. When using VDI, Hyperspace should be installed locally in the VDI image. This will
where should you ensure peripherals on the end-point can be used by the
install Hyperspace? Hyperspace session. This also avoids unneeded complexity.
Why?
11. True or False? Hy- False. Users access Hyperspace Web from within Hyperspace.
perspace Web is in- Issues with Hyperspace can impact Hyperspace Web.
dependent of Hyper-
space.
12. %CLIENTNAME% Your organization ONLY uses full clients and virtual desktops as your
Hyper-
3/
17
