Before you can get started using rules, you must first have a study version in the Testing container that includes the following elements:
Tip: The rule is executed against every visit in the study that contains the form. If you leave -All Visits- in the visits field, the variable data will be retrieved from the form in current visit where rule is being run. If you select a specific visit, the variable data will be retrieved from the form in the specified visit for every visit where the rule is executed.
Note:The Roles drop-down list contains only the study roles that have been created in the study. The template study roles are not included.
Read step by step instructions to Create a rule for an automated query.Note:If the rule expression contains syntax errors the Rule Editor marks it for you to correct. Before it can be promoted to UAT and Approved, a rule must contain a valid expression and at least one action.
Tip: To edit an existing rule, click on the menu icon then select Edit.
For more information on how to use the log helper function properly see logMsg() helper function.For this example, a vital sign form is used to collect the vital sign information from a subject. A rule will be used to calculate the subject's blood pressure by comparing the diastolic and systolic readings and generate a query if the diastolic reading is greater than systolic pressure.
Evaluate if diastolic blood pressure is greater that systolic blood pressure using their variable names and return False to raise a query. Then select Create Query as the action and enter your query message:
if(bpdia > bpsys)
return false;
return true;
For this example, a vital sign form is used to collect the vital sign information from a subject. A rule will be used to display the BMI as a read-only value by reading the weight and height from the form.
Calculate BMI by adding the variables from the form, and return the BMI formula as a read-only item, then select Calculate Value as the action to display the calculated value on the form:
if((weight === 0) || (height === 0)){
return 0;
} else {
return weight / (height * height);
}
For this example, a screening form is used to collect the date of informed consent. This rule will be used to calculate if the date is within a range and create a query notification if the date is outside the defined parameters.
Evaluate if the date of informed consent is within parameters using the "isDateInRange()" helper function. Return False to raise a query, then select Create Query as the action and enter your query message:
var dateFrom = new Date("March 1, 2020");
var dateEnd = new Date("March 30, 2020");
return isDateInRange(dateInformedConsent, dateFrom,
dateEnd, "both");
Note: See other Rule Examples available in the Rules Developer Guide.
You need to test and approve a rule before publishing it to Production.
Note: Click the menu icon (Menu icon) and select View to see a rule's details in read-only mode.
There are two ways in which you can publish a rule: you can either publish one rule at a time or publish multiple rules at once.
Note: You can publish rules in Production by following steps 6 and 7 only if the study is already in the Approved container. If not, you need to move the study from Testing to Approved to publish all rules in Production.
You can modify a published rule and re-publish it as needed. If you modify a published rule in Testing mode, changes won't appear in Production mode until you update that rule's status to Published.
Note: The rule's status is updated to Draft. The rule currently published in Production isn't impacted by this change. If you want to start over, you can always delete a rule with a Draft status.
See the Oracle Life Sciences Clinical One Platform documentation library on the Oracle Help Center. Watch this video on the Oracle Help Center. For assistance, contact Life Sciences Cloud Support. Write to us at clinical_one_doc_feedback_grp@oracle.com.
About Oracle |
Contact Us |
Legal Notices |
Terms of Use |
Your Privacy Rights |
Other resources
Contact support
Can't find what you need?