Using Bahmni Connect App

Purpose and Benefits

Bahmni Connect allows the user to access Bahmni in areas (satellite areas) where there is limited or no internet connectivity. Bahmni Connect records ramped down medical information about patients. The information collected in Bahmni Connect gets synced with the Bahmni online server (mother location) when the device gets internet connectivity.

Bahmni Connect is currently being used by:

  1. Community Health Workers (CHWs) who use handheld devices to register patients and record observations when they have no or limited access to internet.  
  2. Users in outreach clinics where the same device travels across multiple outreach clinics during an outreach tour/s. Such outreach tours occur in resource constrained environments with no or limited internet connectivity.

Bahmni Connect application supplements the regular Bahmni application in the following ways:

  1. Allows patient information from remote areas to reside at a central location to help in clinical decisions, epidemiology, etc.

  2. Makes the work of CHWs visible to the clinicians to help in better healthcare in remote and resource constrained areas

Bahmni Connect currently runs on two platforms:

  1. Chromium Application: This is a web extension which runs on the chrome browser
  2. Android Application: This is an Android application which can run on any android mobile device


Featured Article

Read an article by Arjun on his experience deploying Bahmni Connect app in rural remote India at JSS subcenters here: Offline Patient Search and Registration In Remote Sub-centers of JSS

Using Avni for Field Data capture

Avni is an opensource application, that is offline-first and designed for use in Field Work and Community settings. This is also a good option to consider for field work, data capture based on digital offline forms and then sync them to a centralised cloud instance for Reporting, or into Bahmni. Read more about Bahmni-Avni here: Introduction and Integration-Code-Github. This integration is Live in Ashiwini hospital: https://avniproject.org/blog/how-avni-has-become-pillar-of-community-MIS-at-ASHWINI/


Using Bahmni Connect

Overall Workflow

The image below describes Bahmni Connect usage at a broad level for the end user:

Synchronization of the Client Device

There are two types of synchronization:

  1. Initial sync automatically at first login

    This synchronizes the device with all relevant data for the assigned location such as registration fields, forms and form fields, pre-existing patient data, et al. This happens automatically when a user selects a location for the first time and logs in.

    Detailed below are the steps to sync the Client Device:

    1. Go to an area with Network Connectivity

    2. Enter Credentials, select a location and log in (screenshot below)


    3. In the case of the Initial Sync, the Location Data is synced, and upon successful completion the following screen appears


    To resolve sync errors please contact your System Admin

  2. Regular sync on pressing the sync button 

    This is required to regularly sync the device and Bahmni online with newly captured data. The recommended sync frequency is once a day.

Detailed below are the steps to sync the Client Device:

1. Go to an area with Network Connectivity

2. Enter Credentials, select a location and log in (screenshot below)

3. For Regular sync, the catchment data is synced and the Sync button has to be pressed. Bahmni Connect also has the provision of a scheduled sync, and the device is synced with Bahmni online as scheduled.

Successful Regular Sync with relevant status message

Regular Sync with Errors Logged in the Error Log


To resolve errors please contact your System Admin

Supported Functionality

As of now, Bahmni Connect supports the following features:

Registering a Patient

Viewing Patient Data on Patient Dashboard

Recording Observations

Entering Consultation Notes

Updating the Bahmni Connect Application

Bahmni Connect and Bahmni applications are regularly upgraded with new versions to support a newer set of features. Hence Bahmni Connect must be regularly updated to use the enhanced functionality as well as to be compatible with the newer version of Bahmni. There are two types of updates:

  1. Non-forced Update - This means that a newer version is available, but it is still compatible to use Bahmni Connect client with Bahmni.
  2. Forced Update - This means that Bahmni Connect cannot be used unless it is updated.

Whenever an update is available, the update button is enabled in the top right corner on the landing page.

Upgrading the Android Application


Upgrading the Chrome Extension



The older extension should not be deleted from chrome browser to update the application. Deleting the extension deletes the data as well.

Logging Out of the Bahmni Connect

Click the Logout Button to log out of the Bahmni Connect

The screenshots are taken from a Samsung tablet running on Android 4.2.2. For the Chromium Application, the functionalities look and remain the same

Current Limitations

Initial synchronization of the Chromium Application stops when the User moves out of the tab on the chrome browser and resumes when the User returns to the tab

On this Page

Feature Details
Implementation Details

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