When things just don't seem to work
Hi,
There is a bug in the configuration file: I get a message stating: "Value for QSTEST not found in (CDR TEST) CT codelist", looking at config file i found number Codelist Code number are switch between QSTEST & QSTESTCD.
Hi,
We noticed many false positives with CT0181 and CT0182, and upon further investigation it looks like the configuration file has the CT Codelist Codes switched (C101817 where C101818 should be, and vice versa). We saw this with the 3.1.3 configuration.
Thanks,
Brian
Hi ,
I am trying to validate the input file through java program. I have define.xml in one location.
I tried to open the define.xml file through java , i get schematron error. the file is present in location.
I tried to validate the file in standalone opebdisc clinet , it is generating the error report.
I am new to OPendisc and SAS please let me know any hints. I am stuck on this from 2 days.
In my TS domain, OpenCDISC 1.5 with SDTM IG 3.1.3 and the CDISC CT version 2014-03-28, I'm getting CT0081 and CT0081R errors on the TSPARMCD="SPONSOR" and TSPARM="Clinical Study Sponsor" record.
The message is that the two values do not have the same code in the CDISC CT, but in fact both of them have the code C70793.
Any idea what might be going wrong with this test?
It appears that as of the 2014-06-27 release, the controlled terminology file "QS Terminology.txt" has been renamed to "QS-FT Terminology.txt" to reflect the fact that it now includes terminology for functional tests.
Is it necessary to rename the file to match the old name when I place it in Config\Data\CDISC\SDTM\2014-06-27 ? Or wil OpenCDISC read any correctly-formatted TXT files out of that directory regardless of the name?
Using SDTMIG 3.2 config, in version 1.5 of OpenCDISC, the variable --PSTRGU triggers 'SDTM Required variable not found' in a sponsor defined interventions domain. This variable is not required in any other intervention domain in the SDTMIG. I think this must be a problem with your config file. This should not be required.
We have OpenCDISC installed and it takes many minutes or never for the OpenCDISC window to appear.
We have JRE 1.6.0_17
Actually, as of now, this app is not useable.
Can anyone help?
Tom pineo