COG170 Terms Flashcards
1
Q
is the hub of reporting and analytics in Epic, consolidating reporting content from all corners of your healthcare system. The one‐stop shop for all reporting content in Epic. This includes dashboards, components, SlicerDicer reports, Workbench reports, and links to third‐party reporting content. A centralized repository within Epic where users can find and manage various analytics content, such as reports, dashboards, and data extracts.
A
Analytics Catalog
2
Q
on the UserWeb contains documentation on Epic‐released reporting content. A comprehensive guide that provides detailed information about the data structures, fields, and relationships within a database or analytics system.
A
Data Handbook
3
Q
A visual interface that displays key metrics, data, and analytics in a consolidated and interactive format, allowing users to monitor and analyze performance at a glance.
A
Dashboard
4
Q
the name of Epic’s dashboard application, which falls under the Cogito umbrella. Reports, metrics, graphs, and links to useful activities can all be placed on a dashboard.
A
Radar
5
Q
An individual element or part of a larger system or interface, such as a widget or module within a dashboard. Components can be organized into regions.
A
Component
6
Q
the primary interface for editing dashboards. Both users and administrators can enter the Designer UI. For existing dashboards, the Designer UI is accessed by clicking the View Manager, then editing either the Original View or a personalized view. The user interface used by administrators or developers to design and configure dashboards, reports, and other analytics content.
A
Designer UI
7
Q
When administrators create a dashboard, it is considered a source dashboard and appears in Hyperspace as the Original View. Only administrators can edit the Original View of a source dashboard. The default or initial view of a dashboard or report before any customizations or modifications are made by the user.
A
Original View
8
Q
also called Original View. The original dashboard from which data or components are derived or copied to create other dashboards or views.
A
Source Dashboard
9
Q
A customized version of a dashboard tailored to meet the specific needs and preferences of an individual user. When users modify a dashboard, their changes are saved on a user‐specific view of the dashboard. Personalization to dashboard views includes the following:
* Add, remove, and rearrange components
* Set defaults for dashboard parameters
* Create and add a SlicerDicer component
* Personalize components
o Add, edit, rearrange, and delete links from link components
o Change the display name or display color of a component
o Add a badge to a table or graph component
o Change the thresholds on a table or graph component
A
Personalized View
10
Q
a tool or feature within software applications that allows users to manage and organize different views or perspectives of data or content.
A
View Manager
11
Q
When a user opens a view and the source dashboard has changed since the last time they opened it, the system performs reconciliation to update the view. The process of ensuring that data from different sources or systems is consistent, accurate, and aligned.
A
Reconciliation
12
Q
metadata includes the description, tags, content owner, reviewers, distribution methods, and more. A user with appropriate security can edit the metadata of Catalog content from within the Catalog. A tool used to manage and edit metadata, which includes information about the data, such as its source, structure, and relationship
A
Metadata Editor
13
Q
provide a discrete search option for reporting content. Tags can be added to all content types in the Catalog. Labels or keywords assigned to reports to categorize and organize them for easier retrieval and management
A
Report Tags
14
Q
a conceptual way to group data. For example, you could group your data by department, and department would be a summary level. The level of detail or aggregation at which data is summarized and presented in a report or dashboard.
A
Summary Level
15
Q
a specific entity in a summary level. For example, you might be interested in only the data from one obstetrics department, and that department would be the summary target
A
Summary Target
16
Q
refers to the collection of records that represent your organization’s physical and financial arrangements. Facility structure records define places where patient care happens and levels at which revenue is tracked. While every healthcare organization has a unique set of clinics, hospitals, and departments, the way your organization is structured generally follows a set hierarchy.
A
Facility Structure
17
Q
represents your entire organization. Some settings, such as diagnosis and procedure codes, are set at the facility level. Your organization has only one facility record
A
Facility Record
18
Q
represent distinct operational and financial divisions within your organization, each with its own set of billing tools and separate AR (accounts receivable). The number of service areas varies based on financial considerations and other factors
A
Service Area
19
Q
sometimes called revenue locations, are subdivisions within a service area and typically represent physical locations where your organization provides patient care
A
Location
20
Q
places where patient care takes place, such as a family medicine department, and/or administrative services are performed, such as a business office. Each department is associated with one location, and through that location with one service area.
A
Department
21
Q
Everyone who logs in to Epic
A
Users
22
Q
The 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 users have different workflows.
A
Workflow
23
Q
is Epic’s front‐user interface, accessed on the Hyperdrive client. Users log in to Hyperspace to complete their workflows and do their jobs. Administrators also log in to Hyperspace to test and troubleshoot build.
A
Hyperspace
24
Q
When you launch the Hyperspace icon in training, you’re launching a specialized web browse
A
Hyperdrive
25
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
Activity
26
contains all the activities a user has access to
Epic Menu
27
(under the Epic button) or the Assistant Bar (at the top of Hyperspace) are the most efficient ways to launch a Hyperspace activity.
Epic Search
28
Epic’s database management system, often referred to as “the database.”
Chronicles
29
in Epic can configure parts of the Epic interface for users.
Administrator
30
parts of the Epic software. 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
Applications
31
is another term for an administrator.
Analyst
32
refers to the parts of Epic that configure the interface and the user experience, such as dashboards or order sets.
Build
33
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
Record
34
appropriate permissions
Security
35
a way to keep track of new and modified build in Epic environments, so users and administrators have a smoother experience using Epic
Change Management
36
is a way to track build records. Typically, a spreadsheet that lists new records built in the system. This can be used to manage changes between versions, environments, or by specific teams.
Build Tracker
37
builds, validates, and distributes reports from three different databases, is responsible for the flow of data between those databases, and, depending on the organization, may be involved in building extracts, pulling data into Caboodle from other data sources, or building dashboards in third‐ party systems which rely on Epic data, or any number of other data‐related tasks. This broad range of responsibilities is met by a broad range of people
Cogito Analytics Teams
38
sometimes oversee operation of more than one database
Database Administrator
39
oversees the daily functioning and troubleshooting of Chronicles, as well as updates to the system. The Chronicles Administrator is most often referred to as the ODBA (Operational Database Administrator), or the Cache DBA. The ODBA is not part of the Cogito team, but they may assist in some troubleshooting related to Cogito functionality. Reasons to contact the Chronicles Administrator include
a. Workbench reports are displaying queuing errors
b. Workbench reports are running slowly or not running
Chronicles Administrator
40
oversees and troubleshoots nightly and ad‐hoc Clarity ETL executions that move data from Chronicles to Clarity. Because of this, they are sometimes called the Clarity ETL Administrator. They might also be called the ETL Administrator (without mention of Clarity), particularly if they oversee both Clarity and Caboodle ETL. The Clarity Administrator is also responsible for managing Epic‐released updates to Clarity and adding indexes to the Clarity database when appropriate. Reasons to contact the Clarity Administrator include:
a. Requesting an ad hoc ETL into a test Clarity database to validate a report with test data
b. A Clarity report looking at the last year's data isn't displaying anything for the most recent two months
c. Corrupted or incorrect data has made its way into Clarity reports that used to work perfectly
Clarity Administrator
41
oversees and troubleshoots nightly and ad‐hoc Caboodle ETL executions that move data from Clarity to Caboodle. Because of this, they are sometimes called the Caboodle ETL Administrator. They might also be called the ETL Administrator (without mention of Caboodle), particularly if they oversee both Clarity and Caboodle ETL. The Caboodle Administrator is also responsible for managing Epic‐released updates to Caboodle and any custom Caboodle tables or columns an organization decides to create. Reasons to contact the Caboodle Administrator include:
a. Requesting an ad hoc ETL into a test Caboodle database to validate a report with test data
b. SlicerDicer sessions are missing data for a conspicuous date range
c. Requesting to increase the file size limit for Data Gateway import files
Caboodle Administrator
42
is responsible for the success of the Cogito team. They have a high‐level understanding of each of the databases and tools used by their organization and have a detailed knowledge of the processes and policies that govern the reporting and analytics goals of the organization. Reasons to contact the Cogito Project Manager include:
a. Appropriately estimating time commitments for reporting projects
b. Ensuring data governance on complex reporting projects
c. Triaging or prioritizing reporting projects
Cogito Project Manager
43
BIDs) have some of the broadest responsibilities on the Cogito Team. They use all of Cogito's tools to retrieve and analyze data from all of Epic's databases. They get trained on Chronicles, Clarity, and Caboodle data structures and tools. In Hyperspace, they work with SlicerDicer, Radar, and Reporting Workbench, but may also assist application analysts who are working with registries or extracts and need more understanding of the underlying Chronicles data. Reasons to contact a BID may include:
a. Need for a new workbench report
b. Can't find specific report or dashboard and need someone to grant appropriate access
c. Troubleshooting existing reports, dashboards, or SlicerDicer sessions
d. Want to build or validate SQL‐based Workbench report
Business Intelligence Developer
44
may have different responsibilities depending on which application they specialize in. They interact most often with the Cogito team as subject matter experts ﴾SMEs﴿ who can help a report writer find the right data or understand a workflow used to populate the data for a report. Reasons to contact an Application Analysts may include:
a. Needing someone to validate the data on a dashboard or report and make sure it is realistic and appropriate for that application
b. Finding a specific data point populated by an end user workflow
Application Analyst
45
build the packages to bring data into Caboodle from Clarity and other non‐Epic data sources. They know how and why all data comes into Caboodle. They may also be Caboodle BIDs, building SQL queries to retrieve data from Caboodle. Since Caboodle is the data source for SlicerDicer, these developers also are involved in building custom SlicerDicer Filter or even entire data models. Reasons to contact a Caboodle Developer may include:
a. Need to add custom SlicerDicer Filter to an existing SlicerDicer Data Model
b. Scoping out the possibility of building a SlicerDicer Data Model on non‐Epic data
Caboodle Developer
46
may be one person's full‐time job, or it may be a task that several BIDs share at an organization. They are responsible for building and maintaining Workbench templates, as well as overseeing distribution of dashboards for the Cogito team. This user needs to have a deep understanding of the Chronicles data structure that drives Workbench queries. Reasons to contact a Cogito Tools Administrator include:
a. The need for a brand‐new template that doesn't yet exist
b. Troubleshooting a custom template's parameters
c. A SQL report has been built and needs to be integrated into Hyperspace so users can build reports from it
Cogito Tools Administator
47
is responsible for customizing and delivering reporting training to users at each organization. This may be one person's full‐time role, or a Principal Trainer may be responsible for several applications and include Cogito in their list of responsibilities. Reasons to contact a Cogito Principal Trainer may include:
a. Planning for which users should receive specialized SlicerDicer training after go‐live
b. Some users have been incorrectly building Workbench reports and need re‐training
c. Generating and distributing tip sheets or other training tools for ongoing optimization projects
Cogito Principal trainer
48
is a curated data set with a list of available filters, or data points, to analyze the data set. Epic releases many data models and filters and organizations can create custom data models and filter records as well.
SlicerDicer Data Model
49
filter records, represent data points. The SlicerDicer interface allows users to apply a filter in different ways, such as for grouping, aggregating, or narrowing down the results.
SlicerDicer Filter
50
When a user builds a report in a data model and saves it, that creates a session. SlicerDicer session build is defined by the cards that appear on the right: Population, Slices, Measures, Dates, and Visual Options. Not all cards need to be used when creating a session. Which cards are used will depend on the needs of the report.
Session
51
determines the entities included in your results. Will start with a base and are refined using criteria.
Population
52
Different data models have different bases to choose from. This narrows down the population to data that is most relevant to the user. For example, the My Patients in the Patients data model returns only the patients for whom the logged in clinician has provided care. Other populations include all records within a specific department, location, or service area. Provide an important security layer for SlicerDicer data models.
Base
53
selected from the Population card. They narrow down the results shown. Users can search by keyword or browse to find available criteria
Criteria
54
divide the population into groups, such as diagnoses, statuses, classes, modes, and other characteristics
Slices
55
perform an aggregation function on the data. This can be thought of as the number at the top of the bar in a vertical bar graph. SlicerDicer initially returns a count, but users can add or modify
Measures
56
the only place users get to see identified health information in SlicerDicer. As such, there are security points that limit a user's access to this feature.
Detail Table
57
opens in the Radar Admin workspace. It consists of several forms on the left. The precise forms and options available will vary based on the type of component being built. The Basic Information and Distribution forms are the same for all component types, while the Data Source and Output Format forms may vary
Component Editor
58
Filters records return only the most recent value stored
Last Stored
59
Filters that use the date range. In the Patients data model, the date range will be "All time" until at least one overtime filter is applied.
Overtime
60
users could find all patients who were diagnosed with a broken arm and had an active prescription for Tramadol at any point during the diagnosis
Overlapping Filters
61
users could find all patients with a prescription for Tramadol followed by a home health episode or find all physical therapy visits followed by a home visit. A data model linking path to the Patients data model is necessary for this feature.
Sequential Criteria
62
you could find all patients who were under 18 years of age when they received a diagnosis of depression.
age at the time of event
63
Some date range options are only available for data models with specific build. For example, in the Patients data model, criteria that are affected by the date range can have an override date range. users could find all patients with a broken arm in June who have a home visit scheduled in July.
Criteria Specfic Dates
64
This is used to ensure multiple criteria are met on the same encounter. These criteria can also be manually unlinked by clicking on the link icon.
Linked Criteria
65
shows all user filters
Filter Details
66
can be created in the Advanced Options in the Population card using the gear icon or they can be made from scratch by selecting the filters used as criteria in the session. Once saved, they can be found in their own category when browsing filter. While they are created in the Population card, they can be used anywhere normal filters can: as criteria, slices, measures, etc
combintation filters
67
Exclude slices. can be found below the “Grab Top/Bottom n” buttons and specifying a minimum and/or maximum measure value in the Slices card.
Liit your slice result
68
allow users to add multiple criteria to each bucket, giving them greater flexibility when grouping data, which can be found under the Advanced Options on the Slices card.
Custom Slices
69
An organized collection of data, typically structured to support efficient retrieval and management. In reporting tools, these are also called data sources.
Database
70
The origin and movement of data as it flows from one database to another, including how and when it has changed since being created
Data Lineage
71
Epic's non-relational database that stores data entered by users (e.g., nurses, doctors) in a tree-like structure, optimized for daily healthcare operations
Chronicles
72
A collection of records in Chronicles that stores specific types of data, such as patient information or provider details. (e.g., patient information).
master file
73
A unique entry within a master file that contains data about a specific entity, such as a patient or an appointment (e.g., a specific patient's record).
record
74
refers to an interaction or visit recorded in the system (e.g., a patient's visit).
contact
75
A specific data element within a record in Chronicles, identified by an INI (master file identifier) and item number
item
76
Epic's relational database designed for reporting on large amounts of data over long periods (e.g., date of birth).
clarity
77
Epic's data warehouse that holds data from multiple sources, including Clarity. It simplifies reporting by organizing data in a more intuitive manner.
Caboodle
78
Extract, Transform, Load. A process that transfers data from one database to another, such as from Chronicles to Clarity and then to Caboodle
ETL
79
Structured Query Language. A coding language used to generate sets of data from relational databases like Clarity and Caboodle.
SQL
80
A window in Epic that opens when using Ctrl+Click on an editable field, showing the INI and item number where the data is stored.
Item information window
81
An activity in Epic that allows users to view data from a record in Chronicles, find test values, and investigate relationships between master files.
Record Viewer
82
A unique identifier for a data element within a master file in Chronicles, used to locate and reference specific items.
Item Number
83
The format of data an item can store, such as string, number, date, time, instant, or category.
Data Type
84
Defines whether an item's value is specific to one contact or applies to all contacts in a record. Types include no-add, response each time, and lookback.
Add Type
85
Determines how many values an item can hold at once, such as single response, multiple response, or related group
Response Type
86
Defines relationships between master files by storing unique identifiers that reference records or contacts in Chronicles.
Networking
87
A process that improves the performance of Chronicles-based reports by storing a list of records pre-sorted by an item's values.
Indexing
88
A single entry within an item, especially for items that can store multiple values (e.g., multiple phone numbers).
Line
89
Identifies the master file where the data is stored.
INI (Master File Identifier)
90
Uniquely identifies a data element within a master file.
Item Number
91
A predefined structure in Reporting Workbench that defines the search engine, criteria, and display options for creating reports. Templates can query Chronicles, Clarity, or Caboodle data.
Workbench Template
92
A report created from a Workbench template that queries data based on specified criteria and displays the results. It can be customized and run by users.
Workbench Report
93
An instance of a Workbench report execution. Each time a report is run, a new run record is generated to display the results
Workbench Report Run
94
An instance of a Workbench report execution. Each time a report is run, a new run record is generated to display the results
Report Model
95
The interface in Reporting Workbench where users can view and interact with the results of a report after it has been run.
Report Viewer
96
A tab in the Results Viewer that allows users to visualize Workbench results using a SlicerDicer interface. Visualizations created here can be saved and distributed on dashboards
Explore Tab
97
A graphical representation of Workbench report results created in the Explore tab. These visualizations can be saved and added to dashboards
Workbench Visualization
98
A dashboard component that provides a manually maintained list of links to Workbench reports. It allows users to quickly access specific reports.
link component
99
A dashboard component that automatically updates to include links to reports that meet specified criteria. It helps users find relevant reports based on tags or other filters.
Report listing component
100
A personalized dashboard in Epic where users can access their favorite and recent reports, as well as other analytics tools.
My analytics
101
A report created by a user that is not visible to other users by default. It can be shared with specific individuals if needed
private report
102
A report created by administrators with the appropriate security settings. These reports are visible and can be run by any user with access to the report's template.
public report
103
A visualization of data returned by a Workbench report, created using the Summary tab in Report Settings. Summaries can be displayed as graphs or tables and appear as separate tabs in the Results Viewer.
Workbench Summary
104
A dashboard component that displays data in a tabular format. It can be based on a Workbench summary or visualization and includes options for formatting and thresholds
table component
105
A dashboard component that displays data in a graphical format. It can be based on a Workbench summary or visualization and includes options for graph type, axis labels, and legends.
graph component
106
A visual callout representing a single data point from a table or graph component. Can be configured to display specific measures and can be added to components through the Component Editor or personalization.
Badge
107
* Controls the search criteria, date range, and logic for the report.
* Determines which rows will be returned based on the specified conditions.
* Allows administrators to add additional criteria if they have the appropriate security.
Criteria Tab
108
* Manages the columns that will be displayed in the report.
* Allows adding or removing display columns and detailed views.
* Each display column retrieves and shows specific data on the report
Display Tab
109
* Sets the name of the report, its visibility (public or private), and distribution settings.
* Controls sharing settings for the report or its results.
General Tab
110
* Adjusts the font, color, and highlighting of rows or columns in the report results.
appearance tab
111
* Used for special formatting of printed or emailed report results.
print layout tab
112
* Allows removing or re-ordering action buttons in the report results.
toolbar tab
113
* Used to override template-level or system-level settings for a single report.
override tab
114
* These are criteria based on items that can have multiple values over time (e.g., blood pressure readings).
* The date range in the Report Settings window is used to evaluate these time-sensitive criteria.
* Only contacts within the specified date range will be included in the report results.
overtime parameters
115
* These are criteria based on items that have a single value for the entire record (e.g., date of birth).
* The date range does not affect non-overtime criteria, as they are not time-sensitive.
* The report will include records that meet the non-overtime criteria regardless of the date range.
Non overtime parameter
116
* These are criteria based on items that have a single value for the entire record (e.g., date of birth).
* The date range does not affect non-overtime criteria, as they are not time-sensitive.
* The report will include records that meet the non-overtime criteria regardless of the date range.
row in reporting workbench
117
* Configured in the Summary tab of Report Settings.
* Use a Workbench interface to define graphs or tables.
* Saved in Report Settings and appear as separate tabs in the Results Viewer.
* Based on available or selected PAF columns.
Workbench Summary
118
* Configured in the Explore tab of the Results Viewer.
* Use a SlicerDicer interface to create visualizations.
* Saved in the View Manager and can be distributed on dashboards.
* Based on selected PAF columns only.
Workbench Visualization
119
IDN A record that defines how raw data is summarized into a metric for display. It includes the formula or logic used to calculate the metric, such as the percentage of active MyChart users. To provide a standardized way to calculate and display key performance indicators (KPIs) and other metrics.
Metric Definition Record
120
IDK A record that stores settings related to how metric data is displayed on a dashboard. It includes information such as threshold levels, colors, and links to detailed reports. To configure and customize the display of metrics on dashboards, ensuring that users can easily interpret and interact with the data.
Dashboard Resource Record
121
A searchable library of metric definitions released by Epic, available on the UserWeb. It provides technical and business definitions to help organizations identify useful metrics.
Metric Repository
122
A standard or point of reference against which metrics can be compared.
Benchmark
123
The data and details associated with a specific metric, including its definition, calculation method, and display settings. This information is typically stored in metric definition records and dashboard resource records.
Metric Information
124
o Each row in the component represents a different resource.
o Use this setting to show several related resources for one summary target at a time.
o Example: Displaying different metrics (e.g., patient satisfaction, readmission rates) for a single department.
Resources
125
o Each row in the component represents a different summary target.
o Use this setting to show the same metric for different summary targets.
o Example: Displaying the same metric (e.g., average length of stay) for multiple departments.
Summary Targets
126
field in the Data Source form of the Component Editor determines the meaning of a row in a metric-based component
view as
127
o Acts as the frame for metric-based components on a dashboard
IDM Radar Dashboard Record
128
o Pulls together IDK records for display and controls metric-related settings
IDB (Radar Component Record)
129
o Stores settings related to how metric data is displayed, such as threshold levels and colors
IDK (Dashboard Resource Record):
130
o Defines how raw data is summarized into a metric for display
IDN (Metric Definition Record):
131
o Stores the actual data for the metric, organized by summary level, summary target, and date intervals.
CSF (Metric Data Record):
132
A diagnostic tool used to log and analyze the steps taken by a report or query to generate its results. It captures detailed information about the logic and processes evaluated during the report's execution. To help identify why a report returned specific results, including which records were included or excluded and which indexes were used. This is particularly useful for troubleshooting complex queries and ensuring data accuracy.
Trace
133
A feature that allows users to view unformatted values in addition to the formatted values displayed by a report column. It provides a more detailed view of the data being processed. To help explain unexpected behavior in report columns, such as issues with filtering or sorting
Debug
134
A record in the ECL master file that groups together security points to grant access to related activities and functionality within an Epic application. To manage and assign permissions to users based on their job responsibilities, allowing them to access specific features and activities in Epic.
Security Class
135
A specific permission that grants access to one feature or activity within Epic. To control access to individual functionalities. Users must have the required security to see and use certain activities in the system.
Security Point
136
A record in the EMP master file that contains information about a person who can log in to Epic, including their login ID, password, and security settings. To uniquely identify and configure each user, ensuring they have the appropriate access and permissions based on their role
User Role
137
An EMP record used to configure groups of users by applying a set of shared settings and security configurations. To ensure consistency and simplify maintenance by allowing changes to be made once in the template, which then apply to all linked user records.
User Template
138
A grouping mechanism used to distribute Cogito content, such as reports and dashboards, to users. Users and content must share at least one report group for the content to be accessible. To control which users can access specific reporting content, ensuring that only authorized users can view and interact with the data.
Report Group
139
A classification used to broadly describe a user's responsibilities and capabilities in the system, such as Nurse, Biller, or Physician. To automatically assign appropriate permissions and access to users based on their role, and to distribute content like SlicerDicer data models and Radar dashboards
User Type
140
They control:
Access to Activities:
o Determine which activities a user can see and use within Epic. For example, grant access to patient charting, order entry, or reporting tools.
Permissions:
o They define the permissions a user has within those activities, such as the ability to create, edit, or delete records.
Functionality:
o Control access to specific functionalities within an application, ensuring that users can only perform tasks relevant to their role.
Security classes
141
mechanisms used to control the distribution of reporting content in Epic
Report groups and user types
142
o Distribution: Used to distribute Cogito content, such as reports, dashboards, and SlicerDicer sessions. A user can access content if they share at least one ___ with the content.
o Customization: Can be assigned at the template or report level, allowing for customized distribution of content to specific user groups.
Report Group
143
o Automatic Assignment: Are automatically assigned based on a user's role and responsibilities, such as Nurse, Biller, or Physician.
o Content Access: Determine access to SlicerDicer data models, Radar dashboards, and components. If a user and content share a user type, the user can access that content.
o Overrides: Organizations can override default user type assignments with report groups to further customize content distribution.
User Type
144
Stores records for Radar dashboards. Manages the configuration and settings of dashboards, including layout and components.
IDM Master File
145
Stores records for Radar components. Manages individual components that can be added to dashboards, such as graphs, tables, and links.
IDB
146
Stores settings related to how data is displayed in Radar, known as dashboard resources. Configures the display settings for metrics, including thresholds, colors, and links to detailed reports
IDK
147
Stores records for Reporting Workbench report runs. Keeps track of each instance a report is run, including the results and performance statistics
HRN
148
Stores records for Reporting Workbench reports and SlicerDicer sessions. report records define which criteria, values, and display options will be used.Manages the configuration and settings of individual reports and saved SlicerDicer sessions.
HRX
149
Stores records for Reporting Workbench templates. Defines the structure and criteria for creating new reports, including search engines and display options.
HGR
150
Stores records for display columns used in reports. Manages the configuration of columns that retrieve and display specific data points in reports.
PAF
151
Stores records for SlicerDicer filters. Defines filters that can be applied to SlicerDicer data models to refine and segment data.
FDS
152
Stores records for SlicerDicer data models. Manages the structure and configuration of data models used in SlicerDicer for data exploration and analysis
FDM
153
the original Epic-released record that can be customized using override records. Serves as the foundation for Epic-released content, which can be modified to meet specific needs without altering the original record.
Base Record
154
A record that stores customizations made to an Epic-released base record. Allows administrators to modify Epic-released content to fit their organization's needs while preserving the original settings.
Override Record
155
A record that combines the settings of the base record and its override record to create the final configuration. Ensures that both the original and customized settings are applied, providing a complete and functional configuration
compiled record
156
can be used across all of our tools to limit which data a user sees in their results. Here are some examples of when these values come into play:
Some SlicerDicer data models require a user to have an authorized service area. Without one, the data model is completely inaccessible.
SlicerDicer data models can filter results automatically using the service area(s) listed.
Many Workbench templates use required “dynamic” parameters that filter by these values whenever the report is run. This means two users running the same HRX would see different results based on the values stored here.
Dashboard Summary Level Parameter selection is limited to the values stored here for all users viewing a dashboard.
Cogito Form
