Release Notes: endTB release 2.0

• Note: The version of the software has been changed from 1.6 to 2.0.0 to maintain consistency across the changes done by different implementing partners to various modules. Also this is a major release that includes the Bahmni Upgrade to OpenMRS version 2.0, hence it makes sense to go with this release number.

• We have followed the semantic versioning standards.

• Releases 2.0.1, 2.0.2 and 2.0.3 are patch releases on top of 2.0.0 and as such we have simply updated the release notes to reflect the 2.0.3 release. Both 2.0.1, 2.0.2 and 2.0.3 comprised of only minor patches.

Deployment steps:

The steps for deploying the release 2.0.3 build for endTB are available at this link.

Documentation:

endTB specific documentation can be found here.

Release notes from the Previous releases:

The release notes from the previous releases of endTB are given below,

• Release 1

• Release 1.1

• Release 1.2

• Release 1.3

• Release 1.4

• Release 1.5

• Release 1.5.1

What’s New:

Following are the new features available as a part of this release:

1. Upgrade to OpenMRS 2.0
   

   Bahmni release 0.87 was on the latest version of OpenMRS which is version 2.0. This release has now been made compatible with the release being provided for endTB software:
   The following are the fixes that were needed in order to make the functionality compatible:

   • Fix to the edit of observations: there was a change in the way that OpenMRS saves the edited observations. This change needed to be accounted for in the way Bahmni saves the data. This has been done now and the edit of observations works as it was.

   • Fixing the reports and exports to accommodate the changes that were made in the OpenMRS version 2.0 to ensure that they work as is.

   • Fixing the DQ dashboard to allow the user to edit the forms that have an error on them directly from the Dashboard.  As mentioned, There was a change in the way that OpenMRS saves the edited data, hence this was needed.

   • Fix to edit of bacteriology results: the user was not able to save after adding any results entered by editing the sample from the patient dashboard.  This has now been fixed.

   • Fix to edit of existing forms: the user was not able to save changes to an existing form for some patients due to invalid observations related to bacteriology results. This has now been fixed.

2. Performance improvement on load and print of Patient summary
   There was a performance issue being reported by the end users which was that when there was a lot of data on the patient summary it would take a long time to load. (around 3-4 mins)Also, when ‘print’ was pressed on such a patient summary it would take a long time to print (around 5-6 mins) even breaking (becoming non responsive / failing) in the extreme cases.This issue has now been resolved and the observed improvement in performance is about 70-80%. The print of the patient summary will no longer become unresponsive.This has been delivered as a patch on the 1.5.1 release to the MSF sites and thus should already be visible to the end users. The performance would be similar after this new release too.

3. Changes and enhancements to SAE import

   The data sent from PV unit for SAEs is imported into the Bahmni software. This import functionality has been modified now. Following are the enhancements to this functionality:

   1. Only the data that is present in the file that is uploaded will be kept after the import. This is because the data being sent by the PV unit is more reliable. Thus any data that existed before the import will be overwritten with the values of the import.

   2. If the PV unit SAE data file is imported multiple times, it would not create any duplicate sections, hence now it is fine to re-import the file.

4. Study cohort report

   The study cohort report gives information for all of the patients that are registered into the system monthwise for all the four years (2015-2018).
   The report must be generated in the Custom Excel format and the selection of the dates does not impact the data which is reported. The user just needs to select a start date and stop date for the purpose of running the report and then all of the data for the 4 years would be exported.

   1. To use the report, type in the year in the box “Current year” and then press enter

   2. The report would show the data for that particular year, to switch the view change the year.

5. Bahmni-endTB-batch

   Fixed the batch SQL queries retrieving data to ignore deleted treatments.
   

6. Metadata Changes:EndTB-Export

   Following are the metadata changes done as a part of this release:

   1. Removal of form condition on the SAE and AE form from the section “SAE / AE related to TB drugs?”, since even if the answer to this question is “No”, users would want to record the TB drugs that the patient might be on.

   2. Addition of option “Not Applicable” to the question “Final action” in the section “related to TB Drugs” on the SAE form.

   3. Removal of outcome “fatal” for AEs on the adverse event form.

   4. Removal of some redundant terms from the SAE and AE terms list.

   5. Changing all the audiometry test values from coded (select one option from a list of options) to numeric. All the values now will be recorded as a number between 0-120. Any values outside this would not be saved.

   6. Re-ordering of EndTB-Export codes for patient-related reason concepts.

   7. Migration of existing values for "Xray, Type of assessment" from deprecated value "6-month" to "Other value".

   8. The values that already exist in the system can be migrated from coded to this numeric format

User Feedbacks addressed in this release:

1. 1. Adherence reasons summary report and Adherence Monthly overview report took a long time to run, sometimes up to hours depending on the data load. This has now been addressed and the performance of these reports has improved significantly.

   2. UNITAID report for interim culture results was not counting patients that had no results. This has now been fixed.

   3. The displays for BPNS, Audiometry, Ishihara and Visual Acuity have been made full screen so that they appear in order when the patient summary is printed. This view works fine on the mobiles too.  
      

Fixes to known Issues

1. 1. After installation of Bahmni reports user has be to enabled manually: this issue was happening on a fresh installation of Bahmni, the reports user which is required to run reports in Bahmni was not enabled and had to be enabled manually by the implementer. This has now been fixed.
      

Known Issues:

• • When the drug is stopped on the TB drugs tab, before saving if the user navigates to the Non TB drugs tab, they would see those drugs appearing in the edit pane on the non TB drugs tab. Hence the user must save before navigating away from the TB drugs tab if they have made any changes to the medication.

  • If height, weight is entered such that the BMI calculated is a value out of the permissible range of BMI (like an impossibly large value) then the form does not save. An error message is seen and it should prompt the user to check the value of the weight and height that have been entered.

  • There is a default relationship type that has been introduced in the Bahmni database hence it will be visible on the registration page, this has no implication on the data recording and should be ignored.