d Dave
on

 

I've discovered an issue with the validation of the variable order in the SE domain under SDTMIG 3.2 (model v1.4). 

Looking at the SDTM 3.2.xml configuration file, the timing variables in SE are ordered VISIT, VISITDY, TAETORD, EPOCH, SEDTC, SESTDTC, SEENDTC, SEDY, SESTDY, SEENDY, which matches the order from table 2.2.5 ("Timing Variables for All Classes") of the v1.4 model.

However, in Subject Elements Table section of the v1.4 model (Section 2.2.8 and Table 2.2.8), TAETORD and EPOCH appear after SESTDTC and SEENDTC, and the same is true of the SE table in the SDTMIG v3.2. 

My assumption would be that in these cases the specific ordering provided for the SE domain should override the default order of the timing variables, but it seems that Pinnacle 21 does not use this domain-specific ordering.  Note that the model section 2.2.5 says that the timing variables "are available for use in any domain based on one of the three general observation classes", but that SE is NOT actually based on one of those general observation classes, which would suggest that the order in table 2.2.5 should not override the specific order given for the SE domain.

Forums: Define.xml

Want a demo?

Let’s Talk.

We're eager to share and ready to listen.

Cookie Policy

Pinnacle 21 uses cookies to make our site easier for you to use. By continuing to use this website, you agree to our use of cookies. For more info visit our Privacy Policy.