Release Notes 1.3

Accessing UAT environment for Bahmni Release 1.3

These are the environments that can be used for UAT:

https://endtb-msf.mybahmni.org/bahmni/home/

https://endtb-pih.mybahmni.org/bahmni/home/

https://endtb-ird.mybahmni.org/bahmni/home/

Note: the MSF server is located in Paris, the PIH server in Boston and IRD in Mumbai. Please use the server located close to your location for optimum performance.

User credentials:

User Name-->password

superman --> Admin123

msfuser1, msfuser2, msfuser3, pihuser1, pihuser2, pihuser3, irduser1, irduser2, irduser3 --> endTB123

Deployment steps:

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

What’s New:

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

  • SAE Data Import:

SAE Import allows the user to import data in the SAE forms of treatments.  The SAE data is received from the PV unit in a digital format. The end-user can upload this file in endTB instead of entering the data manually per treatment. The result of this would be equivalent to entering the data for each SAE from the UI. The detailed documentation on this can be found here.  

Please Note: The way to import SAE data is still under discussion with the consortium and this functionality might change. If it does change, the details of how to use the functionality would be updated when the new functionality is completed.


  • Restrictions on data entry:

    Since some of the forms can only be filled once per treatment this restriction has now been programmed into the system. The baseline, treatment initiation and outcome form can now only be filled once for a treatment. Also the monthly treatment completeness form can only be filled once per month per treatment.

  • Data Quality Dashboard:

     

The rules implemented in this release are:

  1. Consent for New Drugs: all the patients who have been prescribed either Bdq or Dlm and do not have the answer to the question “Consent form signed” as “yes” will be listed as per this rule.
  2. Consent for endTB Obs Study: all the patients who have been prescribed either Bdq or Dlm and do not have the answer to the question “endTB consent form signed”  as “yes” will be listed as per this rule.

    The remaining rules would be part of the next release. Data Quality Dashboard is a new and generic Bahmni feature and can be extended by an implementer by plugging in additional rules.

  • UNITAID Reports: 

    The remaining pieces on the UNITAID reports have now been completed. The following have been completed as a part of this release:

    1. The enhancement to the UNITAID reports where only the initial start date of drugs is considered for counting the patient in a particular cohort is completed. Now the patient would only be counted in the cohort that overlaps with the initial start date of Bdq/ Dlm.

    2. Count of culture results for month 6: For patients that do not have an outcome at the end of 6 months; we need to asses the culture status as on the sixth month. This report gives an aggregated view of different culture results for all the patients that are still on treatment.

 

  • Other Reports: 

    To generate a report from the system, the user must navigate to the reports application and select the date range for the report that needs to be run. After this the user must select the format in which the report must be generated.
    (Note: This has been mentioned after the name of the report for the convenience of the user. Running the report in other formats might generate an erroneous file)
    Following are the reports that are available in this release:

 

    1. Adverse Events Report: This report generates a line list of all the adverse events that have been reported between the dates that the user selects. The information recorded for that adverse event is listed in the row for that adverse event.  

    2. Late Visit Report: This report lists all the patients that have not had a visit reported for the past thirty seven days. The date of the last visit is ascertained from the last follow up form that is filled for the patient. This report also gives the basic contact information of the patient so that he/she can be contacted for follow up.

    3. Serious Adverse Events Report : This report generates a line list of all the SAEs that have been reported between the dates that the user selects. The information recorded for an SAE is listed in the row for that SAE

    4. Adherence Monthly Overview Report : This report gives an overview of what the Adherence, completeness and DOT rate for different patients (treatments) have been over the months. It considers the month in which the patient’s treatment was started as the first month for that treatment. It also lists some of the basic parameters of the patient’s treatment like the TB profile and subclassification.

    5. Daily/Weekly Visit Report : This report gives a list of patients that have their next scheduled visit falling in between the date range that is selected by the user. The next visit is determined from the last follow up form that was filled for the patient. It also gives information about some of the latest lab results for the patient.   

    6. Adherence Monthly Summary Report : This report gives the list of months between the date range selected by the user and gives the value of Adherence rate, DOT rate and completeness rate for all the patients for those months. (given that the form for that month has been filled for that treatment). It also lists the reasons for missing adherence for each of the patients for each month.  

 

  • User Feedbacks addressed in this release:

    Following were some of the issues that were reported by the end users and have now  been fixed as a part of this release.

    1. Enter Numeric Value Error on the Lab Results forms: An error of “enter numeric value” would be shown even when all fields had numeric values entered and no fields would be highlighted in red to indicate the error. This was fixed as part of the release. The fields now accept only numeric values and only in case of an invalid entry the system would highlight the erroneous field and display an error message.

    2. Open in a new tab button (green button on top right, that opens enter data on a new tab in the browser): This button helps the user to toggle between the dashboard and data entry, which is sometimes necessary for context and to aid in data entry. The defect that was pointed out was that this button opened the patient dashboard without the context of any treatment and thus allowed patient level data entry. Since this is invalid for the use case of endTB this defect has now been fixed and the button now opens the “Enter Data” screen for that treatment in a new tab.

    3. Patients still in treatment even if treatment is ended: The issue was that the current month of treatment is displayed even after an end of treatment date is specified with an outcome. This was calculated as the difference between the start date and the date when the summary is being seen. As a part of this fix, we introduced Treatment Duration in the Patient summary , that is now displayed for those patients for whom end of treatment date is provided, instead of displaying the current month of treatment.

    4. Date doesn’t Auto-tab : The issue reported was that the Date auto-tabs from day to month but does not to year, causing users to make data entry errors frequently in the month field. The issue was looked into and it was found that with the dd/mmm/yyyy format the mmm field does not auto tab to yyyy format but it does auto-tab to yyyy in case of dd/mm/yyyy formats. This is a browser limitation and the same has been communicated.

    5. Inactive non TB drugs couldn’t be voided: The issue was that there was no void/delete option for the inactive Non TB drugs. Hence if a wrong order was stopped or auto-expired there was no way to remove this incorrect data. This issue has now been addressed by providing a void/delete option for the inactive Non Tb drugs.

Known Issues:

  1. Form conditions that have an “Add Section” do not work on the additional sections.

  2. On the Bacteriology results form when you do an “add section” of the DST results the  “other drugs” below it appears twice in the newly added section; once as a section and a tabular row below that. The result that is entered in the newly appearing tabular row for the “other drugs” will not be saved. Data entered into the non tabular structure is saved. After save the data appears in the proper tabular format.

  3. On the TB drugs tab if a drug is stopped on today’s date and then started again, it is not reflected accurately on the Drugogram. This behaviour is only seen for today’s date. For all other dates, the feature works as expected.

UAT feedback:


This is the sheet where the users can add their feedback post testing. Please follow the conventions being followed so far in the sheet. A demarcation has been made in the sheet for denoting the feedback of this release.

Note: a separate sheet has been added to this titled ‘End User Feedback’. Kindly refer to that sheet for updates on issues related to end user feedback.


Release notes from the Previous releases:

The release notes from the previous releases are given below,

On this page

The Bahmni documentation is licensed under Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)