We were validating our data against 2018-09-28 CT and SDTM 3.2 config file and observed that Pinnacle21 validator community version 2.2.0 is not firing CT2001/CT2002 checks even though our data is incorrect. When we manually edited the format (please ref below example) for that particular CT in config file & CT file, checks got fired and we got warning/error messages (e.g SEX value not found in 'Sex' non-extensible codelist) in the report.
We are suspecting that this CT format change will affect all other CT checks as well. So, could you confirm if this is a known issue? Also, if it is then when can we expect the resolution of this?
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.
We were validating our data against 2018-09-28 CT and SDTM 3.2 config file and observed that Pinnacle21 validator community version 2.2.0 is not firing CT2001/CT2002 checks even though our data is incorrect. When we manually edited the format (please ref below example) for that particular CT in config file & CT file, checks got fired and we got warning/error messages (e.g SEX value not found in 'Sex' non-extensible codelist) in the report.
We are suspecting that this CT format change will affect all other CT checks as well. So, could you confirm if this is a known issue? Also, if it is then when can we expect the resolution of this?
Example:
Current format in SDTM 3.2 config file:
<CodeListRef CodeListOID="CL.C66731.SEX"/>
Edited format by us in config file:
<CodeListRef CodeListOID="CL.SEX"/>
Current format in 2018-09-28 CT file:
<CodeList OID="CL.SEX" Name="Sex" DataType="text" nciodm:CodeListExtensible="No">
Edited format by us in 2018-09-28 CT file:
<CodeList OID="CL.C66731.SEX" Name="Sex" DataType="text" nciodm:CodeListExtensible="No">