The first option determining the autovalidation policy for the current project is whether to allow autovalidation to be based on reports or on report sections. To set the policy, use the menu Autovalidation | Policy.
If you select “Policy is based on reports” (which is the default option for new project), then you will be able to allow each unique report to be autovalidated, and assign it a percentage level. See Allowing a report to be auto-validated.
Conversely, if you select “Policy is based on report sections”, then you will be able to allow each unique report section to be autovalidated, and assign it a percentage level. See Allowing a report section to be auto-validated
Irrespective of the “per report” or “per report section” policy, you are also able to specify that parts of the report are irrelevant as regards auto-validation. You do this by deselecting in the Policy window any report section headings that not relevant as regards autovalidation.
For example, suppose the project has three report section headings: “Diagnosis”, “Management advice”, and “Test eligibility advice”. The last report section may be used for very generic comments about eligibility which should not affect the decision whether to autovalidate the case or not. You would then deselect this section heading. Suppose now a subsequent case is given the report “Diagnostic comment is x. Management advice is y. Test eligibility advice is z”. If you had previously enabled the report “Diagnostic comment is x. Management advice is y.” then the report for this case would now also be enabled.
Similarly, the level associated with the report “Diagnostic comment is x. Management advice is y.” would be now used as the determining level for this case as well (i.e. if rules were not being used for auto-validation).