CORRECT Answers
Compared to views, derived tables True, views are saved queries, their use can affect performance. Derived tables are
generally take less time to run because the stored procedures and thus perform better
data has been stored on the DB
After receiving a report request, you Analytics catalog
consult Clarity resources such as Clarity Database object search
Compass and the Clarity Dictionary without Column search
consulting Chroncile resources such as Clarity Dictionary on the
Item Editor and record viewer. What
problems may you run into?
A lab manager tells you he wants a report Ctrl + Click
on lab specimens, and shows you the field
where he can input various information.
What method would you use to find the INI
+ Item numbers of the data
he's looking for?
I IDM 130 is a networked item that is not Null
filled in for this record. What value will be
extracted to Clarity for this item, and other
Chronicles items that are not filled out?
What value will be extracted to Caboodle if the column is a key column, Caboodle will have a ‐1 letting report writers know that
for this item, and other networked items this value was not populated in the source, while still enforcing referential integrity.
that are not filled out in Chronicles?
T/F columns that are non primary keys True, even foreign key may be null.
contain null values
Not all fields are populated in Chronicles
Why do null values exist in Clarity ETL data cleansing deletes incorrectly formatted data
Data is deprecated y no longer extracted
, !Appendix E: Record Viewer Tip Sheet
contains more information on the filtering
options available in the record viewer
Shows the definition of chronicle items.
Item Editor
Shows information about how the item behaves for all values
Hot Keys Opening Chart Search - Ctrl + Space
What is a category list? a list of defined values that can be stored in a Chronicles item
1. more efficient
Benefits and limitations of using category
2. cannot only see first 100 values in item editor - must use category list maintenance
as a filter
to see complete list
no add
add types response each time
lookback
what is an add type describes how long a piece of data is valid
considered true for all cases.
no add if changed then old value is replaced
example: SSN, birthday
data stored separate on each contact record
response each time if blank then it is considered unknown
example: weight, blood pressure
store each item separately but if blank considers last value to be true
lookback
Example: age, address
add type
No‐Add stored on record, not contact.
considered true for all contacts
!Since both respond each time and
lookback items store data on the contact,
these add types are referred to as overtime
add types.
No‐Add data is stored at the record level
Overtime data is stored at the contact level.
Response type
Response Each Time stored separately on each of the records contacts
if blank, should be considered unknown
add type
Lookback stored separately on each contact
assume that last value entered remains true
determines how many lines an item can hold at one time
- Single Response
Response Type
- Multiple Response
- Related Group
!Since both multiple response and related
group items store more than one type of
data, these response types may collectively
be referred to as multiple response types.
Single data stores one line of data, while
Multiple data stores multiple lines of data.