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
  • Logic model for Mozambique LLIN 2022-2023 CCU (from M&E plan, Aug 2022):
  • M&E products for LLIN distribution during Groups 4 and 5:

Was this helpful?

Export as PDF
  1. Programme

Monitoring and Evaluation (M&E) Tools

PreviousUAT Feedform Form: ProcessNextImplementation Checklist

Last updated 1 year ago

Was this helpful?

The monitoring and evaluation (M&E) for Mozambique is currently being conducted by CHAI. The focus of the M&E is to evaluate between DHIS2 and DIGIT.

To contextualise the indicators and data collected during all M&E facets of the Mozambique LLIN strategy, a logic model for the CCU was developed, and is shown below:

Logic model for Mozambique LLIN 2022-2023 CCU (from M&E plan, Aug 2022):

The model was developed to be applicable to the tool comparison portion of M&E, though its specific deliverables will differ from those produced until now.

M&E products for LLIN distribution during Groups 4 and 5:

A minimum of three products are expected following distribution in Group 4 and in Group 5:

  1. A report on the training of trainers for Group 4 which includes considerations on a range of planning processes (micro-planning, changes to platform, training results, recommendations):

- More qualitative in character, the report focuses on output 1.2 of the logic model above.

  1. A standard province group M&E report, as done for previous distributions in the 22-23 cycle, summarising campaign results (typically at the district, block, and province levels):

- This report communicates results on approximately 30 indicators split across different categories, as shown in the figure below:

The focus of these indicators leans more towards Output 1.4, Outcome 2.1, Outcome 2.2 and Impact 3.1 shown in the logic model above.

  1. A tool comparison M&E report specifically assessing the performance of the DHIS2 and DIGIT tools during the CCU.

- The deployment of different tools provides an opportunity to examine how each tool works and how each is received by stakeholders of the CCU. The current file aims to introduce the methodology to be followed in the tool comparison report, as the original M&E plan outlined its necessity, but did not discuss it in substance. In particular, this analysis means the deployment of further indicators split across two broad categories:

a. System indicators will deal with the technical aspects of the tools - how well they function and if they meet the data solution requirements. These will link to Output 1.1 of the logic model.

b. Users and usability indicators will collect information on how users engage with each tool, as well as the feedback on how satisfied they felt. These will link, mainly, to Outputs 1.2 and 1.3 of the logic model.

Despite the tools themselves being outputs for the Mozambique LLIN M&E strategy, it will be important to showcase rthe esults of their use on the outcomes and impact of the campaign. As such, some key indicators from the provincial report will also be included in the tool comparison report. These will be summarised at the DHIS2 provinces versus DIGIT province level, or will compare Manica versus Sofala versus Tete results as appropriate for each indicator. Hence, the tool comparison M&E report will be built as follows: