Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Panel
bgColor#F4F5F7

PR - Show/Hide - Show when Question is Answer

The resulting Program Rules in DHIS2 will follow the previous naming convention (see Image 3). The rules generated by the PCA are tagged as Scripted in the configurations so the App is able to differentiate custom and automated Program Rules (see Image 4).

...

Panel
bgColor#F4F5F7

PR - Make Field Mandatory - Make mandatory when Question is Answer

...

The configuration is mostly the same as the Hide/Show Program Rules, basically only changing the Program Rule Name and the Program Rule Actions (see Images 8 and 9). Also, the condition would be the same as the Hide/Show rules (see Image 10) without inverting the logic.

...

The first one being used for calculating and debugging, and the second one being used to present the result to the supervisor during the Assessment.

Competency Class

WIP

Overall Score

The Overall Score isn’t a calculation like the Critical and Non-critical Scores, it is basically a copy of the value contained in the Critical Steps or Non-critical Steps.

...

Panel
bgColor#F4F5F7

PR - Calculated - Feedback_Order Score_Name

Then, another Program Rule is generated for each Score, used for rounding the Calculated Score and storing it in a Data Element present in the Assessment (see Images 20 and 21).

...

Panel
bgColor#F4F5F7

PR - Score - [Feedback_Order] Score_Name (%)

You will notice that most of the Program Rules generated by the PCA are Score related, this is due to the fact that each Score needs two rules (one to perform the calculation and another to round and display).

...

Program Rule Variables

In H2 programs where PCA automatically generate the necessary program rules described above, it also generates associated Program Variable. Those variables are named as xxxxx

screenshot showing a couple of program variables generated by PCA h2 caseThe PCA uses Program Rule Variables to reference Data Elements contained in the Assessment, and also to store temporary Calculated Values such as Scores (see Image 22).

...

Similarily to the Program Rules, the variables are identified as scripted when the variable name starts with a underscore (_). The Variables follow some naming conventions:

  • Calculated Values

Panel
bgColor#F4F5F7

_CV_Name

  • Compositive Scores (Variation of Calculated Values)

Panel
bgColor#F4F5F7

_CV_CSFeedback_Order

  • Questions in the Assessment

Panel
bgColor#F4F5F7

_SSection_NumberQQuestion_Number

  • Competency

Panel
bgColor#F4F5F7

_competencyNewest

  • Critical Score

Panel
bgColor#F4F5F7

_criticalNewest

  • Non-critical Score

Panel
bgColor#F4F5F7

_noncriticalNewest

Please Note:

Avoid starting the name of your Program Rule Variables with an underscore (_), as this is used by the PCA to identify scripted variables and will be deleted when generating new Program Rules using the Set Up Program button.