Upgrade cycle

PSI performs the DHIS2 upgrade once a year in order to take advantage of the most recent features available in the platform and which responds to the PSI users needs. This process is usually schedule at the end of each year and all the activities involved can take twelve weeks aproximately, from the communication to the upgrade itself. This cycle is focused on the PSI production instance only, where all the majority of applications and programs used by the PSI users, reside. However, the steps described in this document can be applied to any other instances, with a previous review and adjustments according to the specific context and environment . The Upgrade cycle involves, at a glance, the following steps

1. Testing

2. Documenting and reporting the testing results

3. Fixing bugs when pertinent and possible

4. Upgrade the production instance

5. Training

Preparation steps

The process requires a proper preparation, that includes:

1. A testing instance setup containing a replica of the Production server database

2. An inventory of all the custom applications, including reports, scripts, etc. This is a checklist that will be used as a tracking mechanism of the testing progress

3. Submitting a communication to the System Administrators to inform about the process, the dates and the protocol to perform and complete all the steps involved

Communication

An email message will be submitting by the Head of DHM to the System Administrators and the Head of Countries (CRs) informing about the upgrade, at least with two months in advance that the upgrade effectively happens. This is a notification that contain

1. A list of the most relevant features that the new version contains , briefly explaining their benefits to the PSI users

2. The period that the whole upgrade process involves, from the communication until the platform has been effectively upgraded

3. The Testing protocol, including

   1. What should be tested by country, globaly, instance to test, among other important information to conduct the process

4. The mechanism to inform/ report bugs and issues

5. Any other pertinent information to support the process

Testing Protocol

To ensure a smooth transition to the new version, the testing should be done considering two groups:

1. Global. This are referred to custom applications and scripts that should be testing by the owners/ and the technical and support team

2. Country specific . It is critical that users in-countr, test their DHIS2 configurations in the testing instance, to ensure that the system is working properly.

Any issue found should be reported as explained in the next section of this document, no later than the communication email indicates. The testing period has to be finished at least three weeks before the upgrade happens. Thus, is very important for the tester to reserve the required time to conduct the testing in all their programs, dashboards, etc.

Some TA session could be scheduled if necessary, during the testing period, according to the case/ issue found. Therefore, submit the session request by the mechanism explained in the next section in this document.

To perform the test, og in the testing instance provided in the respective email, using the same credentials your use in the current production server (data.psi-mis.org)

To test by group of Country Specific:

Data capture:

•  Data Capture for your programs and datasets using standard DHIS2 apps (data entry, tracker capture, etc)

• Mobile data entry in Android Data Capture App version 2.6.2 or greater (you should ideally use PSI’s DHIS2 Android App available here)

• Program rules: guide on how to update the syntax at the end of the email

Analytics: all your dashboards and their analytical objects (charts, reports, pivots, maps) should load and open without any problems.

To test by group of Global - you DON’T need to test as Country Specific

•  Data capture for HNQIS1.X or 2.0

• Data capture for RDQA

• Interpretations and its notifications - there are open issues being addressed

• Creation/ editing of new Programs, datasets  

• Creation/ editing of Program Rules, Program Indicators, Data Elements, categories, etc  

• Creation editing of Org Units, Users, etc  

• Import/ Export of metadata

• To add others that will be developed and ready by the next upgrade

Reporting problems related to the Upgrade

If you identify an issue during the testing phase, please report it by submitting a ticket to the PSI DHIS2 helpdesk. No other mechanism or channel should be used for this purpose.

When create the ticket, please consider the following

1. Use the specific Ticket Type indicated during the communication steps. Usually this is something like “ DHIS2 Upgrade 2.XX”.

2. Please, provide as much description as you can and attach an image if needed.

3. Please include the URL, the credentials and any other relevant information that can help to understand the issue reported

4. The Agents will verify whether the issue is related to the new version or not and what measures are required to apply to fix the issue

Testing completion. Signing off

Once you have completed your testing, we need the DHIS2 focal point in-country to sign off that your configuration is working properly. Please find the link to the form here.