Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Help countries achieve Health SDGs by building digital public goods that strengthen public health.
The DIGIT Health platform is being built as an open source Digital Public Good to expand capabilities in public health. It is being designed to work across countries at varying levels of capacity and complexity.
The focus is to help countries reduce “diseases of poverty.” The World Health Organisation (WHO) estimates that such diseases “account for 45% of the disease burden in the poorest countries” and stem from poor nutrition and sanitation, absence of health education, and indoor air pollution. We want to help countries reduce this by building digital tools on top of eGov’s open-source platform - the Digital Infrastructure for Governance, Impact & Transformation (DIGIT) - to enable and manage health campaigns, and disease surveillance.
As platform adoption increases over time, it will continue to generate more real-time and authoritative data in the public health space, besides ingesting data from other sources. The platform will become a “shared source of truth” that all stakeholders can use to align resources and decisions to achieve operational and financial efficiency. The platform will therefore progressively and greatly improve the ability of low-and-middle-income countries (LMICs) to better manage the delivery of public health priorities.
Public health challenges are massive and complex. While many countries have limited capacity and resources to address such issues, the current approach to these challenges tends to strictly focus on delivering one specific outcome, driven by specific nodal agencies. Each programme ends up replicating the same set of efforts and outputs. For example, health campaigns are typically categorised as per the diseases they aim to address - malaria, polio, etc. Each programme involves a similar set of activities: planning, delivery and logistics, human resource management, monitoring and reporting. They suffer from low effectiveness due to the siloed and uncoordinated way in which they are funded, planned, executed, and monitored.
Current digital efforts do not take a “whole of system view” and do not solve the cost of coordination and duplication issues. Each program also develops its own systems (MIS, apps, dashboards). Such siloed, solution-centric approaches and tools create a new set of problems and inefficiencies for countries:
Higher costs and time: This is incurred on creating or procuring and maintaining these systems, including the onboarding cost of the same actors in each program.
Data exists in multiple systems: They are not interoperable, leading to duplication, inconsistencies, poor adoption by on-ground workers, and sub-optimal decision-making.
Limited reusability and innovation: Data and capabilities are intertwined and ‘locked,’ making it extremely hard for the wider ecosystem to innovate and build upon.
Sub-scale: The tools are not able to scale for the national population and across programs.
The DIGIT health platform reimagines the public health space as a set of horizontal building blocks, such as shared registries, and services, accessible through well-defined open APIs, which can be leveraged by multiple countries and disease programs. It will eliminate the above inefficiencies. Further, it will facilitate the independent evolution of each building block and participation by the health ecosystem, leading to faster innovation.
The DIGIT Health Platform is being designed to enable delivery at scale, across various aspects of public health, and multiple country contexts. Using the platform approach, we will create an end-to-end flexible, open, configurable, and reusable platform to plan, manage and run any public health program such as health campaigns so there is detailed and timely monitoring and evaluation to review coverage, target achievement and identification of gaps for their distribution.
Re-usable: Shared data registries and infrastructure
Interoperable: Open API specifications
Secure and scalable
Multi-country support: Support for infrastructure isolation, as well as data isolation
Multi-lingual: Support for multiple languages
DIGIT Health platform will:
allow ecosystem actors to use, contribute and evolve the platform collaboratively and sustainably,
give the option to ecosystems to either host it on their own infrastructure or use it from a hosted environment (hosted by a trusted party) for which a sustainable costing and financial model will be evolved.
The common services and shared data registries can be reused to assemble products that provide a unified and consistent experience for each set of actors. The program-specific context such as roles, workflows, and notifications can be configured by the respective programs, enabling faster rollout and execution.
The APIs will allow data and functionality to be reused across multiple departments, effectively breaking silos across programs. Through APIs, meaningful data and services can also be made available to the various ecosystem stakeholders for innovation and interoperate with other systems like MOSIP, DHIS2, Sunbird RC, DIVOC, etc. that are focused on other parts of the public health delivery value chain, such as disease surveillance, supply chain, verifiable certificates, and health insurance.
The platform is designed to facilitate stakeholders with a digital system to manage and implement health campaign activities in Mozambique. Click to know more.
The articles in this section includes:
Click to learn more about the Master Data Management Service, and configure it.
The development is complete for all the features that are part of the release.
Yes
Kalyan
Code merged to master branch on May 12th.
Test cases are documented by the QA team, reviewed by product owners, and test results are updated in the test cases sheet.
Yes
Guruprasad
Mrunal
Signed-off by Roshan/ Mrunal.
The incremental demo of the features showcased during the sprint showcase and feedback is incorporated. If possible, list out the JIRA tickets for feedback.
Yes
PGR - April 26th. HRMS & Mobile Offline Reports - May 11th.
UI/UX audit review is completed along with feedback incorporation for any changes in UI/UX.
Yes
Sai Neelakantan Bhanu
Andrew
PGR, Dashboard HRMS - UX audit complete and high priority issues fixed.
Incremental demos to the product owners are completed as part of the sprint, and feedback is incorporated.
Yes
Guruprasad
Mrunal
PGR - April 26th. HRMS & Mobile Offline Reports - May 11th.
QA sign-off is completed by the QA team and communicated to product owners. All the tickets’ QA sign-off status is updated in JIRA.
Yes
Guruprasad
PGR - Provided on April 28th. Dashboard v1.1 - Provided on May 2nd. HRMS and Mobile Offline reports - Provided on May 10th.
UI, and API technical documents are updated for the release along with the configuration documents.
Yes
Kavi
Ghanshyam
UAT promotion and regression testing from the QA team is completed. QA team has shared the UAT regression test cases with the product owners.
Yes
Guruprasad
PGR - Provided on April 28th. Dashboard v1.1 - Provided on May 2nd. HRMS and Mobile Offline reports - Provided on May 10th.
API automation scripts are updated for new APIs or changes to any existing APIs for the release. API automation regression is completed on UAT; the automation test results are analysed and the necessary actions are taken to fix the failure cases. Publish the list of failure use cases with a reason for failure and the resolution taken to fix these failures for the release.
Yes
Done for FLW App.
The API backward compatibility testing is completed.
Not applicable
Reason: This is the first version of product.
The communication is shared with product owners for the completion of UAT promotion and regression by the QA team. The product owners have to give a product sign-off within one week of this communication.
Yes
Frontline Worker's App - On March 23rd.
Complaints - On April 28th. Dashboard v1.1 - On May 2nd. HRMS and Mobile Offline reports - On May 10th.
Kalyan
The UAT product sign-off communication is received from product owners along with the release notes and user guides (if applicable).
Yes
Frontline Worker's App - On March 23rd.
User Management - On April 28th. Dashboard - On May 2nd. HRMS and Mobile Offline reports - On May 10th.
Mrunal
Kalyan
The GIT tags and releases are created for the code changes for the release.
Yes
Roopesh/ Kavi
Need to be created for the flutter component.
Verify whether the release notes are updated.
Yes
Roopesh/ Kavi
Kalyan
Tech release notes are updated.
Verify whether all the UAT builds are updated along with the GIT tag details.
Yes
Roopesh/ Kavi
Verify whether all MDMS, configurations, infra-ops configurations are updated.
Yes
Roopesh/ Kavi
All configurations are part of the master promotion document.
Yes
Mihika
Signed-off.
Verify whether all test cases are up-to-date and updated along with the necessary permissions to view the test cases sheet. The test cases sheet is verified by the test lead.
Yes
Guruprasad
Signed-off.
Verify whether the UAT credentials' sheet is updated with the details of new users and roles, if any.
Yes
This should not go into Gitbook as this is internal to eGov
Guruprasad
Signed-off.
Verify whether all the localisation data was added in UAT, and updated in the release kits.
Yes
Roopesh
This should be part of the release kit. This will be shared internally with the team.
Verify whether the product release notes and user guides are updated and published.
Yes
Mrunal
Jojo
Signed-off.
The demo of the released features is done by the product team as part of a sprint/release showcase.
Yes
Mrunal
Done.
Technical and product workshops/demos are conducted by the engineering and product teams respectively to the implementation team (implementation handover).
Yes
Kalyan
Prasanna
Architect sign-off and technical quality report.
Yes
Roopesh
Signed-off.
Product roadmap and success metrics
Yes
Mrunal
Published.
Adoption metrics
Yes
Ankit
Pradipta
Ankit has shared the draft for this. However, final discussion is pending with NMCP.
Programme roll-out plan
Yes
Ankit
Pradipta
Implementation checklist
Yes
Aparna
Elzan
Implementation roll-out plan
Yes
Aparna
Elzan
Gate 2
Ankit
ExCos
Scheduled on June 9th.
The internal release communication along with all the release artefacts are shared by the engineering/product teams.
Mrunal
To be shared post Gate 2.
Plan for upgrading the staging/demo instance with the release product within 2-4 weeks based on a period where no demos are planned from staging for the previous version of the released product.
Not applicable currently.
The release communication to partners is shared by the GTM team, and a webinar is arranged by the GTM team after the release communication, within 2-4 weeks of the release.
Not applicable currently.
This is not the final release. Hence, external communication is not required.
Verify whether all docs will be published to by the Technical Writer as part of the release.