 I was so typed in the chat so I can stop sharing and then I can continue with the day which is analytics tools, considerations. So before you use analytics tools, before you implement them, they have to be a number of considerations that you have to look at. So basically you have to look at what data you want to present as we said earlier, how you want it to be presented, how you present your data already. For example, we have the paper based scorecards. So when we looked at those scorecards, there were also analytics tools that we wanted to be in DHIS and then eventually the scorecard was developed incorporated in DHIS. So basically the number of considerations that you look at when you are implementing analytics tools. So implementing analytics tools is greatly affected by local requirements. What is the local program looking for? What are programs looking for? What is the context? There are standard reports that people are already using. There are reports that people are using to review in a very specific format. So you look at those components and then it determines the type of analytics tools that you are going to prevent. So basically completely custom outputs that are specified to the context of program reports that individuals are used to reviewing in a very specific format. Maybe a report comes in in maybe a report comes in itself. So you might want to use, maybe DHIS might want to use the people table to also have the report in a similar format to use. There are good requirements for data description and interpretations. So if you look at that, you would figure out that the custom app development or report development may be needed to meet those local needs. For example, I talked about the SCOCA. So after the SCOCA was developed, you would see that in DHIS there was a custom SCOCA application that was developed to meet those local needs. You also look at training on using the apps to generate the outputs along with the printing and using these outputs often needs to be conducted. You have to conduct trainings for someone to be able to use the bottleneck analysis to use the WHO data quality tool, to use the SCOCA. There is need for that person to go through different trainings to be able to implement that and to be able to use it and make sense out of that data. So training is also one major component when implementing analytics tools. So also being able to convert a catcher of regular data use can also be particular difficult if not already embedded into the system. So if you have people that have data but don't use it, despite the analytical tools that you implement, they want to be able to use it. So it's a responsibility of us like DHIS2 experts to be able to instill that catcher in the people that are using that data to be able to use the data to be able to take some analysis and use that analysis for decision making and to be able to implement what the data is saying. That's why in the previous session we were going through that related actions component whereby we are defining what needs to be done after this happens and all that. So we are trying to categorize that catcher of people being able to use the different results that come from the analysis that we met. So before implementing this, these analytical tools, one has to start by applying the different outputs that are currently generated and reviewed either outside or within DHIS2. So you look at what you want to put out there and then you look at what is what DHIS2 is capable of doing or what you actually do on a paper basis. The same example of a SCOCAD is a good example and the scenario is the same. There was a SCOCAD paper base and then we were using that and then eventually we incorporated it into DHIS2 to have the person to mimic and develop in DHIS2. So you determine which of these can be implemented in DHIS2 and the demand which of these can be enhanced by using the features in DHIS2. So there are already other features. We have itself can do a lot of things but we also have the people type of the DHIS2. We can also do a lot of things. We can drill down to facilities, we can drill down to, we can drill the periods down to way before I know that. So you look at how some of these outputs that we're looking for can be enhanced by using some of the tools that are later than DHIS2 or you can look at these tools and say this tool is not in DHIS2 but we can seek for guidance on how this can be incorporated in DHIS2 developed and then be commissioned for use. You also assess if any of the output may require custom solutions to achieve that. So there are also other solutions like the WHO data community application. There was a concept to say we want to achieve this and then this was then embedded into the system by developing the WHO data quality issue. So you provide a demo using the in-country data if possible to generate more detailed discussions. So you can, if you want to implement these analytical tools, you can see it as a team as a DHIS2 data quality monitoring and evaluation teams, project management teams to come together and then you can do a demo to them and say there is this tool that we can be using or there is this tool that we are using in proper ways and then we want to push it into DHIS2 or we want to be able for an application to be developed in DHIS2 to do so, so, so, so. So you can provide that demo, you can demonstrate to them how it's done and then you can have a comprehensive discussion, a conservative discussion with them to determine which of the tools can be implemented in DHIS2 or which ones are already in DHIS2 and they can enhance how analysis is done and then you can constitute that as a consortium and then implemented in DHIS. So this process should always involve the subject matter, program experts and as well as DHIS2 experts that understand its analytical capabilities. So there are people out there that are not DHIS2 experts, but they've been using this platform for quite a long time and they understand how those analytical tools work and all that. So it's really relevant to have these people together have a discussion, have a comprehensive collaborative discussion to say we want to use this, we want to see how this can enhance our analytical analysis of the data that we have, how best can we do it. Because most of the time we find that most of the DHIS2 experts maybe they're already involved in the subject matter, the people that are going to be using the analytical tools and then you'll find that this hasn't been accepted by the ministries and that it's a no-go type of situation whereby they're saying you cannot implement it because you didn't involve this department. If it's IHT involved in that and productive health department, you can consult them and be with them and then plan together to implement this. So the process should lead to a lot in which you are trying how various outputs will be implemented in DHIS2. So you can come up with a web panel, I have to say from this period after this period we are going to do so, so, so, and then you can set milestones so that you can be starting your progress. You can say from this one because there are already discussions and then we'll come up with the needs and then you do this, this and then you you do a taking a whole approach where you see which ones would work, which ones would not work and then you come up with a report and then you determine how best you can implement that. So the Lord Mabu helped you to track the progress of that particular discussion that you had earlier with the experts in the subject matter and the program experts to say we want to use this particular tool to track this progress. How best can we do it? So you also developed that Lord Mabu to do that. In case of an existing DHIS system, it may be good time to review existing outputs and see how they can be updated to reflect on your features in the latest versions of DHIS2. So you also see that as DHIS2 experts, you look at the need, you look at the solutions that are available, then you look at which solution can best address this and how best can this fit in an updated version of a particular Amelie to go to. You can also consider developing new outputs. For example, the scope that I've been talking about, that may not have been considered previously. You can look at the bottleneck analysis. A bottleneck analysis is a good tool for tracking good cause of a lot of issues in the DHIS2. So you can also be thinking in various like developing new outputs and embedding them into the system. You can also make sure to test these features in a self-environment before deciding to implement them. So this is for data protection or in case the system may crash. So you need to have a test environment whereby you test these new tools, you test the new developments, and if they work on the test environments, you can also put them on another environment. Development environment, test environment, and then you can push them into the production instance when you are comfortable to say the tools are working and they're not causing any problems to the main database. Because you may end up having a scenario where you use the data for the whole nation of database if you just go straight into the main instance and then test some of the tools. So this is a simulation of how you can do that. So if it's an aggregate system, you need to have a system for production, you need to have a system for development. So on the development system, that's where you do testing, you try out new things, and then if they work that you can push them into the main production system that you have. The very same with tracker and aggregate data, you can also test the tracker you're developing. If you see that it's working properly, you can push it into the main instance. So having this whole process done, there are also other key components that are supposed to be looked at, like capacity gaps. Do you have the technical skills? Do you have the technical capital to develop these and implement them? So configuring an implementation of an aggregate tools, they require different skill sets. You need to have people that are able to configure these platforms on an existing system without causing any problems. So understanding of all these different analytical capabilities that are within DHS2 is also a key. The configuration required to support the creation of these outputs. Do you have programmers? If you want to, are they taking it out of sound to be able to use these? So you don't have the capabilities that are already in DHS and you capitalize on those and use them and maybe enhance them or you think about totally new solutions that can be incorporated there. So if you have the technical skills, you have the people that can support that, you have the people that can view capacity in other people, then you are ready to go to implement these different aggregate tools. So you have to have a Ditto input from subject matter, what they want, how they want it to be presented and how it will be supported. So the implementation and configuration staff will need to understand this information in some Ditto in order to implement the solutions in DHS2. So you also need to have support maintenance of the infrastructure as discussed previously to say you have this setup, but do you have the technical skills to support this, to sustain it? Because some they will bring projects, they say, I think you want something in DHS2, they want to incorporate what they want in DHS2, but it has a limited time to say a project of three years, but DHS2 will stay there forever. Do you have the technical skills that the financial support to sustain this implementation after the project is over? So you also need to look at those areas to see if you are ready to do this can be successfully implemented. Trending staff can also be challenging as we are in outputs. So understanding how to interpret these outputs and reviewing these outputs collectively may not always be possible at all levels. So maybe you want to do analysis at grass root level, at facility level, maybe you want to do analysis at DHO level and at national level. The skill sets and the understanding may be different depending on the people that you're involved in your implementation. So having to understand who is going to use these analytical tools, what are the skill sets, how best do they use DHS2 is also an important aspect because it will help you to understand the training needs. What areas do you need to train these people in and who will be doing the training of these people? So it's important to also understand the training concept of these analytical tools implementation. So to address the wide variety of inputs that are required, we recommend that development of DHS2 core team within the category. As a category in Malawi, we also have the core team that involves everyone else that is working on DHS2 technical. So we have the technical team, so we have people that are doing systems administration, we have people that are doing capacity building, we have people that are doing development, people that are sorry doing implementation of trucker, people that are doing implementation of aggregate. So it's really important to have the DHS2 core team in your country to say we have a team of 20 people. All of these 20 people may be distributed in different things. Some are good at capacity building, some are good at resource mobilization, some are good at concept development, some are good at programming, some are good at systems administration. So it's really important to have a core team that has that technical and administrative knowledge in DHS2 so that you can easily increment this. So when you develop a new output, develop a new tool for analysis, you can see it as a core team and discuss how best it can be implemented. And also this helps when you want to do updates to say there is a new version of DHS2 out there, how best can we do the upgrade, how best can we do an enhancement of this particular application, how best can we do this because you have the technical knowledge in-house. So basically this core team should be involved in training activities together in order to foster teamwork and exchange ideas. In addition, they should get used to solving problems with each other, with each other's input together based on their own expertise. So you can bring a team of programmers to say we have five programmers in the team so they can come and do some analytical thinking and critical thinking on the issues that you're facing and also determine the best solutions to those particular problems. They will also gain further appreciation for each other as well in the system as they are working together as a team. So you have a developer, you have a system that means and you have an implementer. So if all of these people come together and they work together, they will understand the development concept, the system administration concept, and the implementation concept. And in the end, you'll have different tools coming out to have an instance that is always up and running. And then you won't have the system downtowns because all of these people are working together implementing these particular systems. So in some cases, it may be difficult to address all the gaps in DHIS. So we're all trained IT staff who can make, you know, DHS2 system may not be available, implementation, configuration, development, and all of that, they may not be available. You may have a developer, but you don't have a system that means. So some of these issues can be addressed by collaborating with other people that are in the same sector. You have the minister of health, you have IT professionals that are more interested, maybe systems administration, you can incorporate those and work with those and get some knowledge from them about systems administration and be able to implement this. And then also you can also try to build, if you see someone with potential in systems administration, you can also try to build their capacity in systems administration and also maybe taking some DHS2 technical courses may also help to address some of these issues. So you can have an account everywhere you are, your trainings in systems administration. So if you attend those academies, you may build your capacities in system administration and then be able to do administration and server management. So in these cases, it may be best to identify which gaps that need strengthening and work on a plan or action to address them. So the actions are those that I'm saying, attending academies, being able to incorporate the minister of health, IT department, and identifying people that are good at systems administration and work with them and get some knowledge from them, or being able to build capacity in other people that have potential, but maybe they're working in capacity building. So you can build some systems and structure capacity in them and be able to work on DHS2. So custom tools, so if we have assessed that some of your outputs will not be possible using DHS2, you may go for the custom tools. So for example, in Malawi, we had issues in reporting a learning match. So I think we had a GIZ funded project that we worked on on a standard reporting form, which is in DHIS now. So we have a standard reporting form. We have a standard reporting form where we work on that. And also some of the analytical tools that we use, we also use some external analytical tools. If DHS2 is not doing what we want, we also use Tableau. So there is a family planning dashboard that was developed, a comprehensive one. We developed one in DHIS, but we also needed some people to have access to those platforms whilst offline. So we incorporated the Tableau public platform where we configure the family planning, but it's also pulling data from the DHIS. So you can also look at those platforms. You can use Power BI for visualizations. You can use Tableau. You can use Google charts. You can use a number of visualizations tools and that connect with DHIS2 using the connectors. And then you can pull data from DHIS2 and you can analyze this data and present this data in visualizations in other platforms. So there's custom tools that are available, the graphs and different graphs in different things. The maps, they can come from different applications that are out there alone. So you can do a research as a DHS2 content to say we want this to be done this way, but DHS2 currently is not doing it. Maybe the near future DHS2 will do it. So you can use that opportunity to do a research on different visualization tools and be able to analyze this data and put out the color and informative analysis and visualizations out there to the people using other platforms. As of now, DHS2 requires you to have some login credentials so that you can do some of the data, but you can use connectors to push this data outside of DHIS and have it on Tableau and then you can present it on a different type of platform without people needing to log into the platform. So basically that's what I had for this session where we're looking at implementation constellations of analytical tools. If there are questions, I think you can put them in the chat and then we can Yeah, we can address them. There is a question from Kevin.