@yabwon it is just a merge of https://www.lexjansen.com/cgi-bin/xsl_transform.php?x=ah&c=SUGI#donhrson and https://www.lexjansen.com/cgi-bin/xsl_transform.php?x=ad&c=sugi#paulfman 😀 ... View more

@joeFurbee and @yabwon I also love the discussion from the same paper about MD5 versus SHA256, or about the puritans of cryptographic rigor versus SAS programmers who have to deal with real- world data processing. Their conclusion: using SHA256 instead of MD5 for the sake of preventing an infinitesimally small chance of collision at the expense of dramatically poorer performance makes no practicable sense.   ... View more

Joe, thanks for the shout-out 😀 ... View more

Hi Michael,   The CDISCODM xmltype on the libname and PROC CDISC expect ODM 1.2. Also, both libname and PROC CDISC would expect the data and metadata to be in the same XML ODM file. Please be aware that PROC CDISC was deprecated and replaced by the SAS Clinical Standards Toolkit (CST) quite a long time ago. CST supports ODM 1.3 and can handle metadata and data separately. CST is at version 1.7.2, and is supported, but no longer actively developed. For information about CST see: https://support.sas.com/en/software/sas-clinical-standards-toolkit-support.html and also http://support.sas.com/rnd/base/cdisc/cst/ For a paper about CST and ODM, see: https://www.lexjansen.com/pharmasug/2013/HT/PharmaSUG-2013-HT06-SAS.pdf (Using the SAS® Clinical Standards Toolkit 1.5 to import CDISC ODM files).   Lex Jansen Principal Solutions Consultant @ SAS   ... View more

Yes, at lexjansen.com I try to make additional resources available with the papers. But it is a manual process for adding this metadata. For years, I had a banner inviting people to contact me if they wanted any code or presentation added to their paper link. The response to that was minimal. I'm always open to other suggestions. Having people upload their own code would be ideal, but adds a lot of management (user management, security, ...)/   Lex   ... View more

Sorry for the late reply. No, it does not support the CDISC Lab model.   Lex Jansen ... View more

Maybe this is also helpful: http://www.lexjansen.com/pharmasug/2013/HT/PharmaSUG-2013-HT06-SAS.pdf ... View more

How about 10/11/12   (or was it 11/10/12) ...  depends where you are ...  Aaaaaarg! Seriously, the only date format that I really like to see is ISO 8601, being the only universal date format. (2012-10-11) Lex @SAS ... View more

The sample driver <Sample Library>\cdisc-sdtm-3.1.3-1.5\sascstdemodata\programs\create_sourcemetadata.sas contains an example that derives source metadata from either a define.xml file, or a single library of SAS data sets. In the case of SAS data sets as input, you will have to change the macro variable: %let _cstSrcType=SDTMLIBRARY; as documented in the program header. This will the create source_study, source_tables and source_columns. When applicable, source_values and source_documents data have to be created from scratch, or customized from a define.xml import. Lex Jansen @SAS ... View more