Beginning with JMP Clinical v.7, configurations come in two types: Installed configurations and User configurations. Installed configurations are the default configurations shipped with JMP Clinical and saved to the program directory (typically c:\Program Files\SASHome\JMPClinical\14\LifeSciences). Installed configurations can be modified only by individuals, usually system administrators, with Write privileges to the Program Files directory. User configurations, on the other hand, are specific for an individual user and are specified, either by the user or an administrator, and saved to a writable directory in the user’s workspace (typically <Documents>\JMPClinical\). User configurations enable individual users to access and use JMP Clinical software and data on a shared network drive in specified ways without affecting access and usage by other users.
Three main files are shipped with JMP Clinical and exist in the product install directory (C:\Program Files\SASHome\JMPClinical\14\LifeSciences) to control configurations, path preferences, and system preferences.
Note: You should never need to open and directly edit these files. Any changes that need to be made can be done in the Manage Configuration... window and should be made only by an experienced System Administrator.
The installation.configuration.preferences file contains named configuration variations and the root location(s) to look for installation configurations (as defined by the installation.path.preferences file described below). This file should always remain in the installation directory and is used to surface options in the JMP Clinical Main > Settings > Configuration pane to change configurations.
The installation.path.preferences file contains all the path locations that can be configured to change where JMP Clinical reads and writes for system operations. The Default "Local" configuration shipped with the product looks for this file in the install directory. All default paths use a local configuration and store metadata under the JMP Clinical application data USER ROAMING profile (C:\Users\^USER^\AppData\Roaming\SAS\JMPClinical\14).
|
•
|
{"<userRoot>", "$HOME"} where $HOME should be changed to reference the root path of the configuration
|
|
•
|
{"/system/clinical/preferences", "$LS_HOME"} where $LS_HOME should be changed to reference the root path of the configuration (or another location of your choice)
|
|
•
|
{"<userLocal>", "$DOCUMENTS\JMPClinical\Local"} where "Local" should be changed to reference the name of the share
|
The system.clinical.preferences file contains various system-level options for a given configuration. This file should also be copied and placed in the target location specified for the "/system/clinical/preferences" key in installation.path.preferences.
One of the key components of the system.clinical.preferences file is the specification of user role assignments. A user role defines the level of functional interactivity that a user has in JMP Clinical. The following user roles can be set for individual users.
|
•
|
Study Manager - A user with this role can do all of the operations involved in managing studies within JMP Clinical: add, combine, and refresh metadata, rename or move folders, update a review with a new snapshot, update the study risk data set, and delete studies. The code specification for this role is "StudyManager".
|
|
•
|
Study List Manager - A user with this role can manage and delete studies from shared folders. By default, this role is not assigned. The code specification for this role is "StudyListManager".
|
|
•
|
Review Author - A user with this role can create/edit/save Review Templates, do ad hoc analyses, and create and save Reviews. They can also manage the Holiday and Event data set and Risk Threshold data sets used by the configuration. A Review Author implicitly has the Reviewer role as well. The code specification for this role is "ReviewerAuthor".
|
|
•
|
Reviewer - A user with this role can open Reviews. The code specification for this role is "Reviewer".
|
|
•
|
Configuration Manager - A user with this role can add and define JMP Clinical configurations. This role is assigned to all users by default. The code specification for this role is "ConfigurationManager".
|
|
•
|
Settings Editor - A user with this role has access to the Settings tab on the JMP Clinical Main Window. This enables them to select different configurations (if defined), and change how they view Documentation and Help. The code specification for this role is "SettingsEditor".
|
Important Note: We generally do not recommend restricting the "SettingsEditor" rights from users. This should be done only if you want to severely restrict the use of the system for that user such that they are not able to select configurations.
By default, all users are assigned all roles except Study List Manager. System administrators, however, can restrict individual users to specific user roles using the following procedures. See Adding Users and Specifying Role Assignments for information about specifying user roles.
The Manage Configurations... window is accessed from the Settings tab of the JMP Clinical Main Window.
|
Click to open the Manage Configurations... window, shown below:
|
Note: You must have a Configuration Manager role assignment and Write privileges to the relevant folders to add a configuration.
In this case, we will name the folder ClinicalShare. This folder serves as the root directory for the new shared configuration.
|
|
Open JMP Clinical and click the Settings tab.
|
|
|
Click to open the Manage Configurations... window.
|
|
|
Click to open a Choose Directory window.
|
|
|
Navigate into the ClinicalShare folder and click .
|
|
|
Click .
|
The new configuration is added to the Manage Configurations window. If you select it, all of the default paths and system preferences are displayed, as shown below:
Note: While all paths and preferences are editable, you should consult your system administrator before making any changes.
|
|
Click to close the Manage Configurations window.
|
Note: Anyone with Read and Write privileges on the shared drive has access to a new shared folder. As the creator of this folder you can control level of access by changing the permissions using WinOS commands.
Note: All paths are defined in the installation.path.preferences file. Most users will never need to manually change any of these paths. You should never open and directly edit the installation.path.preferences file. Any changes that need to be made can be done in the Manage Configuration... window and should be made only by an experienced System Administrator.
Note the braces ({}) enclosing the key-value pair, the key enclosed in double quotation marks (“”), the comma (,) after the key, the value enclosed in double quotation marks, and the comma following the enclosed key-value pair unless it is the final key-value pair in the file.
|
Specifies the location of the system.clinical.preferences file.
|
||
|
By default for JMP Clinical 7.0, this path is set to: $DOCUMENTS\JMPClinical\<CONFIGURATION><JMPC_7.0>, where <CONFIGURATION> is the name of the configuration. You can change this path to any directory for which you have Write privileges.
|
|
Specifies the location of the system.clinical.preferences file.
|
||
|
By default for JMP Clinical 7.0, this path is set to: $DOCUMENTS\JMPClinical\<CONFIGURATION><JMPC_7.0>, where <CONFIGURATION> is the name of the configuration. You can change this path to any directory for which you have Write privileges.
|
||
These path keys refer to folders within the JMP Clinical installation location (typically in Program Files). In almost all circumstances, you are strongly advised not to modify their values.
These path keys refer to the user folders created while running JMP Clinical. In most cases, you should not need to change these values, but the most likely values that you might want to change are for the /user/clinical/notes (notes), /user/clinical/output (output), /user/clinical/reviewtemplates (review templates), and /user/clinical/reviews (reviews) keys. For example, you might decide that each user maintains their own study list (on the ‘same’ set of studies) but that notes, review templates, and reviews should be shared amongst all users. Where location changes are desired, you are encouraged to use path wildcards (see Advanced File Path Options) to reduce future maintenance, should these locations change again.
|
Templates used by the Adverse Events Narrative report.
|
|
You can add, modify, or remove path wildcard keys (for example, <userLocal>) and values, so long as no subsequent path values refer to undefined keys. However, you must not add, modify, or remove standard keys (for example, /user/clinical/notes) -- you can modify only their values.
For demonstration purposes, pretend that your user name is zzsmith, and your current study is named Nicardipine. $HOME and $DOCUMENTS are reserved JMP path variables that refer to two different user-specific locations. <STUDY> is a reserved JMP Clinical wildcard that refers to the current study. Keys, values, and corresponding example resolved values are shown below.
|
Example Resolved Value1
|
||
Your value resolution might differ depending on your operating system configuration, environment and path variable definitions, and user-defined JMP Clinical path wildcard definitions made elsewhere in installation.path.preferences.
Note: All preferences are defined in the system.clinical.preferences file. Most users will never need to manually change any of these preferences. You should never open and directly edit the system.clinical.preferences file. Any changes that need to be made can be done in the Manage Configuration... window and should be made only by an experienced System Administrator.
Note the optional comment enclosed by /*** ***/, the left, and right braces ({}) enclosing the key-value pair, the key enclosed in double quotation marks (“”), the comma (,) after the key, the value (the presence of enclosing quotation marks or braces varies depending on its type), and the comma following the enclosed key-value pair unless it is the final key-value pair in the file.
|
||||||
|
Abbreviation Only: Defines a domain on the report dialog and all options by its abbreviation only. For example, the Laboratory Test Results domain is defined as LB.
Label Only: Defines a domain on the report options by its label1 only. For example, the LB domain is defined as Laboratory Test Results.
Abbreviation (Label): Defines a domain on the report options by both its label and its abbreviation. For example, the Laboratory Test Results domain is defined as Laboratory Test Results (LB).
Label (Abbreviation): Defines a domain on the report options by both its abbreviation and its label. For example, the Laboratory Test Results domain is defined as LB (Laboratory Test Results)
|
||
|
Abbreviation Only: Defines a domain on the report results by its abbreviation only. For example, the Laboratory Test Results domain is defined as LB.
Label Only: Defines a domain on the report results by its label only. For example, the LB domain is defined as Laboratory Test Results.
Abbreviation (Label): Defines a domain on the report results by both its label and its abbreviation. For example, the Laboratory Test Results domain is defined as Laboratory Test Results (LB).
Label (Abbreviation): Defines a domain on the report results by both its abbreviation and its label. For example, the Laboratory Test Results domain is defined as LB (Laboratory Test Results)
|
||
|
Metadata, then rules: When this option is selected, JMP Clinical first attempts to find and use labels in the study metadata file. It then assigns a label, based on CDISC rules, for any domain missing a label in metadata.
Rules, then metadata: When this option is selected, JMP Clinical assigns labels based on CDISC rules. For custom domains, for which CDISC rules are not available, JMP Clinical uses labels found in metadata
|
The label displayed is the version specified using the DomainLabelSupplySource option.
|
|
A study management lock is a temporary restriction imposed on users to prevent conflict with an ongoing study management operation (for example, adding, combining, refreshing, renaming, and deleting studies). Under normal circumstances, these locks are removed automatically when the study management operation is complete. Operations on very large studies generally take more time. Exceptional system events might prevent the operation from completing, keeping the lock in effect.
|
0...1e+308, with fractional hours permissible.
|
|
|
A study usage lock is a temporary restriction imposed on users to prevent conflict with an ongoing study usage operation (for example, running reports in Review Builder). Under normal circumstances, these locks are removed automatically when the study usage operation is complete. A user leaving Review Builder open, as well as exceptional system events, might keep the lock in effect.
|
0...1e+308, with fractional hours permissible.
|
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
Specifies whether to make the JMP button available on the JMP Clinical Main . This button surfaces the JMP Home , which allows easy access to core, non-Clinical specific, JMP functionality.
|
|
|||||||||||
|
||||||||||||
|
icon to the options bar for each report. Checked by default. Options include:By default, a JMP Clinical installation is fully functional with all reports and options available to you. However, the JMP Clinical installed on your machine, might be configured for a specific user role. These roles are set as described in Adding Users and Specifying Role Assignments.
A user with this role can remove studies from shared locations. This option is not enabled, by default.
|
|
Click the Studies tab.
|
|
|
.A user with this role can create/edit/save Review Templates, do ad hoc analyses, and create and save Reviews. They can also manage the Holiday and JMP Life Sciences / SAS Institute Event data set and Risk Threshold data sets used by the configuration. A Review Author implicitly has the Reviewer role as well.
This role is normally found in conjunction with one or more of the other user roles. A user with this role has access to the Settings tab on the Main Clinical window. This enables them to select different configurations (if defined), change how they view Documentation and Help, and download and install a local copy of the documentation.
Use the Role Assignments options to define roles for additional users,
In this example, user anisco is assigned all user roles. User CARYNT\sasajf is assigned to all roles except Study Manager.
Note: CARYNT\sasajf actually designates both the user name (sasajf) and the network domain (CARYNT) to which the user belongs. This ability to define both the domain and user gives the system administrator flexibility in identifying individual users.
|
|
Click
 to open the Add window. |
|
|
|
|
|
|
Click to add the user.
|
|
|
Click
 to open the Edit window. |
|
|
Check the appropriate boxes to Grant the user one or more additional roles.
|
|
|
Check the appropriate boxes to Revoke from the user one or more assigned roles.
|
|
|
Click to save the changes.
|
to delete the user.
Advanced file path options can be viewed by checking the Show Advanced path options check box.