Benefits of Global Goods
Since global goods are open source tools, there are multiple benefits to their use:
- Many developers can contribute to a global good, thereby reducing the risk of vendor lock-in: a situation in which customers are unable to switch providers/developers without a substantial cost.
- Source code is freely available and modifiable, creating more opportunities for collaboration across organizations and health programs areas.
- The cost of new feature development and software maintenance is more likely to be shared across users and supporters of global goods, freeing up resources for adaptation and implementation.
- Software development best practices in requirements gathering and user acceptance testing have already been undertaken, so resources can be focused elsewhere.
- Interoperability leads to improved data analysis and synthesis, enhanced support for continuity of care as clients engage at multiple points of service across the health care system, and reduced costs for data acquisition and management.
- Many of the global goods represented in this guidebook already support interoperability standards, in particular the standards identified in the OpenHIE architecture.
Historically, Digital Square has run specific Notices to identify global goods, the most recent being Notice G0 for software global goods in 2022 and G1 for content global goods in 2023. Since the beginning of 2024, applicants interested in submitting their digital health tool for consideration as a global good are able to do so at any time using our application portal, and applications are reviewed on a quarterly basis.
To be considered a global good, the digital health tool must meet certain minimum requirements:
- Published under an open license such as OSI-Approved licenses or Creative Commons licenses
- Supported by a strong community with a clear governance structure.
- Funded by multiple sources.
- Deployed at significant scale.
- Used across multiple countries and with demonstrated effectiveness.
- Software that is designed to be interoperable.
Applicants must fill out the relevant application form and complete a self-assessment using the Digital Square Maturity Model. If you have any questions, you reach out to the Digital Square team at [email protected]. The Peer Review Committee (PRC) reviews all applications and make recommendations. The Global Goods Review Board (GGRB) meets quarterly to consider the PRC’s recommendations and decide whether to accept, reject, or request additional information. All applicants will be notified of the GGRB’s decisions. Successful applicants will be added to the Global Goods Interactive Guidebook and will be publicized through our communication channels.
Global Goods Product Suites
Digital Square defines product suites as a configuration of open-source technologies and tools that are aligned to meet a functional health domain (such as telemedicine services, primary care,
immunization, antenatal care, neonatal care, etc.) and support standards-based data exchange. A product suite packages digital tools together and exchanges data through appropriate data exchange patterns to achieve a desired set of functionality and outcomes. Product suites may leverage international guidance documents, such as the WHO Digital Adaptation Kits (DAKs), to frame the expected system-wide workflows, features and functional areas. Product suites must:
- Be comprised of Digital Square approved global goods and/or technologies that meet the definition of a global good. All software components must registered as a Digital Public Good
or and meet the DPG standard. All software components must be available under an OSI approved open-source license or use this opportunity to become open source.
- Meet well-defined and documented functional and non-functional requirements to ensure all major functional areas are catered for and core non-functional needs are considered.
- Support appropriate standards-based data exchange to achieve a fully interoperable solution. Data exchange should be enabled through adherence to globally recognized standards, and
with the Open Health Information Exchange (OpenHIE) specified workflows where relevant. Health Level Seven (HL7) Fast Healthcare Interoperability Resources (FHIR) is the preferred
open standard and work on product suites should reference and contribute to the development of the WHO L3 work where appropriate. For supply chain systems, the use of the GS1
standards are preferred.
- Be aligned with the WHO’s SMART Guidelines (Standards-based, Machine-readable, Adaptive, Requirements-based, and Testable). Ideally, the ultimate vision is that product suites
should utilize Level Two (L2) (operational) and Level Three (L3) (machine readable) components to produce Level Four (L4) (executable) reference software.our (L4) (executable)
reference software.
- Include comprehensive up to date user and technical documentation that is available under an appropriate Creative Commons license.
- Provide documented evidence of the quality assurance framework used and results of testing.