ACING CLR 110 EXAMS WITH THE LATEST A+ QUESTIONS
AND ANSWERS GUIDE BOOK.
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
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
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?
AND ANSWERS GUIDE BOOK.
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
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
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?
