Accessing UAT environment for Bahmni Release 1.5
These are the environments that can be used for UAT:
Note: the MSF server is located in Paris, the third server is hosted in India and the PIH server in Boston and IRD in Mumbai. Please use the server located close to your location for optimum performance.
superman --> Admin123
msfuser1, msfuser2, msfuser3, pihuser1, pihuser2, pihuser3, irduser1, irduser2, irduser3 --> endTB123
The steps for deploying the release 1.5 build for endTB are available at this link.
Following are the new features available as a part of this release:
The image upload feature will enable the users to upload images or documents to treatments. This feature is available as a form in the observations tab and allows the user to enter a date and description for each image that is uploaded. The form has an add more facility, so multiple images can be uploaded for a treatment. The uploaded images/documents can be viewed and accessed from the ‘Documents’ Dashboard.
This feature will help the users in monitoring whether patients adhere to a set of visits and Lab tests etc as per the DRTB treatment schedule. The patient monitoring tool gives a visual representation of the following:
The planned treatment schedule for the patient
The patient's position in the treatment schedule as of today
Missed or erroneously captured data
The columns in the patient monitoring tool represent the different milestones of that treatment. For e.g the months (M1-M24) of treatment from the drug start date or the treatment start date.
There are some milestones like MTx and M6M which are defined by the End of treatment date.
The rows represent the data that is to be tracked across those milestones. For e.g These could be clinical observations, drugs, or bacteriology results.
The colours in the Patient Monitoring tool represent data that is expected, data that is missing and data that is present according to the defined schedule.
The current month of treatment and the end of treatment in highlighted in the patient monitoring tool.
The patient monitoring tool can also be printed.
The schedule of what needs to be recorded and when can be defined at a local level by the implementers in the configuration.The details of configuring the tool are available here.
3. Cohort Reports:
The following 4 cohort reports are a part of this release:
Cohort report: Enrollment (T) Report (DRTB) - This report would consider all the patients in the ‘Second-line TB Treatment register’ who have started the treatment in the date range entered and provide aggregates across age, gender and case definition parameters like WHO registration group, MTB confirmation, Drug resistance profile etc
Cohort report: Enrollment (D) Report (DRTB) : This report would consider all the patients who have started either Bdq or Dlm in the date range entered and provide aggregates across age, gender, HIV status and case definition parameters like WHO registration group, MTB confirmation, Drug resistance profile etc
Cohort report: Outcome (T) Report (DRTB) : This report would consider all the patients in the ‘Second-line TB Treatment register’ who have started the treatment in the date range entered and provide aggregates of case definition parameters like WHO registration group, MTB confirmation, Drug resistance profile etc across various treatment outcomes.
Cohort report: Outcome (D) Report (DRTB) : This report would consider all the patients in the ‘Second-line TB Treatment register’ who have started either Bdq or Dlm in the date range provided and provide the aggregates of case definition parameters like WHO registration group, MTB confirmation, Drug resistance profile etc across various treatment outcomes.
4. Mobile View of Patient summary:
The Patient summary has been modified to made suitable for viewing in a mobile phone screen. The users will be able to view the patient summary in both landscape and portrait mode and navigate easily on the page.
The feature allows the user to scroll the table and view the data in case the data does not fit completely in one view. There is one single menu to access the dashboard tabs – General, Patient summary, Patient Monitoring Tools (T&D).
However, this modification to the patient summary page is only meant for viewing the patient summary and does not fully support data entry through a cell phone.
5. Revised Drug-o-gram Behaviour
The drug-o -gram behaviour has been enhanced to now indicate errors for some entries of drug orders. In the following scenarios, an Error indication will be displayed in the column of that drug:
When two orders of the same drug are such that even one day in the orders overlaps,
When a drug is started and then stopped at the same date
When there is an error in one column, the other columns still show the correct information.
The user is expected to go to the medications tab and rectify the error in entry to remove error indication from the drug-o-gram.
NOTE: When a drug is prescribed for a future date, the drug can be stopped only on today's date. This will not be indicated as an error on the drug-o-gram, but an empty column will be there for that drug on the drug-o-gram to indicate this.
More details about the drug-o-gram can be found here.
6. Enhancement to AEI UNITAID Report:
A new AEI ‘Peripheral Neuropathy’ has been added to the list of AEI.
7. 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.
Unable to revert when italian Locale is selected: The dropdown for the locale for would go away when ‘it’ was selected as a locale. This has been rectified as a part of this release.
Order of dates in the Treatment Information: The End of treatment date would appear after the Treatment start date. The information on the Treatment information table has been configured to display the Dates in Order.
The answers to ‘Consent for endTB Obs Study signed’ have been changed to ‘Yes’, ‘No’, ‘Pending’ and ‘Not possible’ as per updated metadata. The DQ rule related to this question has also been updated to accommodate this change.
Title of the late visit report has been changed to ‘ Late Visit Report For The Start Date (Excel)’ to indicate that the report takes only the start date into consideration.
Addition of a column to the Basic register: A column has been added to the Basic Register (T) and (D) to specify whether the treatment is from the Basic Management Unit TB register or the Second-line TB treatment register
Type of Assessment in the X-ray and Radiology form: The ‘6-month post treatment assessment’ has been removed and will now be a part of ‘Other assessment’.
Fixes to known Issues
Incorrect data on the Drug-o-gram : The drug-o-gram would show the STOP information incorrectly when drugs were started and stopped on the same date. This has been addressed in this release.
The “Late visit list report” shows all the inactive treatments too: This has been fixed in this release by putting a check for inactive treatments.
"Monthly Treatment Completeness is already filled for this month and year for this treatment." error when entering data in some other form: This happens in release 1.4 because checks have been introduced from 1.3 onwards to ensure that a MTC form is filled only once for a month. In case duplicate MTC forms exist previously, then this error comes when some other form is saved.The user is unable to void the MTC form that has been filled twice for the same month from the dashboard. This has now been fixed in this release.
If the adverse events form has been voided for a treatment (by deleting each of the observations), we still see the line for that form in the adverse events report. This has been fixed and we no longer see this row on the report if the form has been voided.
Refreshing the Documents Tab takes you to the general dashboard: The behaviour with rest of the dashboards is such that on refresh we stay in the same dashboard. This will be addressed in the next release.
Print of Patient Monitoring tool: Patient monitoring tool print cuts out the milestones and concepts in the section that needs scrolling.
Documents form cannot be voided.
Workaround: In order to void the form, first clear the image from the form and save it. After this remove the date and the description and save the form again. This will void the form.
Test Results for Automated tests
In this release, we ran automation scripts that we have written as a part of our test suite. They are divided into specifications (specs) and each spec contains test cases. We currently have 5 specs with 10 test cases. The test suite is work in progress, and we would be adding more test cases in the future.
These tests were run on the MSF, IRD and PIH environments. One sample of such a test result is shown below:
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,