Consultant, Digital Health (Achieve Project)

This role was posted on August 6, 2026. Please note that we will review applications on a rolling basis.

The Role

At Last Mile Health, we make bold commitments that inspire innovation. Do you have experience designing digital health solutions, strengthening health information systems, and working with government partners to improve interoperability? If so, you may be the next Digital Health Consultant in Malawi with the Achieve Project.

The Digital Health Consultant will lead the development of a technical architecture and costed roadmap for the integration of MaHIS and iCHIS. Working closely with government stakeholders and technical partners, the consultant will define the technical, operational, and financial requirements needed to strengthen interoperability and support improved maternal and newborn health outcomes.

The consultant will design a practical, phased roadmap that enables secure and reliable data exchange between the two systems, reduces duplicate data entry, improves data quality and use, aligns with national digital health architecture and governance standards, and provides a clear investment case for government and development partners.

This position is based in Lilongwe, Malawi, and is open to Malawian nationals.

Project Background

The ACHIEVE grant is a US Department of State-funded initiative implemented by Pact and partners in Malawi to accelerate sustainable reductions in maternal, neonatal, and child mortality and morbidity by improving access to, quality of, and continuity of care across pregnancy, childbirth, postnatal, and early childhood health services. In Malawi, the grant will be implemented in Karonga, Balaka, Thyolo, and Zomba districts, with Last Mile Health supporting the design and implementation of Integrated Community Health Information System (iCHIS)-driven interventions in Balaka district.

Within ACHIEVE, the planned work contributes to Objective 3, which focuses on strengthening the health system through improved emergency referral systems, commodity management and supply chain function, enhanced use of data systems for decision-making, and improved preparedness for public health emergencies. To support this broader goal, Last Mile Health will lead two strategic objectives,  which is: 

Strategic Objective 1: Enhance iCHIS functionality and develop an architectural and costed roadmap for Malawian Health Information System (MaHIS) and  iCHIS integration for improved Maternal and Newborn Health (MNH) outcomes

Strategic Objective 2:  Build capacity of community health workers (CHWs) in Balaka on iCHIS and Community-based Mother, Neonatal Care (CBMNC) to facilitate focused community based maternal and child health service delivery. 

Consultancy Details

  • Estimated start date: mid-August 2026
  • Estimated end date: September 30, 2026
  • Estimated Fees Amount: $3,000- $4,000 USD per month.
  • Location: Lilongwe, Malawi
  • Reporting to: The Consultant will report directly to the Digital Health Specialist at Last Mile Health while maintaining close technical coordination with the Head of the Systems Architecture and Security Unit in the Digital Health Division in the Ministry of Health and sanitation.
  • Work modalities: The Consultant will be based in Lilongwe and stationed within the Ministry of Health and Sanitation's Digital Health Division under the Quality Management Directorate and the Community Health Services Section. The consultant will work hand in hand with Ministry of Health and Sanitation officers in the Digital Health Division and relevant stakeholders in the digital health space

Scope of Work/ Key Deliverables

Deliverable 1: Inception Report

Confirm understanding of the assignment, timeline, and stakeholder engagement plan.

  • Define the integration scope, including:
    • Systems to be integrated (name, version, hosting environment, current users).
    • Data domains to be exchanged (e.g., CHW registrations, service delivery data, stock data, indicators).
    • Direction of data flow (unidirectional vs bidirectional).
    • Priority use cases (e.g., “automatic submission of CHW monthly summaries into the national HMIS”).
  • Define the scope of integration for the MaHIS and iCHIS 
  • Provide a high-level workplan (Gantt-style) for producing the costed roadmap.
  • Provide a high-level description of the approach to undertake the upcoming deliverables.

Deliverable 2: Technical Architecture & Requirements Document

This document should clearly describe what it will take, technically, to integrate the two systems.

2.1. Current State Assessment

  • Brief description of each system:
    • Architecture (cloud/on-premise, vendor, database type).
    • Existing APIs, export/import mechanisms, or integration points.
    • User base and deployment scale (number of facilities, districts, CHWs).
  • Data landscape:
    • Key data elements and indicators to be shared.
    • Current data flows and manual processes.
    • Known data quality or duplication issues.

2.2. Integration Architecture Design

  • Proposed integration pattern, e.g.:
    • Point-to-point API integration.
    • Interface engine / middleware (e.g., OpenHIM, Mirth Connect, custom API layer).
    • File-based exchange (CSV, XML, JSON) if APIs are not feasible initially.
  • Data standards and interoperability:
    • Recommended data standards (e.g., HL7 FHIR, DHIS2 data model, OpenHIE profiles).
    • Mapping approach between data models in System A and System B.
  • Security and privacy:
    • Authentication and authorization mechanisms (tokens, OAuth, API keys, role-based access).
    • Encryption requirements (in transit and at rest).
    • Compliance with national data protection policies and any donor requirements.

2.3. Functional & Non-Functional Requirements

  • Functional requirements:
    • Specific data sets and events to be exchanged.
    • Frequency of exchange (real-time, daily, weekly, monthly).
    • Error handling and reconciliation processes.
  • Non-functional requirements:
    • Performance (expected transaction volumes, latency).
    • Availability and uptime expectations.
    • Logging, monitoring, and audit trails.
    • Scalability (e.g., ability to add more facilities or new data modules).

2.4. Infrastructure & Hosting Requirements

  • Servers, hosting environment, and connectivity needs.
  • Any additional infrastructure needed for integration (e.g., interface engine server, API gateway, database).
  • Internet connectivity requirements at facility/district levels, if relevant.
  • Backup, disaster recovery, and business continuity considerations.

Deliverable 3: Costed Implementation Roadmap

This is the core product. It must present a clear, phased plan with costs, suitable for inclusion in donor proposals and internal budgeting.

3.1. Phased Implementation Plan

Structure the roadmap in logical phases, for example:

  • Phase 0 – Preparation & Governance (1–2 months)
    • Stakeholder alignment, technical working group establishment.
    • Finalization of data sharing agreements and governance frameworks.
  • Phase 1 – Design & Prototyping (2–3 months)
    • Detailed data mapping.
    • Development of pilot integration (limited sites or data sets).
    • Initial testing and validation.
  • Phase 2 – Pilot Rollout (3–6 months)
    • Deployment in selected districts/facilities.
    • Training of key users and technical staff.
    • Monitoring, troubleshooting, and refinement.
  • Phase 3 – Scale-Up & Institutionalization (6–18 months)
    • National or multi-region rollout.
    • Integration into routine operations, SOPs, and job aids.
    • Handover to the government or host institution for long-term management.

For each phase, include:

  • Key activities.
  • Responsible actors (MoH units, implementing partners, vendors).
  • Estimated duration.
  • Key milestones and decision points.

3.2. Detailed Costing

Provide a line-item budget aligned to the four pillars commonly used in digital health integration: People, Platforms, Process, and Time to Value. Structure costs by phase and by cost category.

a) People Costs

  • Technical staff:
    • Integration architect / lead developer (level of effort in person-months).
    • Backend/front-end developers.
    • Data engineer / ETL specialist.
  • Health informatics & data specialists:
    • Data mapping specialists.
    • Data quality and validation officers.
  • Project management:
    • Project manager / coordinator.
    • M&E specialist for tracking integration performance.
  • Training & change management:
    • Trainers, facilitators, and development of training materials.
  • Governance & coordination:
    • Technical working group meetings, stakeholder workshops.

Indicate:

  • Estimated person-months per role.
  • Unit costs (based on local or regional rates).
  • Total cost per phase.

b) Platform & Infrastructure Costs

  • Software:
    • Interface engine or middleware licenses (if applicable).
    • API management tools.
    • Additional modules or customizations for System A and/or System B.
  • Hosting & infrastructure:
    • Servers (physical or cloud), storage, and networking.
    • SSL certificates, security tools, monitoring solutions.
  • Security & compliance:
    • Identity and access management solutions.
    • Audit and logging tools.
  • Maintenance & support:
    • Annual maintenance contracts, support retainers, and contingency for upgrades.

c) Process Costs

  • Data mapping and terminology harmonization exercises.
  • Testing environments and devices for QA.
  • Data privacy and legal reviews (e.g., data sharing agreements).
  • Documentation:
    • Technical design documents, API specs, SOPs, user manuals.
  • Change management:
    • Communication materials, stakeholder engagement sessions, helpdesk setup.

d) Time to Value / Opportunity Costs (qualitative)

  • While not always monetized in donor budgets, include a brief narrative on:
    • Expected efficiencies (e.g., reduced duplication, faster reporting).
    • Risks and costs of delay if integration is not implemented.

Deliverable 4: Risk Analysis & Mitigation Plan

  • Technical risks (e.g., system downtime, API changes, data loss).
  • Operational risks (e.g., low user adoption, high staff turnover).
  • Financial risks (e.g., currency fluctuation, delayed disbursements).
  • Governance risks (e.g., unclear data ownership, policy changes).

Deliverable 5: Final Roadmap Package & Presentation

A consolidated, donor-ready package including:

  • Executive summary (2–3 pages) highlighting:
    • Rationale for integration.
    • High-level architecture.
    • Phased plan and total estimated cost.
    • Expected benefits and sustainability approach.
  • Full technical requirements document.
  • Detailed costed roadmap (with tables and narrative).
  • Risk and mitigation plan.
  • Annexes:
    • Data dictionary / key data element mapping (high level).
    • Draft data sharing agreement outline.
    • Implementation timeline (Gantt chart).

The consultant should also deliver a presentation (PowerPoint) to walk through the roadmap with your team and key stakeholders.

What You’ll Bring:

  • Bachelor’s degree in a relevant field, health informatics, computer science, public health, or related field.
  • Progressive experience designing and cost planning for digital health system integrations, preferably in LMIC settings.
  • Demonstrated experience with National health information systems (e.g., DHIS2, OpenMRS, CommCare, ODK, iCHIS, or similar).
  • Demonstrated experience with Data governance, data sharing agreements, and privacy/security requirements.
  • Strong skills in costing and budgeting for digital health projects, including experience preparing documents for donors (e.g., Gavi, Global Fund, USAID, World Bank).
  • Demonstrated experience engaging and working with government stakeholders (Ministry of Health departments), Digital health governance structures and development partners. Particularly to facilitate digital health planning, multistakeholder consultations and  build consensus 
  • Excellent written and verbal communication skills in English; ability to translate technical concepts for non-technical audiences.
  • Years of experience with Interoperability standards (HL7, FHIR, OpenHIE, API design).

You’ll impress us if:

  • Experience supporting national digital health strategies, enterprise architecture, or interoperability initiatives.
  • Experience working with maternal, newborn, and child health or community health programs.
  • Familiarity with Malawi's digital health ecosystem and Ministry of Health digital health priorities.

About Last Mile Health

Last Mile Health (LMH) saves lives in the world's most remote communities by partnering with governments to bring critical primary care services to the doorsteps of people living in the last mile. LMH is a registered 501(c)3 non-profit organization and currently works in Ethiopia, Ghana, Liberia, Malawi, Uganda, and Sierra Leone with US offices in Boston. For more information, visit www.lastmilehealth.org. We are an equal-opportunity employer and value diversity at LMH. We do not discriminate on the basis of race, religion, colour, national origin, gender, sexual orientation, age, marital status, veteran status, or disability status.

At Impactpool we do our best to provide you the most accurate info, but closing dates may be wrong on our site. Please check on the recruiting organization's page for the exact info. Candidates are responsible for complying with deadlines and are encouraged to submit applications well ahead.
Before applying, please make sure that you have read the requirements for the position and that you qualify. Applications from non-qualifying applicants will most likely be discarded by the recruiting manager.