Set up configuration parameters for the TRIALEX System

Details
This tool allows the administrator to configure system level parameters for the TRIALEX system.  The macro interface allows easy access for administrators to set system configuration parameters.  Valid parameters include:

• Analysis Root - physical disk path to the root level where all programs and related data are located.
• batchserver:network sastemp - The network path to the SAS temporary folder for the batch server.  The "batchserver" is replaced by the batch server name.  A sample value would be: \\sasbatch\sas\sastemp
• CC Note Type [1...n] - Change control notes type.  This classifies the different types of notes to distinguish the level of important.
• CC Note Status [1...n] - Change control note status.  The status identifies the current stage of testing and validation of the changes the the system.  
• Clinical Object Type [1...n] - Clinical object type defines the different objects within the Trialex System.  The default settings include:
  • Programs
  • Data
  • Reports
    
    There may be other user defined objects beyond these examples.  The number in square brackets will determine the order in which these objects appear on some lists.

• Connect Communication Access Method - The SAS/Connect communication method such as the protocol.  For example, tcp is a valid value for the tcp/ip protocol.
• Connect Configuration - SAS/Connect configuration file location.   For example: c:\sas\config.sas *
• Connect Link Script - The SAS/Connect script file including the full path.  For example: C:\SAS\connect\saslink\tcpwin.scr  *
• Connect Remote Host - The name of the remote host machine.
• Connect SAS Executable - SAS executable on the batch server location.   For example: c:\sas\sas.exe *
• Current Company - The name of the company for the current installation of the Trialex System.
• Email Server - Machine that is hosting the email services.  For example, mailserver.org.com
• Emailer - Command line email tool executable including path.  For example: d:\postie\postie *
• First Page Exclusion [1...n] - This defines the report type which are to be excluded from the first page tool.  In cases such as graphs or in-text tables where ODS may have been used, first page can not be applied.  In this case, it will just create a link to the output file rather than parsing the first page.
• First Page Intext Type - This defines the report type which is associated with "in-text" tables in RTF format.  First page treats these differently so this configuration setting captures this distinction.
• Level Status [1..n] - This defines the status for each clinical level.   Use this to assist in managing clinical levels in the level design.  Among possible status values include:

• Active
• Archived
• Retired

• Main Server Label - The text label of the Main SAS server.  This will be displayed on screens referring to the main server. 
• Mapped Drives -  The valid names of mapped lettered drives on the network.  Specify just the letter without colons or slashes and separated by spaces.   For example, if you have three mapped drives: N, O, P; the entry would be:
  N O P
• Password Expiration Period - The number of days which a password is valid.  The system will require an updated password beyond this duration.  A sample value is: 90
• Password Expiration Warning - The number of days before the end of the password expiration period when the system will warn the user of password expiration.   A sample value is: 20
• Primary Privileges Administrator - This identifies an administrator user name that is going to be assigned the owner of objects within the Trialex System once the prior owner leaves the system.
• Publishing Directory - The designated publising directory relative to the trialex assigned study directory.  For example: ..\publish
• Report Display Field - The field name defined in the report which will be displayed for choice selections.  An example of this is found in the first page tool.
• Report Type [1...n] - Report object type.  This distinguishes different types of reports.  For example: Listings, Summary Tables, Figures and Graphs, etc...  Multiple entries are distinguished in the parameter name by syntax similar to arrays. An example would be:
     Report Type [1]  has value of  Listings
     Report Type [2]  has value of Summary Tables
    ...

• Sasroot - physical path to the location where SAS was installed.   For example: c:\sas *
• Sastemp - physical path to the location of the WORK area within the SAS system.  For example: c:\temp *
• SAS Configuration - SAS configuration file including the full path.  For example c:\sas\config.sas *
• SAS Engine Configuration: Local [1...n] - SAS configuration file including the full path.  This is an optional parameters for distinguishing multiple data engine.  For example c:\sas\config_v6.sas *.  Note that there could be additional definitions where the server label,  such as in this example "Local", can be replace with remote server if SAS/Connect is configured.
• SAS Engine Label: Local [1...n] - Descriptive label corresponding to the engine definition.  This is an optional parameters for distinguishing multiple data engine.  For example SAS Version 6 Data Engine.    Note that there could be additional definitions where the server label, such as in this example "Local", can be replace with remote server if SAS/Connect is configured.
• Schedule Stop Time - The default scheduled stop time for repeating jobs.  This is calculated relative to the starting time.  This is entered in seconds so some possible entries may be:
  • 60 - one minute later
  • 3600 - one hour later
  • 86400 - one day later
  • 604800 - one week later
  • 2419200 - one month later
• Scheduler Application - This define the application used to invoke the schedule.  This include the path and the executable file of the scheduling application.
• StatIcon [1...n] - Status Icon matches each status with the appropriate icon GIF images from the existing library.  These icon images have the names statn.gif, where n is the distinguishing identifier number.   These images are stored on the web server under the images folder.
• Status [1...n] - Status defines the different types of status associated with clinical objects such as data and programs.  Among some sample status categories include:
  • Planned
  • Draft
  • Verification Started
  • Verification Completed
  • Compliance Audit Started
  • Compliance Audit Completed
  • Frozen 
• Thesaurus Confirm Mapping - During the review of tentatively mapped terms, the user will be prompted with radio buttons with three options to confirm.  This will set the default value for confirmation.  The possible values include:
  • Yes
  • No
  • Hold
• Thesaurus Level [1...n] - The various levels of thesaurus dictionaries.   This can be used to distinguished between external dictionaries which can be considered global compared to site specific dictionaries.  Among some possible values include:
  • Global
  • Project Specific
  • Externa
• Thesaurus Long Body System - The variable name for the descriptive long term of the body system.
• Thesaurus Long Term - The variable name for descriptive long term of the thesaurus preferred term.
• Thesaurus Mapping Status - During manual mapping, the user is presented with the option of mapping the term tenatively for review or final.  The default value will be set to the possible values of:
  • final
  • tentative
• Thesaurus Meddra Webroot - The URL path to the root of the Meddra Navigator.  An example would be: http://server/thesaurex/meddra/thesaurex
• Thesaurus Review Options - The user can can be presented with different review options during the mapping process.  The default can be set to one of the following:
  • Tentatively Mapped Terms
  • Mapped Terms for Review
  • Mapping History
  • Unmapped by Patient ID
• Thesaurus Status [1...n] - This defines the various status levels associated with thesaurus mapping.  Among some sample thesaurus status categories include:
  • Draft
  • Unmapped
  • Auto Coded
  • Manual Coded
  • Mapping Completed

• User Roles [1...n] - Suggested user roles for the Trialex System.   Some examples may be:
  • Administrator
  • Bio Statistician
  • Clinical Data Associate
  • Clinical Research Associate
  • Data Manager
  • Medical Reviewer
  • Programmer Analyst
  • Thesaurus Manager

• Variable Role [1...n] - The variable role as defined for the domain documentation.  Some examples of possible roles include:
  • Key
  • Support
  • Selections
  • Review (Derived)
  • Date Time

• Web Root- physical disk path to the location of the web root.
• Web Server - web server name.  This does not include the http:// or any slashes.
• Zip Application -This defines the application used to zip or archives files.  This includes the path and the executable file for the zip application.

Example

%config (param=Report Type [1], value=Listings);

%config (param=Report Type [2], value=Summary Tables);

* On Windows operating systems, special characters and spaces may not work. It is therefore recommend that path names are void of spaces and special characters.