PCA - H2 Scoring Program Rules

In H2, any numeric type question can contribute to the scoring process of an Assessment. By numeric question we refer to any question with a DHIS2 Value Type of Number, Integer, Positive Integer, etc. This includes questions limited to the options contained in an Option Set (requiring the Option Set to be of numeric type).

A numeric question can contribute to a score if the question Numerator, Denominator and Feedback Order are defined (see Images 1 and 2). Lacking any of the previous configurations means that the question doesn’t contribute to any score.

Open

Image 1: Question Numerator, Denominator and Feedback Order configured in the PCA Data Element Editing feature.

Open

Image 2: Question Numerator, Denominator and Feedback Order configured in the Excel Template.

Critical Score

The Critical Score is calculated by using all the Critical Questions answered in the Assessment. This means that if a question has been left unanswered, it won’t be taken into account for the Critical Score Calculation.

The PCA generates a Program Rule named PR - Calculated - Critical Questions that operates the Numerator, Denominator and Answer Value of all the answered Critical Questions in the Assessment (see Image 3).

Then, it generates another Program Rule named PR - Score - Critical Questions (%) that stores the value into a Data Element named Critical Steps located in the Critical Steps Calculations section (see Image 14).

Meaning that two Program Rules are used for this process:

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.

Non-critical Score

Similarly the Non-critical Score is calculated by using all the Non-critical Questions answered in the Assessment.

The PCA generates a Program Rule named PR - Calculated - Non-Critical Questions that operates the Numerator, Denominator and Answer Value of all the answered Non-critical Questions in the Assessment (see Image 15).

Then, it generates another Program Rule named PR - Score - Non-Critical Questions (%) that stores the value into a Data Element named Non-critical Steps located in the Critical Steps Calculations section (see Image 16).

Meaning that two Program Rules are used for this process:

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

If an H2 Program has been configured to include Competency Classes, the PCA will also generate five additional Program Rules to handle the Competency Class definition and assignment (see Image 17).

Three of the rules are used to define the Competency Class and assign it to the Competency Class Data Element located in the Critical Steps Calculations section. The rules are named as follows:

To learn more about the contents of these Program Rules please refer to the H2 Competency Classes page.

Another Program Rule is generated to assign the value stored in the Competency Class Data Element into the Competency Class Attribute of the Tracked Entity Instance (see Image 18).

The rule is named as follows:

Then, the PCA generates another Program Rule to Hide the Global Score and Competency Class Attributes of the Tracked Entity Instance if the Critical and Non-critical Scores are not defined. The rule is named as follows:

If a H2 Program hasn’t been configured to use Competency Classes, the previous Program Rule will be generated to hide only the Global Score Attribute, and will be named as follows:

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.

Basically, if the Assessment contains Critical Questions, the Overall Score is the same as the Critical Score. On the other hand, If the Assessment doesn’t have a single Critical Question, the Overall Score is the same as the Non-critical Score instead.

The Program Rule generated by the PCA is named as follows:

This rule assigns either the Critical Steps or the Non-critical Steps value to the Global Score attribute of the Tracked Entity Instance (see Image 9).

Compositive Score

The Compositive Scores are scores that group questions by using the Feedback Order, for example, Compositive Score 1 is calculated using every question or Sub-score derived from the Score 1, which means that:

1. If there are other Sub-scores like 1.1, 1.2, 1.3 and so on, the questions contained within those Scores would be used to calculate Score 1.

2. If there are only questions with Feedback Order 1.1, 1.2, 1.3 and so on, these are used to calculate the Score 1 directly.

3. A Sub-score cannot be grouped with other questions in the same level, for example: there cannot exist a Sub-score 1.1 and questions 1.2, 1.3, 1.4 and so on. However, a Sub-score 1.1 can contain questions 1.1.1, 1.1.2, 1.1.3 and so on.

The PCA will generate all the necessary Score Calculations Program Rules by using the Feedback Order, Score Numerator and Denominator and Answer Value of each answered question (see Images 10 and 11). This means that if a question has been left unanswered, it won’t be taken into account for the Score Calculation.

These calculation rules are named as following:

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 22 and 23).

These rules are named as following:

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).