Cog170 Fundamentals Questions With
Solutions
What is an administrator An administrator in Epic can configure parts of the Epic
interface for users.
Administrators can have many responsibilities depending on which applications, or parts of the
Epic software, they are responsible for managing. Examples of Epic applications include
EpicCare Ambulatory for outpatient workflows, Stork for obstetric workflows, and Cogito Ergo
Sum, or Cogito, for analytics tools and content.
Another term for an administrator in Epic is an analyst. The term administrator typically refers to
a user's login setup (Lorena logs in as a Cogito Tools Administrator) while analyst refers to the
individual's role in an organization (Lorena works as a Cogito Analyst), although exact usage
may vary depending on your organization. More information about Cogito roles, or roles on an
Epic reporting team, will be covered in a later lesson.
A common administrator workflow is to update existing or create new build in the system. Build
refers to the parts of Epic that configure the interface and the user experience, such as
dashboards or order sets. While users interact directly with data about patient care, administrators
interact with the build that presents the data in a certain way.
Much of the build in Epic is saved in discrete records in Chronicles. Each record has an ID and
build records can be edited by administrators who have the appropriate permissions, or security,
to do so. To help keep track of new build records, administrators are encouraged to use build
, Cog170 Fundamentals Questions With
Solutions
trackers, spreadsheets with a list of new record IDs, names, owning teams, and any other relevant
information to assist with tracking and maintenance.
Hyperspace vs Chronicles vs Classic The Classic client is the original Hyperspace client.
As of Epic's May 2022 release, all end-user facing activities are available in the new, web-based
Hyperspace. However, many administrative activities have not yet been migrated and are
available only in the Classic client.
Throughout the Cogito Fundamentals class you will edit build records using administrator
activities in Classic. Most of these activities are also available in Hyperspace.
If you need to build, configure records, or use utilities, do so in the Classic client. Some admin
activities are already available on the Hyperdrive client, and more will be migrated over time. Be
sure to test your build/configuration in Hyperspace on the Hyperdrive client. Log in to
Hyperspace as an appropriate test user, one who represents users affected by your build. For
example, if you build an order set, log in to Hyperspace as a test physician to confirm that the
order set works as expected.
Epic plans to eventually migrate all administrative activities from Classic to the new web-based
Hyperspace. When that migration is complete, the Classic client will be retired.
What term describes the tasks a user performs in Hyperspace as part of their job? A
workflow
Solutions
What is an administrator An administrator in Epic can configure parts of the Epic
interface for users.
Administrators can have many responsibilities depending on which applications, or parts of the
Epic software, they are responsible for managing. Examples of Epic applications include
EpicCare Ambulatory for outpatient workflows, Stork for obstetric workflows, and Cogito Ergo
Sum, or Cogito, for analytics tools and content.
Another term for an administrator in Epic is an analyst. The term administrator typically refers to
a user's login setup (Lorena logs in as a Cogito Tools Administrator) while analyst refers to the
individual's role in an organization (Lorena works as a Cogito Analyst), although exact usage
may vary depending on your organization. More information about Cogito roles, or roles on an
Epic reporting team, will be covered in a later lesson.
A common administrator workflow is to update existing or create new build in the system. Build
refers to the parts of Epic that configure the interface and the user experience, such as
dashboards or order sets. While users interact directly with data about patient care, administrators
interact with the build that presents the data in a certain way.
Much of the build in Epic is saved in discrete records in Chronicles. Each record has an ID and
build records can be edited by administrators who have the appropriate permissions, or security,
to do so. To help keep track of new build records, administrators are encouraged to use build
, Cog170 Fundamentals Questions With
Solutions
trackers, spreadsheets with a list of new record IDs, names, owning teams, and any other relevant
information to assist with tracking and maintenance.
Hyperspace vs Chronicles vs Classic The Classic client is the original Hyperspace client.
As of Epic's May 2022 release, all end-user facing activities are available in the new, web-based
Hyperspace. However, many administrative activities have not yet been migrated and are
available only in the Classic client.
Throughout the Cogito Fundamentals class you will edit build records using administrator
activities in Classic. Most of these activities are also available in Hyperspace.
If you need to build, configure records, or use utilities, do so in the Classic client. Some admin
activities are already available on the Hyperdrive client, and more will be migrated over time. Be
sure to test your build/configuration in Hyperspace on the Hyperdrive client. Log in to
Hyperspace as an appropriate test user, one who represents users affected by your build. For
example, if you build an order set, log in to Hyperspace as a test physician to confirm that the
order set works as expected.
Epic plans to eventually migrate all administrative activities from Classic to the new web-based
Hyperspace. When that migration is complete, the Classic client will be retired.
What term describes the tasks a user performs in Hyperspace as part of their job? A
workflow
