> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/health/v2.0/deploy/configuration/microplan-service-configuration/microplan-web-service-configuration/supervisor-workflows/village-details.md). # Village Details ## **Overview** The Village Details screen is used to access microplan details for the selected village and linked information. ## Interface Elements When a user clicks on a village name in the **Population Data Table**, they are directed to the **Village Details Page**, which provides detailed information about the selected village.

*** **2. Header Information** * **Microplan Name**: Displays the name of the microplan associated with the village. * Displays the Hierarchy of the village. *** **3. Security & Accessibility** * **Village Security**: Provides an input field for entering security details about the village. * **Master Details :** * [Click here ](https://github.com/egovernments/egov-mdms-data/tree/UNIFIED-DEV/data/mz/health/hcm-microplanning)to fetch the MDMS data. * **Security Questions** 1. **Is your village prone to civil unrest, like violent protests, riots, etc.?**\ Captures the frequency of civil unrest occurrences using the following options: * **All the time (At least once a month):** Frequent civil unrest. * **Often (At least once a year):** Civil unrest occurs occasionally but is a notable concern. * **Rarely (Once in 2–3 years):** Rare civil unrest. * **Never:** No recorded instances of civil unrest. 2. **How often do the security forces patrol the village?**\ Measures the frequency of security patrols to ensure safety, with the following options: * **Every day:** Daily security patrols. * **Often (At least once a week):** Regular but less frequent patrols. * **Rarely (Once in a month):** Infrequent security patrols. * **Never:** No security patrols.

* **Village Accessibility**: Allows entering accessibility details for the village. * **Master Details :** * [Click here](https://github.com/egovernments/egov-mdms-data/tree/UNIFIED-DEV/data/mz/health/hcm-microplanning) to fetch MDMS data. * **Village Road Condition:**\ Captures the type of road infrastructure present in the village. The options include: * **Concrete:** Indicates the presence of a well-paved concrete road. * **Gravel:** Represents roads made of gravel. * **Dirt:** Denotes unpaved roads made of dirt or soil. * **No Road:** Indicates the absence of any road infrastructure. * **Village Terrain:**\ Specifies the geographical terrain of the village. The available options are: * **Mountain:** Villages located in mountainous areas. * **Forest:** Villages surrounded by dense forest areas. * **Plain:** Villages situated in flat, open landscapes. * **Desert:** Villages located in arid, desert regions.

*** #### **4. Population Data** The data displayed here can be reviewed, modified, and validated by the appropriate users, depending on their role. **Data Table:** | Village Name | Uploaded Total Population | Uploaded Target Population | Confirmed Total Population | Confirmed Target Population | | ------------ | ---------------------------- | ----------------------------- | ---------------------------- | ----------------------------- | | Gblebo Town | (Total population submitted) | (Target population submitted) | (Total population validated) | (Target population validated) | > Note : The data inside table will change based on selected campaign. *** ## **Steps** **Actions:** * **Edit Population Data:** If needed, the confirmed population data can be modified. * **Cancel:** Discards any changes made to the population data. * **Submit and Validate:** * If the **Root Population Data Approver (RPDA)** is logged in, they can **directly validate** the data. * If the **Population Data Approver (PDA)** is logged in, the data will move to the "Pending for Approval" status and will need further validation by higher-level approvers.

*** *** **5. Comment Logs** * **View Comment Logs**: This feature displays the history of changes and comments made about the village's population data, enabling transparency and tracking.

## API Endpoints

Endpoint	Purpose	Role
/census-service/_update	To Update the census data	POPULATION_DATA_APPROVER ROOT_POPULATION_DATA_APPROVER ROOT_FACILITY_CATCHMENT_MAPPER FACILITY_CATCHMENT_MAPPER
/egov-workflow-v2/egov-wf/process/_search	Search process history for this plan	ROOT_POPULATION_DATA_APPROVER, POPULATION_DATA_APPROVER, ROOT_PLAN_ESTIMATION_APPROVER, PLAN_ESTIMATION_APPROVER, ROOT_FACILITY_CATCHMENT_MAPPER, FACILITY_CATCHMENT_MAPPER, MICROPLAN_VIEWER

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.digit.org/health/v2.0/deploy/configuration/microplan-service-configuration/microplan-web-service-configuration/supervisor-workflows/village-details.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.