Epic Cogito Certification (Set
1) test with 100% correct
answers
User
-everyone who logs in to Epic
-perform a variety of tasks using different parts of the Epic system
-log into Epic to do their jobs
Administrator
-build content to meet users' needs
-their Cogito tasks include creating dashboards and reports
Previous
Play
Next
Rewind 10 seconds
Move forward 10 seconds
Unmute
0:01
/
0:15
Full screen
Brainpower
Read More
Workflow
-steps that a user takes in Epic
-For example, a clinician might open their schedule, review a
patient's medical history, open the patient's chart, place an order,
,and sign a note.
-Different for different users
Hyperspace
Epic's front‐user interface (front-end), accessed on the Hyperdrive
client (what most users think of as "Epic")
-Users log in to it to complete their workflows and do their jobs
-Users log in here, do stuff
-Administrators log in here, test stuff
-Many admin activities not yet available here
Administrators and Hyperspace
log in to Hyperspace to test and troubleshoot build
Activities
-Users navigate to different activities in Hyperspace when
completing their workflows.
-A scheduler can use the Appts activity to create a new
appointment, a clinician can review messages from the In Basket
activity, and a report writer can modify report settings from the
Analytics Catalog activity.
Epic menu
contains all the activities a user has access to
Epic search
under the Epic button; an efficient way to launch a Hyperspace
activity
Assistant bar
at the top of Hyperspace; an efficient way to launch a Hyperspace
activity
Chronicles
-Epic's database management system ("the database")
-The data that users access in Hyperspace lives in Chronicles. -When
a user logs in to Hyperspace and opens a patient's chart,
Hyperspace is requesting data from Chronicles.
-When a user documents information in a patient's chart, they are
saving data to Chronicles.
Administrator
, -can configure parts of the Epic interface for users.
-can have many responsibilities depending on which applications, or
parts of the Epic software, they are responsible for managing.
-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﴿
Applications
-parts of the Epic software
-Examples include EpicCare Ambulatory for outpatient workflows,
Stork for obstetric workflows, and Cogito Ergo Sum, or Cogito, for
analytics tools and content
Analyst
refers to the individual's role in an organization ﴾Lorena works as a
Cogito Analyst﴿
Build
A common administrator workflow is to update existing or create
new build in the system
-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.
Security
appropriate permissions
Record
Each record has an ID and build records can be edited by
administrators who have the appropriate permissions, or security,
to do so.
Change Management practices
to keep track of new and modified build in Epic environments so
users and administrators have a smoother experience using Epic
Build Tracker
-way to track build records, typically a spreadsheet that lists new
records built in the system.
1) test with 100% correct
answers
User
-everyone who logs in to Epic
-perform a variety of tasks using different parts of the Epic system
-log into Epic to do their jobs
Administrator
-build content to meet users' needs
-their Cogito tasks include creating dashboards and reports
Previous
Play
Next
Rewind 10 seconds
Move forward 10 seconds
Unmute
0:01
/
0:15
Full screen
Brainpower
Read More
Workflow
-steps that a user takes in Epic
-For example, a clinician might open their schedule, review a
patient's medical history, open the patient's chart, place an order,
,and sign a note.
-Different for different users
Hyperspace
Epic's front‐user interface (front-end), accessed on the Hyperdrive
client (what most users think of as "Epic")
-Users log in to it to complete their workflows and do their jobs
-Users log in here, do stuff
-Administrators log in here, test stuff
-Many admin activities not yet available here
Administrators and Hyperspace
log in to Hyperspace to test and troubleshoot build
Activities
-Users navigate to different activities in Hyperspace when
completing their workflows.
-A scheduler can use the Appts activity to create a new
appointment, a clinician can review messages from the In Basket
activity, and a report writer can modify report settings from the
Analytics Catalog activity.
Epic menu
contains all the activities a user has access to
Epic search
under the Epic button; an efficient way to launch a Hyperspace
activity
Assistant bar
at the top of Hyperspace; an efficient way to launch a Hyperspace
activity
Chronicles
-Epic's database management system ("the database")
-The data that users access in Hyperspace lives in Chronicles. -When
a user logs in to Hyperspace and opens a patient's chart,
Hyperspace is requesting data from Chronicles.
-When a user documents information in a patient's chart, they are
saving data to Chronicles.
Administrator
, -can configure parts of the Epic interface for users.
-can have many responsibilities depending on which applications, or
parts of the Epic software, they are responsible for managing.
-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﴿
Applications
-parts of the Epic software
-Examples include EpicCare Ambulatory for outpatient workflows,
Stork for obstetric workflows, and Cogito Ergo Sum, or Cogito, for
analytics tools and content
Analyst
refers to the individual's role in an organization ﴾Lorena works as a
Cogito Analyst﴿
Build
A common administrator workflow is to update existing or create
new build in the system
-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.
Security
appropriate permissions
Record
Each record has an ID and build records can be edited by
administrators who have the appropriate permissions, or security,
to do so.
Change Management practices
to keep track of new and modified build in Epic environments so
users and administrators have a smoother experience using Epic
Build Tracker
-way to track build records, typically a spreadsheet that lists new
records built in the system.
