Validation Rule Suggestions

Hi all,

I'm having the following situation:

If I populate TFRESCAT for situations when TFSTRESC=TFORRES is empty and TFSTAT=NOT DONE, the SD0045 warning is trigerred: "Missing value for --STRESC, when --RESCAT is populated".

But TFRESCAT is a Required variable, so if I try to leave it empty, the SD0002 error  is trigerred: "NULL value in -- variable marked as Required".

I could either:

a) change optionality for TFRESCAT from Required to Permissible (as for MIRESCAT); but the SEND requirements will no longer be followed...

Hello,

This rule fires when there are unscheduled/unplanned visits in a domain and the visit is not in the TV domain. However, we would never expect unplanned visits to be in the TV domain since it only hold planned visits.

Is it possible to modify the rule so that if the VISIT contains the word "Unscheduled" the rule does not fire

Regards,

David

Rule SE0001 seems to be included in SD0007. See below:

SE0001 - "Inconsistent value for Standard Units" - Standard Units (--STRESU) variable values must be consistent for all records with same Short Name of Measurement, Test or Examination (--TESTCD) and  Specimen Type (--SPEC) variables values.

SD0007 - "Inconsistent value for Standard Units" - Standard Units (--STRESU) must be consistent for all records with same Short Name of Measurement, Test or Examination (--TESTCD), Category (--CAT), Specimen Type (--SPEC) and Method of Test or Examination (--METHOD).

Hi all,

I noticed that the following rule was excluded from the latest config-send-3.0.xml from SVN:

CT0009 = "Value for DOMAIN not found in (DOMAIN) CT codelist" = "Domain Abbreviation (DOMAIN) variable values should be populated with terms found in 'Domain Abbreviation' (C66734) CDISC controlled terminology codelist".

I was wondering what was the reason for removing this rule. The rule seems legit.

When the disposition date (DSSTDTC) is specified with a precision of date/time (e.g., 2012-12-31T10:59:03) whereas the exposure end date (EXENDTC) is specified only to the date-level (e.g., 2012-12-31), rule SD0082 ("Exposure end date must be less than or equal to latest disposition date") fires.

It appears as though the processing assumes that the EXENDTC without a time specified must be 12am (e.g., 2012-12-31T00:00:00), so it will always appear as before the DSSTDTC.

I would like to request the removal of validation rule SE0063 ("SEND/dataset variable label mismatch") from the SEND 3.0 ruleset.

There is no stipulation in the SENDIG or SDTM that the SAS XPT file variables' Label field must be populated with the Variable Label from the implementation guide.  In addition, this information is redundant with what is already represented in the define.xml.

Troy Smyrnios

Would it be possible to add to each rule description in the Rules tab the corresponding WebSDM ID (e.g.  IR5136)?

Hello there,

After checking out the latest version of config-send-3.0.xml from SVN, I get the following warning: "SD1054" - "Non-recommended variable length" for variables like BWBLFL, BWFAST, BWEXCLFL, CLEXCLFL.The warning's description is: "The length of flags variables (----FL, --FAST, --OCCUR, --PRESP) is expected to be 2".

But the values for those type of variables (that are controlled by the CL.C66742.NY code list) are "Y" or null.

Hello all,

SEND specs allows you to specify some numeric results (e.g. for weighings) in both "collected" and "standardized" form, where:

a) the "collected" form is "Result of the measurement or finding as originally received or collected." (--ORRES and --ORRESU variables);

b) the "standardized" form is the "the result value for all findings or derived from ORRES in a standard format or standard units" (--STRESC, --STRESN, --STRESU variables).

Hello,

I am using Validator 1.3 and I ran it on a study that did not have IDVAR and IDVARVAL in SUPPDM. No error was produced in the report. I think this should be a check in OpenCDISC validator.

Regards,

David.