SAS INSTITUTE INC. IS PROVIDING YOU WITH THE COMPUTER SOFTWARE CODE INCLUDED WITH THIS AGREEMENT ("CODE") ON AN "AS IS" BASIS, AND AUTHORIZES YOU TO USE THE CODE SUBJECT TO THE TERMS HEREOF. BY USING THE CODE, YOU AGREE TO THESE TERMS.
YOUR USE OF THE CODE IS AT YOUR OWN RISK. SAS INSTITUTE INC. MAKES NO REPRESENTATION OR WARRANTY, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NONINFRINGEMENT AND TITLE, WITH RESPECT TO THE CODE.
The Code is intended to be used solely as part of a product ("Software") you currently have licensed from SAS Institute Inc. or one of its subsidiaries or authorized agents ("SAS"). The Code is designed to either correct an error in the Software or to add functionality to the Software, but has not necessarily been tested. Accordingly, SAS makes no representation or warranty that the Code will operate error-free. SAS is under no obligation to maintain or support the Code.
Neither SAS nor its licensors shall be liable to you or any third party for any general, special, direct, indirect, consequential, incidental or other damages whatsoever arising out of or related to your use or inability to use the Code, even if SAS has been advised of the possibility of such damages.Except as otherwise provided above, the Code is governed by the same agreement that governs the Software.
If you do not have an existing agreement with SAS governing the Software, you may not use the Code.
---CREATOR:---
Assumptions:
1. The set of studies and review templates needed by Autobot will be created in
JMP Clinical by the creator.
2. The review template repository path is correctly defined in the underlying
CreatorCopyReviewsToVDrive.jsl within the Copy Clinical Review Templates to
Repository addin. (To edit this script, navigate to JMP's menu
bar: View > Add-Ins... > (name of addin), then click the "Home Folder" link.)
Instructions:
1. Create review templates.
2. (First-time, only): Double-click com.jmp.clinical.copyrevtemptorepos.jmpaddin
to install a JMP add-in for copying review templates to the central repository.
3. On the JMP Clinical Starter menu bar, select Add-Ins > Copy Clinical Review
Templates to Repository.
4. Select the review templates needed for the JMPC Autobot. Click OK.
---AUTOBOT:---
Assumptions:
1. The machine that Autobot runs on will be dedicated to Autobot, has its own license,
and can freely open and close JMP without having to worry about conflicting with
ongoing operations from a human user.
2. All path definitions are correct in the two .sas7bdats (active_studies_daily.sas7bdat
and active_studies_monthly.sas7bdat), three JSL scripts (Autobot's UpdateReviewStudies.jsl,
Creator's "Copy Clinical Review Templates to Repository" (CreatorCopyReviewsToVDrive.jsl)
and Consumer's "Get Clinical Reviews" (ConsumerGetAndViewReviews.jsl) in addins (JMP's menu
bar: View > Add-Ins > (name of addin), then click the "Home Folder" link to
edit the underlying JSL scripts), and JMPC_Autobot.bat (JMP executable location).
(These path definitions are always located in the first few lines of a JSL file.)
Instead of requiring inferred review template names based on study name, explicit
path definitions are used for greater flexibility in naming and processing.
The active_studies_... datasets will define study name, new SDTM and ADaM paths,
whether to update a monthly study, the corresponding "root study" (monthly study)
for a daily study, and review template to use. Processes running prior to, or
after, Autobot need to set the "Update" cells in active_studies_monthly.sas7bdat
from 1 to 0, or 0 to 1, as needed (likely on the first day of each month).
3. All studies have already been added to JMPC before Autobot attempts to update them.
4. All studies will have both an SDTM and ADaM folder defined.
5. Every study will be run with only one review template. This allows the output from
the review to be simply named after the study name.
Instructions:
1. In some batch file (e.g., StartingScript.bat), include the following line to
call Autobot's batch script (JMPC_Autobot.bat):
call JMPC_Autobot.bat
2. Modify JMPC_Autobot.bat to reflect the location of the JMP executable and the
Autobot JSL script (UpdateReviewStudies.jsl).
3. Modify the lines at the top of UpdateReviewStudies.jsl (jg:GLOBAL_AUTOBOT_SETTINGS =
[...]) to point to paths for files needed by this script (to edit this script in JMP,
right-click on it, then hold down the Ctrl key and select "Open"):
- study_list_monthly_file: Studies to process once per month. Actually, studies
in this table are processed whenever the "update" column is set to 1.
To make this happen only once per month, set all rows to have a value of
1 for update, on one day (e.g., the 1st of the month), and reset all rows
back to 0 after that day.
- study: Name of the study (e.g., TevaJMPCStudyMonthly)
- update: 1 to process, 0 to not process.
- new SDTM path: Path to the SDTM folder to update to on the next run
(e.g., temp/jmpc/monthly/MMMYYYY)
- new ADaM path: Path to the ADaM folder to update to on the next run
(e.g., derived/jmpc/monthly/MMMYYYY)
- review template name: Name of the review template to use on this
study (e.g., TevaJMPCStudy).
- study_list_daily_file: Studies to process in every run (e.g., daily).
- study: Name of the study (e.g., TevaJMPCStudyDaily)
- SDTM path: Path to the SDTM folder to update to on the next run after
study has been reset to the root study data (e.g., temp/jmpc/daily)
- ADaM path: Path to the ADaM folder to update to on the next run after
study has been reset to the root study data (e.g., derived/jmpc/daily)
- root study: Name of the study for which to first reset this study's
data to (e.g., TevaJMPCStudyMonthly) before updating it with daily
data (new snapshot).
- review template name: Name of the review template to use on this
study (e.g., TevaJMPCStudy).
- template_repository: The path where review templates should be stored for
sharing with Autobot.
- output_repository: The path where review output should be stored for sharing
with consumers.
- clear_output_repository_sub: If set (1), clears each study's output repository
subfolder so that multiple runs on a study don't generate duplicate
copies of files with numeric suffixes.
- log_file: Path to the file that will contain JSL output from Autobot's
last run.
---CONSUMER:---
Assumptions:
1. The set of studies for which the consumer will want to view reviews will already
be added as JMP Clinical studies to the consumer's machine.
2. The output repository path is correctly defined in the underlying ConsumerGetAndViewReviews.jsl
within the Get Clinical Reviews addin. (To edit this script, navigate to JMP's menu
bar: View > Add-Ins... > (name of addin), then click the "Home Folder" link.)
Instructions:
1. (Somehow, studies of interest will already be added on the consumer's machine.)
2. (First-time, only): Double-click com.jmp.clinical.getviewreviews.jmpaddin to
install a JMP add-in for getting and viewing the latest reviews pertaining to
your JMP Clinical studies.
3. On the JMP Clinical Starter menu bar, select Get Clinical Reviews.
4. All reviews in the central output repository for which the consumer has a study
of the same name will be automatically copied to the consumer's JMPC user folders.
Simply click the button for a review which you'd like to view. You can either
leave this window open all of the time and periodically click "Update", or close
the window and rerun this command (step 3) again.
