Forums: General Discussion
Hi Donna, welcome to the OpenCDISC community.
The Validator does support extending CDISC Controlled Terminology in cases where the codelist is extensible. To make this work, you'll need to provide it with a define.xml document that contains your custom codelists. Then, during validation, the Validator will use your codelists in place of the CDISC extensible codelists, where appropriate.
If you don't happen to have a define.xml file for the data that you're trying to validate, the OpenCDISC Validator provides a utility to create one that's created from your data and our configuration documents. You can access this utility by selecting the "Generate define.xml" radio button in the desktop client. In order to add your codelists to the generated define.xml document, you'll need to use the Excel template in the config/examples folder and specify it in the Code Lists field.
Regards,
Tim
Tim,
I am also intereseted in doing the same thing but I am really new to modifiying the define.xml. I created define.xml as you described but I don't know what to put in it to reference the codelists. Can you supply more step by step instructions on how I would customize the define.xml to reference our CT.
Regards,
David
Hello,
When running Open CDISC, is there an option to include additional controlled terminology (Sponsor-Specific or Internal) to the SDTM CT where the Codelist is Extensible before running data through Open CDISC? I am seeing many errors that can be eliminated if I had this option?
Thanks,
Donna