Custom Program Rules
The PCA currently does not support In-app creation of custom Program Rules, meaning that the standard Program Rules management in the DHIS2 Maintenance App is required for this. However, the custom Program Rules are displayed in the PCA as described in the Checking Existing Program Rules page.
Please Note: A Program Rule creation feature is being planned for a future release of the PCA.
H2 Program Rules Generated by the PCA
If the HNQIS2 Metadata Package has been installed in the server, the PCA will enable the H2 features. These features allow the creation and modification of H2 Programs, enabling access to other features like the Import/Export of Excel Templates, and the Set Up of H2 Logic and Analytics (see Image 1).
...
| Note |
|---|
Executing this process again will delete all Previously generated Program Rules and Program Rule Variables to create new ones. Your custom Program Rules and Program Rule Variables will not be deleted. |
...
Parent Logic - Hide/Show Rules
A Parent Question displays more questions if a specific answer is given, this means that some questions can be hidden from the Assessment until the Parent Question has one specific value. This is useful for displaying questions related to another question, for example:
...
The logic of these Program Rules is “Inverted” due to the fact that DHIS2 can only Hide Questions. This means that if the Rule is “Show Questions when Answer is 1”, the logic would be “Hide Questions when Answer is not 1” (see Images 5 and 6).
...
Special Case: Mandatory Child Questions
Mandatory questions in DHIS2 represent a problem when these are hidden by a Parent Question. DHIS2 always displays mandatory questions, this means that a Child Question cannot be mandatory directly, or else the question will be shown even if the Parent hasn’t been answered.
...
With that new set of Program Rules, Mandatory Child Questions are no longer an issue.
...
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).
...
| Info |
|---|
Questions are also divided into Critical and Non-critical, which generates a new set of Scoring Rules. This configuration can also be applied using the Excel Template or directly from editing a Data Element in the PCA. |
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 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
Similarily the Non-critical Score is calculated by using all the Non-critical Questions answered in the Assessment.
...
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 a 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).
...
| Panel | ||
|---|---|---|
| ||
PR - Attributes - GlobalScore |
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.
...
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 19).
...
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:
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.
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.
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.
| Info |
|---|
For more information about Feedback Order and the Scoring process please refer to the Scoring Technical Documentation. |
...
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
The 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 24).
...