You may refer to the Bahmni Roadmap document to see what is in the roadmap and in backlog.




End User


  • Capture visit attributes for non-clinical information and visit meta-data
  • Barcode integration (patient registration)

    • Generate barcodes at registration and integrate barcode scanners with registration module
  • Program dashboard and tracking patient within a program
    • Generate and track the adherence of the patient according to the schedule of the program patient s/he is enrolled in
  • Track the location of the patient within and outside the hospital over a time
  • Manage patient's food and drug allergies from the clinical module
  • Capture drug administration to the patient in an inpatient like setup (Medication Administration Record)
  • Search patients in the EMR based on user defined queries
  • Patient queues
    • Define different queues
    • Manage patients within a queue
  • Household
    • Create and edit household
    • Assign patient to the household
    • View household
    • Household information in the reports
  • Pictorial observations
    • Make observations about patient by drawing a picture using pointing device or touch gestures
    • Make observations on pre-created drawings
  • Cost of care
    • View the cost of encounter and the visit based from the EMR at the time of consultation
  • Email integration with clinical module
    • Send patient records via email from the clinical module (after removing patient identifiable information)
    • Integrate email based reply notes into the patient's medical record accessible from the clinical module
  • Alerts
    • System raised alerts based on rules
    • Provider raised alerts for another provider
    • Provider manages the alerts raised to them either by dismissing them or taking native action (action embedded in the alert)
  • Patient and user context based behaviour for clinical features
    • Customise the behaviour of the clinical module based on patient's profile, diagnosis, user's location and patient's program enrolment
  • Non-drug order related clinical decision support
    • not too many examples available as of now
  • Print observation form to create blank paper forms closer to system forms
  • Support for OpenMRS forms based collected observations
    • A control to display such information on the dashboard and visit pages
  • Regional calendar support in EMR
    • support for non-gregorian calendars
  • Remaining multiple language support in EMR
    • Inpatient module
    • Remaning apps in clinical module
    • Reports
    • Admin module
  • Maintain complete audit trail of all patient data changes
  • Maintain checklist for a visit or a program
  • Rule based data access platform
    • Define rules based on patient's data and user roles/privileges to selectively display patient information
  • Patient's diet management in inpatient like setup
  • Ability to make coded observations that have a numeric code behind the observation concept

EMR Offline

  • Patient home visit schedule management
    • Works in offline mode
    • Allows outreach workers to manage the home visit for the patient based on their treatment schedule
  • Chronic treatment schedule for patients in a program
    • Automatically generate the expected visit schedule of a patient
    • Track patient's visits against the schedule, helping in followup and assessment of the treatment
  • Barcode support in EMR
    • Generate and print barcode for the patients based on their registration ID
  • Multiple (generated) patient identifiers
  • Capture patient's contact details
    • Contacts who are not patients
    • Capture details in a structured way
    • Allow multiple contacts
  • Capture visit attributes
    • Capture non-clinical information while doing visit management as visit attributes
  • Patient referral
    • ..with in the facility to departments and clinicians
    • a different facility to departments and clinicians


  • Provider's duty schedule management
    • Define the work schedule for the providers
    • Capture provider's attendance against the schedule
  • Blood bank
    • Donor registration
    • Blood sample verification
    • Administration of blood to patient


  • Label printing for lab samples
  • Multiple laboratory support for a single deployment
    • Manage workload of different labs independently
    • Meta-data per lab
  • Platform for integrating with sample analysers in the laboratory
    • Support for HL7 compatible analysers
    • Allow for custom REST based integration with non-HL7 analysers
  • Support for long running tests like culture tests in the lab
    • Capture complex results
    • Workflow support


  • DHIS 2 Integration
    • Calculate the aggregates based on rules/reports defined and submit these to DHIS 2
    • Preview the aggregates to be submitted to DHIS 2
    • Create DHIS 2 events based on rules/reports and submit these to DHIS 2

Implementer (and data administrator)

  • Drug and lab tests management

    • User interface for management of drugs from a single page (concept drugs and concept)
    • User interface for management of samples, tests and panels (abstracting the OpenMRS concept dictionary details
  • OpenERP upgrade to Odoo (version 7 to 8)
  • Drug order configuration via user interface
    • management of total quantity calculation rules
    • mapping between drug forms and route, total quantity units
    • other drug order related application configuration
  • Patient filters management (patient listing are done using patient filters in clinical, inpatient modules)
    • define new patient filter
    • manage existing filters and which modules they are visible
    • manage the refresh interval of a filter
  • Define user context and patient data based behaviour mapping via a user interface
    • user interface to manage the application behaviour using the meta-data mapping
    • Order type, fulfilment, referral meta-data management
  • Export and import of EMR configuration - capturing app config, reference data and meta-data
    • Export data from an environment in a form that be applied (imported) into another environment
  • Bahmni CD
    • Package and publish ISO image of Bahmni containing operating system and Bahmni components
  • Ward, physical space and bed layout management
    • User interface for defining bed layout in a WYSWYG form
  • Clinical location to billing shop mapping
    • Helps in routing orders placed at certain clinical locations to be mapped to billing shops
  • User interface to manage the address hierarchy (used in patient registration)
  • Support for Ubuntu



On this page:

This page contains a high level listing of the various features that are in plan for Bahmni in 2016. The exact release/month of these is not decided yet though. You are most welcome to ask questions about the roadmap on our Q&A forum, and make suggestions for things you would like to see.



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