e Elizabeth


When the Inclusion/Exclusion criteria do not change, but a new one is inserted in a subsequent version, the criteria number has been identified by adding a suffix to the IETESTCD.


TIVERS=Version 1


IETEST=Ongoing infection


TIVERS=Version 2


IETEST=Patients with melanoma


IETEST=Ongoing infection


Pinnacle 21 however gives the following message for the EXCL02A record, since the same IETEST now has two different IETESTCD.

Inconsistent value for IETESTCD within IETEST


With further explanation:


All values of Inclusion/Exclusion Criterion Short Name  (IETESTCD) should be the same for a given value of Inclusion/Exclusion Criterion (IETEST).

I believe this business rule should exclude the TI domain for this reason.  The criteria number must be reference in IETESTCD, or there is no way to link it to the CRF/Protocol/Data entry value.  This rule should be for IETEST within a TIVERS.

Forums: SDTM

on February 2, 2023

Hi Elizabeth, 

SD1150 and SD1151 rules will be updated in the next Engine release by adding TIVERS variable as shown in your example.

Kind Regards,

e Elizabeth
on February 2, 2023

Thanks Sergiy, that's great.  I think, however, that SD1150 is correct without TIVERS.  The SDTM IG makes it clear that a different exclusion criteria (IETEST) should have a different code (IETESTCD), which is why my example includes a suffix.


on February 2, 2023

It looks like invalid utilization of IETESTCD instead of TIVERS variable for versioning of IE Criteria

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.