4: COG 240- FLEXIBLE DATA STRUCTURES
Clarity Report Component: Connection to Context - Answer -SMRTDTA_ELEM_DATA
Granularity: One row per HLV
Clarity Report Component: Answer - Answer -SMRTDTA_ELEM_VALUE
Granularity: One row per value per HLV
Clarity Report Component: Question - Answer -CLARITY_CONCEPT
Granularity: One row per HLX
Same as AttributeDim
SMRTDTA_ELEM_DATA provides context in two ways: - Answer -1) The type of
context is identified by the column CONTEXT_NAME, which includes values like
'PATIENT', 'ENCOUNTER', 'NOTE', and 'EPISODE'.
2)Based on the context, we will join to an appropriate table using one of the following
columns:
a. RECORD_ID_VARCHAR
b. RECORD_ID_NUMERIC
c. CONTACT_SERIAL_NUM
True or False: Filtering on context is critical for Clarity‐based SDE reports! Without the
appropriate context filter, there is no way to know if a given record ID represents a note,
an order, or something else entirely. - Answer -True
Note - Answer -Notes will be written during an encounter to record pertinent information
about a patient
Addendum - Answer -After a note has been signed, users may wish to revise the note.
In order to do so, a user must create an addendum to the note. After the addendum is
signed, it becomes a new contact on the existing note record. However, before the
addendum is signed, it exists as a separate, temporary note record. While the
addendum exists as a separate note record, it includes a pointer to the original note;
once the addendum is signed, the addendum becomes a part of that original record and
the temporary addendum record is deleted.
SmartData Element - Answer -We can think of SmartData Elements ﴾SDEs﴿ as discrete
questions that a user must answer in a particular situation
Clarity Report Component: Connection to Context - Answer -SMRTDTA_ELEM_DATA
Granularity: One row per HLV
Clarity Report Component: Answer - Answer -SMRTDTA_ELEM_VALUE
Granularity: One row per value per HLV
Clarity Report Component: Question - Answer -CLARITY_CONCEPT
Granularity: One row per HLX
Same as AttributeDim
SMRTDTA_ELEM_DATA provides context in two ways: - Answer -1) The type of
context is identified by the column CONTEXT_NAME, which includes values like
'PATIENT', 'ENCOUNTER', 'NOTE', and 'EPISODE'.
2)Based on the context, we will join to an appropriate table using one of the following
columns:
a. RECORD_ID_VARCHAR
b. RECORD_ID_NUMERIC
c. CONTACT_SERIAL_NUM
True or False: Filtering on context is critical for Clarity‐based SDE reports! Without the
appropriate context filter, there is no way to know if a given record ID represents a note,
an order, or something else entirely. - Answer -True
Note - Answer -Notes will be written during an encounter to record pertinent information
about a patient
Addendum - Answer -After a note has been signed, users may wish to revise the note.
In order to do so, a user must create an addendum to the note. After the addendum is
signed, it becomes a new contact on the existing note record. However, before the
addendum is signed, it exists as a separate, temporary note record. While the
addendum exists as a separate note record, it includes a pointer to the original note;
once the addendum is signed, the addendum becomes a part of that original record and
the temporary addendum record is deleted.
SmartData Element - Answer -We can think of SmartData Elements ﴾SDEs﴿ as discrete
questions that a user must answer in a particular situation
