List of thresholds for Depot Lot Expiration Alert. The threshold list represents when the alert should trigger, in days. For example, 180,120,0 would fire the alert once at 180, once at 120, and once at 0. Add as many threshold triggers as you like, separated by comma.
Last Updated:
The value, if meet or exceeded, for which a "Subjects Randomized in Study Alert" will be sent via email to subscribers. This is a study wide count, not a site specific count.
Last Updated:
The value, if meet or exceeded, for which a "Subjects Screened in Study Alert" will be sent via email to subscribers. This is a study wide count, not a site specific count.
Last Updated:
The interval, in days, the system will send a Low Depot Inventory Alert when the threshold is crossed. For example, a value of 7 will send the low depot inventory alert every 7 days while the threshold value is crossed. Used in conjunction with Low Depot Inventory Alert Threshold
Last Updated:
The threshold, in kit count, that will trigger a low depot inventory alert. The inventory level has to been below the threshold, and will be sent based on the Low Depot Inventory Alert Interval Days value.
Last Updated:
The interval, in days, the system will send a Low Site Inventory Alert when the threshold is crossed. For example, a value of 7 will send the low site inventory alert every 7 days while the threshold value is crossed. Used in conjunction with Low Site Inventory Alert Threshold
Last Updated:
The threshold, in kit count, that will trigger a low site inventory alert. The inventory level has to been below the threshold, and will be sent based on the Low Site Inventory Alert Interval Days value.
Last Updated:
List of thresholds for Overdue Shipments. The threshold list represents when the alert should trigger, in days. For example, 5,7,9 would fire the alert once at 5 days, once at 7 days, and once at 9 days. Add as many threshold triggers as you like, separated by comma.
Last Updated:
List of thresholds for Site Lot Expiration Alert. The threshold list represents when the alert should trigger, in days. For example, 180,120,0 would fire the alert once at 180, once at 120, and once at 0. Add as many threshold triggers as you like, separated by comma.
Last Updated:
Add Synonyms, Views and Sprocs from Code First Migration 1 for yes, 0 for no.
Last Updated:
Used by the Site Activity Management page to set the default value of the Randomization Cap column
Last Updated:
Used by the Site Activity Management Page to set the default value of the Screening Cap column
Last Updated:
Used in Depot Reconciliation function to control the dropdown max limit
Last Updated:
Type of drug order acknowledgement, can be Simple, Detailed, or TempTail
Last Updated:
Place initial order after site activation
Last Updated:
The PatientStatusTypeID that fires the initial drug order once a subject at that site is in this status. ONLY used when "InitialOnSiteActivation" != "true"
Last Updated:
Used for manual drug & acknowledge drug orders. Drives the max quantity number displayed in the drop downs on these pages.
Last Updated:
Minimum kit quantity in each order
Last Updated:
Used for manual drug & acknowledge drug orders. Drives the in quantity number displayed in the drop downs on these pages.
Last Updated:
Length of the order number, will pad with 0s to get to the length if needed
Last Updated:
First order number
Last Updated:
This is the local path to the PredictiveResupply.exe application that performs drug orders
Last Updated:
Is the system and resupply using label groups? 1 for yes, 0 for no.
Last Updated:
The max amount of shippers one order can have, controls the drop down at site acknowledgement
Last Updated:
The min amount of shippers one order can have, controls the drop down at site acknowledgement
Last Updated:
Used in Lot Management Function. If set to 0, the secondary lot number (used by third party supplies) is not used. If set to 1, a secondary lot number is used.
Last Updated:
1 for predictive, 0 for non-predictive, manual orders only.
Last Updated:
Used for Data Transfer, not used for any configuration. This is a data placeholder.
Last Updated:
The full path to to the Merge executable used by SQL Agent Jobs
Last Updated:
The flag to indicate if this study processes EDC through Merge
Last Updated:
Used for Data Transfer, not used for any configuration. This is a data placeholder.
Last Updated:
Rave EDC Service integration, values are(true, false)
Last Updated:
Drug Order File is also sent via sFTP. 1 for yes, 0 for no.
Last Updated:
The end date on the Subject Counts by Month and Cumulative Subject Count graphs
Last Updated:
The start date on the Subject Counts by Month and Cumulative Subject Count graphs
Last Updated:
[bool 0/1] Use the batch release approval process.
Last Updated:
Name of the method used to selection additional blinding kits for resupply blinding groups
Last Updated:
Cohort Managemnt dynamically adds choice to question
Last Updated:
Enable sending requests to concierge
Last Updated:
Delimiter for grid csv exports
Last Updated:
1 = Classic DCF module , 2 = Automatic DCF module
Last Updated:
Default cohort randomization cap at a site
Last Updated:
When 1 = Display Site Local Time Transaction Date only When 2 = Display System UTC Transaction Date only When 3 = Display both Site Local Time Transaction Date and System UTC Transaction Date
Last Updated:
The FROM address for all Alerts and Confirmation emails
Last Updated:
Use this key to prepend anything to the email subject line. Key is required.
Last Updated:
SponsorName for Email Confirmations
Last Updated:
StudyName for Email Confirmation
Last Updated:
This controls the environment display on the default page.
Last Updated:
Genesis Logo Url
Last Updated:
Format for date used throughout the system
Last Updated:
The value, if meet or exceeded, for which the randomization page will display a error message and not allow any further randomizations.
Last Updated:
The value, if meet or exceeded, for which the screening page (either with or without IC) will display a error message and not allow any further screenings
Last Updated:
Enable or Disables the email pdf attachement for confirmations.
Last Updated:
Number of decimal places to allow when entering shipper temperature details
Last Updated:
Override the system time for scenario based tests. Put this as "NULL" or empty to turn this off.
Last Updated:
true if subject number should be generated based on subject count in study, false if count should be at site level
Last Updated:
Controls starting patient number
Last Updated:
List of Patient Statuses (CSV). Based on that list, patients with that statuses will be shown on the landing page.
Last Updated:
Enable the PCI DT
Last Updated:
This controls the Protocol number displayed on the front page.
Last Updated:
Protocol identitfication to be used by the pooled material system
Last Updated:
Question identification to be used by randomization
Last Updated:
The Id of the rescreening questionnaire used to attach the rescreen cap check
Last Updated:
Show the temperature excursion question on simple order acknowledgment
Last Updated:
This is the site investigator role id used in confirmation pages
Last Updated:
Site number length
Last Updated:
This is the target value for total number of completed subjects in the study
Last Updated:
ID for the study matching the Study table in auth db
Last Updated:
Internal logic use it, please do not update.
Last Updated:
Logo displayed in the study summary region, top left position of the front page.
Last Updated:
This is the name of the study displayed on the front page and functions.
Last Updated:
This controls the name of the sponsor displayed on the front page and functions.
Last Updated:
Enable/Disable track of the print button. Values: True/False
Last Updated:
Patients with projected visits between today and today + interval days are included on the widget.
Last Updated:
1 for yes, 0 for no ( or 1 for on and 0 for off)
Last Updated:
The url of the ZenDesk chat service, it should NOT include https://
Last Updated:
This string is used to populate custom fields inside the ZenDesk ticket (see the "custom_fields" section in the curl example, this entire script of custom_fields should be configurable in case the fields change in zendesk we don't have to modify the code, we can modify this key.
Last Updated:
The group this ticket is assigned to in Zendesk
Last Updated:
The url of the API service
Last Updated:
The email address of the user making the api call for authentication
Last Updated:
The token of the user making the api call for authentication
Last Updated:
[bool 0/1] When creating a new subject/patient number this value indicates whether the site id will be included.
Last Updated:
Control the overall format of Subject number.
Last Updated:
[string] When creating a new subject/patient number this value will be placed at the beginning of the number. (ie. "S" + SiteNumber + SubjectNumber)
Last Updated:
[string] When creating a new subject/patient number this value will be used as a seperator between the prefix and the site id. (ie. Seperator is "-": S + "-" SiteNumber + SubjectNumber)
Last Updated:
[string] When creating a new subject/patient number this value will be used as a seperator between the site id and the subject number. (ie. Seperator is "*": S + SiteNumber + "*" + SubjectNumber)
Last Updated:
Subject Role
Last Updated: