Bahmni as Health Information Provider (ABDM/NDHM)


Bahmni to function as a Health Information Provider and Health Information User under the ABDM ecosystem

Key outcomes

  • Bahmni will be certified by National Health Authority as Health Information Provider

  • Bahmni will be certified by National Health Authority as a Health Information User




Thoughtworks (Certification Link, News Announcement Link by MoHFW)

Project Overview

The National Digital Health Mission (NDHM) aims to develop the backbone necessary to support the integrated digital health infrastructure of the country. It will bridge the existing gap amongst different stakeholders of Healthcare ecosystem through digital highways. NDHM has laid out 3 milestones that facilities must incorporate in order to be certified by National Health Authority and integrate with the NDHM ecosystem. Bahmni would serve as a goto NDHM compliant Hospital Management System which facilities can adopt to integrate seamlessly with the NDHM ecosystem

Milestones and deadlines

The following image depicts the patient experience that can be leveraged after integration with the NDHM infrastrcture.

Patient experience under NDHM infrastructure

To leverage the above mentioned complete patient experience, NDHM recommends developing this experience in three milestones:


Completion date



Completion date


  1. Health ID creation and capture & verification for seamless patient registration

Nov 9, 2021


2. Building Health Information Provider (HIP) services to share digital records via Personal Health Records (PHR) app

Nov 9, 2021


3. Developing  Health Information User (HIU) services  to provide view of patient’s medical history to authorized healthcare workers with complete consent

Nov 9, 2021



Must have:

  1. Health ID verification during registration where patient verbally shares the Health ID

  2. Authentication of health ID via patient’s preferred authentication mode (Mobile OTP/ Aadhar OTP)

  3. HIP should be able to link the care contexts to the patient’s health ID

  4. HIP should ensure that an SMS is sent to patients with a trigger to PHR app when a new care context is created

  5. HIP should be able to create a care context and share the following types of records: Prescription, Diagnostic report, OPD notes and Discharge Summary.

  6. Bahmni should enable authorized medical providers to raise consent from the HIU portal to access patient’s medical data

Nice to have:

  1. Health ID verification via QR code where patient scans the HIP QR code / Facility scans the QR code on the patient’s Health card

  2. Health Documents as a medical record type

Not in scope:

  • Creation of Health ID

Architecture diagram

Bahmni ABDM is

  • Core Bahmni Product along with ABDM specific extensions (additional set of s/w components and subsystems) that augment Bahmni to become compliant for HIE-CM. Thoughtworks has developed and open sourced the extensions as MIT License.

  • Bahmni went through the sandbox process successfully, having demonstrated functional flows and compatibility, and also passed through the WASA assessment.

The above architecture shows the integration of Bahmni as a Health Information Provider and Health Information User with the NDHM ecosystem. The following components exist:

  1. HIP Service + ABDM FHIR Lib + ABDM UI Extension: Written in C#, React.JS (with an HIP Backend module written in Java as a Bahmni module). The UI Extension is used for HealthID pop-up/verification before pulling it into Bahmni. The HIP service uses a Postgres DB for data storage.

  2. HIU UI + HIU Service: Written in Java + JS, to provide clinicians with a UI for viewing users past health records (after consent). The HIU service uses a Postgres DB for data storage.

Code Repository


Demo Video of Bahmni with ABDM Workflows

A good blog by @Abhinab Bharali on his experience of incorporating ABDM support in Bahmni:


Reference materials