SEND

A warning SD0018 "Invalid value for CLTESTCD variable" seems to be thrown when CLTESTCD is not upper case.

There is no rule in the SENDIG which requires that entries in this variable be in uppercase text, and CLTESTCD does not use controlled terminology.  It seems perhaps that this rule has somehow been assumed based on controlled terminology in other domain TESTCD entries. 

If there is a source for this rule, please provide this as a reference, otherwise I think this is not a valid check.

Edit: obviously I did something wrong, next time I tried everything worked fine.

It appears there may be an error in the SEND Config file.  Up until Pinnacle21 Community version 2.1.2, the dataset variable types seemed to match the SENDIG.

Now they appear to no longer be in alignment.  This is returning false errors I believe.  I noticed this case in the LB Domain, where the dataset type according to SENDIG is Num or numeric for LBORNRLO and LBORNRHI.  Our LB.xpt file contains this information at the metadata level, but the validator returns error SE0055/FDAN032.  Prior versions had this type as float.

Please check the SENDIG, but I believe that in “config-send-3.0.xml” you should remove the “s” from the end of this line: <ItemDef OID="LB.LBSTNRC" Name="LBSTNRC" DataType="text" def:Label="Reference Range for Char Rslt-Std Units"/>

Bill Houser.

Hi,

SD0007 (Inconsistent value for standard unit) is currently flagged as an Error by the validator.  However, there are legitimate cases where there can be multiple units for a given test in a domain, such as the LB domain in SEND (one sample case is where differing values of LBCAT can have different standard units for the test within the LBCAT; but there are also other cases like LBMETHOD or a random SUPP variable are what keeps them unique).

Please change this rule to a warning.

Hi all,

I'm getting this Error reported for the following scenario:

TSSEQ   TSGRPID   TSPARMCD   TSPARM   TSVAL

1    1    TFCNTRY    Test Facility Country    USA
1    2    TFCNTRY    Test Facility Country    CHE

Do you think it is normal to get this error, that TSSEQ is the same (1) for TFCNTRY when the TSGRPID values are different?

Hi all,

Please see below a set of observations made after running some tests with Validator 1.5 on some SEND datasets. The info was also sent by e-mail, but is also shared here for the public review.

Hello all,

I am trying to implement a new rule. The rule description is:

Missing values for DSDTDY and --DY and --DTC & RFSDTC. Either of these three timing variables should be populated: [DSSTDY] or [--DY] or [DTC and DM, RFSTDTC].

This rule is applied to OM,MA,MI,TF,DM.

I implemented as follwoing:

--------- System Information ---------
 Version: 1.4.1
     JRE: 1.7.0_01
      OS: Windows 7 6.1 amd64
--------------------------------------

java.lang.IllegalArgumentException: The variable USUBJID does not exist in this DataRecord
    at org.opencdisc.validator.data.DataRecord.getValue(DataRecord.java:130)
    at org.opencdisc.validator.data.DataSupplement.<init>(DataSupplement.java:59)

Hello all,

I've noticed some differences of the validation report on the same studies, when using:

a) the GUI 1.4.1 version available for download on the website;

and

b) the command-line version from the SVN repository.

The version available now on SVN contains some improvements / bug fixes on top of the 1.4.1 released version? Or it is an older, unmaintained version?

What would you recommend using for our internal tests for now?

Thanks!