Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

S.No.

Component

Role

 1.

STOP TB Mobile / Tablet Application (Offline/Online)

Primary data entry device for all roles; operates in full offline mode or direct online mode

 2.

Local Server (Offline Staging Endpoint)

Receives data from all devices on the same local Wi-Fi/LAN when no internet is available; forwards accumulated data to central server on connectivity restore. When this server comes online, it pushes the data to central server.

 3.

Central Server — AMRIT (National Data Store)

Authoritative data store; receives data directly from devices when online, or batched from local server when offline connectivity is restored


"Role Configuration and User Management”: Admin can add/remove users and assign/modify roles from the local server (laptop) interface; role changes propagate to all devices on sync; role assignment is device-agnostic (handled at login, not device level).

Role based user access to be provided and single user can have multiple roles. This has to be managed by Admin role in the central server as well as the local server. Based upon the role access permission only the application should have specific role privileges. Roles will be registrar, nurse, counsellor.

2.2 Operational Mode Requirements

...

UI Field Name

Field Type

Options

Validations

State

 Drop Down

·       Auto-Populate

·       This must be configurable and must allow to add different states in Future)

·        

·       (One Time Activity)- User must be registered with the State that he selected while enrolling himself for the first time under "Settings"

District

Drop Down

·       Auto-Populate

·       (This must be configurable and must allow to add different District/Town/City in Future)

·        

·       (One Time Activity)- User must be registered with the district that he selected while enrolling himself for the first time under "Settings"

Block

Drop Down

·       Auto-Populate

·       (This must be configurable and must allow to add different Taluk/Tehsil in Future)

·       (One Time Activity)- User must be registered with the block that he selected while enrolling himself for the first time under "Settings"

TU

Drop Down

·       Auto-Populate

·       (This must be configurable and must allow to add different TUs in Future)

·       (One Time Activity)- User must be registered with the block that he selected while enrolling himself for the first time under "Settings"

Health Facility

Drop Down

·       Auto-Populate

·       (This must be configurable and must allow to add different health facilities in Future)

·       (One Time Activity)- User must be registered with the block that he selected while enrolling himself for the first time under "Settings"

Village

Drop Down

·       Auto-Populate





·       (This must be configurable and must allow to add different Taluk/Tehsil in Future)

·       (One Time Activity)- User must be registered with the Block


  • Beneficiary and Household search should default to Village level first, then escalate to Block level (camp host village). The search validation stating  "Search is scoped to the currently selected Village by default. If no result is found within the Village, the system then offers an option to expand search to Block level." After login, the search scope should start from the selected village. Same validation for Beneficiary search pre-registration.

Submit

Button


Submit

Button

·       On clicking Submit Button it must navigate to HWC Page

...

  1. Household Registration (HH Reg)
    • Search for Household using:
      • HoF (Head of Family) Name
      • Mobile Number
    • If Household does not exist, create a new Household (HH).
  2. Add Family Details
    • Add HoF details.
    • Add other family members to the Household.
  3. Beneficiary Registration (Ben Reg / Family Member Registration)
    • Search Beneficiary using:
      • Name
      • Father’s Name
      • Mother’s Name
      • HoF Name
      • Mobile Number
      • Other available identifiers
      • Beneficiary and Household search should default to Village level first, then escalate to Block level (camp host village). The search validation stating  "Search is scoped to the currently selected Village by default. If no result is found within the Village, the system then offers an option to expand search to Block level." After login, the search scope should start from the selected village.
      • Name
      • Father’s Name
      • Mother’s Name
      • HoF Name
      • Mobile Number
      • Other available identifiers
      • Beneficiary and Household search should default to Village level first, then escalate to Block level (camp host village). The search validation stating  "Search is scoped to the currently selected Village by default. If no result is found within the Village, the system then offers an option to expand search to Block level." After login, the search scope should start from the selected village after logging in.

  4. Scenarios
    • Scenario 1: If Beneficiary record is found → Proceed to Screening and further workflow.
    • Scenario 2: If Beneficiary record is not found, but Household exists → Proceed with Beneficiary Registration (Ben Reg).
    • Scenario 3: If neither Beneficiary record nor Household exists → First complete Household Registration (HH Reg), then proceed with Beneficiary Registration (Ben Reg).

...

Role

Modules Accessible

Write Access

Read Access

Cannot Access

Registration Officer

Registration, Anthropometry

Registration, Anthropometry data for own camp

Own records

All Nurse, Counselling, Diagnostic, and Admin screens

Nurse

General Examination, TB Screening, General OPD, Diagnostics Screen

All Nurse module data

Registration + Anthropometry data

Confirmed TB Cases (write); Counselling; Admin panel

Counselling Officer

Confirmed TB Cases, Counselling, TPT / Household Contact Line Listing

Counselling data, Treatment initiation, Follow-up

Confirmed TB case data, Line list

Registration, Nurse modules (write); Admin panel

Admin / NTEP / STOP TB

Full Dashboard, Reports, All modules (read), Configuration

Configuration, User management

All data — district and national level

 full access


Role Configuration and User Management: Admin can add/remove users and assign/modify roles from the local server (laptop) interface; role changes propagate to all devices on sync; role assignment is device-agnostic (handled at login, not device level).

Role based user access to be provided and single user can have multiple roles. This has to be managed by Admin role in the central server as well as the local server. Based upon the role access permission only the application should have specific role privileges. Roles will be registrar, nurse, counsellor.