l Lenny
on

 

Hi,

I had generated a define.xml 2.0 using SAS Clinical Standards Toolkit 1.6, and it was successfully validated by OpenCDISC community 2.0.1 (0 messages were generated; 50,473 checks were performed).

But when I try to re-validate the xpt data together with this define, unexpected situation was met (Validation Complete! Validation took 10 seconds; 0 messages were generated; 0 checks were performed). The same xpt data were successfully validated before without define, how come they couldn't be put together now?

I have tried the validator 1.5 and everything was good, did I miss anything here for community 2.0.1?

Thanks a lot in advance!

Lenny

 

Forums: Define.xml

m Michael
on July 15, 2015

Can you delete your logs here, reproduce this event, then send us those logs files ? there should be two.

opencdisc-community\components\logs

 

 

s Steve
on October 29, 2015

I am having the same issues when trying to validate the define.xml with the *.xpt files.  It takes seconds to run and I get 0 records for output.  Is there any more information about this topic.

 

s Sergiy
on November 4, 2015

Hi all, 

Most likely this issue is due to a bug in current version of OpenCDISC. There is a conflict between Value Level Standard Terminology and Value Level Codelist in define.xml file. The application is confused about a correct source of metadata (standard vs. define.xml).

A typical example is when a codelist is defined for value level DSDECOD (when DSCAT= DISPOSITION EVENT).

In current v2.0.2 version the only option is to remove a codelist from define.xml  for Value Level which has standard Control Terminology.

Other examples are standard QS, VSSTRESC (VSTESTCD= FRMSIZE), etc.

Sorry for inconvenience, 

Kind Regards, 

Sergiy

Want a demo?

Let’s Talk.

We're eager to share and ready to listen.

Cookie Policy

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.