2.            Requirements for the IT solution

2.1       Description of the existing IT solution

I.        Software Stack

After a migration of the openIMIS codebase from proprietary technologies to a full open source technology stack, the following frameworks are now in use and recommended as reference technologies for running an openIMIS instance:

• Web-Frontend: React JS

• Backend: Python (Django)

• Data Access: GraphQL

• Database: PostgreSQL (recommended), but MS SQL is still supported

• Packaging: Docker

• Server: Linux (recommended), but any server OS supporting docker will work

II.        Previous Results of the openIMIS Initiative

The openIMIS Initiative together with other development partners has previously supported the maintenance and support of the openIMIS product. The results include among others:

• A harmonised version (main) was created from the country specific adaptations of the openIMIS software package and migrated to a modular architecture using open source technologies and implementing international interoperability standards. It is available in a public code repository and updated regularly with recent code contributions. (https://github.com/openimis )

• A regular release cycle according to a defined change management process was established and successfully applied since 2019.

• A technical roadmap was developed as a living and constantly updated technical document based on a series of workshops with different stakeholders and ongoing technical strategy discussions. (https://openimis.atlassian.net/wiki/spaces/OP/pages/40763442/Product+roadmap )

• Community platforms were set up as resource repositories and communication channels for the openIMIS community. A regularly maintained helpdesk was set up and established.

• A sandbox environment to demonstrate openIMIS features and its interoperability options was set up for testing and show-casing.

• In a series of migration projects, functionality of the CORE-MIS software package by the World Bank was migrated to openIMIS(https://openimis.atlassian.net/wiki/spaces/OP/pages/3531407380/) )

2.2       Description of the application/use of the IT solution

openIMIS is an interoperable, versatile open source software which supports the administration of health financing and social protection schemes. It is designed to manage the complex, high-volume data flows which are required to operate such schemes by seamlessly integrating beneficiary, provider and payer data. More than 23 million people in 12 countries benefit from health insurance, employment injury insurance, cash transfer and voucher schemes managed using openIMIS.

2.3       General conditions at the partner end

I.        General Conduct

The staff members seconded by the Contractor must cooperate closely with the GIZ project officer who is responsible to BMZ for the German and Swiss contributions to the openIMIS Initiative and the programme officer appointed for this contract. All activities of the Contractor have to be done in line with and on the basis of ongoing activities of the openIMIS Initiative to achieve all programme outputs (see chapter 1.IV above).

Ongoing activities that must be taken into account and built upon during this assignment are:

1. activities of the openIMIS Initiative geared towards community building and regional support structures. This activity is supplemented by additional contracts for regional openIMIS hubs.

2. activities of the openIMIS Initiative geared towards implementation support for new scheme operators.

3. software development as well as release and solution management by other contractors and implementation partners.

4. active involvement of the openIMIS Initiative in the interoperability networks OpenHIE, GovStack and the Digital Convergence Initiative in Social Protection.

5. Merger with the CORE-MIS software from the WorldBank

Developments that may lead to difficulties in a later project phase should be identified as quickly as possible. Furthermore, in view of the focus on the results described above, results monitoring is crucially important. An efficient monitoring and evaluation system must therefore be proposed and set up that allows all entities of the openIMIS governance structure, the Contractor and the GIZ Global Programme GASP to monitor project progress. Progress reports are submitted quarterly based on a format which will be agreed upon during the inception. Regular feedback sessions may be convened by the GIZ Global Programme GASP depending on the progress of the assigned tasks. The Contractor is expected to respond to changes flexibly, especially if the project is in danger of straying from outputs mentioned in Chapter 1.

II.        Integration into the Existing openIMIS Structures

The openIMIS initiative builds upon existing software for health insurance management that is being used by insurance organisations in several countries already. Although the migration of openIMIS to the new modular architecture is completed and the legacy version will not be included in future releases any more, continuous support for smooth operations of those legacy implementations is still important to this commission. Besides simply operating openIMIS, these local organisations also support the openIMIS Initiative with own code developments, which need to be integrated into the core system on a regular basis.

Within the openIMIS governance structure regular exchange meetings are foreseen for different stakeholders, some of which are also relevant for the Contractor. In the context of this commission, the Contractor is currently especially expected to take part in the weekly calls of the Developers Committee and the monthly review calls but might be invited for additional events – online or in person.

III.        Co-operation with Partners of the openIMIS Initiative

In order to build a sustainable community of practice, the openIMIS Initiative is co-operating with various international partners and sub-contracting other consultants. The Contractor is expected to work together with these partners in a co-operative and friendly way, respecting and supporting the work of others and disclosing relevant information where necessary. Apart from the consultants that work on the ongoing activities mentioned in chapter 2.I and those who work on short term consultancies, the openIMIS initiative currently co-operates closely with other players such as the OpenHIE community, the GovStack Initiative, the Digital Convergence Initiative and other Digital Public Good Initiatives from related sectors. Finally, it can be expected that free implementers and developers who are interested in the project want to associate and contribute to the project. The openIMIS Initiative has a special interest to nourish this kind of relations through a welcoming community culture of trust.

2.4       Functional Requirements

Since this tender is asking for generic software development capacity, the functional requirements will be defined in the Jira-tickets that will be given to the contractor by the Maintenance team.

2.5       Non-functional requirements

The following non-functional requirements must be taken into account by the contractor when implementing the service.

2.5.1 Interfaces

openIMIS provides external access to data and functionalities through standard APIs. The currently used standard is based on the specifications of the HL7 FHIR version 4. The APIs are documented in the openIMIS implementation guide: https://fhir.openimis.org/

Additional standards will be added according to demand. Currently the emerging standards of the Digital Convergence Initiative for Social Protection are under revision. The existing DCI definitions will need to be implemented as openIMIS APIs in the context of this tender to an extend that will be defined by the Product Group according to the overall context.

2.5.2    System requirements/technical framework

The openIMIS Initiative is committed to operate according to international development principles that are endorsed by the supporting GDC and SDC and correspond to the guiding principles of GIZ. The Contractor is especially expected to comply to

• the Principles for Digital Development (https://digitalprinciples.org/ )

• the Digital Investment Principles (https://digitalinvestmentprinciples.org/ )

As one direct consequence, the development of openIMIS is oriented at standards set by

• the Business Process Framework for National Health Insurance Information Systems elaborated through the Joint Learning Network (JLN)

• the World Bank Sourcebook on the Foundations of Social Protection Delivery Systems

• the security recommendations of the Open Web Application Security Project (OWASP)

• the digital health architecture of the Open Health Information Exchange (OpenHIE) community of practice.

• the interoperability specification for Fast Health Interoperability Resources (FHIR) by the Health Level Seven International (HL7) 

• the emerging standards GovStack and Digital Convergence Initiative for Social Protection

The Contractor is expected to align with the ambitions of the openIMIS Initiative to further harmonise openIMIS with those standards in terms of terminology, workflows and interoperability.

2.6       Use of open source software (OSS)

Being an Open Source project itself, the openIMIS initiative strongly supports the use of Open Source Software in the given context. The Contractor must be willing to use Open Source Software where possible and avail all software and non-software products in a timely manner to the openIMIS Initiative in source versions that can be further maintained with Open Source tools without loss of product quality.

2.7       Hosting

The openIMIS Initiative is hosting all community platforms and communications channels with an eye on sustainability. Code-repositories, documentation servers etc run on free web-platforms that are common in open source development to allow continuity beyond funded project phases. Only the demo servers of the openIMIS sandbox environment are hosted on a commercial server.

The existing repositories, communication channels and community platforms that were established by the openIMIS Initiative shall be used. They were set up according to best practices in the community and are running at production scale. Specifically, these are

• openIMIS code repositories (https://github.com/openimis )

• openIMIS issue tracker (https://openimis.atlassian.net)

• openIMIS documentation server (https://openimis.readthedocs.io )

• openIMIS wiki (https://openimis.atlassian.net/wiki/spaces/OP )

• openIMIS translation platform (https://lokalize.com )

• openIMIS chat channel (https://discord.gg/khDgTDWUZV )

The contractor shall not provide hosting services.

2.8       Further specifications/general conditions

1.            Responsibilities of the contractor

The contractor must deliver the following services and work packages (along with the corresponding milestones). The work packages have no chronological order and can also be implemented on an integrated basis, depending on the development methodology:

1.1      Work package 1: Needs Analysis and Roadmap

1. Together with the openIMIS Product Group, identify and analyse high priority issues and feature requests from the openIMIS issue queue.

2. Analyse the affected system components of openIMIS and layout the needed fixes and code supplements.

3. Estimate the need workload to integrate the needed changes into the openIMIS code base.

4. In a collaborative process with all involved partners (compare chapter 3), set up a lean and agile strategy based on the analysis results from the previous points with a special focus on high volume demand during the bi-annual release cycles.

3.2       Work package 2: Implementation

1. Apply essential code-changes and extensions to the openIMIS software packages.

2. Closely co-operate with other software development projects managed by the openIMIS Initiative and initiate changes and feature requests that support a smooth integration of the needed changes into the main openIMIS branch.

3. Create the needed pull requests to integrate the chode changes into the main openIMIS branch.

4. Do extensive developer and integration tests of the code changes.

5. Provide a reasonable set of synthetic data that allows for meaningful user acceptance tests of the code changes. The generation of the synthetic data should be automated and scalable to higher data volumes for performance testing.

6. Document all changes in the appropriate platforms (including inline code documentation) and initiate secondary documentation changes (e.g. user manuals, translations).

3.3       Work package 3: Roll Out and Maintenance

1. Support community managers, trainers and higher support levels with technical expertise. This includes support during technical workshops, capacity development activities and product presentations.

2. Provide basic support to user organisations who want to backport similar changes into their systems.