Why RFSTDTC, RFXTSDTC , RFENDTC and RFXENDTC are called record qualifiers in DM whereas __STDTC variables in other domains are called as timing variables?
To get a more accurate and complete answer, I'd suggest asking the SDS team at CDISC.
I will take a stab at answering, but my answer doesn't feel particularly fulfilling even to me. Unlike the --STDTC variables where the -- takes on the domain id, the DM domain's Subject Reference Start Date/Time uses RF and not DM as the prefix. I can't give you a justification over the difference, but there is one. Interestingly, in the 3.1.1 STDMIG the DM RFSTDTC variable was classified as Timing as were the other --STDTC patterned domain variables like CMSTDTC.
Best regards,
Bill
RFSTDTC, RFENDTC, RFXSTDTC, RFXENDTC, RFICDTC, RFPENDTC and BRTHDTC represent date/time values, but they are considered to have
a Record Qualifier role in DM. They are not considered to be Timing Variables because they are not intended for use in the ge neral observation classes.
This is a great question that touches on the nuances of SDTM (Study Data Tabulation Model) terminology.
1. Record Qualifiers in DM:
The variables RFSTDTC
, RFXSTDTC
, RFENDTC
, and RFXENDTC
in the Demographics (DM) domain are referred to as "Record Qualifiers" because they define key aspects of the subject’s record that are critical to interpreting the entire dataset for that subject. In the context of DM, these variables provide important temporal references:
These dates are central to defining the study period and key events such as randomization for each subject. Since the Demographics domain serves as a summary of each subject's participation in the study, these dates are essential for interpreting the entire record and are therefore termed "Record Qualifiers."
2. Timing Variables in Other Domains:
On the other hand, __STDTC
variables (like AESTDTC
in the Adverse Events domain or LBSTDTC
in the Laboratory domain) are called "Timing Variables" because they provide the timing of specific events or observations within those domains. These timing variables help determine when an event (e.g., an adverse event) occurred or when a measurement (e.g., a lab test) was taken.
Unlike the DM domain, where the focus is on defining the overall participation timeline for the subject, the purpose of timing variables in other domains is to provide context for individual records or observations. They are critical for understanding when specific data points were collected but are not central to defining the subject's record as a whole.
In Summary:
Understanding this distinction is important for correctly interpreting the SDTM datasets and ensuring proper data analysis.
I hope this clarifies the difference! Please feel free to ask if you have further questions.
Best regards,
Sarath
Are you ready for the spotlight? We're accepting content ideas for SAS Innovate 2025 to be held May 6-9 in Orlando, FL. The call is open until September 25. Read more here about why you should contribute and what is in it for you!
Need to connect to databases in SAS Viya? SAS’ David Ghan shows you two methods – via SAS/ACCESS LIBNAME and SAS Data Connector SASLIBS – in this video.
Find more tutorials on the SAS Users YouTube channel.