2026/2027 WITH ACTUAL CORRECT
QUESTIONS AND VERIFIED DETAILED
ANSWERS |CURRENTLY TESTING
QUESTIONS AND SOLUTIONS|ALREADY
GRADED A+|NEWEST |BRAND NEW
VERSION|JUST RELEASED!!
You have a patient query and would like to display the name of the patients providers. Item EPT
18867 Admitting Provider is a networked item that points to the SER master file. How can you
use Column Search help to display the name of the admitting provider
Use Column Search on EPT 18867 to find the foreign key column in the starting table. You can
also use Column Search on SER .2 to find the table that stores provider names. Use the foreign
key of the starting table to join to the primary key of the destination table.T
True or False Would it be possible to have more than one copy of the same table in one report?
Why or Why not?
True because Chronicles master files can reference each other multiple times there are multiple
ways to link Clarity tables together.?
If an items response type is multiple what element will be present in the primary key of the
table that extracts the item?
LINE
What is the most common database object in Clarity
Extracted tables are the most common database object in Clarity.
The Clarity data model
simplifies the Clarity ETL process allowing data to move efficiently from Chronicles to Clarity.
1|Page
,A number of view and derived tables have been developed by Epic
These database objects obtain information from existing extracted tables and combine data
together in one place for ease of reporting.
ER Diagrams
Entity Relationship Diagram. A visual tool that shows relationships between database objects
relevant to a particular reporting area.
Contain information such as:
Common tables and their links for a particular reporting area.
Relationship cardinality of frequent joins.
ER Diagrams will not document all possible joins between Clarity tables.
Data Mart
Subset of date designed to meet the needs of specific reporting area.
Views and Derived tables are considered SQL based data marts which use information already
stored in Clarity database.
Dependent Database Objects
Section of the Summary tab. Provides a list of Clarity tables and columns and even views and
derived tables that form the underlying structure of a given database object.
Clarity Console verifies that all dependent database objects have finished loading data before
running any scripts to populate derived tables.
Entity
A person, place or concept about which information is kept. An entity is a database object in the
Clarity Data Model.
Relationship
An association between two entities. A relationship is a foreign key in the Clarity Data Model
Parent
2|Page
,An entity that contributes a foreign key to another entity. The one side of a one to many
relationship
Child
An entity that inherits a foreign key from another entity. The many side of a one to many
relationship
Cardinality
The numeric relationship between rows in the parent table and rows in the child table. This
usually denoted in the "M to N" statement. For example one to one or zero to one to one or
more
Existence
Also known as optionality. Existence refers to whether or not the child entity must have a parent
entity. There are two kinds of existence mandatory and optional.
Mandatory Existence
Ifs not possible for the foreign key in the parent entity to have a null value in the child entity. For
example the relationship between PAT_ENC.PAT_ID and PATIENT.PAT_ID is mandatory because
there cannot be an encounter for a patient without having the patient. The cardinality of such a
relationship is always one to X so such relationships are drawn with a 1 on the parent side.
Optional Existence
It is possible for the foreign key in the parent entity to have a null value in the child entity. For
example because an encounter may not be closed when the Clarity extract process occurs the
relationship between PAT_ENC.ENC_CLOSED_USER_ID and CLARITY_EMP.USER_ID is optional.
The cardinality of such a relationship is always zero to one to X such relationships are drawn
with a 0 on the parent side.
Type
3|Page
, The type of a relationship is determined by how the parent entity primary key is used in the
child entity. There are three types of relationships identifying and non identifying and non
specific.
Identifying Relationship
The primary key of the parent entity is contained in the primary key of the child entity and is
used to define the relationship between them. Note all the primary keys of the parent and child
entity do not have to be equal the child can potentially have more columns in its primary key
Such relationships are always mandatory and are drawn with solid llines.
Non Identifying Relationship
The primary key of the parent entity is not contained in the primary key of the child entity. Such
relationships are drawn as dashed lines.
Non Specific Relationship
Many to many relationships are referred to as non specific and are rare in the Clarity Data
Model. In almost all cases where such a relationship could arise. it has been resolved by the
introduction of an intermediate table.
When would you use V_PAT_ENC_FACT
When reporting on age of patients at the time of encounter
How is age calculated for hospital admissions?
It can be calculated in years or days at the time of an encounter. This information can be found
by checking the Scripts tab or by reading the column information.
What are dependent database objects listed in Clarity Compass How can you use this
information?
The list of database objects upon which this object depends.
This list can help determine what extracted tables and columns a view or derived table can be
used in place of.
4|Page