The %CSTCHECK_CROSSSTDCOMPAREDOMAINS
macro compares values for one or more columns in one table with those
same columns in another domain in another standard. Or, it compares
the values against metadata from the comparison standard. The macro
requires use of _cstCodeLogic as a full DATA step or PROC SQL invocation.
This DATA or SQL step assumes as input a work copy of the column metadata
data set returned by the %CSTUTIL_BUILDCOLLIST macro. Any resulting
records in the derived data set represent errors to be reported.
Here are example validation
checks that use the %CSTCHECK_CROSSSTDCOMPAREDOMAINS macro:
-
ADaM subject not found in the SDTM
DM domain
-
ADaM SDTM domain reference (for
traceability), but the SDTM domain is unknown
An ADaM 2.1 validation
check that uses this macro is ADAM0653. Here is the rule description
for this check:
“Specified record
not found in SDTM for this subject.”
Here is the message
text for this check:
Corresponding
SDTM record not found based on STUDYID, USUBJID and AESEQ
Here is sample code
from the codelogic field from the ADaM 2.1 Validation Master data
set for validation check ADAM0653. In this example, &_cstDSName
(ADaM data set name) and &_cstCrossDataLib (SDTM library) are
generated by the macro prior to execution of codelogic.
%let _cstCheckVar=AETERM;
proc sql noprint;
create table work._cstproblems as
select adam.studyid, adam.usubjid, adam.aeseq, adam.&_cstCheckVar
from &_cstDSName as adam
left join
&_cstCrossDataLib..ae as sdtm
on adam.studyid=sdtm.studyid and adam.usubjid=sdtm.usubjid and
adam.aeseq=sdtm.aeseq
where adam.&_cstCheckVar ne sdtm.&_cstCheckVar
quit;