Standards

The definition of each standard (and version of each standard) is done in the global standards library. A best practice recommendation is that you do not (permanently) modify the global standards library files, but instead modify copies of the files.

The files and metadata that constitute a standard vary from standard to standard. Use the files that define each standard, located in the global standards library directory/standards/standard directory, as templates, adding your customizations. You can rename or otherwise introduce your own subfolders and files that constitute each standard. If you want to create your own version of an existing registered standard, review the information in the next question.

Use the SAS Clinical Standards Toolkit framework utility macro cst_registerstandard.sas to register a new standard. A new subfolder hierarchy is added to the global standards library directory/standards/ directory, and the global standards library directory/metadata/standards.sas7bdat data set is updated with metadata about the new standard. This metadata is provided in the form of two data sets, standards, and StandardSASReferences. These data sets are passed to the SAS Clinical Standards Toolkit as parameters in the call to the cst_registerstandard macro.

See “Maintenance Usage Scenarios” in Chapter 2, “Framework,” in the SAS Clinical Standards Toolkit: User's Guide.

New production releases of the SAS Clinical Standards Toolkit routinely provide updates to previously released standards. For information about how these updates are provided, see Does a New Version of the SAS Clinical Standards Toolkit Automatically Overwrite Files Installed with a Previous Version?.

SAS also makes available a SAS support knowledge base focus area ( http://support.sas.com/rnd/base/cdisc/cst/index.html) to communicate product information, references, and updates. Preproduction files are also available for download.

The SAS Clinical Standards Toolkit development team also supports the early adopter phase and works with development partners on future product releases.