You join ResearchStudyPatientAssociationFact.StudyCoordinatorComboKey to
EmployeeBridge in the FullAccess schema by following Caboodle's documentation
and discover that one research study returns multiple rows. What does this indicate?
A. The bridge neglected to apply the IsCurrent = 1 filter, and there would have been
one row had it been applied
B. The research study had multiple study coordinators
C. One employee is the study coordinator for multiple research studies
D. All research studies have multiple study coordinators
Give this one a try later!
, B. If you use the FullAccess schema and follow Caboodle's documentation
and return multiple rows from the bridge for one row of the starting table,
then the one row of the starting table was associated with multiple rows of
the target table.
How are ProcedureDim.ProcedureKey and ProcedureDim.DurableKey different?
A. ProcedureKey is the primary key, and DurableKey identifies each procedure
B. ProcedureKey identifies each procedure, and DurableKey is the primary key
C. ProcedureKey is the primary key, and DurableKey is a lookup column
D. DurableKey is the primary key, and ProcedureKey is a lookup column
Give this one a try later!
A. ProcedureDim is a snapshot table with a durable key column. In such
tables, the primary key and durable key are different. The DurableKey
column identifies the entity represented by the table.
Consider the documentation shown below from SurveyAnswerFact in the Cogito Data
Dictionary. What is the difference between using PatientKey and PatientDurableKey?
Which one should you
use?
[Image]
Give this one a try later!
The PatientKey column joins to PatientDim.PatientKey. This join will return
exactly one matching row from PatientDim. This will be the row in
PatientDim that was current at the time SurveyAnswerFact was populated,
but it may return stale data at the time the report is run.
The PatientDurableKey column joins to PatientDim.DurableKey. This join will
return at least one matching row from PatientDim. Adding the filter WHERE
, PatientDim.IsCurrent = 1 will return only the current row from PatientDim.
This join is preferred.
A query filters PatientInfectionFact to only rows where InfectionStatus = N'Active'. Can
this query return PatientInfectionFact rows that are inferred rows or
PatientInfectionFact rows whose source data has been deleted?
A. No
B. Just inferred rows
C. Just rows whose source data is deleted
D. Both inferred rows and rows whose source data is deleted
Give this one a try later!
A. If you filter on a column that stores source data, it removes inferred rows
(which store *Unknown in nvarchar columns) and rows whose source data is
deleted (which store Deleted in nvarchar columns).
Suppose you're creating a report using EncounterFact and ProviderDim that displays
the name of each provider for each encounter. If an encounter's data loads into
EncounterFact, but that provider's data hasn't been extracted to ProviderDim, what
value would appear in ProviderDim.Name for this encounter?
A. *Unspecified
B. *Not Applicable
C. *Deleted
D. *Unknown
Give this one a try later!
EmployeeBridge in the FullAccess schema by following Caboodle's documentation
and discover that one research study returns multiple rows. What does this indicate?
A. The bridge neglected to apply the IsCurrent = 1 filter, and there would have been
one row had it been applied
B. The research study had multiple study coordinators
C. One employee is the study coordinator for multiple research studies
D. All research studies have multiple study coordinators
Give this one a try later!
, B. If you use the FullAccess schema and follow Caboodle's documentation
and return multiple rows from the bridge for one row of the starting table,
then the one row of the starting table was associated with multiple rows of
the target table.
How are ProcedureDim.ProcedureKey and ProcedureDim.DurableKey different?
A. ProcedureKey is the primary key, and DurableKey identifies each procedure
B. ProcedureKey identifies each procedure, and DurableKey is the primary key
C. ProcedureKey is the primary key, and DurableKey is a lookup column
D. DurableKey is the primary key, and ProcedureKey is a lookup column
Give this one a try later!
A. ProcedureDim is a snapshot table with a durable key column. In such
tables, the primary key and durable key are different. The DurableKey
column identifies the entity represented by the table.
Consider the documentation shown below from SurveyAnswerFact in the Cogito Data
Dictionary. What is the difference between using PatientKey and PatientDurableKey?
Which one should you
use?
[Image]
Give this one a try later!
The PatientKey column joins to PatientDim.PatientKey. This join will return
exactly one matching row from PatientDim. This will be the row in
PatientDim that was current at the time SurveyAnswerFact was populated,
but it may return stale data at the time the report is run.
The PatientDurableKey column joins to PatientDim.DurableKey. This join will
return at least one matching row from PatientDim. Adding the filter WHERE
, PatientDim.IsCurrent = 1 will return only the current row from PatientDim.
This join is preferred.
A query filters PatientInfectionFact to only rows where InfectionStatus = N'Active'. Can
this query return PatientInfectionFact rows that are inferred rows or
PatientInfectionFact rows whose source data has been deleted?
A. No
B. Just inferred rows
C. Just rows whose source data is deleted
D. Both inferred rows and rows whose source data is deleted
Give this one a try later!
A. If you filter on a column that stores source data, it removes inferred rows
(which store *Unknown in nvarchar columns) and rows whose source data is
deleted (which store Deleted in nvarchar columns).
Suppose you're creating a report using EncounterFact and ProviderDim that displays
the name of each provider for each encounter. If an encounter's data loads into
EncounterFact, but that provider's data hasn't been extracted to ProviderDim, what
value would appear in ProviderDim.Name for this encounter?
A. *Unspecified
B. *Not Applicable
C. *Deleted
D. *Unknown
Give this one a try later!
