Accessing UAT environment for Bahmni Release 1.5
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 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.
...
The steps for deploying the release 1.5 build for endTB are available at this link.
What’s New:
Following are the new features available as a part of this release:
1.Image/Document Upload:
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.
...
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:
...
More details about the drug-o-gram can be found here.
6. Enhancement to AEI UNITAID Report:
...
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
...
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.
...
The release notes from the previous releases are given below,