Health
PlatformDomainAcademyDesign SystemFeedback
v1.0
v1.0
  • Introducing DIGIT Health Platform
    • Roadmap
  • Platform
    • Release Notes
      • Release Checklist
    • Platform Features
    • Architecture
      • Master Data Management Service (MDMS)
      • High Level Design
        • Health Campaign System High Level Design
        • Design Decision Log
      • Low Level Design
        • Registries
          • Individual
          • Household
          • Product
          • Facility
        • Services
          • Project
          • Stock
    • Technical Skillset & Pre-requisites
    • Installation
      • Setup Requirements
      • Supported Clouds
    • Configuration
      • Localisation Keys
    • Development Guide
    • Source Code
    • DHIS2 to DIGIT Integration
      • DHIS2-DIGIT Field Mapping
  • Products
    • Health Campaign Management
      • Frontline Worker's App
        • User Personas
        • Features
        • User Interface Design
          • User Management
          • Complaints Management
          • Supervision Flow
          • Beneficiary Registration
          • Service Delivery
          • Inventory Management
          • User Login
        • HCM App User Manual
          • Language Selection
          • Login
          • Forgot Password
          • Project Selection
          • Beneficiary Registration
          • Delivery Intervention
          • Stock Management
          • Checklist
        • Test Cases
        • Functional Specifications
        • Field App Architecture
        • Installation
          • APK Installation
        • Configuration
          • HCM Configuration
            • Individual Registry
            • Household Registry
            • Product Registry
            • Facility Registry
            • Stock & Inventory
            • Project Services
            • Complaints
              • QA Sign-Off
                • Test Cases
            • User Management
              • QA Sign-Off
          • HCM Master Promotion Guide
        • Release Notes
          • Success Metrics
        • Product Sign-off
        • Architect Sign-off
          • Health UAT API Execution Report
          • Performance Report
        • QA Sign-off
        • Products Requirement Documents (PRDs)
          • User Management
          • Complaints Management
          • Supervision Flow
          • Role Action Mapping
          • Beneficiary Registration
          • Service Delivery
          • Inventory Management
          • User Login
      • Campaign Management Dashboard
        • Features
        • User Stories
        • User Interface Design
        • Dashboard User Manual
        • Test Cases
        • Installation
        • Configuration
          • Dashboard UI Enhancements
          • HCM Dashboard Master Promotion Guide
        • Release Notes
          • UX Audit
          • PM Audit
        • Product Sign-Off
        • Architect Sign-Off
        • QA Sign-Off
        • Product Requirement Document (PRD)
  • Programme
    • Standard Operating Procedures (SOPs) and Plans
      • SOP for Helpdesk Support
      • User Management SOP
        • Master Data Collection Template
          • Boundary Hierarchy
          • Boundary Data Specs
          • System User Setup
          • Facility
          • Product
      • Master Data Management SOP
      • Training Plan
      • Field Test Plan
      • Programme Roll-Out Plan
      • Change Management Strategy
      • UAT Plan
        • UAT 1
          • UAT 1 Test Scenarios
          • UAT Test Cases
            • Registration & Distribution
            • Inventory Flow
            • Supervision
          • User Acceptance Test Report
            • Plan Dates
        • UAT 2
          • UAT 2 SOP
          • UAT 2 Test Scenarios
          • UAT Observations
            • Registration and Distribution
            • Inventory Flow
            • Supervision
            • General Feedback
          • UAT Feedback Form: SUS
          • UAT Feedform Form: Process
    • Monitoring and Evaluation (M&E) Tools
    • Implementation Checklist
    • DIGIT Pre-Training Tutorials
Powered by GitBook

https://creativecommons.org/licenses/by/4.0/

On this page

Was this helpful?

Export as PDF
  1. Programme
  2. Standard Operating Procedures (SOPs) and Plans
  3. User Management SOP
  4. Master Data Collection Template

Boundary Data Specs

Name of Field
Description
Mandatory
Input
Data Type
Validation
Comments
Need Data from Program/ State

Sr. No.

Boundary Code*

This is a code for the sub-classification for a particular boundary. Should be unique across all boundaries defined

Mandatory

MDMS

String

Yes

Boundary Name* (In English)

The name of the boundary that is being defined in the English language

Mandatory

MDMS

String

Yes

Boundary Name* (In Local Language)

The name of the boundary that is being defined in the local language of the state e.g. Portuguese, Hindi etc.

Mandatory

MDMS

String

Yes

Parent Boundary Code*

This is the boundary code of the parent which identifies to which parent the child belongs to

Mandatory

MDMS

String

Yes

Boundary Type*

The name of the boundary type i.e. Ward, Zone etc.

Mandatory

MDMS

String

Yes

Hierarchy Type Code*

The code of the boundary hierarchies for which this particular boundary is defined

Mandatory

MDMS

String

Yes

Campaign Start Date

Date when the campaign starts in the respective boundary in dd/mm/yyyy format

Mandatory

MDMS

Date

Yes

Campaign End Date

Date when the campaign is supposed to end in the respective boundary in dd/mm/yyyy format

Mandatory

MDMS

Date

Yes

Total Households

Total households present in the boundary (as per the micro-plan)

Mandatory

MDMS

Numeric

Yes

Targeted Households

Total households targeted for the respective boundary (as per the micro-plan)

Mandatory

MDMS

Numeric

For bed net, the total and the targeted is likely to be the same

Yes

Total Individuals

Total individuals present in the boundary (as per the micro-plan)

Mandatory

MDMS

Numeric

Yes

Targeted Individuals

Total individuals targeted in the boundary (as per the micro-plan)

Mandatory

MDMS

Numeric

For bed net, the total and the targeted is likely to be the same

Yes

Bed nets estimated to be delivered

Total bed nets estimated to be delivered in the boundary (as per the micro-plan)

Mandatory

MDMS

Numeric

Yes

PreviousBoundary HierarchyNextSystem User Setup

Last updated 1 year ago

Was this helpful?