Miscellaneous

See “References” in Chapter 1, “Introduction to the SAS Clinical Standards Toolkit,” in the SAS Clinical Standards Toolkit: User's Guide.

In general, the code base for the SAS Clinical Standards Toolkit is designed to be backward compatible with prior releases of Base SAS, with only limited use of new features introduced with recent SAS releases. The open-source nature of the product allows user updates to all product components. “Off-label” use of the product is at the discretion of the user.

Releases of the SAS Clinical Standards Toolkit occur periodically. Your site representative should contact your SAS account manager for updates on the release schedule.

Availability of product updates is typically announced on the SAS and Clinical Trials Community forum ( http://communities.sas.com/community/sas_and_clinical_trials). You can use e-mail notifications and RSS feeds to ensure that you do not miss any announcements.

The SAS Clinical Standards Toolkit development team members report on product updates and availability at user conferences for specific industries such as PharmaSUG and PhUSE.

No. The installation prompts you to define new locations for the SAS Clinical Standards Toolkit global standards library and the sample library. SAS has a strategy of adding the release number to folder names for the global standards library files and the sample study library files. For example:

In addition, SAS does not automatically reset the default version of any previously installed version of a standard to the current version. Instead, you must make the decision to upgrade to the current version.

See “Unregistering an Old Version of a Standard, and Then Registering a New Version of a Standard” in Chapter 2, “Framework,” in the SAS Clinical Standards Toolkit: User's Guide.