...
Document Revision History
Date | Version Number | Author | Approved By | Document change reference |
| Dr Vanshika | Madhav | Initial draft | ||
| 23.4.2026 | Dr Vanshika | Madhav | Beneficiary Registration, TB screening, Vitals after feedback and several updates done | |
| 24.4.2026 | Dr Vanshika | Madhav | Mock ups and flow diagram | |
| Dr Vanshika | Madhav | TPT screening module in progress | ||
| 01.05.2026 | Dr Vanshika | Madhav | Offline/ Online functionality with cross device communication. |
1. Document Overview
This document defines the functional requirements for the TB Screening mobile application developed under the TB Mukt Janjati Abhiyan: A community-driven TB elimination initiative targeting tribal populations across India. The application is purpose-built for field use by community volunteers in tribal areas where connectivity, literacy, and device familiarity may be limited.
The application should be simple to use, comprehensive and must work in low/no-connectivity environments.
...
| S.No | ||
|---|---|---|
| Offline Functionality with cross device communication including online functionalities to communicate with central server (AMRIT). | ||
| Role based user access (with actions and privileges) | ||
| Beneficiary Registration Module | Enlisted in the PRD | |
| TB Screening, tracking and conformation, treatment follow up and TPT (TB Preventive treatment) modules. | Enlisted in the PRD | |
| General Examination and General OPD modules | Enlisted in the PRD | |
| User Dashboard indicators | Enlisted in the PRD | |
| Integration of NIKSHAY application | External technical dependency | |
| Integration of portable digital chest Xray device (AI enabled) | External technical dependency | |
| Integration of Lab testing device (sputum testing and others) | External technical dependency | |
| Integration of AMRIT inventory management module | ||
| ABDM M2 | |
| Pre Camp Work Plan Preparation Module | Subjected to requirement |
1.4 Workflow at the Camp Site
...
Architecture Overview-
The application must support three distinct operational modes. The synchronization architecture is tiered: device-level data is routed to a local server in offline conditions, and to the central server directly when online.
📱 Stop TB application (Offline / Online) | → | 🖥 Local Server (Offline staging endpoint) | → | ☁ Central Server (Central data store) |
Login Page
- Login Page Name should be "STOP TB" Application.
- It must be followed by "STOP TB" Logo.
- It must have both Online and Offline capabilities. For online- Mobile number OTP based with 5 min expiry. For offline- 4-digit PIN which can be set during the first login.
- It must have Multilingual Feature with English, Hindi and other Indian languages enabled, and must be configurable to accommodate all the Indian languages as and when required in future.
...