endTB release 1.1 Release notes


What’s new?


We have added the fix for two issues that were encountered:

  1. Taking an export was generating empty/erroneous files for some of the exports. This has been fixed.

  2. On saving the date for bacteriology samples, the value of the date was being saved as a day less than the data entered. This issue has been fixed.

Accessing UAT environment for Bahmni Release 1.1


You can access UAT environment at

https://endtb.twhosted.com/bahmni/home

User credentials:

superman --> Admin123

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

Note: The EndTB users will not be enabled in the base database dump by default. These are available only on the UAT environment mentioned above.


Features:


Following are the features available to the end user

  1. Patient Registration:

    1. This is the first step the user needs to perform

    2. Patients can be registered into the system, by providing basic information like (mandatory) Full Name, gender, date of birth, age (auto calculated from date of birth) and (optional) patient address details.

    3. There is an EMR ID to identify the patient in the system. It is a mandatory field and should be entered by the user by default. This ID can be generated by the system if needed. It is a site specific configuration.

  2. Treatment registration:

    1. Next step after registering a patient

    2. The patient can be enrolled into a treatment, on the treatment registration page. The user can select a Treatment, a start date, enter a registration number for the treatment and select a registration facility (optional).

    3. The details for a treatment can be edited on a later date.

    4. The patient can be enrolled into multiple treatments and the user can select one treatment.

    5. The treatment can be ended by the data entry person when it is no longer active.

  3. Searching for patients:

    1. When a patient is created in the system the user can search for them via their EMR ID or “Registration Number” in the registration app.

    2. When a patient is enrolled into a treatment, a user can search for them via their name or registration number in they can be searched for in the “Patient Record” application.

  4. Data entry:

    1. Once the treatment of a patient is selected, data can be recorded by clicking on “Enter data”. The system provides the ability to fill forms, record bacteriology samples and TB and non-TB drugs.

    2. The user can fill more than one form of the same type, by clicking the “Add More” button.

    3. The user must select the date using the date field. This date will be shown on the display.

    4. The user can record information regarding bacteriology tests against “Samples” in the “Bacteriology” tab

    5. Note: Data can be entered for past (or inactive) treatments too.

  5. Data Validation:

    1. The implementor can make fields activated conditionally on forms

    2. The implementor can make fields mandatory on forms

    3. The implementor can highlight values as abnormal on the forms if they are outside a designated range (lab results)

    4. The system gives a reminder to save data if the user navigates away from the data entry screen.

  6. Data update:

    1. A data entry operator can add more data to forms that have been saved by selecting an edit button that is on each form

    2. A data entry operator can change/update data entered as a part of that form by clicking on the edit button.

  7. Data Display:

    1. Data is displayed for a particular treatment on the General dashboard

    2. Data filled in forms can be viewed by clicking the view icon

    3. Data recorded as a part of the bacteriology samples is displayed on the dashboard.

    4. Data is displayed for the treatment on the patient summary page

  8. Exporting data: In order to  export data, a date range needs to be selected. The data is exported at a treatment level. The data for treatments started within that date range will be exported. Data entered can be exported in CSV and XLS formats in the following ways:

    1. Data entered into forms is exported per form as  “<Template Name> export”

    2. Data entered for bacteriology samples is exported as “Bacteriology Export”

    3. Information regarding drugs is exported in the “Drug Information Export”

    4. Information of all the patients in the system can be exported by using the “Patient Data export”

UAT feedback and related fixes:


This is the sheet where the complete UAT feedback can be viewed. The items that have been addressed are marked in Green color.


Known Issue: 


During the final round of testing we discovered that “First Year of TB treatment” on the baseline form is not checked for the range(1900-2015) before saving the data. This will be addressed in the next release.

 All the other range validations were found to be working fine.


Deployment Steps of endTB Bahmni Release 1.1

The general deployment steps wiki page is available  here.

Deployment instructions specific to EndTB release are mentioned below


Note: If an older version of Bahmni is running in the machine, make sure to drop the “openmrs” database in MySQL, before running the “bahmni install <inventory_file>” command


  1. Use the bahmni-installer  https://bahmni-repo.twhosted.com/rpm/bahmni/bahmni-installer-0.80-201.noarch.rpm   (in Step 2 in the deployment steps link mentioned above)

  2. Download and copy app config and base database dump from  https://bahmni-repo.twhosted.com/endtb/release-1.1/ (in Step 3 of the deployment steps link mentioned above)

  3. Make sure to add “bahmni_repo_url: https://bahmni-repo.twhosted.com/rpm/bahmni (without quotes) in /etc/bahmni-installer/setup.yml, along with “implementation_name: endtb” (as mentioned in Step 4 of the deployment steps link above)

On this page

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