Hi Snehal,
It is fixed now. Please re-upload CT files.
Sorry for inconvenience.
Thank you for reporting this bug!
Kind Regards,
Sergiy
Hi Sergiy,
Thank you for your reply and fixing the issue.
P.S: We can be beta testers for your next community version if you would prefer.
Regards,
Snehal
Hi Sergiy,
I download the latest odm file for 2018-12-21 CT and experiencing the same issue where CT2001 and CT2002 issues are not being output. Can this be fixed please?
Thanks
Hi Deepika,
Our CT files look fine. Please ensure that you correctly follow our instructions on CT installation.
https://www.pinnacle21.com/configuring-pinnacle21-community-validator-cdisc-controlled-terminology
Kind Regards,
Sergiy
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">