7 How to Set-up DHIS2 in a New Context?

More documents

Recommendations

Info

How to Set-up DHIS2 in a New Context?203ScalabilityThe Internet, cloud infrastructures and mobile networks have drastically improvedthe scalability of the DHIS2 platform; anyone with Internet can download DHIS2 andbuild their own specific applications, which can then be accessed by anyone amongtheir targeted users, as long as they have Internet access. Applying the principle ofcentral servers, innovations in the nodes, such as new modules and functionalities,are immediately spread to all users, and, providing that innovations be included inthe global core, all DHIS2 implementations globally.Agile and Rapid Development CyclesWe regard innovations as emanating from technological learning, which again, iscatalysed through the use of technologies, and learning from trying. Innovations, thatis, in our contexts, represent new ways of addressing old as well as new problemsand needs, and more concretely, new modules and functionalities developed withinthe DHIS2 platform. ‘Trial and error’ is the archetypical approach to innovations. Thisprinciple is well translated to ‘rapid prototyping’ in the DHIS context. In order to enableinnovations, what is normally regarded as product-cycles, need to be short in time, andthey need to be rapid. The DHIS platform is developed and evolved in this way.Support and Interfaces to other Groups and Third-party DevelopmentIdeally, local innovations in the country and other nodes should ‘flow-up’ directly andbe included in the DHIS2 core, and thus be made available to everyone. However,as discussed earlier, to include local innovations seamlessly requires organisation andmanagement at the levels of core developers and implementers, which is the keyorganisational challenge of building the DHIS innovation ecosystem. The next levelin developing DHIS as a real innovation engine is to make it possible and easy forthird-party development of modules that can be plugged into the DHIS. Typical usecases would be where DHIS is serving as a larger data repository and the third-partyinnovators are building modules that in various ways are enhancing the access, analysisand use of these data. The development of ‘apps’ and ‘plug-ins’ for Google, Firefox,Mobile telephones and so on, is the driving engine behind the Internet economy ofinnovation. In the case of more context sensitive application areas typically addressedby DHIS, however, these approaches of creating a ‘market’ where such applicationswould provide an economic opportunity, are of course less immediately obvious.However, the cloud infrastructure will for sure create more demands for health andother data from, for example, country data warehouses based on the DHIS2 platform,which may spur innovations by third-party developers. In order for DHIS2 to be ableto tap into this potential avenue of innovations, we will need to develop a genericand easy to use web-API, that is, a way to access the data in DHIS2 by an applicationthrough the web presentation layer.Implementing Good DesignInnovation EcosystemThe DHIS2 innovation ecosystem is the label we give the network of action surroundingthe development and implementation of the variety of instances of the DHIS2 aroundthe world and all the developers, groups, HISP nodes, Ministries of Health, Universities,NGOs, international agencies and so forth, involved in the network. We may distinguishsome key groups of actors in this set-up:
204Integrated Health Information Architecture: Power to the UsersThe core DHIS2 platform developers: The global team who are developing the softwareconstituting the platform in close interaction with the use context through the DHIS2implementers and designers. They are developing the innovations that are shaped astechnical artifacts.The DHIS2 implementers and designers: These are the facilitators and developers of theDHIS2 instances that are being implemented in countries. They are working in closecooperation with users, and they are mediating ideas and requirements for newfunctionalities and feedback on the software between the users and the developers.They are the innovation mediators between users and core developers. They are alsoinnovators in terms of developing new ways of applying and using information.Potential and actual users of the range of information and services: These provided bythe DHIS2 are many, and they are ranging from the individual users in the field to thehealth managers at district and higher levels, policy makers, international organisation,to the general public. This is the both the context and driver of innovations. Innovationsare generated in direct interaction with the DHIS2 platform, resulting in its furtherreconfiguration, extension and development. Key innovations are linked to new waysof doing things with the help of technology.Third party developers: These are targeting actual and potential users and use cases asa market for their particular innovations, which may take shape as new modules orplug-ins, but also as new configurations of the platform, without new add-ons.Educational schemes, training and universities: Make up the institutional glue, whichenables innovations to actually materialise through the cycles of use-ideas forimprovements-trial-workable module or work practice. While ‘learning through use’ asa first step in a process of innovation and ‘conceptualising new ways of doing things’as the second, the following steps of bringing ideas all the way to technologies andimplementations will require a range of skills where universities and wider trainingschemes are key components. Masters and PhD programmes and now also the DHIS2academy have been important building blocks in the innovative DHIS processes sincethe start in the 1990’s.Figure 7.13 provides an overview of the DHIS2 innovation ecosystem.A key challenge in the DHIS2 innovation ecosystem is to establish ways for localinnovations to be spread globally by being made part of the global core, or by beingcompatible with the generic interfaces to the DHIS2 core. In the previous chapter, wehave discussed the complicated process to organise distributed development anddeployment in such a way that all the country specific branches and versions of theDHIS2 are compatible with the ‘core’, that is using the generic interfaces. This is neededin order to ensure that local innovations are becoming part of the global core andthereby are shared by all nodes in the system. Innovations may become part of thecore through simple inclusion, in the cases where the module is developed as beingcompatible with both the global core code base (using standard interfaces) and theDHIS2 coding standards. If this is not the case, the essence of the local innovationwill be included through redevelopment, as was the case with the Indian Dashboard.Ideally, therefore, the more synchronised the local module development is with theglobal core development, the better, that is, the less resources it takes to make it partof the global core.
Page 6 and 7: How to Set-up DHIS2 in a New Contex
Page 28 and 29: I-V-X-II-III-IV-VI-VII-VIII-IX-XI-X

7 How to Set-up DHIS2 in a New Context?

Create successful ePaper yourself

Delete template?

Save as template?