Related Experiment Video
Updated: Sep 27, 2026

An Automated Culture System for Use in Preclinical Testing of Host-Directed Therapies for Tuberculosis
Published on: August 16, 2021
Evolution of TB programmatic information systems in India
Manu E Mathew1, Jyoti Jaju1, Kiran Rade2
1International Union Against Tuberculosis and Lung Disease (The Union), New Delhi, India.
Abstract:
The development of tuberculosis (TB) programmatic information systems in India reflects the broader evolution of health information systems from paper-based reporting to integrated digital ecosystems. This paper documents three major phases in that evolution: the management information system era led by EpiCentre, the electronic case registry era under Nikshay V1, and the current transaction-based ecosystem represented by Nikshay V2. Each phase emerged in response to changing programme needs, technological capabilities, and expectations for data quality, timeliness, and operational usefulness. EpiCentre supported structured quarterly reporting from TB units but depended heavily on manual consolidation, delayed reporting cycles, and triangulation across multiple registers. Nikshay V1 introduced case-based digital registration and enabled more flexible reporting across the programme hierarchy, but it also exposed limitations related to change management, incomplete transition from legacy systems, and persistent data quality challenges. Nikshay V2 marked a conceptual shift from reporting systems to transaction-based architecture, linking service delivery events across the TB care cascade through lifecycle-based records and interoperable applications. This architecture enabled integrated workflows for diagnostics, treatment, adherence support, direct benefit transfers, call centre services, and automated dashboards. However, the transition also created new challenges, including continuous adaptation requirements, user learning burdens, validation with external data sources, and the need for stronger analytical conventions. The experience shows increasing prioritization of interoperability, field level usability, automation of reporting, generation of insights, and facilitation of programmatic decisions, while boldly transitioning between system versions. Lessons from this experience of maturing information systems toward a transaction-based architecture may be replicated elsewhere.
Related Concept Videos
Pulmonary Tuberculosis V
Latent tuberculosis infection occurs when TB bacteria are present in a person's body, but are not causing illness or symptoms. It is not contagious, and preventive treatment is crucial to avoid the progression...
Pulmonary Tuberculosis I
Causative Organism
The primary infectious agent causing tuberculosis is Mycobacterium tuberculosis, a slow-growing, acid-fast, aerobic rod that exhibits sensitivity to heat and ultraviolet light. Instances of Mycobacterium bovis and Mycobacterium avium contributing to the development of TB infection are rare.
Mode of...
Pulmonary Tuberculosis II
Here is a detailed explanation of its pathophysiology:
Transmission: The process begins when a person inhales droplet nuclei containing M. tuberculosis. These are typically released into the air when an individual with pulmonary or...
Tuberculosis
Pulmonary Tuberculosis III
The first classification is based on the development of the disease, and it includes the following categories:
Pulmonary Tuberculosis IV
Several diagnostic approaches are used to detect TB. The conventional method is the Tuberculin Skin Test (TST), also known as the Mantoux test. However, this method has...

