Alright, so general guidance on assessment planning and implementation, I'll go through a session on assessment. That will be most of the content and then some shorter sections on planning and additional guidance all related to planning and implementing this kind of project. And again, to give a general overview on what we're talking about with public health supply chains quoting Chris right here who works within the sector. Those working public health supply chains view the supply chain is one as one among a number of different interdependent systems and I think that's one important aspect. And then further the supply chain is focused on delivering medicines and other supplies that enable the health worker to meet a client's or patients health needs so that's the overall objective that we're trying to reach with these different interdependent systems. We're relating back to a slide which you saw in Mike Frost initial presentation when he was starting the, the Academy on day one, showing this very broad view of the health information system landscape, and how these different systems fit together to serve specific purposes and needs for health services medicines and supplies human resources finances, and that again, this is what's related in the definition in the previous slide that you have these interconnected systems working together to provide health services. And it's really key to understand this interconnection how they work together and support each other to reach that overall objective. It's an introduction to have in mind as we then talk about assessment. Because with assessment and planning, you have to look at the LMS landscape you're looking at that perhaps a bit more, more closely, and you want to know how is that structured, which systems are being implemented for which products and programs at which level. So what is the information, and how is the workflow structured, and what the purpose of this implementation will eventually be so what is the goal that you're trying to reach. Because you'll have different tools, it might be paper based for periodic reporting this is oftentimes what you find at the health facilities, it may be Excel or some other locally stored tool, which then is shared. It may be available, or it may be some ELM is or other digital tool that's implemented at one scale or another and it may be maybe well a mix of all of these. It may be implemented, you know, completely at a central medical store you have your warehouse management system managing your central stores. But at district level, you're only covering maybe part of the sites. It's not every site that is running this ELMS or other solution. So even less so. And community health workers they only have perhaps a pilot running so this is entirely hypothetical but this is a situation which you may find. And then for the different programs that are being run, if you may have an immunization program, which has one type of LMS running to manage all the products. In 2019, which was oftentimes came with a lot of funding and had to be implemented quickly due to the urgency of the pandemic. So another solution was was brought along with it and was supported for your HIV TB you may have a bespoke system and it's only used for reporting and not for for management and decision making. And then other programs are still using paper or Excel or other tools. So you have this mix of different solutions. And then of course you have the donors, Gavi, Global Fund, UN agencies, USAID and others, including their implementing partners all working and supporting these different initiatives implemented at different levels with different support. And they also have both ongoing and planned project projects or planned initiatives, which you also need to work to understand. What is it that they're planning to do and what is it that they currently have ongoing. So now to get kind of an overview of what is happening in the country and what you have available we can then look at the systems that you have in place so we recommend a tool and this is again available in the drive. Which gives a simple overview over the systems and provide some relevant information. It should be adapted to your context if you know that there are certain specific needs then you can add or remove columns and just change this. And then determine if some of the needs you're trying to achieve are already there. There may be a system that's already meeting needs for what it is you're trying to achieve. So you would want to categorize the system, the unit responsible who's actually managing and it has system administration responsibility, who's actually ensuring that this is functioning and users are receiving support. The type of system that is being used and the technology. So if it's an ERP or an LMIS if it's an online system or a local system this kind of information. So really you're cataloging the systems that you have. We also want to know what the primary data sources are so where is that data coming from at which level is it being input into the system. Are these paper forms that are being used at a facility sent to a district and at that point they're being input into the LMIS the DHS to or another tool. And then the reporting flow. Again, where is it the data coming from and where is it going who is making use of that data is it being simply used for reporting or also for decision making. You want to know the data itself what data is being captured what type of data, and then information on the user and there are some other fields that are not here and you can add and remove. You can quickly inventorize the different systems that you have available and you can work towards making a decision about where it is you're trying to go and what you're trying to achieve. Another aspect that might be interesting here is to understand what type of indicator and visualizations are you trying to to to perhaps create to then inform your users because some of these may also be available. If you look at, for example, DHS to there are immunization packages, there are malaria HIV to be packages that may already have stock data. Being used in the generic packages, these are already included and countries may already be collecting this data visualizations and indicators on the amount of stocks issued, comparing the to the number of patients that are being treated to make this kind of triangulation it may already be available for help teams. So when you come in as a supply chain person and LMS person and want to develop certain tools, you want to have access to certain data you want to make this kind of advanced analysis. It may already be available to a certain extent. Of course, in that case it would be used for health program management and decision making. For other purposes, it would be nothing more than having access to a visualization that's already there the data is available. So it's really also important to catalog this here to ensure that you're not overlapping or doubling up work for something that's already that may well be available. It's just a question of getting to know that and being aware of what is being used. And then we move on to then a more specific ELMS assessment so supply chain and stock assessment. We want to know what kind of data is being collected and how is that being used within the supply chain. What's the flow of goods and then also the flow of information so goods are moving from a central level down to two facilities to service sites where it's being issued, and then eventually the information is flowing in the opposite direction informing decision making or should be flowing in the opposite direction informing decision making, and that's what we're trying to to improve. So understanding the supply chain design and specifically the replenishment systems and methodology would be very key to then propose and use something that will add value to that. So the updates for all of these are available on the drive and you can go through and conduct this kind of assessment to know what tools are being used and what scope and how it's currently informing decision making and the supply chain. I know for this George is really our true expert I don't know George if you want to add a word or two on this slide if not I can continue. Yeah, I can go on to then using DHS to. So now we've promoted this approach, you're using certain LMS tools, and you want to improve your systems you want to digitize facilities you want to bring this data into the decision making and into the LMS sphere and we're promoting and proposing using DHS to we have this overview here showing a broad implementations 69 countries using at a national level as we said in the first day. And this is all well and good. And you want to take advantage of that. And now what we want to then show is that we also need to make an assessment because as you see here it looks like they're all equal and all the same. However, we need to understand how is that being implemented in your context and this is part also of the assessments to understand that generally the HMIS teams are the ones implementing and running the DHS to instances and with close support from the his groups. And that normally aggregate data so report data is what's being first implemented to collect reports, and then eventually moving to individual data using the tracker app. And this may be in a separate DHS to instance not the same instance. So that data may already be available including indicators and visualizations as I mentioned before, there may be stock data module already included with the malaria or HIV TB package or with an immunization package. Some indicators already using that stock data may be available to the health teams. So it's important to understand what they're currently using what already is there. And there may also be some in some level of integration oftentimes it's stock data being sent from the LMS to DHS to for the purposes of analysis but again knowing how this is being implemented by which teams and what the scope of implementation is is really key to then start developing and promoting using the same system for your LMS purposes. Get to know the DHS to core team in your country, this will be the team that's responsible for system administration implementing and support within that country. And now there are some tools and a lot of information on this slide and a lot of things that you can go through on your own about the development of a DHS to implementation, but I want to focus on what everybody is certainly looking at is the house. So there you go, there's this house and the house is a metaphor for DHS to implementation. So the house looks nice and beautiful, and this can be your program collecting health data and showing these visualizations and these different dashboards which we saw yesterday with with Scott. The foundation is not necessarily the best it's standing on some pillars or some palates it looks like. And we have to look at what is the quality of this foundation for you to be able to build programs on it and the LMS features. This would be an additional program that's sitting on a foundation of an LMS DHS to implementation. So we have to understand a bit what is the current state of that implementation and how can we best optimize it and use it. We want the LMS purpose. So we went from that overall view where we see many implementations in many countries. We want to use it to improve and maximize our supply chain management we want to digitize facilities and bring that data for decision making and analysis. But what is the current possibility what is the infrastructure available for that. These different assessments for DHS to these are already completed for many countries. Most countries have already done this type of assessment first the readiness assessment when implementing that's what you see on the left. But then I'm referring more to the maturity profile, which is the one that will focus on now, and the maturity profile identifies the quality of the current DHS to implementation and areas where it's very strong and mature and other areas where it needs further development. The questionnaire, which has already been completed. We promote that it's shared with partners and donors and that all of those working with DHS to are aware of the quality of the implementation. So you have a questionnaire where you go through specific areas such as security, administration, metadata, training and user management, using Android and other points, and you answer questions and you come up with a evaluation of the quality of the implementation so you may have a mature implementation where all the needs are met and and resources are sufficient to fulfill those needs. This is an adequate one which is good enough but needs improvement early progress where it's only being implemented or not yet achieved or that maybe service or or is not at all being met. So these are the different levels and I think it's important to know where it's at for these foundational features. So with that evaluation would be applied to programmatic data so this is individual tracker data for specific program malaria HIV tracker, or other. The first time stock management would be eventually in this column up here. You then have the same programmatic data for aggregate. HMS data case based surveillance malaria and eventually your stock reporting option would be in this line here and this is great this is what you want you're using DHS to for data entry you're storing this data. And that's all well and good. However, that happens on a set of foundational pieces that need to be in place for those programmatic areas to be properly implemented including your stock management features and again biomedical equipment lifecycle management and all of the others. So these are important points to understand that you need to have facility and population profile to be properly functioning. And make sure that the facilities that you have in DHS to. So each health facility, and that entire health structure is properly organized active facilities are captured new facilities are included older facilities are removed and this requires consistent management, and that then that list is aligned with the LMS. When you're sharing data from one site that it properly matches another site. So you have. You can have a closer look at these foundational pieces so that when you have data for a site being reported it's properly matching the same facility data in the ELM is for the infrastructure that you have sufficient server capacity, either if it's locally hosted or if it's on a cloud solution that you have capacity to run the programs that you're looking to run when you're adding your LMS program that they have capacity. That the DHS to metadata that over time that's also managed that you're not simply adding and adding and adding but older items are not removed. So all of these different points are very important. Maybe another one that's really relevant is training end users. What happens when your storekeeper or the person if it's a health person at a facility who's capturing data, if they lose their password, if their devices damaged and they need some support if they don't know or remember how to do a certain workflow who will actually answer their email or pick up the phone or give them support for all of the new persons in the in the health system that are coming and going you know people are leaving their position and you people are entering. So these are all the foundational pieces that ensure that the programmatic that the features that we show you and propose can be properly implemented so it's really important to understand what that level of maturity in the implementation is, and how you can work together with the HMIS team the team responsible for the DHS to implementation to properly support your initiative. So here you have two very simple examples on the top you have a DHS to maturity assessment that shows a country that needs some more support with some key foundational pieces. And you see that the programs are also suffering in their level of success and implementation, due to these foundational pieces. One idea and one thing to have in mind is that before proposing we want to have the LMS features being installed and implemented is that you should also promote and advocate for funding to support some of these foundational pieces you see the training end users is a key weakness within this implementation. And that could be something that could be looked into to say, we can support and we'll identify funding and you advocate and promote to have this funding from from different donors or different sources to implement your LMS solution but then discuss with the community if you can support some of the needs for this training of end users that you support the overall capacity it may be supporting a 50% position that simply works on customer support that becomes that first line support for any user who has issues with passwords or axing accessing the system, or any kind of workflow challenge that they're available to support LMS or other program persons and in that way you support a existing need. You build capacity in the overall system which is again owned and maintained by the country, and then you build that good will within the team to implement the LMS features within the existing instance. For example, you have a much more developed maybe a longer term implementation where you have a stronger team and you have more capacity. Maybe the infrastructure has been well, well funded and you have good resources training and end users you may have a very strong team of dedicated person that they've been there for quite some time they know the system they provide trainings for users. It's great, but you can still help with the one piece which they maybe need some more support it may be a lot less resources needed. But this would be a lot easier to propose then an implementation to say we have a strong working DHS to implementation and we have a strong support team infrastructure and the entire environment is strong. It would not be very problematic to add also the stock data and that level of support with the additional user that that it would take so really important to understand the DHS to then landscape. And how you can support it and should support it at a foundational level in order to get the good will buy in and cooperation to then implement these DHS to LMS features. The second new maturity assessment is has been conducted for very many countries, most likely for the country you're in. We've encouraged all countries to share this widely to share this with partners. So it should be possible to share with you as well. If you're coming from an LMS team and really get to know that team that's managing and get to understand their challenges and see how you can both make use of the existing infrastructure, and, and also support areas where they can. We gave the example of Molly, where there was the integration with the Medexas LMS on Monday afternoon. And this was a perfect example where they had a quite mature implementation, a very good team with very good support to his members in and the level of effort and the cost were quite quite low for the amount of input and and and and value that they got from the integration. There was some effort done in the actual technical technical integration, but their implementation was much more like the bottom here where it was quite strong developed mature, lots of resources, connecting that data which was already available in the system was very low effort for what the actual outcome was getting access to this facility level data. All right, I'll go through briefly some quick points on infrastructure for aggregate versus tracker. And again to remind that Jaime will be following up speaking specifically about mobile so I will not go into details of that. But just to say that for aggregate data entry. There will be a possibility or the requirements would be lower than for the real time stock tool so for aggregate reporting, you're reporting on a monthly basis. There's the ability to share devices there's the ability to do this reporting on on a much less basis it might be once or twice a month that you're actually needing to go in and input information whereas with the real time stock tool you're making. You're capturing every transaction so the availability of a device, maybe having a dedicated devices much more important so this is something that we need to consider is, what is the need for that specific workflow. What is the need for that specific device and in the specific in the facilities, do you have multiple people using the same device can it be shared, or do you need to have dedicated devices, keeping in mind that it may be the same person collecting health data is also the one issuing in very small facilities where you may have just two or three persons working. It may be the same person actually inputting that data for multiple programs including the stocks. Power and connectivity of course and this is something that I know Jaime will get back to thinking about especially mobile solutions. However, we're looking at using mobile for the purposes of the offline capacity. The support structure, I mentioned it a few times who will actually pick up the phone and answer a user who needs support who will actually follow up and ensure that there's capacity within the health staff to use the system and report on the data that you want reported. That's a very key aspect to keep in mind and something that you can definitely support when adding more users to the implementation. Server hosting, this is a similar to the other where with aggregate reporting, the requirement for the system would be much lower whereas for tracker having transactions, the quantity and frequency of data will be much higher. So these are all considerations to take into account. And then mobile data. These are the considerations that Jaime will elaborate on with LMS going mobile. I have these for the purpose of reference here now but it's devices management inventory airtime and so on. And we'll hear a bit more about that soon for planning. Just a shorter section on that that once you have this broader assessment you understand which systems are available. What are your work flows and requirements are for your LMS workflows. What are you trying to improve. You understand then the DHS to landscape so we've gone from systems to then logistics management to then the DHS to implementation and what's possible there those sort of three broad aspects that I just went through in the assessment. You should then have a clear goal. What is it that you're trying to achieve. What is the scope of what you're trying to achieve with this implementation. Oftentimes you're, you may be starting from at the facility, particularly that you have your paper based management. And perhaps it's good to look at achieving or improving that one step at a time. So going from paper based to a fully transactional based system with a full integration. It may be a very ambitious objective, it may be a fine objective if you have the resources, the buy in and the commitment from donors. However, it may be also interesting to simply take that one step to using the aggregate implementation. So the month of reporting as a first step, introducing users if not all of them are familiar and already using the address to making them familiar with the application, building that connection between teams, and then slowly building up to this broader implementation. So have that goal in mind, based on then the landscape and what is possible given that landscape given the systems that are available to different donors and partners and internal agencies that are implementing. The resources and funding available so just ensure that the goal of what you're trying to achieve is in line with what's possible in terms of resources, commitment and buy in from everyone involved. Timeline again where are you trying to be within one year three years five years and so on. Look at this as a long term engagement and not simply that's something that will be quickly implemented as a one off. One step at a time. Look at the foundational support and that again is something that will be over time user support. For example, the facility management, ensuring that all of these pieces are in place will greatly increase your chance of succeeding supporting areas which are lacking will improve the likelihood that your specific implementation will succeed. And among internally and also with donors and partners is essential that you understand and get to know who those those responsible persons are. And then of course the sustainability again going back to supporting those foundational pieces will improve the sustainability and likelihood of success of the project budgeting now this is a very key point this is from another slide from a from a colleague which I borrowed that you may be looking at the Patronus towers but the budget only allows you to build your baby corn towers so that needs to match and that's something that really goes back to setting achievable. I think that's one of the goals with the amount of resources that are available and here we're talking about budgeting, but it also has to do with with the buy in from the different partners involved that they have people in capacity to implement that that objective. The funding is also for the one off implementation but also having in mind the recurring costs and what that will mean over time. And I think that's a question we can have for him as well on the recurring cost specifically for airtime and other things related to mobile. Right so once we have this assessment and planning we should have then an idea of how we expect to fill the gap that we've identified, keeping in mind that we want to promote this holistic supply chain and product management and avoiding tools that are either limited or limited in time or scope that cannot be built upon that cannot be developed for future for future work that we have even though we may have a very specific objective or trying to achieve. We can also look beyond that it may be simply implemented for one program with a relatively limited scope. What is the eventual development of that over time once you have new projects and new funding with new maybe partners coming in. And that goes to other programs from immunization to also HIV TB from district level down to facilities that you have this overall understanding and consideration in mind when planning. So for that we have some a little bit of additional guidance and I'm already nearing the end of what I want to share with you for today. So for that it's the interoperability considerations. And for that, you already have it from day one that you're you have this in the back of your mind, you have it in your in your mind. Is there a need for interoperability and we know that with the approach that we're promoting. It's essential to, to using the HS to as an end to end solution it's having that central el minus so we know that it's essential, but in an initial project you may first want to start with simply capturing data and facilities. So interoperability or integration would come in a follow up project in the second project that would look at specifically again the system design and report your forms the alignment of the master data which I've mentioned the facility data and then planning for future workflow requirements. So you'll already have this in the back of your mind. One good example is using the standard data entry forms and not a custom data entry form so that it doesn't limit the use of mobile in a future implementation so these kinds of ideas should be there from the start. However, when you're looking more specifically at integration that that should be part of your project as well. Then we also share with you a data source mapping tool and this is something we develop with our integration team. So Austin who you heard on Monday, and a few others where we got some more detailed information that can be used to map the systems and more specifically information related to an integration. So, some of this is partly overlapping with that system inventory tool that that we shared. But here we want to know in more detailed exactly where it's being implemented and how, and that we then go into questions related to the data model so we need to really ensure that the organizational units. And the users are the same within the system so if you have and this is a common thing that we've seen is that you may have in the country, multiple health facilities with a similar name so we need to ensure that we can properly identify those using standard codes so that we know that the two facilities are actually the same one they may have the same name but they'll have a unique identifier unique code or ID, and this needs to be aligned between the systems. When you facilities are opened or closed that that is updated again on both systems, when new users are coming in that they're trained on how to work within that integrated workflow. And that is possible within both sides that there's both systems are working in a coordinated way, ensuring that you know what kind of a period of reporting or if it's a transaction based model that all of that is properly mapped that the data elements and specifically the products being reported are aligned that you have this central repository for all of the products that are being used in the country. For that we've referred often to the ELMIS or ERP that would, or should have this this master list should have the should be the source of truth for the data. We generally use DHSU as the source of truth for the for the facility profiles or for the organizational unit structure, but that that is understood and aligned between all the systems, same with the metadata. Not necessarily terminology but that you know that stock issued stock received and all of these parameters are aligned and are the same so that you're feeding in the right data that's being expected. For the more technical integration and now we're moving more into the more IT technical, a system may say that they have API's but that needs to be confirmed at a more specific more granular level. It doesn't mean that there's API's for every single piece of information within the system. That's actually system architecture and system development that needs to be built so simply saying there are API's is one thing but there may not be API's for every piece of data that you're trying to access from the systems and it it needs to be identified that for you know stock on hand for every specific facility. Maybe it might be some configuration data or some master data that you want to access that may not be available so here you're trying to identify that at the granular level, the workflow you're trying to implement the data will be there and that workflow can be supported. Then we're getting feeding back into them the the presentation which which Austin made on Monday, connecting this very specific assessment into ensuring that that can be done. And last but not least system owner I think that's mentioned a few times and that's really important to get to know for DHS to it's getting to know that the HMIS team the ones implementing the system. The ones responsible for the system administration for the users ensuring that everything is functioning. So we're going to have to look at who's responsible for the ELMIS or ERP or any other system when it comes to integration who's actually responsible for that because there will be different hierarchies different management responsibilities and different accountability structures, and resources coming in to support these. The systems and of course different donors so it may slightly increase in complexity so aligning all of this beyond simply the technical is also quite important. And this data source mapping tool will help with identifying at a granular level of the requirements but then also identifying who the responsible persons should be in working on that integration. So we have the Gavi technical country assistance. So the his center at UIO coordinates funding from Gavi to support DHS to development in 54 countries. So we have this role where we're coordinating the support at a global level. However, countries also have access to country level budget so country level financing, which happens or you can access outside of this coordinated UIO work. So this is on a high level engagement so ensuring that the tools that we've presented here during this academy the stock management cold chain equipment management and so on. This is aligned with Gavi requirements at a very high level or they meeting global standards or they meeting, you know, standard set by different partners and UN agencies is a little aligned with initiatives from other partners that were, and we've mentioned this multiple times in terms of mapping and developing tools that are already existing in the market. So that's kind of the global work that we're engaged in and that's a lot of what George and I are doing is ensuring that what we develop at the core level is relevant and realistic and needed. Now at the country level, you can then ask for the support to say we want and need and this is beneficial for our country to implement the aggregate you know monthly stock reporting. The cold chain equipment management. So for that you can apply for funding, which will help to launch a project to do a stakeholder analysis and this entire kind of assessment that I mentioned here, bringing people together around the table and it's very recommended if you can to have these people face to face in the meeting in the same room to talk about what is your system, have them demo the system so you see how it's used. Ask them if they can have you know access to is to a kind of sandbox so that you know what's what's happening that you build this buy in within the different agencies that are implementing these systems that you have an understanding of what's happening in the industry and you have a proper plan to identify a goal. So all of this can can be done and then having even a limited pilot that you test this in a few sites, 510 or 50, or however many sites that would be possible with the funding available. So this would be very possible and is is recommended to do through this Gavi funding. So these different ones that I list here are available through this country level grant. So it would be, you would need to just contact. If you have a Gavi contact for the country then you can go through them. You can also speak to our colleague on the tour saying you have her contact there who coordinates that work, and that these funding mechanisms, and she can put you in contact with the right persons and including the local his groups that can help you to explore and then eventually get to a point where you're launching a small project that would be doing the assessment planning and even a limited pilot for any one of these tools. And then building then buy in and they would also be, I think, useful and helpful in that building buy in from other donors and trying to coordinate these initiatives. So that they're spending for a full level scale up, because then we get to this more broader donor coordination. The Gavi funding will not help us particularly for for for any mid size to larger size country, a full scale implementation there's a lot of users, a lot of requirements, specifically equipment requirement. So they could also help with coordinating and aligning the donors and initiatives that may be happening in a country with showing that we've done an assessment we have a project plan we've done a limited pilot showing that this can work. Now we want support to be able to scale this to, you know, from 5% of facilities to to to 95% of facilities, those with connectivity and power or whatever the objective might be that you have this alignment with other donors and you're bringing resources and competence within this DHS to environment, different donors can also support different foundational pieces within the DHS to system, and that you promote this holistic supply chain management and LMS approach that we've also been promoting, and that very much has been identified as a challenge that many systems are implemented in a siloed way within very specific programs that don't account for parallel systems. So now the donor community is really trying to align behind a one LMS approach, supporting one holistic solution that's that with the discussion and the talks now are within the donor community and Gavi very much is pushing for that approach global fund as well. And then through these mechanisms, you can work on the assessment planning and then eventual implementation of the solutions for your country, reaching this kind of end to end supply chain management with the integration, connecting health facilities in the last digitizing all of these workflows and making this data available for decision making and program management. Alright, so that was a lot of information and a lot of talking from my side. We have, let's see. Yeah, we should go over to to Jaime's presentation now on mobile but I wonder if there's any questions we should take any immediate questions before we continue I haven't been able to add slack but if George or Alice if you if you see that there's any burning questions we can take it up before moving on. If not, we can go over to you Jaime. We, we have one question from Kosei was asking, will there be any dedicated channel for LMS integration on the COP that can always lean to in case we run into issues while implementing some LMS as an integration. Or so within the COP we have, there's both the supply chain LMS page or channel, and then there's an integration and interoperability channel so I think it would be between those two so I think if you have challenges with, for example, workflows, how you're structuring metadata how you're aligning data between one system and another. There might be more George myself and supply chain people looking at that. If you maybe have a more it technical integration technical challenge, it might be better to take that up in the interoperability or integration so if a system has limited APIs, or I remember Austin presented also the difference between pulling for data or notifying notifying data with webhooks so how is the data being synchronized between the systems in a sense, are you asking for data or are you pushing data when you have it. So that more it technical can be taken an interoperability or integration, but those two channels I think serve already the purpose that that you will need so if it's more it technical use the integration if it's more supply chain logistics data, so I don't know if you can use the supply chain page, but we're generally following both as soon as LMS is there somebody will ping us and we'll let us know that there's a question related to our work areas. No, please go ahead. Go ahead. So Sean did you might have been answered would you share with us a maturity questionnaire I don't know if there's a link in the presentation. I'm in the Google Drive so if you look at the Google Drive the contents for day five I've uploaded uploaded these files I only showed the header for for these, and the full headers are not there but you can access these let us know if you don't find them. I'm posting the link to the day five folder in the chat. All right, thank you Alice. All right, maybe one, the maturity assessment for your country, we do not have that so you should, this is what I'm saying get to know the HMIS team, the ones managing the HS to, they will have the maturity assessment and we are promoting supporting and the donors as well that they share this broadly so it's not and should not be any secret information but it's the HMIS teams the ones managing the HS to that will have the maturity profile for your country. And for some 3040 plus countries. So, if the country hasn't done it yet you can also let us know reach out to you to myself but also to Anna who I have the contact on the slide. She is working with that as well and she can also help if your country hasn't done that yet and we can give you an update of what the plans are to to conduct that. Any more questions or do we move on to Jaime Bosque and Android. I think we can move to the next presentation. Yeah. Okay, so over to you Jaime. All right. Thank you much Bruno. That was interesting. Let me see if I can share my screen because the last time I tried this I was having submissions. This did. Yes. Is it big enough or Yeah. Okay. I don't, I cannot see zoom. So in case someone is in the waiting room please kindly make them join because I was doing this while I was presenting, but I cannot do anymore. Okay, so good morning after evening. I've seen already I cannot see the chat anymore but I see some faces or names that I know. So most of the things I'm going to be sharing with you today here you already know from previous academies or from other events. This session should last around 45 minutes probably a bit less because I'd like to have a little bit of time at the end of the session for questions. So basically what I would like to explain or I would try to make you understand is that whenever you decide to put Android in your implementation in case you already have an implementation and you decide to start using Android the Android application for your project. It's not as simple as okay I will just buy phones I will put them into place and everything should work. Well hopefully it will work but there are some considerations that you need to plan ahead and you need to understand. So basically these are the three key points that I will try to go over and over again. This presentation should help you identify those main concerns issues implications from different perspectives. How you should plan also in terms of budgeting, etc. And then how you can distribute the application to your devices, again this is going to be very general in case I mean it's a presentation that sometimes we take much longer time to do. But in any case at the end I will say we do some resources for you to dig a bit further or in case you need to reach us you know we are usually in the COP or you can finance the other channels. So before I jump into the growing mobile the implications one or the key concept that I want to transmit and I will reiterate this thing over and over again during the presentation is that as I was saying. You might be used to a typical client server application where you have laptops or workstations that connect to a server. They work because the server is properly configured and you think that doing the same or that doing something similar with a phone should have the same results. This is not the case and the main thing is because when we develop the Android application. It was developed with the key concept in mind that the application would be use offline. This means if you're going back to the same I have a computer now I'm giving a presentation to zoom I'm connecting to the server and I'm transmitting. Indeed test you or my yes if you're using the workstation laptop etc should be the same but with the mobile phone. The thing is that because it was conceived with this offline capabilities. You can put it on the phone and we let you or you are able to work without connectivity to the server. And this is the key concept that has huge implications and the whole presentation is based on that concept that information is not on the phone and you can operate without connectivity to fall. At the initial moment you need to reach and download information for the server. And at one point when you want to make this information reaching the server you need to have connectivity, but the fact that I can work offline has all these implications that I will be talking about now. So, the first thing is what I've been saying going mobile means going offline. You could also use the phone, open your browser and connect the server and operate and work is not going to work maybe well for sure it's not going to work as good as with the application because the application has been specifically developed for this. But in case at one point you will open the browser for this you will need connectivity, not with the application. So all the content is going to be prefetched on the device so initial thing you log in with your credentials and Android will put all the information that might need and this is the key concept might need and not will need in order to work offline. This means that if you are not setting up properly your DHS to and you have been using one user that connects to server at works, but this user has been not properly assigned the organization units or the programs because they were assigned many more programs, Android application will not know if this user is only going to be using this program or this browser. Okay, I'm going to load everything. So the key concept is that there can be heavy things overloaded if you overload if you have not seen a set up properly, etc. So the key concept here and I'm putting here is to balance between the metadata access and download what you know that the users will be using on the server. So if for example, talking about logistics, you know that this specific worker is only going to be working on datasets, probably you need to set your DHS to configuration for not giving permissions to this user to use trucker or event problems. Because if not, this will be downloaded by Android. This is basically it so there are many things where we're listening here to key ones. And as I was saying the organization's units capture and search, if there is one worker who's going to be working in this specific facility, there's no need to give other facilities access because what would happen is that Android will download all the list of facilities that have been assigned to this user. So probably you want to limit the scope. The same for programs and datasets if this worker is only going to be putting monthly reports, for example, you don't want to assign weekly reports or you don't want to assign the traffic programs, etc. And another thing that might apply in some specific scenarios where you have out generated ideas. There is something this very technical so I'm not going to list it here. But yes for you to know that the application what it does is asking the server a I'm going offline because I'm Android. So give me X amount of generated ideas and these generated ideas are calculated on the server are downloaded by Android. So in case you're using a specific patterns that using are using dates or sequential. There might have some implications and you might find that afterwards things are not working as expected. I'm not going to list it here in this document. I'm not going to talk about it because it's quite technical but just for you to know that it will have implications in case you are using out generated ideas. Yeah. So that was for metadata so we have set up the server. Some of you I saw here were in the Android Academy so you know what I'm talking about. Some of you might not be there but just for you to know maybe you have set up the test system. The metadata we're talking about data that will allow these users to work. And then the other things we have is data. So, we want to be able to work offline because we want to create data or we want to analyze data. And for this you will need to set up your sync process, meaning that you need to, or you can define how much data you want these users to load. Not to allow because there's no limit on this but it's more. Do I want my users to have one year of historical data on their phones. Do I need them to have only one month because I don't care about the past they're not doing analysis they're just inputting. Are they going to be in very remote areas where they will need not be connectivity so I want the data to be as little as possible. So these are things that you can define. And I'll show you quickly how you can do it later. But for you, I've been listening here that you could define the number of TIs or the events or data sets or data sets you would like to load. And you have been working or you have been demonstrated during this week about the LMS basic configuration on the server that was shared. So there we have the tracker and event programs. And here we have the data sets. So what I was saying before, imagine that you have a user who's only going to be using putting some biomedical equipment at the life cycle management. So probably you want to set up your DHS to for they for them not to see these programs because they will not use them are also to not use these data sets. On top of this you could see that maybe this person here is going to be using the system he's going to be going offline for a year because he's going to be traveling to very remote areas and you don't need to receive the information on the server for a year. So that's making a dumb use case here, but right then you want this person to be assigned only this program and you need them to have a specific amount of other ideas in case this person is going to enter 100 devices per month. Okay, so these are things you need to tweak in the system for the application to work according to your needs. And we can never give you a specific numbers in terms of how you should do because this is a process of thinking how the system will be used, maybe the same system can be used in different ways by different users. So my point here is that I try to give you ideas for you to process and try to come out with a solution that adapts to your needs. And again, maybe this user will be using in this specific way and this one in the other one. So there's something that you need to try to come out with a perfect or the best configuration you can find. This I was mentioning that this person might go on the field for a year is not going to be the use case by this person will be going maybe max of line one week, two weeks. But another thing that you need to set up is or define a strategy for the, the data syncing process. This means that the users will be collecting information on the field on their Android devices and at one point this information needs to leave the device to reach the system. So this is a process that can be defined in terms of periodicity. So you could say okay I want this to be downloaded or be pushed to the server every day. Most likely for we have been advised that for an LMIS implementation with one day should be enough. This is where you want this to be manual or you need this to be specific. So these are things that you can tweak and you can define. And this is something that you can define. All these have been talking about is something that you can define at server level using the other settings as well. This is an application that you can install on your LMIS, the HIS2 server. And you can define all these parameters in terms of how much data I want my users to download, how much metadata, or how, which specific metadata I need them to load and the syncing process up and down for them to be. Okay. I'll give you afterwards in the resources list how to investigate much more about this application. Okay, because we have a whole session for this in a specific academies. Because of what I was saying that the information is not loaded on the phone. If I would be working at workstation and I unplug my server the information is on my server. Well, maybe I have been so I suffer an attack or something but the information is on my server I have much more control over the server that I would have on a devices because on the devices and as I was saying the information is downloaded from the server to the device. This means that if I'm collecting specific information, I don't think it might be the usual case for logistics, but I don't know, maybe Bruno and George afterwards can come up with a scenario where this could happen. So far I cannot foresee anything, but just for you to know that the information is on the device so even if the server is unplugged even if you decide to put security measures on the server because the information is on the phone or the devices you need to think and define security strategies for this. I will not go into this. But it has, yeah, what I'm putting here, it has a huge implication and probably in case at one point you're dealing with sensitive data privacy or personal information. It can be applied by the law of your country to perform a specific task or run a specific checks, etc. on this. So, again, going mobile, it has a huge impact in several things, and one of the big ones is security. I know that we don't take this no seriously and actually we have put into place some risk mitigation measures that I'm listing here. Some of you might already know this one and you might be very very annoyed because we're not allowing to take screenshots from the phones. This is something that we implemented following a specific security guidelines. It's something that you can enable or disable since the last version at server level, but just for you to know that we are doing our work in terms of security. But it's not that because we have done our job, you're free to go. You also should be doing some stuff. And I'm listing here some of the things that you could do. You should make sure that you do this. I will say, for example, make sure that this user who's going to be working in this specific facility only is able to see this and that on the devices you could do this kind of things. For example, asking users to put a pink code on their phones, using the pink code module on the application. For implementation, you could decide to use an MDM, which is a mobile device management, but it's something that will go quickly afterwards through it. Okay, very roughly because we we don't have much time but just for you key ideas that you can look into further afterwards. So that was a bit from the implementation perspective. I want to talk about from the project management. I think Bruno has been covering some of these things. Let me go over some others. But basically, what I was saying the same this and this, but because you are going to make changes maybe on your configuration, and your devices are offline already they have perfect all the information they might need. I realize that your configuration is not ideal in a normal scenario, normal, not mobile scenario, you will make changes on the server and these changes are reflected immediately on the clients. For example, now I'm doing this slide, moving up and down and you're seeing immediately but if I could be working offline, this will not happen. You need to make sure that when you have defined a specific configuration. It's the ideal one, because making changes might mean that these changes will not reach the clients until much further in time.  So is this it here we have in the guidelines that I will show you with you later more information about this, but basically it means that start small, make tests, make sure everything is working properly, then go try to reach a broader use case more people. Let's see if they are comfortable with the application if they understand how it works if they're having issues make the changes you need on the server and eventually go to the pilot phase. Once you're sure that this is working properly a scale up to your whole country or your whole project whatever you're doing. It does not mean that you cannot make changes afterwards but bear in mind having mind that making changes might take very long time to apply because if the users are not connected and are not prefetching this metadata changes they will not be able to to see them. So on top of this maybe on your work plan you could say okay every month I need to make sure my users or when I make a change on the server I need to have a way to communicate to my users so they get this new information. In terms of budgets, Bruno has mentioned something with you, I'm going to list some of the key things that we think that apply when going mobile. They're not the only ones where you can find more and there are some of them that might not apply, but basically probably you will need to add budgets for human resources, because you will need to do more testing, as I was just saying before. The infrastructure probably your server might need to be tweaked to adapt to a mobile implementation, I will go through this very quickly afterwards. You need to plan in terms of device acquisition and accessories before you had a laptop, this laptop probably it's very easy to use by different users. In Android this is a bit different because you at the moment we have a limitation of three accounts per device. Is this enough for you if you have five people working on the same device, maybe you need to buy two devices or maybe you need to set different accounts on Android. The device that we do from the implementation team provided is something that we want them to use, we allow them to use their own devices, this means bring your own device. If yes, can we ensure because of the security things that I will mention before, can I ensure that these people using their devices are going to comply with my security policies? So these are things that you need to think from the very first moment, because they will probably have a big impact on your budget. If at one point you think that you're going to have 100 people working there and you think 100 devices might be enough, you might plan, but maybe you can say, okay, listen, I might ask them to use their own device. I've seen that it works in some ways, so maybe this is something that you don't need to buy it, or maybe yes, or maybe you need to buy it for this plus other things as we will see now with the recording cost, et cetera, et cetera. Another key concept is the connectivity. As I was saying, Android is made to be working offline, but you need to have internet at the beginning for sure to allow this metadata and eventually data and then you will need connectivity to push this information back to the server. This might mean working on Wi-Fi, but might mean working via 4G, 3G, whatever you have available in your country or place where you are. And also the mobile device management that I will talk briefly about afterwards. On top of this is not that you only have budget lines that you define once and then you forget about it, is that you are going to have recurring costs. And I will not go through them, but just for you to know, for example, for connectivity, if you are going to have or deploy a project that is going to last for three years and you are working on mobile data, you need to know that these phones, devices, tablets, whatever, will need internet for two years, so this means having data bundles or having subscriptions, et cetera. So are recurring costs that you need to take into account and do not forget when planning or budgeting your project. That was project management decisions. I'm going to start with the last section of the presentation, which is related to infrastructure decisions. We have divided this section in two. First, we're going to be talking about from the mobile perspective, so devices like telephone, tablets, et cetera. And the last one is going to be about the server. Again, a bit technical, but yes, for you to collect some key concepts that afterwards you can go and discuss with project managers, technical people if you're not. So from the mobile perspective, at one point, what we need is to make sure people have their DHS2 or LMIS application for the phones. I'm having here the tablet. I'll show you eventually. But well, as we need this application to be installed, again, I'm going back to the explanation from the beginning, DHS2 works usually on the web browser. So if you have not been using Android, you know that you can type whatever your country slash DHS2 and it brings you to the website. This, well, it's a web application, let's say, even though you don't have to install anything, but you access via the browser. In the Android application, you need to download this application and there are several ways to download it. I'm covering here this one and this one. So all the channels and the main one that people use, which is Google Play Store. If you have one, if you open your Android devices now and you search for DHS2 capture, you're going to bring to this release page, I don't see a screen where you can install the application. And in order to install this application, you need to have a Google account or devices. So these are things that you need to plan from the beginning. Okay, I'm going to distribute and I'm going to put a specific example. I have an implementation logistics. I have 40 facilities. I have 40 devices. So one device per facility. Do I want to have 40 different Google accounts or do I want to use LMIS, my project at Google.com or, for example, or Gmail or whatever Google account you have. These are things that you need to decide and distributing the application via this. It's quite simple because then you can just open the Play Store, install it and that's it. Even though if you do this, you will have zero control over the updates. This means that when we put a new release out there, it will happen in the next two weeks, probably. If your devices have not been set up to disable the automatic updates, you will receive new updates. And this might be, I mean, it's good from the security perspective because it makes it means that we have updated and we have include some security patches in case there were some security issues, but also we have to include new functionalities. And this means that if your users have not been trained on the new functionalities, they might find a new application and they might get lost. So in case you are using Google Play Store to distribute the Android application, make sure that you disable the automatic updates, or if you don't, because maybe you say, okay, we want to be always to the latest test. Make sure you understand there are consequences and you should probably test or have a team of testers. And excuse me, that can quickly produce documentation according to their piece or they can follow our development. They can even be in the beta release. And they can be ready for when this happens to talk to their users and make sure they know how, how the new changes affect their mobile phone, for example. There are other challenges to distribute that I will not cover because they are a bit more difficult to manage. But just for you to know that if you are not happy with the Google Play Store distribution, you could put your own market, for example, you could install or deploy an MDM and you could distribute the specific version that you want whenever you. Okay, it's here. And again, I have more information about them in the last slide. I mentioned several times in the presentation, mobile device management so MDM. Sometimes I will mix these terms. It's exactly the same MDM. And basically, just for you to know that an MDM is a specific security software that you install somewhere, and then you can apply policies to your mobile devices. Okay, basically that's the name. So, in case you are deploying or you have a huge period with a lot of devices and you think that going manually to perform certain tasks on these devices is something that you cannot afford because there are too many or because they are very remote. At one point you could consider having an MDM and means that in the central console you will define policies and these policies are installing the devices. Before I was mentioning bring your own devices so it's another thing that you need to think about. If I'm having an MDM to manage my devices, can I impose people who are using the devices to use my MDM policies, maybe yes, maybe not something that you need to think about it. Sorry. So, example for example for the MDM trying to be more specific. Imagine that you're dealing with sensitive information. Again, I don't know if this can happen maybe yes instead of a stock management or vaccines somewhere where you think they might get stolen. But you need to make sure that this information remains secure on the phone. You might impose security policy on your phone saying, okay, I can remotely wipe the phone, the phone. So, if at one point the user notifies me a my phone has got stolen. You could remotely wipe it. You could also impose a policy that okay all my phones that are going to be using this application they need to have a very strong passport in order to open the unlock the screen. For example, just key things that you could implement with the MDM. We have a full guideline of how to use MDM so in case you want it's going to be also on the last slide. And then these are some examples of things that you could do. Another thing that might be interesting for you is that restricting access so imagine you are in an implementation where mobile data is very expensive. I don't know you're in a country where mobile data is very expensive. And you know that some users are using the device that you have provided to work on the logistics application they are using to serve the web, Facebook, etc. So with an MDM you could block these accesses so people will use the phones or the devices specifically only for what they are meant to be used. For example, okay, things that you can do with an MDM. And here there's a full guideline that you can see afterwards. So if you can help you with this. I'm close to the end. So this is the last slides, a set of section of the slides. And it's going to be about infrastructure related decisions in terms of the server. So I've been talking about things that you need to think about while deploying from the mobile tablets perspective. Now let's go back to the server. At the beginning of the presentation I talked about configuration of the VHS to I'm not going now into that I'm going now really to the to the hardware of the server so the specifications the technical specification of the server not the configuration we can forget about the logistic application I'm talking really really about the server. I'm going to make here a very quick comparison trying to you to to see why this happened this could have an impact. So imagine that we have an office where we have 30 users, sorry, 10 users, and then users are bringing one little predict. So we have one person working on the post office. And every day that person has to receive 10 letters because there are 10 users and one other day. So probably it's something that he or she can handle 10 letters per day I could handle that. Now imagine that these users decide not to come every day because they are going in very remote areas but they write a little per day. So at the end of the month, then users they're going to bring 30 letters. So we have had a person working on the post office for 29 days doing nothing. Let's see. I'm not going to go into this. I mean probably he or she's doing a lot of things but not doing anything with letters. And now they are receiving 30 letters. So 300 letters. So this person 10 users 30 years on the last day of the month. They will have a lot of work. So this is something which is similar what could happen with Android when you're using with your workstation with your laptop. You enter a new stock management numbers you say okay I have this and this and this you say to the server immediately.  So I'm registering here everything. And then when I'm synchronizing, I'm going to send all this information so the server is going to receive a huge amount of data in a very short period of time. If it's only me it's fine but if we have 1000 devices doing the same it might have a huge implication of the server because it will receive a huge peak of load and it need to be able to handle that. I was saying before that you can define via the Android settings without how often you want this to happen. Probably, as I was so discussing with Bruno. Once per day should work but maybe some users will not be able to reach Internet. Daily, or if they do maybe we need to make sure they synchronize at different times because of this. Okay, so it's not that. The size of the request are going to be bigger. Yes, because I'm not going to be sending one change in the stock management, I'm going to send everything that I have recorded at the same time so a huge load compared to what is happening in the workstation that is a little one. And also if I have several users doing this at the same time. It's big and it's going to multiply for every user doing this at the same. Okay. So maybe you think that your server has been working very well with make numbers hundred users using their laptops, and you say okay, now these people are going to be using phones so I didn't I don't need to do anything on the server. Well, probably yes, because of what have explained. This is the last light of the presentation. So I hope it has been clear and I've been talking a bit, I've been talking a bit fast. At least I thought I think I, I managed to transfer the key concepts, if not a very quick quick up going mobile. It's going to have a very big impact on your logistics DHS to LMIS implementation. And we have put this into four groups, maybe they can, they can be split more but the big one. Here is a configuration, as I was saying you need to trigger configuration to define specifically and you can probably not use the same configuration that you are using when you're using laptops or desktops. From your project management is going to have a huge impact because it's going to impact how you travel shooting how you train your users and how you budget your, your project. In terms of security, we saw it has a huge impact because the data is not longer on one specific place but in many, many more one per device. And in the infrastructure because we have many more devices to handle, we need to distribute an application on those devices. And my server might suffer from all these heavy loads that might reach eventually when users perform this integration. That's pretty much it. This I have put here and I think this, this slides you already have access because they have been shared in the drive. And I have here some of the key official guidance that we have written. You can also find us in the COP. I know some of you already from the COP or from previous things. So you really know that we are quite active there. So in case you have questions you can always come back to us. I haven't listed here GDAR or anything but eventually if you have a problem I will refer to it from the COP. Eat from my presentation. I don't know if you have questions. I'm going to stop sharing my space so I can see your questions in the chat or in Slack. Yes. Yeah, actually, there's quite a few questions, a lot of activity, I think a lot of interest on your presentation so big thank you for your for all the inputs. Yeah, the recording will be available on YouTube as well so I know you gave a lot of information in a short time but they can refer back to it but I want to pick out two key questions that I think it's good if you answer in plenary. The first question is from Colse Bilali. He's in South Sudan he writes the download is really a headache, especially with the tracker and sometimes it overloads device capacity. We faced an issue where we have thousands of data that needed to be downloaded this is because before a data entry data entry officer needs to first search the TI to see if the data is already entered, and this was for COVID-19 and this may be very specific but if you can give a general feedback on that and the second question is from Nora, who says there is never enough time to do proper testing. So if you can comment on that as well from your experience. Yeah, one second. So for the first one, in terms of having to search etc. Let me go back to this. Okay, so what's the name Bilal, I don't know what's your name. Sorry, the guy from Sudan. Well I didn't see it doesn't matter. So you were saying that Android requires you to search before entering. This is true. The reason it was made. This decision was taken. It's because in retrogo it obligates and this is kind of a headache the way it's implemented now. So I'm going to try to be more specific. I have two devices. These devices has entered my data, COVID data, and has not synchronized. So when this other device comes to me and reads the same data, same user and we are using the unique unique identifier which is the my national ID. So this one is going to synchronize to the server the first one. So when this one tries to synchronize going to say hey, you are trying to put a person in the system that is already there. So in this specific case, there's nothing you can do because this one did not synchronize. The first one that synchronize is the one that had the authority to write into the system. In a good or in the best setup that we could thought is like, okay, I'm talking about COVID in this specific case, we know that patients might come daily, for example, to different facilities. I'm going to set up my synchronization process as I'm showing here daily. This means that this patient, sorry, this health worker registers me, goes back to the system, and now I'm going to a new facility. I'm going as Jaime to the facility and say this is my national ID number. I have to search before. So these phone will search in the system and will say, Ah, okay, no I'm not going to let you put Jaime in the system because already there. So if you need to update your server of Jaime, in case you need to update information, update this, but you cannot create a new Jaime because Jaime is already there. This is in case you're using unique identity fires because if you are using patients with not uniqueness limitations, this could not happen. But this is why Android was developed and forces you to perform this search before entering date. This is cumbersome. Actually, at the beginning was all like this, and then people requested the field and we're having too many duplicates you need to put this back. So it's a very difficult thing to handle because, again, we are developing an application that can be used in huge number of scenarios so it's very, very difficult to try to adequate. This is a phone that having this search before it works. If you would not want this to happen, what you can do is be offline if you have your airplane mode activity on your phone because the phone cannot record you could release the person in the system but when you synchronize you will suffer this. And you were also mentioning that downloading data might be too much, of course, and that's the reason we are recommending everyone to use the Android settings web app, because with the Android settings web app, and it's here. Yeah, well here. What you do is you could define and you could say, okay, I'm going to be in a scenario where these two health workers are going to go to very remote areas and they don't have very good internet connectivity, and they're only going to be entering patient data. They don't need to go through all data because we're just vaccinating with one short vaccine, making a scenario here health that I know a bit more. So you have your server to say, okay, this phone and this phone, or in general this user, the vaccinator user will not download any data. So you could go here and going out to the presentation and you could say, okay, I think this is not problem. This is a number of guys download you could say, okay, download zero. So this means that I will only make a very quick synchronization at the beginning, I will download all the metadata but I will not take time to download more data because there's nothing that I want to load because I have told my server not to download any piece of data. I don't know if I answered your question, I hope yes, otherwise I can come back to it in this lab because I think we're right out of time. Or if I have time, if they let me continue, I will continue. The second question was for Nora saying, proper session, there's never time, of course, I know actually we're going to release the new, the new version in two weeks and we're already testing. Already or still testing, better said. The thing is that, and I know you know this, but I need to tell you is that sometimes if you do not allocate time interesting. It will have a worse impact later on, because if you have not tested properly. There will be some problems and then you will need to make changes on your DHS to configuration, and then you will need to ask these people to come back to synchronize or you will need to suffer and perform changes on the database, because what these users have input already the system is not correct. So I'm not telling you something that is not new to any of you. I'm just trying to tell you that if you do not test, you might regret it. So here, from the previous management, we're telling you, make sure that from the previous management project management perspective you allocate resources like human resources, monetary resources and time resources for this testing to happen. Again, if you don't do it. I just want to tell you, when you come for support, it is happening another time you should have done testing. Well, I might say it, but I saw that I will not help you but if you perform, or if you try to foresee what you might need. So if you do a proper testing and you follow these things that we recommend to use. Normally, you will be much more likely to succeed in your implementation. I don't know, Nora, if I answer your question, maybe you didn't want to hear me say that, but is the way is it. Yes, testing and the time and the resources to testing is always a challenge and you are always chasing yourself. No, I know. I mean, in the end, this is just a personal experience here. I'm part of the security team in DHS too. I used to work in a company. We had always the same. It was like, I'm always going there and say, hey, I need money for security. And they tell me my bosses would always tell me, nah, it's okay, everything is working fine. Yes, but the problem is that whenever a promo rice, rice is like, ah, shit, I should have invested.  Damn. I should have invested more in this because now I have to spend more money or now I my data has been stolen. So I know it's difficult with this information I'm giving you here. Maybe maybe you will be more likely to convince your boss and okay, listen, they've told me that if we don't do this in the future, we will need to spend more money. And if they're only promise money, maybe you convince them. If, for example, with COVID. So two years ago, we understood that people did not have enough time for testing. So, in the end, it's a balance that you have to play with. I say, I don't have time. I have money. I don't have time. Let's go. I have money. I have time. Okay, I do testing. I'm not getting anything. Okay, I go and then I will regret it. But that's a bit, I know it's impossible to have a good answer, but that's what I try to advocate sometimes. All right, I know we're a bit over time on the break, but I think there's one more question. Hi, me if I can ask you to answer and it's from Mohammed almighty writes in the zoom chat. How can I find the data in the mobile device. I mean the storage data file for Android using DHS to app and Mohammed you can also speak up if you want to clarify any of that. Yeah, Mohammed, I don't know if I mean, I'm going to show you something quickly.  I'm going to do it like old school like showing the screen like this, instead of putting through the computer just to show you one thing. Okay, so this is my. That's my other phone is starting up. Okay. This is the information I have on my phone. And if I go here. Let's see about settings. So, I don't know if you can see otherwise I'm going to share my screen. So here I have gone to settings and here there is one thing that I can say delete data. So if I could click delete local data. The phone is going to tell me are you sure you want to delete local data. This is the information that is on the phone you cannot. And that's one of the security measures we have implemented. You cannot connect a cable. So imagine I've lost my device my tablet that contains sensitive information. If you take a cable you cannot pull the information from the device because we rely on Android as safe or secure operating system. So if I steal this tablet from you, I will not be able to pull the data from there. It doesn't mean I cannot delete it. I show you how to do it but this is from inside the application but I could also go like this. I'm going to show you. So I'm going to click here this that is training application if I click it here for a little bit is going to pop up something. I can go to application information. And there is something called storage. I think it's up there. You could see that says clear storage clear data. If I clear data. That is what I'm going to do. I know clear storage clear cache. So clear stories as me. Are you sure you want to delete this if I click okay. I think I did it. Now I've completely delete all the information. So now when I go back to the test you will see that actually it brings me to the login screen because all the information has deleted. Your question was where can I find the data of this data is stored safely or securely better said, or in your device via the Android story mechanism that ensures that this information cannot be taken away via means like this or this, but you can still delete it and you can use the Android operating system up management settings to delete it. I don't know if that answered your question Mohammed. Maybe you want to clarify if I did not. We stopped sharing so I can send it. That was good Jaime thank you and I wonder if maybe close it below like you can ask the last question before we go to break. So, so I wanted to just follow up on the issue of the downloading a lot of that is like for instance when you're having the two vaccinations or like three phase vaccinations. So in that scenario we needed to download all the data from the first vaccination to know that the person has already been around to the first. So I'm just curious whether there's some optimisation that can be done in that process to reduce the device capacity from being overloaded. Thank you. Okay, so for me, I mean not knowing how you don't need to done right. So soon. Okay, sorry. I don't know how how connectivity is in South Sudan. I was not far from there a while ago and there was connectivity, quite decent connectivity. Well, pretty much everywhere. But maybe your facilities hospitals or health facilities you have good Wi-Fi connection, let's say and then you have internet via whatever. You have connectivity. So my recommendation in this setup, in order to be able to work as quickly as possible. I mean, I have not studied the case, but what I would probably do is I would go to my settings of the server. And I would make sure people are downloading zero TIs. Because if I put my phone, my device setting up in the server to download zero TIs, because of the imposition of Android to search before my initial configuration will be very fast because there's nothing I need to download. Just metadata and this metadata only is downloaded when it changes. So first time, let's say it takes two minutes. Then next time. Every time I open the phone is going to search for metadata. No changes. So zero things to the load because I have set to zero TIs to download. Nothing is allowed. So I can immediately start working. So now the patient arrives. Me, Jaime, I want to take a vaccine. I arrived there. And I'm writing poses searching before. So they're going to search Jaime Bosque national ID. This one. Then this triggers a search to the server. The server finds and it doesn't mean okay have found Jaime Bosque do you want to load you click on download and you're only going to be downloading me as the TI. You work on me. You put my new shot today for the October I got Pfizer vaccination. And then you click on synchronize or you have automatic synchronization so it goes up to the server. And this is in case you have internet. If you don't have internet this that I just told you will not work because you are reliant on being able to serve for the system. If you don't have internet. Unfortunately, you need to download the patients beforehand. So the first synchronization is going to take a lot because it's okay. I have to deal with patients that have only been in this organization unit they always come to the same facility. Well, then I could trick my system for my users to only download data from this health facility. I could treat that. So then I will already have used data. The promise if that patients are coming to this health facility to take the first shot, but then they are going to this one, I need to make sure that my phones are set up to the load these patients and these patients. And this again it's data that in the end you need to download. There's nothing we can do because data needs to be downloaded on the on the device to work. So again, it's very difficult for me to to provide a specific answer for me what I would try to do is this analysis I have very quickly done and see how could I treat. Do I have internet. Yes, then I reduce my data load at the beginning. I don't have internet then I'm going to try to limit as much as possible the scope in terms of organization units. I don't know if I helped you there. Alright, great. Thank you. Hi, man. Thank you to the participants. This was really a lot of good input and a lot of good feedback. We've been, as I mentioned throughout the whole week, lots of engagement on the topic. So this is just continued. I know we've gone way over time. But I think it's useful to make use of him is expertise. So I didn't want to cut off early and not have access to all this great feedback. I just wanted to comment from George and one of the channels that this data overload and ti overload is not necessarily applicable to the logistics use case, you're not registering new patients. Because the product list is more or less set so this is something that I think is less. The logistics cases of course are for COVID vaccine delivery and surveillance so for the logistics the specific issue may not necessarily be a problem but I think the overall considerations and especially the testing because there can of course be other things that don't come up in the in a health case that will come up in a logistics case so I think the testing and learning is really important there. I have a few more questions Jaime if you have the time and patience to answer in slack I didn't want to take everything up here we could be here for the entire day because there's so many questions and so much engagement but we can try to answer a few of those on slack. Now what I had mentioned is that I would try to summarize that and maybe share all of this feedback and these questions in a consolidated way after the Academy as well. But what we'll do now is we'll go to break. We'll come back at in 15 minutes, or we can say 17 minutes we can come back at 12, also time, and then we can continue with the Mentimeter recap and just closing words and closing statements for the Academy alright. So we'll meet back here in exactly 17 minutes now 16 minutes at 12. Alright, big thank you again to Jaime and see you guys in a few minutes my pleasure. Thank you everyone. Thank you everyone for listening. Cheers.


This study investigated the effect of a chromium layer on the heat transfer in a steel tube during a series of heat impulses. It found that the thicker the chromium layer, the lower the maximum temperature reached by the tube wall. Additionally, it was observed that the temperature of the wall decreased significantly after the first heat impulse, but increased again after the second one. Finally, the study concluded that the temperature of the wall did not exceed 750 degrees Celsius after 7 heat impulses, indicating that the chrome coating would crack if subjected to more heat impulses. This article was authored by Mateusz Silinski, Piotr Koniorksyk, and Zbigniew Serma.