Versions Compared

Key

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

...

Layer

What it shows

 

Notes

Confirmed case markers

Distinct icon/colour; shape or badge for DR-TB and DS-TB

Tap for case card (respecting role-based data masking)

Presumptive case markers

Separate style; awaiting test result

Auto-updates on result sync

Contact markers

Coloured by risk score band

Clustered at zoom-out to avoid pin soup

Household boundaries

Polygon or grouped pin per household

Groups all members; deduplicates visits

Lines between linked cases/contacts

·       Household (solid),

·       Occupational (dashed)

·       Social (dotted)

Heat map

KDE density surface of cases

Adjustable time window

Risk zones

Statistically significant hotspots (Gi*)

Outlined polygons with significance label

Administrative boundaries

Village, PHC, Block, District

Standard NTEP boundary layers; selectable admin filter

Health facilities

DMC, NAAT site, PHC, DR-TB centre

Icon by capability; shows nearest-facility

routing

Screening coverage

Choropleth map: % of index cases with completed contact investigation

The core quality metric, visualised

Pending investigations

Households/contacts overdue

Colour by days-overdue

Active treatment

locations

Where patients are on treatment

For adherence/follow-up geography

...

Multi-Level Geospatial Navigation (India to Village)

The solution should include a cascading geospatial navigation layer that connects the national picture to a single household on one continuous map. A user begins at an India view and drills down through state, district, and block to reach a village, where the existing GIS surveillance dashboard opens. This puts into practice a core design principle of the module: every management tier works from the same data, seen at a different zoom.

How it works- All levels share one geographic coordinate space, so moving between them is a true zoom rather than a switch between separate screens. When a user drills in, the surrounding areas scale outward and stay visible as context, which preserves orientation. Transitions are animated. Administrative boundaries are colour-coded by level, and each area carries an interactive summary pin. A breadcrumb trail (India, state, district, block, village) is always visible, and any step can be clicked to return to that level. A side panel shows aggregate statistics that become more granular at each descent, from national totals down to a single village.

The five levels.

  1. India. All states and union territories appear as distinct coloured boundaries, each with a headline indicator such as active clusters. Selecting a state zooms in.
  2. State. The state's districts are shown with contact-investigation coverage and cluster counts. Selecting a district zooms further.
  3. District. The district's blocks are shown with block-level coverage and overdue indicators.
  4. Block. The block's villages are shown with their names, coverage, and active-case-finding priority.
  5. Village. Selecting a village opens the full GIS surveillance dashboard already built into the module: index cases, household, occupational and community contacts, probable transmission links, and all existing layers, legends, filters, and the AI recommendation panel.

This feature helps a district officer, a state lead, and a surveillance officer no longer depend on separate reports or tools to understand the same outbreak. The national and village realities are the same underlying data, which supports the state function of directing diagnostics, staff, and logistics by live risk rather than historical burden.

For production, the navigation would ingest the authoritative NTEP administrative boundary layers down to sub-district, and village-level geometry where available, with case and contact positions drawn from geocoded Ni-kshay data. The design stays offline-first at the village level, preserves role-based data masking, and keeps the principle that the AI ranks and suggests while people make every clinical and confirmation decision.

3. Product Requirements

Functional requirements-

...