 Hello, hello, one, two, one, two, yep, and now with, can you hear me there? Yes, I think I can decide. Okay, hello, hello. Hi everyone, can you hear me well there? Yes, yes, yes, okay, good. Are you coming or are you leaving? Okay, so good afternoon everyone and good morning, evening or afternoon to the people that are joining us online. We are going to talk today about the, in this session about the Android implementation stories. Okay, and just to remind you, this chart that was shared during the conference on Monday, the first day, this is the adoption of Android, right? This is the number of devices that are using Android during the last 30 days. Okay, so we have already almost 100,000. Okay, so it is a big success, I believe for the, for, for UIO and for the whole community, but we want to keep improving. So if we go to see this country by country, we can see that we have Nigeria, Mozambique, Togo, Lesotho Malawi, okay, and it's been used in most of the countries of Africa, in many countries of Southeast Asia. We are starting in Latin America as well. Of course, we as the Android team, we can like taking care of the roadmap, we can take care of the features that we are developing for the, for the, for the application, for the mobile application. But of course, the most important piece is always the implementations, the deployments and all that, right? So how the, the users are using the Android application, the implementers, how they are deploying, deploying the Android application in the field. So it's something that we really, really want to hear from you. And I hope with this session, the community will learn about the different, very interesting use cases, right? So we have four groups here, and we're going to start with Jerry from his West Central Africa, please Jerry, eight minutes. I think now I'm left with seven minutes and 30 seconds like this. Okay, okay, great. So I'm going to talk about the Togo experience. So here in the picture, you can see our Prime Minister getting the vaccine. So I mean, we have an article just down there talking about Togo initiating the vaccination campaign. Okay, so we're going to talk about the context, the deployment approach, the main successes, the challenge and the lesson learned. Okay, so yes, COVID appeared on the 17th of November 2019. And I mean, in Togo, we actually had our first cases in March 2020, on March April 2020. And we had like 37,000 cases up to now, with 273 deaths. Okay, so there was a need actually to make sure that we don't have a high peak of cases and deaths. So we actually wanted to start the immunization. So one thing you need to understand is that for COVID surveillance, they use another system to actually track the cases, but it actually failed. So for COVID vaccination, they wanted to use another system, but the minister was like, we've been using DHIS for a while, and it's been working. So why can't we use DHIS for vaccination? And then we actually were able to use DHIS for vaccination. And this was actually the process. Yeah. So this was a process. So you needed to be enrolled into a website or platform, whereby when you enroll, then you can go to a health facility, and then they'll look for your ID. I mean, you need to go with your ID, because an SMS will be sent to you. And then you'll be registered. I mean, not registered, but you, they will actually take information about the first dose, the second dose, and the third dose, et cetera, et cetera. So we had this kind of process whereby the data was actually sent via another platform to DHIS too. The health professionals were supposed to actually enter the data into DHIS too. And then this data was actually sent to analytics for processing. So yeah, what we were able to do was, first of all, to configure the package with the the Ministry of Health. And then we actually were able to train them on data entry. Okay, we trained the ones that are supposed to enter the data and data entry. There was a pilot face in the capital city to see how it will go. And it went well. So we finally wanted to roll it out. Of course, they had a lot of support. One, because we had a lot of DHIS users in the country that could actually support from the Ministry of Health, support from us. What we did was, of course, we actually downloaded the application on Play Store. And in some places, you had phones provided to them, but others actually used their own device. So it was a hybrid system. But what we also did was to have a WhatsApp group and a Telegram group in order to make sure that people were kind of assisted or supported when needed. So this is just like a screenshot of the data entry screen using Android. So the main success was, we were able to use that for Nationwide rollout. So people were enrolled and data was collected into the system. So it was a success story. We are using that currently to generate the vaccination certificate in Togo. And it's actually compliant with Euro, how do you call it? Euro standards. We also were able to use that for informed decisions. For example, when they hire lower rate of teachers being vaccinated, the Ministry of Education was able to act upon it and encourage the teachers to get more vaccines. It also triggered the use of DHS for COVID surveillance. And you probably realized that we are the third country that was downloading the application most. But it's actually because we are now using it for COVID surveillance. And we're also using it for community health information system. So we are now, people are like, oh, you can use Android for a lot of data collection things. And you realize that it's actually increasing, the demand is increasing. Okay. So the last part is a Nationwide success story. So our Ministry of Digital Economy has been praising the national system of vaccination, the electronic system, saying that we've been able to enroll people and people who have their certificate is compliant. And due to DHS too. Challenges, analytics. I mean, we had issues with analytics in bringing up the data. But I mean, when we upgraded to 235, it was fine. Thanks to the developers and the feedback that they got, we were able to have the system to 235 and it was okay. We also had issues with managing devices, because some were using their own devices and a bit difficult to manage to upgrade to support and the versions were different. Those were the things that we had. We had also a problem in the beginning with the process, because they actually wanted to enroll the population via an electronic system whereby the people that were above 50 were not that used to internet and website. So when you come to the health center, they were like, we want to get vaccinated. They said, you need to get enrolled in the system, the what system. So we needed to actually educate them and make sure that they get enrolled into the system. So that was one of the challenges. Lesson learned. Well, it was possible to actually roll out a system in a fast period with the local support. So the fact that we were around and the Ministry of Health was already used to DHS2, we could actually quickly support a system like that. The good thing also is that we had this feedback mechanism. So we were able to talk with the Android developers, with the web developers, on the feedback that we got on the field and it was implemented immediately. And I mean, that actually was quite crucial for the rollout, because we didn't have a lot of problems. So thank you very much. Oh, yeah, good. Thank you very much. Jerry, it's a problem when you have the long hair to take this. Anyway, so then our next presenter is, sorry, I forgot your name, Tiwanga, sorry, Tiwanga from Malawi. Thank you. Thank you. All right. Good afternoon everyone. Okay, so the use case I'm presenting is on the community health information system for Malawi. So what you see on the screen to the right is just a list of the modules that we have within the community health information system at the moment. So from the test server. So as we go, give you the rest of the details of something of the connection. Yes, so the connection is off. All right. So the connection is back again. So I think largely that's also why we use the Android app for offline work at the community level. All right. So what we have as the integrated community health information system for Malawi is an approach to having an integrated solution that supports all the work at community level. So over the years, there have been varied implementations to support the frontline workers. So now the ministry as part of its community strategic plan wants to have a unified system where you'd have the community health worker using a single device to support all the services that they provide. So this is where the community health information system comes into place. So the system is owned by the ministry of health. It's coordinated through the digital health division with the support of the community health services section, so which is responsible for the services at community level. So like what I showed you from that initial slide, we have various modules implemented at the moment, not all as because we still developing the components. So we're developing and then rolling out. But at the moment where we have deployed, we have a community health register which observes or gets data on community or village demographics as well as community health. So schools, speed and collection points and so on and so forth. And then there's a household register which is used for tracking environmental health at household level. Then the person register for person registration and linkage to various health programs. And then we have the integrated community case management, which is an embedded protocol to guide the community health workers in managing childhood illnesses. So there's an embedded protocol that gets them through assessment. And then the app does tell them what the assessment classification is and what the management for the various detected conditions should be. And then we've also implemented all the tools for the aggregates reporting. So at the moment in terms of the scope, we've deployed in five districts, the fifth one being handled as we speak. So with over 750 mobile devices and the primary users, community workers, so these are Saturday government workers who are called health surveillance assistants. So in terms of the deployment approach, we've mainly tried to advocate for similar devices so that we're able to manage things better. And in prepping for the deployments, usually we have various teams coming together to do the installations as well as register the devices. And then there are also agreement forms that are given to the community health workers regarding how they should manage these devices. So for deployment, we're using fdread for the visioning and pushing to the users. In terms of upgrading to various versions, we're largely looking at staying a vision behind just so that we see that things are stable. And then in terms of troubleshooting, because in the field, there are a few things that we need attending to. So one, for example, where people have issues like with syncing, we check the synced logs. So in some cases, we do ask them to send us the synced logs. So then also we do utilize system logs. And then we have configuration testing sessions mainly to check and validate program rules, because since this is meant to guide service delivery, we have extensive program rules implemented. For the main successes is that over time we've put together different teams to have training of trainer sessions, and then also had combined training because the ministry is also at the same time deploying paper-based community registers. And to make people comfortable, we are at the moment also facilitating the trainings for those paper registers together with the app. And then also over time introduce pre and post assessments for the trainings, just to also have some quality checks in terms of the work that we do. And post deployment, we do have routine visits to the districts to evaluate how things are progressing. And then we've had an integrated approach in terms of system development and the trainings roll out as well as the supervisions. You see that in the final slide. In terms of the main challenges, I think at times the challenges with data syncing program rules, testing can be a nightmare at times where you have extensive rules and also you have different people working on rules. So one fixes, the other one does another rule and it just messes things up. And one also interesting thing that has come at community level is the need for supporting a dual track entity support because the tracker model mainly looks at a track entity. But here we have, let's say a household. So you want to track the household, but then you also want to track people inside the household. So that's a bit tricky at the moment, but we'll use relationships, but at the moment the implementation, the relationship linkage is soft. So you link, you tap on that X, that's gone. And then one other, I think a slight challenge that we've had is in terms of stages that are supposed to be linked. So in some cases where you would want the stage to be locked, some program rules still run. And then also linking related stages, like events across related stages in some cases has proved quite challenging. So for the lessons linked, we've seen that it's also important that we invest in digital literacy because when you go lower, more especially for older staff, digital skills can be quite a challenge. And also with the rapid expansion of the implementation, we feel it's important that we also expand the various competencies that we require. And then we've been able to coordinate multiple implementations using different partners and deploying in multiple places at once. And then one key thing as well is the balance between work plan flexibility and QA, like quality assurance, because we have a plan, but funding availability also has other plans. So you have to be able to balance those two, follow the funding, but also maintain the right level of quality. And I think one other thing, final is, we've also felt, I think, the need that we need to communicate with the global Android team more than we actually do, given our implementations, because I think in the cases where we've done that, the response has been quite good. So we'll improve on that. And so in terms of the partnerships, these are the different entities that have taken part in doing this. So the ministry coordinating the university and also last mile health, coordinating the technical assistance, UNICEF and Wandikwe is providing also part of the funding with UNICEF funding the most for this implementation. Thank you very much. Our next guest is Patrick from Hispuranda. Okay, good afternoon for those who are in here. So Patrick Omeel is my name and I'm here to share the experience of Uganda implementing Android for the different projects that we... Okay, so as that gets on, so I'm here on behalf of a team from Hispuranda and of course the Minister of Health that we've been working with to implement Android. So ours won't be one use case, but basically it's a sum up of what we've done and generally the entire experience of implementing Android. Of course from the team, we have Immaculate, a colleague who was not able to join us for the conference, who kind of leads country implementation in Uganda and she has been very, very key in making sure this works for us and she has been coordinating well with the team. Of course Prosperizia is also part of the team that we've been working with to implement. So mine is just to present. So if the hard questions come, reflect Prosper and probably if Emma is online, it's supposed to be offline but... Okay, so we have, I would say, maybe much longer history in terms of our implementation. It starts way back in, could be 10 years ago, way back in 2012 is when we had the first Android implementation and this was one NC project that was interested in tracking, of course, NC mothers across districts. That was the first and that used version 2.16, I'm sure some of you have not been using the HIS too. So that was the first Android implementation we had in 2012 and then in 2013, we had another one that was for global health security that was helping with the disease surveillance and after that, the interest grew. We realized that, yeah, you can use Android to capture data and the interest, of course, was how do you use this offline capability. And that was actually also the query requirement and I think that is the sole purpose of Android. So currently, as we speak, we are using Android for the EIDSR. We're using it for TV surveillance. We're using Android for the COVID vaccination and then we're using Android for the point of entry tracking. So those are some of the major use cases we have and like you can see Emma, Emma is the colleague I was talking about. She really does the support for Android implementation. So this is just a summary of what we've done with Android. Like I mentioned, we had a first implementation of the MCH project in four clinics and we used four tablets and same as the one of EIDSR through the global security, also for tablets and we're also acknowledging the partners because getting these devices together, you need support and most times we don't have those resources. So most of where we get is that when we get support, sometimes it comes with the devices, sometimes you have to look for other partners to provide the device. And for again, EIDSR, looking at mainly the COVID, we have 160 tablets deployed at district level and also that supports both point of entry and also the CTUs, the COVID treatment units. We also caused the TV surveillance. We've rolled out TV surveillance in Uganda and we also facilities that are not fine. We are doing a kind of hybrid deployment in there. Facilities that don't have computers, we've been able to provide them with the tablets to be able to capture data. And then the health facility, that's quality assessment, basically an assessment for health facility. We've also deployed Android for that. So basically it helps them to assess district teams and national teams to do assessment and facility. So we did the tracker configuration and also deployed Android to support that. And of course, the big one, the COVID vaccination, where we had a lot of support from the WHO and CDC to deploy Android. So in terms of our approach, and this is missing this slide, it's I think the same. We usually do the configuration, make sure tracker is up and running on the web and just make sure every program rule and everything is working well. And then when we forget the devices, we put them up in office and start doing the configuration. Making sure you've put the app, you've done all the configurations, you've put the username, so that by the time you hand over to the end user, it's kind of set and ready for them to use, so that again, they don't struggle a lot with being able to set it up. So we do the setup ourselves before we deploy the devices to the field. And most of these, we've been able to try and avoid the private own. Apart from this TD, for most of the others, we do the configuration and everything, then we hand over for them to be able to use. So in terms of benefits, some of these benefits are known. Of course, the offline capability is really a big benefit to the users that they're able to, we're able to deploy in remote areas and be able to get data. We've been able to also utilize the part of the picture for some cases. Like if you're doing a health assistance assessment, sometimes you need to capture some proof to show that, you know, you've been able to, if you say you're assessing and doing a scoring, there has to be some evidence that what you've scored is correct. So is what you're able to observe. So that was also been a very good feature that we're using. The barcode scanner has been good with the lab integration. The QR scanner has allowed for applications such as the self-registration at points of entry. We've been able to use that for points of entry. And then using the guide, you know, this is something that I personally went through a very bad experience of not following the guide and basically getting Android with my super user account and then setting up Android and going to demonstrate. And then when I reach there, I touch things freeze. I touch things freeze. So really, the experience of Lancia is trying really to stick to the guidelines, yeah, making sure you create the right user account that works for Android. It's very, very important to follow the guidelines. And then we learned, of course, less is better. This is mobile for a tablet, for you don't have to have so much. Yeah. And that goes back to the idea of using it for vaccination and there's a line of people and you are there with a tablet. It can be slow. So sometimes when you have less, the better. It will work first and you'll be able to quickly capture, you know, yeah. So less is better. So as you do the design, try and make it tight and something that fits mobile, you know, and then the assessment is a good use case. So we've learned, you know, people feel good when they're going to do an assessment and holding a tablet and asking questions and just, you know, so it has been one of the interesting use cases for us. The last slide. So in terms of challenges, of course, the software issues are there. On the update, when newer versions come, yeah, we've had some challenges coming. One more minute, okay. When you get your versions, you run into issues. This is known, yeah. And then there are times when you fail to sink and you cannot even like redeem. So you kind of lose that data and just flash it out and re-enter. And clear logging, I think this one has been mentioned. Inconsistency is between the web and Android. I guess this was also mentioned by other colleagues. We also have other competing flashy web Android apps that people use. Like COVID, we are really, you know, in the field of struggling, you know. Other people wanted to use CompCare and other tools to do so. But still, once we have deployed, it's usually had to be pushed out. And then the last, the operational part is really you have limited budget for these devices. So you have to plan for it, you know. The event re-management. When you give these devices out, sometimes you may not recover it. Especially when you're working people in the district and very remote areas. It may become someone's mobile phone or mobile device. So it becomes very difficult, remote maintenance and support. And that comes with the cost of the MDM. We are not able to run this for now. Yeah. So that was the Uganda experience. And over to the next presenter. Thank you. Thank you very much, Patrick. And our last guest is Shaila from South Digitus. Good afternoon. Good afternoon all. My name is Shaila. I'm leading the implementation team in Mozambique. And I will be telling you guys some stories about the implementation of Android in Mozambique. I think, as Patrick, we are not going to focus on one specific implementation use case. We will be talking broadly about this implementation process in Mozambique. As a quick introduction, we start using DHS2 in Mozambique since 2015. And in 2017, our country started adopting the approach of using the Android version for this national control for CB program. And after that, the malaria program also starts using with iMiche, which is integrated malaria system storage. And the surveillance program also starts using the Android version. Currently, the Ministry of Health has several trucker implementations, which why we are in the second place of using this device has a way of implementing the DHS. For instance, in terms of DHS, Android, the Ministry, and we have been using most over 18,000 devices for the iMiche program, 2000 for the TB program, and also 15 for the COVID. We have supporting other countries using the same approach, such as Guinea-Bissau, São Tomé, and pre-CP, using the device as a mechanism to implement our programs. As a deployment approach, we used the testing, and Android version was performed by SD, us, to cope of a DHS version similar to the production version. We used the web version, and then we tested to see how it works on the Android version. We have worked also on installing the devices on all devices. And then in some countries, we had used the fDroid as a mechanism of uploading the DHS, because we're more easier for us to have this control of the version for some implementation. Lately, we started using the Mirador because of the advantages of using Mirador, such as remote control, because we have been working with several countries, and sometimes it's very easy to have these management devices control for this remote monitoring and upgrading version. We have also worked with the capacity building of the users, and during this deployment approach, we did a lot of TOTs with our local members from the health facilities to make sure that they will also train the other people. And then we had this regular support and troubleshooting. We had created a lot of WhatsApp groups, which were more easier to have feedback from them during this interaction and during the implementation. And also we have been helping on upgrading the devices and the DHS app versions. It has a main success. Using the Android version, it brought more flexibility in terms of data entry, because I think we all know that one of the main reasons we are using these devices is because of the advantages of using offline data entry process, because we have health facilities that don't have connectivity in certain areas with this future. It allows more of them to do the data entry, and then when they have connectivity, they can send. Also allow the individual and aggregate data to be entering in this offline mode using the device to input data from different programs. In terms of saving resources, having these devices in each health facility helped the health facility person to entering this data from several programs. And also we use the mirror door has a way of ensuring this remote and centralized device update, allowing tracking devices and also allowing being mobile data consuming. Because one of our biggest challenge is regarding to data consuming. And with this control, it was more easier to have how can I say on how much and how facility could consume regarding to data. And then we use has planning for other implementations. As a challenge, our colleagues mentioned some challenge regarding to the app, the program rules and everything I think we have been discussing in other groups. But in terms of implementation on site, the literacy of the health facilities in manipulating the devices was one of the biggest challenge. For that, actually one of our approach when we are doing the capacity building is to make sure that one of the first things that we teach them is how to use a mobile phone. Because it starts from there. And also maintaining the devices, it has been a big challenge. Because we have high costs to use the MDNs and sometimes we have to use in the not paid version. And then we have this limitation on help the people remotely. And also sustainability with the device acquisition. Because we know the device have like a lifetime very, very short. And sometimes we have to make sure that we have a plan that it's sustainable for all these devices. The compatibility of Android devices or field devices with the DHS capture versions. For example, for the TB program that was the first one using the mobile implementation. We had a version of Android which was five. And these devices couldn't be upgraded for new versions of Android. These ones that it's being displayed there. And the new features of the DHS app, sometimes this incomparability, it makes us to not update the version of the app in these Android phones. And this device starts to be not helpful. Because for example now we have new updates for the analytic part for the Android. And they cannot use because the device version doesn't allow them to have a new version of the DHS one. And also management of internet. There is a lot of costs regarding to the internet management. And this has been also one of our biggest challenge for the most of the experience. It was this. Thank you. Hard with the long hair, I know. Okay, thank you, Sheila. So we open this for questions. I have a question about the incompatibility of versions. Because if it doesn't work on 5.0, then we need to know because in theory it was working down to 4.4 until the last version. Okay. For the first versions of the capture, yeah, it's possible. This is the one that we are using. But for example, for 2.6, the minimal, it's not the 5. Yeah, but it's not when we are using, it's kind of doing a crush. And that's why we have to use the lowest point so far. Okay, then it will be good to learn about that. Okay, thank you. I'm going there first, then come into prosper. And I'm going to run the room. I have a question regarding the usage of Eftroid. Did the teams that used Eftroid for distributing the app set up their own repositories? Or were you distributing it publicly? And could you please share your experiences with using it? Sorry, can you repeat the last part? I didn't get it very well. So with Eftroid, did you set up your own repository for distributing the app? Or did you upload it to the public repository of Eftroid? Okay. For the Eftroid, we created our own repository, and then we uploaded the versions, because we have a different link for each implementation, because sometimes it uses different versions of DHS2, and then we upload the right version for each one. So when we set up for the androids, they have a direct link for this specification, for this specific Android version, the DHS app that they have to use. I mean, yeah, so in short, we also set up our own repository that we use for distributing the apps. I don't think we can publish the app in the public Eftroid because it uses some Google services and libraries that prevent us from that. We're trying to remove all dependencies, and then it will be available in Eftroid without requiring individual repositories. Okay. Yeah, thank you very much all the presenters. One of the challenges we are having is using one device at one clinic for multiple programs, which are running with multiple instances. So you have a TB program, which has its own instance, that's a different URL. You have HIV program, you have an assessment program, and so on. So most of the users have been coming to us and like, why do I have to have different devices? Because right now, it is forcing me to have different devices. So for the Android developers, is there something that we are thinking about and also to the implementers? Do we have any solution to that? Yeah, we support multi-user offline now. From 2.6 up to 3 accounts. You can instantly or different servers. It's the combination of the URL and the user. One last question. There we go. Thanks. I'm not a DHS to expert at all, but we're coordinating this project on surveillance. And so I had a similar question to Prosper. So I saw that in Uganda, you're using each program has a different device, and it seems like it's the same device for several programs. And how can we make sure that we can use one device for the different programs? And then another question is, can you use the Android for case-based surveillance where you have so many variables and entering that at health facility level? Do you think that's something that's recommended or do you recommend more like having paper-based for case-based data with, you know, 100 different variables? He's taking that. All right. So yeah, so I think on the, as I said, in terms of, I think the multiple accounts, those can be supported. But also in some cases, I think where things can be combined, it's best to do that because you also get to run away from one health worker having multiple devices for each program. Like what we've done is to also assess the districts who already has devices from other programs and see whether those are fit to deploy on. And then we use those and then give to those that don't have. In terms of surveillance, I think, yeah, there are different ways of organizing the data. So you can be able to support that like on the Android. Yeah. And you can, you also use, I think, multiple stages if you have too many rules, if you want to do computations, but you should be able to handle that. Yes. Okay. So for any of the presenters, I was curious, for those of you that specified the hardware as opposed to the bring your own, can you talk about the specific vendors that you used, any specific models that you specified? And yeah. Okay. Most of the devices that we are using are like Samsung. And now we have been working also with Lenovo. There is a different advantage of these two devices. For example, for the Lenovo ones, they are more used for the work because there is this, for example, we did not allow you to use a phone. There is no mobile phone calls. So it reduced the use for non-use work activities. And for the Samsung one, we use with some specifications, but there is this MDNs that allow us to create a restriction. Thanks for the phone. It also reduced the use of non-use beside work activities. Just on the device, I think the one that we are preferring is the Galaxy S7 Lite. At the moment, it fits what we want to do quite well. Thank you so much. I wanted to find out from Malawi the issue of security of devices. Again, lost or theft, how are you managing that? And also just from Togo, a quick one, how many devices are you using? And what is your internet penetration percentage within your country? Okay. So I think for us in terms of the management of the devices, as I said, there is an agreement form. So these are government devices. So I think it's part of giving the devices to the frontline workers, because these are also government employees. They sort of like an agreement form that they would have to sign in terms of the responsibilities for keeping the device and also the way of escalation, if they were to lose a device. And then there's the structured district level. And then at the central ministry level to follow through, should there be a loss or any other thing that needs attending to? That's a tough one. Well, I don't have the correct figures for the number of devices that we have, but all the health facilities are currently having devices for how to call it. The ones that the facilities that are supposed to enter data for vaccination have their devices. So I don't have the correct figures. So I don't want to say wrong figure. For internet penetration, I mean, you have internet, of course, in the capital city and around the capital city. In the northern part, it's a bit remote. The internet penetration is not that I mean, you don't have internet all the time. But of course, there is this offline capability. So people have been using that for synchronization. Of late, we didn't have any complaints from the site. Related to internet, they've been able to send the data and people have been able to get their certificates because we use that to get the certificates. Okay, over. I forgot to use Android.